[chef] Re: Simultaneous node edits

[Brian Hatfield < >]

We avoid it by abstaining: we don't do individual node edits, ever. The advantage of this is that nearly all of our chef server can be recreated by an upload and client resync, with the exception of the client keys.

On Wed, Jul 1, 2015 at 3:23 PM, Daniil S < " target="_blank"> > wrote:

Hello.

I'd like to know how people avoid collisions, while two simultaneous node edits take place. Some very common (and painful) examples from my practice:

1. Two sysadmins +/- simultaneously issue 'knife node edit' on the same node. First of them who save edits will lost them because of the save of the second admin;

2. Person for sure lost his edits if he try to 'knife node edit' while chef client runs on this node. And you can't predict it even if you are single person who can manage nodes because chef may run as a daemon or via cron.

I would we grateful for any advices or ideas.

--

Thanks in advance, Daniil.