Gavin M. Roy
2015-07-30 02:14:14 UTC
Version 0.3.0 of rabbitmq-autocluster-consul has been released.
The rabbitmq-autocluster-consul plugin joins RabbitMQ nodes as they start
after they register themselves Consul. The result is that you can quickly
spin up RabbitMQ clusters with little or no pre-configuration. When
RabbitMQ registers with Consul, it will register the service with a
configurable AMQP port and TTL health check. Additionally, you can specify
a cluster name in rabbitmq.config that allows you to have multiple
RabbitMQ clusters on the same network.
This version adds new functionality and bug fixes:
- All configuration can now be made via operating system environment
variables in addition to the rabbitmq.config file
- The service prefix in Consul is now optional (#8, #11)
- The service is now registered in Consul with the AMQP port and a TTL
health check
- The Consul URI scheme can not be configured (http/https)
- The startup process is reworked and addresses a bug when a node is
restarted or is rejoining (#5)
Special thanks to Wes Morgan for his testing and contributions to this
release.
Instructions and a zip file with pre-built binaries for RabbitMQ v3.5.x are
available at:
https://github.com/aweber/rabbitmq-autocluster-consul#readme
Cheers,
Gavin
The rabbitmq-autocluster-consul plugin joins RabbitMQ nodes as they start
after they register themselves Consul. The result is that you can quickly
spin up RabbitMQ clusters with little or no pre-configuration. When
RabbitMQ registers with Consul, it will register the service with a
configurable AMQP port and TTL health check. Additionally, you can specify
a cluster name in rabbitmq.config that allows you to have multiple
RabbitMQ clusters on the same network.
This version adds new functionality and bug fixes:
- All configuration can now be made via operating system environment
variables in addition to the rabbitmq.config file
- The service prefix in Consul is now optional (#8, #11)
- The service is now registered in Consul with the AMQP port and a TTL
health check
- The Consul URI scheme can not be configured (http/https)
- The startup process is reworked and addresses a bug when a node is
restarted or is rejoining (#5)
Special thanks to Wes Morgan for his testing and contributions to this
release.
Instructions and a zip file with pre-built binaries for RabbitMQ v3.5.x are
available at:
https://github.com/aweber/rabbitmq-autocluster-consul#readme
Cheers,
Gavin
--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+***@googlegroups.com.
To post to this group, send an email to rabbitmq-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-users+***@googlegroups.com.
To post to this group, send an email to rabbitmq-***@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.