…and technology is not always the answer.

Mcollective and RabbitMQ on Centos

OK, so a few people heard that I was playing with RabbitMQ and MCollective and hinted (less than subtly I might add!) that a blog post might be in order, so here it is. If you want someone to blame, look no further than @patrickdebois and @garethr 🙂

The original issue was as follows:

I already use MCollective with ActiveMQ over STOMP, but the XML config format is a nightmare.

I want to use LogStash but that uses AMQP and ActiveMQ doesn’t support that.

I don’t want to have to run two message queuing servers on my network.

@ripienaar mentioned that he’d managed to get MCollective working with RabbitMQ’s new stomp plugin, and RabbitMQ is the AMQP server suggested by the logstash site. This looked promising – could I really kill two birds with one stone?

The answer – I’m pleased to announce – is yes, I was able to kill two birds with one stone, and this is how I did it…

Installing RabbitMQ

Install RabbitMQ-server 2.2.0 from the package downloaded from the RabbitMQ website as the version in EPEL doesn’t support the STOMP plugin.

I’ve found (as with so many of these things!) if the package is available as an RPM it’s probably easier to create your own YUM Repository on a webserver somewhere and point a yum.repo.d config file at it – that way you can let YUM pull in the dependencies instead of sinking into rpm-hell!

If you’re installing from RPM, you’ll need to install EPEL (for the dependencies) and then install the following packages:

>I’ve found (as with so many of these things!) if the package is available as an
> RPM it’s probably easier to create your own YUM Repository on a
> webserver somewhere and point a yum.repo.d config file at it – that way
> you can let YUM pull in the dependencies instead of sinking into rpm-hell!

you can also use the ‘localinstall’ action to install an rpm with yum, eg: