I don't know how puppet enterprise works with mco, but in the open source version you have to create a certificate for the user you are going to call mco and sign in with the middleware certificate. El 17/02/2014 18:50, "Deep" <skitdeep...@gmail.com> escribió:
> Hi Jose, > > Thanks for your quick response and explaining me in details. I tried mco > ping command but getting below error. > > error 2014/02/17 16:23:00: activemq.rb:131:in `on_ssl_connectfail' SSL > session creation with stomp+ssl://mcollective@gsldev23:61613 failed: > nested asn1 error > > I am using below ssl configuration in client.cfg > > plugin.activemq.pool.1.ssl.ca = > /etc/puppetlabs/mcollective/ssl/mcollective-cacert.pem > plugin.activemq.pool.1.ssl.cert = > /etc/puppetlabs/mcollective/ssl/mcollective-private.pem > plugin.activemq.pool.1.ssl.key = > /etc/puppetlabs/mcollective/ssl/mcollective-cert.pem > > > securityprovider = ssl > > # SSL plugin settings: > plugin.ssl_server_public = > /etc/puppetlabs/mcollective/ssl/mcollective-public.pem > plugin.ssl_client_private = > /etc/puppetlabs/mcollective/ssl/mcollective-private.pem > plugin.ssl_client_public = > /etc/puppetlabs/mcollective/ssl/mcollective-public.pem > > Can you tell me if this is wrong? > > > On Monday, February 17, 2014 5:30:52 PM UTC, Jose Luis Ledesma wrote: >> >> Hi, >> >> Mcollective has 3 roles: >> - the server installed in every puppet client >> - the middleware installed in puppet master >> - the client installed anywhere, puppet master is a good place >> >> The client is just the utilities to call commands, it attacks the >> middleware, authenticate with certificates, and it is the middle ware who >> spread the command to every mcollective server. It doesnt have an agent >> running. >> >> Just try 'mco ping' from the server/user that is the mco client to check >> if it works. >> >> Regards, >> El 17/02/2014 18:14, "Deep" <skitd...@gmail.com> escribió: >> >>> Hi All, >>> >>> I have installed puppet enterprise which comes with Mcollective. I have >>> installed Puppet Master on node 1 and puppet agent on node 2 and node 3. >>> while installing , it asked me if I want to install Mcollective. I wanted >>> to have Mcollective client on my Puppet Master. and Mcollective servers on >>> node 2 and node 3. >>> >>> But when I checked, there was no client.cfg file created at >>> /etc/puppetlabs/mcollective/. And Mcollective was started using server.cfg >>> >>> How can I use Mcollective client on puppet Master? >>> >>> I have created client.cfg but still Mcollective needs server.cfg to >>> start. Can anybody suggest me on this please? I am new to Mcollective and >>> trying to learn it and implement it. >>> >>> Regards, >>> Deep >>> >>> -- >>> 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/eb01e6ad-ecb1-4dc9-acb5-ca6768af6173% >>> 40googlegroups.com. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> -- > 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+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/d02964e3-b236-489c-9710-f406fea7a114%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF_B3dcOXCAWtG13pyD-%3D8qg-X4aR%3DUvD166D4BZhw5XLXOxfw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
