[chef] Re: Re: Re: Re: Re: suggestions for upcoming community summit

[Daniel DeLeo < >]

On Tuesday, November 1, 2011 at 10:56 PM, Bryan Berry wrote:

> what would be the best to protect my current system before testing it?
> 
> off the top of my head
> back up couchdb
> back up gems directory
> backup /{var,usr}/lib/chef
> stop chef services
> put new chef code in place of old, depending on whether using gems or rpm
> restart chef services
> 
> 
> did I miss anything in this list?
Backing up your Solr data is not strictly required (you can run `knife index 
rebuild` to get it back), but may make for a smoother recovery. Similarly, 
your rabbitmq config (generally in var/lib/rabbitmq/mnesia/ or similar) can 
be recreated (and Chef generally won't touch it except in something like the 
bootstrap cookbook) but may be worth backing up as well.

And please do let us know about your experiences testing, both good and 
bad--it will help us decide when to go from beta to RC. For RCs, we've 
instituted a three day freeze policy where we wait for three days without a 
reported regression before shipping the final version.

Thanks in advance!

-- 
Dan DeLeo