hi all, I am working with development environment .( configured puppet + LDAP ) each day build number changes from X to Y .....( there may be changes in templates and deployable files -addition/ deletion. or in configuration parameters ). Once i have configured puppet modules for build number X.....,i m able to configure node according to build no X. Suddendly need to setup puppet moludes for build number Y .......so that nodes can be configured for build number Y. what i need here that i want to setup puppet in such a way that it can support build numbers.... means that it would be able to configure nodes according build number , we want . i had setup puppet modules according to specific build..... 1) Is there any machnism in which we can select puppet modules according to build number..? another way... . 2) Is there any machnism in which we can make puppet modules/ classes argumented , so that it work according to build number ? another way..... 3) Have puppet inbuild support for versioning ? specificaly , i am going through critical time, where i need to configure one node with build number X for one development team ....... and need to configure second node with build number Y for second testing team. (hopefully i m able to explan what i m trying to say.) Thanks & Regards - Sanjiv Singh (iLabs) Impetus Infotech (India). -- 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 Nov 15, 11:11 am, "sanjiv.singh" <sanjiv.si...@impetus.co.in> wrote:> 1) Is there any machnism in which we can select puppet modules > according to build number..?Look at the support for modulepath with multiple environments[1]. You can set the "environment" value to any string. So you can use revision numbers or tags [1002, 1003, X, Y] instead of [production, testing, development] for $environment. This way clients can be tied to a ''tag'' of modules, while defaulting to ''main'' path for unknown or unset "environment"s.> 2) Is there any machnism in which we can make puppet modules/ classes > argumented , so that it work according to build number ?Parameterized classes[2] may work for you, depending on what you need. You could set the $build_version from a customer Facter fact or from External Node Classifier[3] or LDAP Nodes.> 3) Have puppet inbuild support for versioning ?Basically it relies on your puppet master manifest & module content to come from the VCS of your choice. For example /etc/puppet/modules would be an work directory of svn://puppet/branches/production/puppet/modules/. You can also track the catalog "version" based on the output of a script[4]. So you could provide a version based on `svn info /etc/ puppet/`, for example. Be careful that config_version is built on tracking changes to manifest files. It may miss changes in Resources collected from storeconfigs, File resources, template content, etc.> specificaly , i am going through critical time, where i need to > configure one node with build number X for one development > team ....... > and need to configure second node with build number Y for second > testing team.I think this sounds like setting $environment on a per host basis using External Nodes. [1] http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environments [2] http://docs.puppetlabs.com/guides/language_tutorial.html#parameterised-classes [3] http://docs.puppetlabs.com/guides/external_nodes.html [4] http://docs.puppetlabs.com/references/latest/configuration.html#configversion -- 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.
hi donavan , thanks a lot... i am able to use environment option for build support ...... Thanks Sanjiv singh Impetus Infotech (India) On Nov 16, 4:54 am, donavan <dona...@desinc.net> wrote:> On Nov 15, 11:11 am, "sanjiv.singh" <sanjiv.si...@impetus.co.in> > wrote: > > > 1) Is there any machnism in which we can select puppet modules > > according to build number..? > > Look at the support for modulepath with multiple environments[1]. You > can set the "environment" value to any string. So you can use revision > numbers or tags [1002, 1003, X, Y] instead of [production, testing, > development] for $environment. This way clients can be tied to a ''tag'' > of modules, while defaulting to ''main'' path for unknown or unset > "environment"s. > > > 2) Is there any machnism in which we can make puppet modules/ classes > > argumented , so that it work according to build number ? > > Parameterized classes[2] may work for you, depending on what you need. > You could set the $build_version from a customer Facter fact or from > External Node Classifier[3] or LDAP Nodes. > > > 3) Have puppet inbuild support for versioning ? > > Basically it relies on your puppet master manifest & module content to > come from the VCS of your choice. For example /etc/puppet/modules > would be an work directory of svn://puppet/branches/production/puppet/modules/. > You can also track the catalog "version" based on the output of a > script[4]. So you could provide a version based on `svn info /etc/ > puppet/`, for example. Be careful that config_version is built on > tracking changes to manifest files. It may miss changes in Resources > collected from storeconfigs, File resources, template content, etc. > > > specificaly , i am going through critical time, where i need to > > configure one node with build number X for one development > > team ....... > > and need to configure second node with build number Y for second > > testing team. > > I think this sounds like setting $environment on a per host basis > using External Nodes. > > [1]http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environ... > [2]http://docs.puppetlabs.com/guides/language_tutorial.html#parameterise... > [3]http://docs.puppetlabs.com/guides/external_nodes.html > [4]http://docs.puppetlabs.com/references/latest/configuration.html#confi...-- 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.
hi donavan , thanks a lot... i am able to use environment option for build support ...... Thanks Sanjiv singh Impetus Infotech (India) On Nov 16, 4:54 am, donavan <dona...@desinc.net> wrote:> On Nov 15, 11:11 am, "sanjiv.singh" <sanjiv.si...@impetus.co.in> > wrote: > > > 1) Is there any machnism in which we can select puppet modules > > according to build number..? > > Look at the support for modulepath with multiple environments[1]. You > can set the "environment" value to any string. So you can use revision > numbers or tags [1002, 1003, X, Y] instead of [production, testing, > development] for $environment. This way clients can be tied to a ''tag'' > of modules, while defaulting to ''main'' path for unknown or unset > "environment"s. > > > 2) Is there any machnism in which we can make puppet modules/ classes > > argumented , so that it work according to build number ? > > Parameterized classes[2] may work for you, depending on what you need. > You could set the $build_version from a customer Facter fact or from > External Node Classifier[3] or LDAP Nodes. > > > 3) Have puppet inbuild support for versioning ? > > Basically it relies on your puppet master manifest & module content to > come from the VCS of your choice. For example /etc/puppet/modules > would be an work directory of svn://puppet/branches/production/puppet/modules/. > You can also track the catalog "version" based on the output of a > script[4]. So you could provide a version based on `svn info /etc/ > puppet/`, for example. Be careful that config_version is built on > tracking changes to manifest files. It may miss changes in Resources > collected from storeconfigs, File resources, template content, etc. > > > specificaly , i am going through critical time, where i need to > > configure one node with build number X for one development > > team ....... > > and need to configure second node with build number Y for second > > testing team. > > I think this sounds like setting $environment on a per host basis > using External Nodes. > > [1]http://projects.puppetlabs.com/projects/1/wiki/Using_Multiple_Environ... > [2]http://docs.puppetlabs.com/guides/language_tutorial.html#parameterise... > [3]http://docs.puppetlabs.com/guides/external_nodes.html > [4]http://docs.puppetlabs.com/references/latest/configuration.html#confi...-- 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.
Stefan Schlesinger
2010-Dec-30 00:32 UTC
Re: [Puppet Users] Re: puppet +with build support
Hey Sanjiy, On Nov 16, 2010, at 11:41 , sanjiv.singh wrote:> i am able to use environment option for build support ......Don''t know whether this might still be of use to you. I wrote a puppet-sync script, which in this setup could maybe solve your problem. http://sts.ono.at/blog/2010/12/22/synchronize-puppet-with-git/ Regards, Stefan. -- 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.