Hi. Thanks for the detailed explanation.
> MCollective enables you to write agents on all your nodes and talk to > them in an RPC fashion. It has more dependencies than some of the other > tools but provides tight integration with puppet and other such tools > meaning instead of host lists etc you can pick and choose > which machines to target your actions based on facts, classes, > hostnames and regexes of all of those. It sounds as very close to what I need, i.e. performing different actions according to types of machines, rather then running over a list of hosts. Does it contain any deployment-oriented tools? > I'd say if you were looking for something to run just random cli commands > with on all your machines then its the wrong choice but if you had to write > code that interacts with your infrastructure and orchastrate cross machine > states then its the right tool. You probably mean that just for firing commands over group of machines, it's better to be done in "SSH loop" tools, like Func/Fabric/ etc, as it doesn't require client installation? Does MCollective allow any raw CLI, or all needs to be done via Ruby? > It's more programming heavy than some of the other tools though the RPC > framework > is a bit like Rails in that it makes a lot of assumptions about how you build > agents > and if you work within those assumption boundaries you can pull off some nice > stuff > quite quickly. Any plans to support other languages? > It comes with agents package, service, puppet, iptables, exim and a few > others. > Provides centralized auditing of all actions and in the next release very fine > grained authorization of all actions. The auditing, authorization, security > encryption and even what serialization you use is all pluggable and > replacable. These packages mostly for audition? Or I can control them (though it probably should be left for Puppet)? > > It really shines on larger infrastructures where you would want high > concurrency. > And the payoff in its extra dependencies becomes really apparent in those > larger > platforms though. What overheads MCollective + deps add? > I don't really want to do a point for point comparison between tools but any > tool in this > space that is based on threads of parallel ssh will run into resourcing > issues fairly soon. > Similarly tools that are based on static hosts lists rather than the reality > of what > is there now will also have issues. MCollective doesn't use any of these > modes of operation. I think CTier works according to similar notation, where you need to define classes of machines, though it doesn't seem to integrate as well with Puppet. Regards. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
