On Thu, Mar 7, 2013 at 12:42 PM, Mohamed Abbas <[email protected]>wrote:
> I'm wondering what is the canonical way of associating "specific" versions > of a module to a node? Is there a way of doing this in puppet? Let me > explain a "Use Case" of what I'm trying to accomplish: > > Say we have created a puppet model called apache to manage and configure > apache webserver. > We have the apache module under version control and there are several > versions. > We use puppet to apply apache-1.0.3 across an entire "environment" > We want to be able to do a rolling upgrade across that entire environment, > where some nodes in the environment have apache-1.0.3 and other have > apache-1.1.2. > > From what I understand of puppet, there is no way of associating a > specific version of a module to a specific node. The only way of doing that > would be to "embed" a version tag in the module/class name. However that is > ugly and does not work well with version control systems. > > Any suggestions of to accomplish this using puppet? > Github's boxen project powered by librarian-puppet, or r10k: https://github.com/adrienthebo/r10k are good examples using Puppetfile for module version control. Nan -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
