- From: James Le Cuirot <
>
- To: DV <
>
- Cc: "
" <
>
- Subject: [chef] Re: Re: RE: Running chef in multiple environments
- Date: Wed, 30 Jul 2014 09:15:52 +0100
On Wed, 30 Jul 2014 00:30:39 -0700
DV
<
>
wrote:
>
So, my point is something my colleague brought up recently - why run
>
chef-client as a daemon on production runway at all? Why not run it on
>
demand, such as when changes need to go out to production? From my
>
experience anyway, our production runways never get any updates when
>
they are actually serving production traffic, so it's safe to turn
>
chef-client off to prevent any accidental promotion of cookbooks,
>
environments, or roles to production.
>
>
That way you can keep using just one Chef server and keep using roles.
We haven't got to the point where this has become a problem yet but I
had been thinking the same thing. Not sure whether we'll take that
approach yet.
Archive powered by MHonArc 2.6.16.