similar to: About Facter via YAML and mcollective

----- lists@truthisfreedom.org.uk wrote: > We have a team of system administrators within our organisation who love the > look and power of MCollective but are currently "unable" to utilise it fully > as they don''t know ruby (for some reason Python is the language of > choice here!). > > I''m writing a new web interface for our change management

Hello, I''ve mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2 setup from http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. Now I''ve create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/ customer_status.rb. On the client; Running facter customer_status works. Running ''puppet agent --test'' works, customer_status

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?

http://saltstack.org/ http://puppetlabs.com/mcollective/ I found this link that talks about Func, Rundeck, Salt and mcollective, but it doesn''t really compare and contrast. http://www.coloandcloud.com/editorial/func-mcollective-salt-and-rundeck/(From a 10,000 overview Saltstack and mcollective look very similar. IE: both integrate with facter/puppet, have queuing mechanisms, allow remote

I find the cause of the problem, because the client and server time not synchronization. 发件人: 刘亚丹 [mailto:lyflyd@gmail.com] 发送时间: 2012年7月10日 10:10 收件人: ''puppet-users@googlegroups.com'' 主题: puppet mcollective problem Hi, I am a new puppet user . I had some trouble when I using the mcollective. Soft info: Mcollective :2.0.0

Has anyone else ran into this? debug: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: Executing ''diff -u /var/tmp/facts.yaml /tmp/puppet-file20121214-13448-933j3r-0'' notice: /Stage[main]/Mcollective/File[/var/tmp/facts.yaml]/content: --- /var/tmp/facts.yaml 2012-12-14 00:53:20.000000000 +0000 +++ /tmp/puppet-file20121214-13448-933j3r-0 2012-12-14

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 everyone, I''m going to try announcing new versions of Modules I''m working on as I release them to the Forge. puppet-users and mcollective-users seems like the best place, but please let me know if you have other preferences. I''ve added a small change to the mcollective module we''ve recently released [1]. This change ensures all of the resources managed by

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

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 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

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

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).

Each run of the mcollective is spitting out errors about being unable to connect to my virtual ethernet devices. root@hostname# /opt/puppet/sbin/refresh-mcollective-metadata entstat: 0909-003 Unable to connect to device vi0, errno = 19 entstat: 0909-003 Unable to connect to device vi1, errno = 19 entstat: 0909-003 Unable to connect to device vi2, errno = 19 entstat: 0909-003

Hi, I was wondering if there was an easy way of managing database schemas and content on different servers using mcollective/puppet Some of my thoughts are - since puppet seems to use ruby on rails maybe I can use active record migrations to do this ?(I don''t know much about ruby or rails by the way). One problem I faced when doing something else was that other vendor libraries?

I was just thinking about the problem of host groups and such trying to set up our puppet infrastructure properly and came to the realization that using MCollective better in puppet dashboard would allow for more cloud like scaling of infrastructure services. Here is the concept: Right now in puppet dashboard groups can have nodes, facts (parameters) and Classes. What I am suggesting would

I have set up puppet to create a facts.yaml file for mcollective using the following line: content => inline_template("<%= scope.to_hash.reject { |k,v| k.to_s =~ /(uptime.*|timestamp|.*free|macaddress.*|ipaddress)/ }.to_yaml %>"), However, it is creating a lot of unnecessary changes by reordering the facts in the yaml output as you can see in the diff output between to

Hi, I want to use a file resource to write a facts.yaml file for Mcollective. For some reason it won''t provide a valid yaml format if I dump my scope to hash and convert to_yaml. file { "/etc/mcollective/facts.yaml" : owner => root, group => root, mode => 400, loglevel => debug, #content => inline_template("<%= scope.to_hash.reject {

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