Hi at all, what do you do if you have fixed a bug or have developed a new feature for puppet and want to use that customized puppet? Here''s an example: We have a few HP-UX Servers and the mount provider dont work here. I used the fix (http://projects.puppetlabs.com/issues/4279) to patch puppet and I''m shipping this new puppet as a package to my clients. This was ok since I found the bug while testing puppet and havent had installed it at all my systems Now there are a few other patches (like http://projects.puppetlabs.com/issues/5012) I want to use. Now there are a few possibilities: * Apply patch on my build servers, repack Puppet and reinstall puppet with the new package. This may be the cleanest solution but it takes time to repack and reinstall (since we use Linux, Solaris and HP-UX an all have their different packaging systems) * Replace the files with puppet: I could ship the modified files with puppet. I dont know how puppet behaves if you change its files at runtime * Provide the files as plugins. Will puppet load my modified providers and mask the original ones? How do you that and what do you think is the best solution? Or do you always wait until every fix is in the upstream version? Kind regards Stefan ---------------------------------------------------------------- Powered by http://www.taunusstein.net IPv6 running -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I recommend running puppet from a git clone using a wrapper script managing the RUBYLIB and PATH environment variables. you''re then free to "git checkout" the branch with the patch you want. It''s also easy to switch branches quickly in this case. In this case you should be aware you may need to clean up puppet in the ruby site_lib directory. You could also deploy your custom patch using pluginsync. Code in modules is not limited to functions, providers and facts. -Jeff On Monday, October 18, 2010, <stefan.schulte@taunusstein.net> wrote:> Hi at all, > > what do you do if you have fixed a bug or have developed a new feature for puppet and want to use that customized puppet? > > Here''s an example: We have a few HP-UX Servers and the mount provider dont work here. I used the fix (http://projects.puppetlabs.com/issues/4279) to patch puppet and I''m shipping this new puppet as a package to my clients. This was ok since I found the bug while testing puppet and havent had installed it at all my systems > > Now there are a few other patches (like http://projects.puppetlabs.com/issues/5012) I want to use. Now there are a few possibilities: > > * Apply patch on my build servers, repack Puppet and reinstall puppet with the new package. This may be the cleanest solution but it takes time to repack and reinstall (since we use Linux, Solaris and HP-UX an all have their different packaging systems) > * Replace the files with puppet: I could ship the modified files with puppet. I dont know how puppet behaves if you change its files at runtime > * Provide the files as plugins. Will puppet load my modified providers and mask the original ones? > > How do you that and what do you think is the best solution? Or do you always wait until every fix is in the upstream version? > > Kind regards > Stefan > > > > ---------------------------------------------------------------- > Powered by http://www.taunusstein.net > IPv6 running > > > -- > You received this message because you are subscribed to the Google Groups "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- Jeff McCune http://www.puppetlabs.com/ -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Oct 18, 2010 at 7:12 AM, <stefan.schulte@taunusstein.net> wrote:> Hi at all, > > what do you do if you have fixed a bug or have developed a new feature for > puppet and want to use that customized puppet? > > Here''s an example: We have a few HP-UX Servers and the mount provider dont > work here. I used the fix (http://projects.puppetlabs.com/issues/4279) to > patch puppet and I''m shipping this new puppet as a package to my clients. > This was ok since I found the bug while testing puppet and havent had > installed it at all my systems > > Now there are a few other patches (like > http://projects.puppetlabs.com/issues/5012) I want to use. Now there are a > few possibilities: > > * Apply patch on my build servers, repack Puppet and reinstall puppet with > the new package. This may be the cleanest solution but it takes time to > repack and reinstall (since we use Linux, Solaris and HP-UX an all have > their different packaging systems) > * Replace the files with puppet: I could ship the modified files with > puppet. I dont know how puppet behaves if you change its files at runtime > * Provide the files as plugins. Will puppet load my modified providers and > mask the original ones? > > How do you that and what do you think is the best solution? Or do you always > wait until every fix is in the upstream version?There are many options, but I''m always most comfortable building my own in-house packages with the patches applied.> > Kind regards > Stefan > > > > ---------------------------------------------------------------- > Powered by http://www.taunusstein.net > IPv6 running > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- nigel -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.