similar to: Trying to understand how mcollective differs from saltstack?

Hi, I am using puppet as my configuration solution, it is a very good for system-level configuration management and compliance. But it is not good at batch jobs. For now, I have three options: puppi, MCollective and ControlTier. I don''t know much about them. Can anyone give me some advices that which of them is better at batch jobs. Thanks Yunfeng -- You received this message because

Hi, we see a growing need for a better Configuration management for our servers. Are there any known good resources for a comparison of e.g. Puppet, Chef, Ansible etc? What would you suggest and why? :) Thanks and Regards . G?tz

Hi All, I have a working installation of a Puppet Master (CA) with Puppet agents, this using The Foreman. I really see the usage of Puppet this way but because The Foreman supports pushing your classes/templates to you nodes (agents) and uses the depricated Run/Kick for it I''m looking into Mcollective. Mcollective is supported by The Foreman since 1.2, the version I''m

Hi, I am writing scripts for deployment of our software and I am also using MCollective on linux. I hope to use MCollective in order to reduce the requirement of opening a putty session to each VM and running the puppet agent manually the first time (when its registers/ creates keys etc). The problem I see with this is that I need to log in to each machine and install/configure mcollective

Im new to puppet and installed it in my home lab to mess with, when i installed it i used the hostname rather than FQDN so went back and changed puppet and reran the certificate tool to regenerate the certificates etc, the agent works fine now but i am getting an mccollective error i think, is there anything in the config i need to change for mccollective after altering the name to the FQDN?

I have a test setup like this: host ======= *puppet-idc*: Ubuntu 12.04 running ActiveMQ, Mcollective, puppet agent and server *puppet-node1*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node2*: Ubuntu 12.04 running MCollective and puppet agent *puppet-node3*: CentOS 6.3 running MCollective and puppet agent I installed the *mcollective-plugins-puppetd plugin* on all *3 Ubuntu

I''m getting these errors when running ''puppet agent --test'' after doing a new installation of an agent: err: /Stage[main]/Pe_mcollective::Plugins/File[/opt/puppet/libexec/mcollective/mcollective/security/sshkey.rb]/content: change from {md5}512f42272699eaa085c83d2cc67c27ea to {md5}8fa3e9125fd917948445e3d2621d40e5 failed: Could not back up

Guys Compliments of the festive season to everyone. Ive looked at mcollective plugins from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki And I tried / installed some of them. What im looking for is a method or really a mcollective plugin to ''aptitude safe-upgrade'' on my test VMs. Would anyone have a solution or method on how I can go about this. The only

I have a puppet server and various puppet agents. I want to do mcollective stuff. So please anyone tell me what should i install on puppet server and agent to run mcollective? Is there any need to install ActiveMQ also and where should i install it? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe

Over the years many shops have come to start running puppet via cron to address memory leaks in earlier versions of Ruby, but the official position was that puppet was meant to be run as a continually running service. I am wondering if the official position has changed. On one hand many if not all of the early Ruby issues have been fixed, on the other, the addition of mcollective into the mix as

Hello- I''m running puppet enterprise 2.5.1 and just installed the puppet- rundeck gem. When I try and start puppet-rundeck, I receive the message below: You need to have Puppet 0.25.5 or later installed /usr/lib64/ruby/gems/1.8/gems/puppet-rundeck-0.0.7/lib/puppet- rundeck.rb:34:in `configure'': uninitialized constant Class::Puppet (NameError) from ./puppet-rundeck:62

HI, i''m currently trying to develop a task-driven rails-based frontend for some tasks that puppet/mcollective is doing in the background ( basically some user-management and some asset queries...). But i''m currently stuck at finding some puppet/mcollective API classes for ruby. (you''ll only find results for using ruby within puppet, which is of course more obvious).

I''ve been thinking a lot about running mcollective on my production servers recently, especially about its nice integration with puppet (using facts and so on). However I''ve got some concern about its scalability - how publish/subscribe middleware scales in terms of speed and flooding the network. I run about 2000 servers. Has anyone got any experience running mcollective on

Hi! Is it possible to use Mcollective to run different cli commands remotely on nodes? Cannot find anything related in the documentation. -- Best regards, Sergey Arlashin -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to

On 12/05/16 10:21, James Hogarth wrote: > On 12 May 2016 at 08:22, G?tz Reinicke - IT Koordinator < > goetz.reinicke at filmakademie.de> wrote: > >> Hi, >> >> we see a growing need for a better Configuration management for our >> servers. >> >> Are there any known good resources for a comparison of e.g. Puppet, >> Chef, Ansible etc?

Hi, I deployed MCollective to our Puppet clients. approx. ~ 200. Our platform requires the most secure setup possible, so PSK as securityprovider is not an option. Therefor I changed the security provider to aes_security reusing puppets certificates in the server.cfg as found in the docs (1) Our goal is to use mcollective to offload event-driven actions to agents running on designated nodes from

I''ve been trying to find information, suggestions, etc. for how to combine scaling Puppet with the use of management tools like Dashboard/Foreman and MCollective. Our current thinking for an initial deployment is two VMs as Puppet Master worker nodes fronted by a pair of NetScalers. However, I''m not sure how to go about implementing Dashboard or Foreman and MCollective servers in

I am currently trying to get mcollective 2.2.4 up and running on RHEL 6 activeqm appears to be running and bound to the correct port, I see the server and client connections to the activemq box. However when I run mco ping all "seems to go well" except I get "No responses recieved" and above that I get the following log messages, debug 2013/05/29 17:02:12: activemq.rb:233:in

Hi everyone, I run MCollective 1.2.1 together with ActiveMQ 5.5 under Scientific Linux 6.1 on Amazon EC2. Overall it works like a charm, but sometimes (eg. 1/30) discovery fails. Still the exit-code of mco will be 0, which is a problem for me as I use MCollective e.g. to trigger deployments from Jenkins. I would like to ask for some feedback on the following ideas, that could fix this problem.

Now, I am getting this .... Thanks for the help! puppet5 : Cannot validate input: Unknown validator: ''puppet_server_address''. Cannot validate input: Unknown validator: ''puppet_server_address''.puppetdev04 : Puppet command ''puppet agent --test --onetime --daemonize --color=false --no-splay