On Jul 17, 2013 9:06 PM, "Arnold Krille" <
">
> wrote:
>
> On Wed, 17 Jul 2013 18:04:12 +0200 Torben Knerr <
">
> wrote:
> > Hi Michael,
> >
> > That sounds very cool what you are doing!
> >
> > I think there are two camps in Chef land:
> > - the folks who are using roles
> > - the folks who are using application cookbooks
> >
> > If you are in the roles camp, then your only choice is to use
> > environments for locking cookbook versions, and maybe this is the
> > sole purpose of environments then.
>
> Environments are usefull for a lot of other stuff too:
> For example the question "all non-virtual machine with ntp in my
> environment" (because that is the same subnet by coincidence) is a good
> choice to select peers (for non-virtual machine) or server (for virtual
> machines).
> Another example: "All machines with the recipe munin::client in the
> 'dev'-environment" is also a nice way to configure the munin-server.
Oh, I did not mean to say that environments are used for locking cookbook dependencies only -- that was just a reference to an earlier statement in this thread.
100% agree that environments are totally useful and should be used for other things like search or setting environment specific attributes etc.!
> Doing that with cookbooks or roles would certainly be possible: a role
> "dev-munin-client" that inherits the role "munin-client" and then
> search for all "dev-munin-client" to get the same as with the previous
> example. Buts its not as nice I think.
>
Me too, that would be abusing roles/cookbooks for environments. Definitely Not Like! -1. :-)
> Yes, I think I am part of the roles/environments-camp...
>
> Have fun,
>
> Arnold
Archive powered by MHonArc 2.6.16.