- From: Juanje Ojeda Croissier <
- Subject: [chef] Re: Re: Re: Re: Where to keep your <node>.json files?
- Date: Mon, 23 Apr 2012 17:31:58 +0100
I think Spiceweasel could be a good idea to track all those changes:
Still it doesn't sync with your real infrastructure, but it is easy to
keep updated and is a good picture of your infrastructure-as-code.
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?
> Am 23.04.2012 10:59 schrieb "AJ Christensen"
>> I don't keep these. We only store them for backups when deleting
>> nodes, in the event that some data required for recovery is persisted
>> to node data.
>> I wouldn't recommend the overhead of ensuring nodes are synchronized
>> from server to disk and back, but perhaps a tool could be built for it
>> Embrace chaos, destroy nodes regularly -- build for failure.
>> 2012/4/23 Motiejus Jakštys
>> > On Mon, Apr 23, 2012 at 07:36, Torben Knerr
>> > <
>> > wrote:
>> >> Ohai Chefs,
>> >> But where do you keep these files? I was considering to put them under
>> >> chef-repo/nodes as the chef-repo git repo seems to be the right place
>> >> for
>> >> me. But since there is no such directory in the default chef-repo
>> >> structure
>> >> I was wondering if you guys know a better place for it?
>> > Well, I am using this directory for this purpose.
>> > --
>> > Motiejus Jakštys
Archive powered by MHonArc 2.6.16.