- From: Bryan McLellan <
- Subject: [chef] Re: Re: Re: Re: Where to keep your <node>.json files?
- Date: Mon, 23 Apr 2012 13:49:25 -0400
2012/4/23 Torben Knerr
> @AJ: how do you keep track of modifications to nodes, e.g. who added a new
> role or cookbook? Does Chef Server keep track of that?
> I was thinking that infrastructure-as-code wise one would keep the nodes in
> source control as well, as I would do for databags (and I see good reasons
> for doing that). Is this just a matter of taste or did I miss something?
The best-practice-goal is for nodes to be more of a commodity and not
have anything unique about them beyond their run_list. Data should be
stored elsewhere, which saves you the trouble of 1) backing up nodes
and 2) sifting through nodes for their unique data.
The Chef Server doesn't keep an audit trail, but Opscode expects to
ship some features in Chef 11 that would be useful here.
Archive powered by MHonArc 2.6.16.