Puppet and MCollective
46 views
Skip to first unread message
ro001
Dec 12, 2013, 11:54:53 AM12/12/13
to puppet...@googlegroups.com
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 (server.cfg & client.cfg), so for this reason I do not save myself very much effort by using mcollective.
I am using vms so I can add mcollective to the vm template, but I wont know the name of mcollective/activemq machine nor would I know the name of the machine at that point.
How do you guys deploy mcollective? It seems abit like a chicken/egg scenario!
Jeff Bachtel
Dec 12, 2013, 12:46:03 PM12/12/13
to puppet...@googlegroups.com
I install puppet agent on provision (kickstart, VM template, whatever)
and do a puppet agent -t -w 1 (we don't autosign) at the end of the
provision script. MCollective in our environment is handled as part of
the puppet manifest, so after the agent run the host should be
registered in mco.
Jeff
> --
> 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 puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d1e0fc41-6558-4abf-bcc3-1a19e418d6f5%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
and do a puppet agent -t -w 1 (we don't autosign) at the end of the
provision script. MCollective in our environment is handled as part of
the puppet manifest, so after the agent run the host should be
registered in mco.
Jeff
> 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 puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/d1e0fc41-6558-4abf-bcc3-1a19e418d6f5%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
Jason Antman
Dec 13, 2013, 7:07:44 AM12/13/13
to puppet...@googlegroups.com
It's great that you're using Puppet and MCollective and trying to get
them setup everywhere, and there are some really easy ways to do that
when provisioning a new VM - either through templates or the build
process. Personally, I have Puppet baked in to our base installs (we
actually don't use templates, we kickstart each machine via Cobbler) and
use Puppet to install MCollective.
If you're wondering about *existing* VMs that for some reason you can't
just rebuild... what about a good, old-fashioned ssh-in-a-for-loop?
-jantman
On 12/12/2013 11:54 AM, ro001 wrote:
>
>
them setup everywhere, and there are some really easy ways to do that
when provisioning a new VM - either through templates or the build
process. Personally, I have Puppet baked in to our base installs (we
actually don't use templates, we kickstart each machine via Cobbler) and
use Puppet to install MCollective.
If you're wondering about *existing* VMs that for some reason you can't
just rebuild... what about a good, old-fashioned ssh-in-a-for-loop?
-jantman
On 12/12/2013 11:54 AM, ro001 wrote:
>
>
Reply all
Reply to author
Forward
0 new messages