We'd recently began using MCollective along with Puppet in our setup. MCollective is a framework to build server orchestration or parallel job execution systems. We had MCollective running with ActiveMQ as MOM for management of our EC2 infrastructure, however for our setup at Softlayer we decided to go ahead and make use of RabbitMQ as our MOM.
Thanks to R.I. Pienaar we were quickly able to get solution to some of our issues and very recently one of our developers suggested that we should be making use of a separate vhost for use of mcollective. Seems like a great idea, we all thought ! However after discussions on mcollective user group we found that stomp connector provided with mcollective, by default doesn't allow for passing of host header information to RabbitMQ.
R.I. Pienaar once again came as a saviour and suggested some changes to our stomp connector which now allow us to make use of /mcollective as a vhost while communicating with RabbitMQ.
So here is a change we made to /usr/libexec/mcollective/mcollective/connector/stomp.rb (This location can change with distribution).
@connection = connector.new(user, password, host, port, true, 5, {"accept-version" => '1.0,1.1', "host" => "/mcollective\"})
0 comments:
Post a Comment