Christian Flamm <christian.le.fl...@gmail.com> writes:
> Hi all,
> I'm trying to find a nice way to model different stages (like: live,
> test, dev) of puppet modules. Initially I thought of different
> branches inside one (Git) repository...
>
> * either being checked out on one puppetmaster into different
> directories being used as different puppet environments
>
> * or being checked out on different puppetmasters
I map git branches ("testing", "production") to puppet environments,
with the "r10k" tool, and use dynamic environments on my puppet master.
Each branch contain a "manifests" directory with "site.pp", and a
Puppetfile. "r10k" creates a "modules" directory, and checks out the
modules using the versions set in the puppetfile.
After that, you need at least the following in your puppet.conf on your
puppet master to set up dynamic environments:
[main]
environment = production
[master]
manifest = /srv/puppet/env/$environment/manifests/site.pp
modulepath = /srv/puppet/env/$environment/modules
> but then colleagues of mine recently attended Citconf in Turin were
> somebody strongly recommended not to use puppet environments and/or
> branches.
Did you get a reason for this recommendation?
--
Stig Sandbeck Mathisen
--
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 puppet-users+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
