3 ms·
There may be a scale of braindeadness, but chef still scores pretty high on it. For example, chef server cannot tell a difference between a new node and an upda
by viraptor 11y ago
There may be a scale of braindeadness, but chef still scores pretty high on it. For example, chef server cannot tell a difference between a new node and an update of node state. (and that's enforced by the API design, not specific implementation) Just think of all the weird things that can happen this way in a very dynamic environment.
(example: if you made some mistake while provisioning new hosts, you'll have one node data overriding another, without any notification)
- vegardx 11y agoHow do you manage that exactly? Using the same client certificates? Client names are unique, so you can't have duplicate entries of the supposed same node.
- viraptor 11y agoWhen cloning machines for example you can race to replace the credentials. Also when deleting nodes, you need to make sure you first delete the client, then node - otherwise the node can get silently recreated and mess up your discovery. Also when... (quite a few possibilities).
- vegardx 11y agoAh, yes. It's somewhat annoying that there isn't a clean way to remove both client and node in one go. But when it comes to cloning the images should be prepped before cloning. Or just don't clone.