On Friday, May 23, 2014 6:16:28 AM UTC-6, Michael DeHaan wrote: > > No config system really handles "this shall not be X". >
sounds like NixOS is doing that. Granted their config management is built into the OS giving it some advantages in tracking state. > FWIW, this nothing to do with "idempotence". It's unfortunately one of > the most misued words, and I blame Puppet/CFengine for making it so popular. > perhaps wrong choice of words - I haven't come across something that would describe what I'm looking for quite precisely. > If you are using cloud hosts, it's easier to destroy the hosts, and that's > the generally accepted way to do it. > sure, clouds with disposable OS'es - kind of tolerable. But even then - you don't want to "re-format" your entire cloud just to move services from A to B? What if that is a chain move with more hosts involved? P.S. not trying to start a flame-war or point a finger of blame - just looking for some solution (or workaround). -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/25d9c7e4-0f4c-40cc-8a59-f9014716d652%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
