More secure and efficient triggering of puppet updates by deploying MCOLLECTIVE+ACTIVEMQ modules

Experimental environment:

puppetserver.rsyslog.org

Mcollective Client +ACTIVEMQ service side +puppet service end

agent1.rsyslog.org

Mcollective Service-Side +puppet Client

Application: Apache

agent2.rsyslog.org

Mcollective Service-Side +puppet Client

Application: Apache+mysql

agent3.rsyslog.org

Mcollective Service-Side +puppet Client

Application: PHP

Experiment steps:

First, deploy the RABBITMQ at the Puppetserver end

1. Installation Activemq

[Root@puppetserver yum.repos.d]# yum install tanukiwrapper ACTIVEMQ

2. Configure ACTIVEMQ

<simpleAuthenticationPlugin>

<users>

<authenticationuser username= "admin" password= "123.com" groups= "Mcollective,admins,everyone"/>

<authenticationuser username= "mcollective" password= "secret" groups= "Mcollective,admins,everyone"/>

</users>

</simpleAuthenticationPlugin>

<transportConnectors>

<transportconnector name= "Openwire" uri= "tcp://0.0.0.0:61616"/>

<!--<transportconnector name= "Stomp+nio" uri= "stomp+nio://0.0.0.0:61613"/>-->

<transportconnector name= "Stomp" uri= "stomp://0.0.0.0:61613"/>

</transportConnectors>

3, Start ACTIVEMQ

[Root@puppetserver activemq]#/etc/rc.d/init.d/activemq Restart

Stopping ActiveMQ Broker ...

ActiveMQ Broker is not running.

Starting ActiveMQ Broker ...

[Root@puppetserver activemq]# chkconfig activemq on

[Root@puppetserver activemq]# NETSTAT-NLATP | grep 61613

TCP 0 0::: 61613:::* LISTEN 3098/java