Am Tuesday 02 February 2010 schrieb mir Michael DeHaan: > Oliver Schad wrote: > > Is there a tool outside where I can use puppet descriptions to > > program such jobs? Or is there a tool outside you know, that allows > > me to program network wide jobs without puppet where I could built in > > the usage of my LDAP tree? > > > There have been various things like this, though I think what I really > would like to do is understand what the types of use cases are for > these various things, so we can figure out how to teach puppet to do > them best in a way that fits in well with puppet.
I had a look at mcollective and maybe this could be a way for me. Thanks for your pointer. > used to just run shell commands and replace SSH loops). MCollective > is doing similar things as Func, though with a message bus. (Aside: > having Puppet optionally grok message buses is something we should > probably look into). I think that messaging between systems is strongly needed for system automatisation. > There seems to be two different classes of things we'd like to do: > > (A) Have the orders for a recipe wait until a condition on another > host meets some certain state... for example, installation of a service > requires that first a database setup is fulfilled on another host. > > (B) Be able to run tasks that are not neccessarily declarative, such > as "power off these machines now / network go into emergency off mode > now / etc". These kinds of things aren't exactly what you would store > in the recipe, but puppetd is well suited to enable these sort of > tasks. > > Do you have other specific examples? I see a network as one system with certain dynamics. On dynamic actions you need dynamic reactions, some of them you know now, some not. Assume you have a farm with webservers and no central storage. Now you declare that you need those vhosts but you can't declare on which host you need those virtual machine because it's purly dynamic. The decision is based on the load of the machines. If a machine has a too high load you have to move one or more vhosts to a free host but maybe this decision is in one hour not valid any more. Moving a vhost means to copy data and change a configuration on the load balancer and the specific host (maybe every webserver has a configuration for all vhosts and only the load balancer has to be reconfigured). That is only one example. If I want to reinstall a system I want maybe to use a PXE server. If I want to make it secure, I have to reconfigure the switch so my host is alone with the PXE server in one subnet. Then install it and change the switch configuration again to the old state. regards Oli
signature.asc
Description: This is a digitally signed message part.
