[chef] Re: Re: Re: Re: Re: Re: Re: Re: Best practices for keeping repo and server sync'd

[Mike Tewner < >]

That sounds like a plan -

Is there any effort in the Chef community to put together some sort of redundancy/replication? Are large installations (recent press releases of Chef 11 on >11,000 servers come to mind) running on non-redundant platforms? Is redundancy of our Chef something which I'll need to implement on the Infrastructure layer only (VM snapshots, etc)?

On Thu, Mar 28, 2013 at 5:29 PM, Daniel DeLeo < " target="_blank"> > wrote:

On Thursday, March 28, 2013 at 2:46 AM, " target="_blank"> wrote:

That all sounds good - I'll have jenkins push the cookbooks, data bags, roles,

etc. from GIT - BUT - What about DELETING or renaming objects? If I delete a

data bag item, what's a recommended method of propagating the change to an

"upstream" Chef server?

-Mike

One way to do this would be to have a "tombstone" directory, and have Ci delete everything in there.

-- 

Daniel DeLeo

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Please note that any disclosure, copying or distribution of the content of this information is strictly forbidden. If you have received this email message in error, please destroy it immediately and notify its sender.