I found out.
I only make 2 configuration.

_______________________________________________________________________________
file activemq.xml
<broker xmlns="http://activemq.apache.org/schema/core"; 
brokerName="mypuppetserver.domain.com.br" dataDirectory="${activemq.data}">

_______________________________________________________________________________
file credentials.properties
activemq.username=mcollective
activemq.password=marionette
_______________________________________________________________________________
Mcollective file server.cfg

main_collective = mcollective
collectives = mcollective

libdir = /opt/puppetlabs/mcollective/plugins

# consult the "classic" libdirs too
libdir = /usr/share/mcollective/plugins
libdir = /usr/libexec/mcollective

logfile = /var/log/puppetlabs/mcollective.log
loglevel = info
daemonize = 1

# Plugins
securityprovider = psk
plugin.psk = unset

connector = activemq
plugin.activemq.pool.size = 1
plugin.activemq.pool.1.host = mypuppetserver.domain.com.br
plugin.activemq.pool.1.port = 61613
plugin.activemq.pool.1.user = mcollective
plugin.activemq.pool.1.password = marionette
#plugin.activemq.pool.1.ssl = false

# Facts
factsource = yaml
plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml

_______________________________________________________________________________
Mcollective file client.cfg

main_collective = mcollective
collectives = mcollective

libdir = /opt/puppetlabs/mcollective/plugins

# consult the "classic" libdirs too
libdir = /usr/share/mcollective/plugins
libdir = /usr/libexec/mcollective

logger_type = console
loglevel = warn

# Plugins
securityprovider = psk
plugin.psk = unset

connector = activemq
plugin.activemq.pool.size = 1
plugin.activemq.pool.1.host = mypuppetserver.domain.com.br
plugin.activemq.pool.1.port = 61613
plugin.activemq.pool.1.user = mcollective
plugin.activemq.pool.1.password = marionette

connection_timeout = 3
_______________________________________________________________________________

Mcollective works fine.


Em sexta-feira, 26 de fevereiro de 2016 13:34:11 UTC-3, Leonardo escreveu:
>
> Puppet-agent-1.3.5 is all-in-one but how to configure mcollective in this 
> new version of Puppet?.
>
> I don't need to install mcollective-* because puppet-agent do that. 
>
> The oficial documentation is deprecated.
>
> Puppet-agent all-in-one (puppet, facter, hiera, mcollective). 
> Puppet version: 4.3.2  (puppet -version)
> puppet-agent-1.3.5
> puppetserver version: 2.2.1
>
> I've installed ActiveMQ and did the basic configuration (activemq.xml / 
> credentials.properties - user and password).
>
> Mcollective configuration.
> #cat /etc/puppetlabs/mcollective/{server.cfg,client.cfg}.
> #
> main_collective = mcollective
> collectives = mcollective
>
> libdir = /opt/puppetlabs/mcollective/plugins
>
> # consult the "classic" libdirs too
> libdir = /usr/share/mcollective/plugins
> libdir = /usr/libexec/mcollective
>
> logfile = /var/log/puppetlabs/mcollective.log
> loglevel = info
> daemonize = 1
>
> # Plugins
> securityprovider = psk
> plugin.psk = marionette
>
> connector = activemq
> plugin.activemq.pool.size = 1
> plugin.activemq.pool.1.host = puppetserver.domain.com.br
> plugin.activemq.pool.1.port = 61613
> plugin.activemq.pool.1.user = mcollective
> plugin.activemq.pool.1.password = marionette
>
> # Facts
> factsource = yaml
> plugin.yaml = /etc/puppetlabs/mcollective/facts.yaml 
> #
>
>
> But the commands "mco ping" and "mco find" not works, It does not result.
> Any Documentationor help?
>
>
> Thank you so much.
>

-- 
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/4b80ba67-cff0-4024-8245-e6b54f23adbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to