# RabbitMQEstimator RabbitMQEstimator - RabbitMQ configuration management database, provisioner, and heuristic analysis of traffic.
This project is a result of many discussions around the use and provisioning of RabbitMQ which has become pervasive in the past year. The issue is that when you initially setup RabbitMQ and expose it to the different needs of the business it typically will fail. As the use increases, the setup out of the box does not suffice. This is where the RabbitMQEstimator comes into play. The plan is for it to be a small clustered application that will work in a Pivotal Cloud Foundry, Docker compose or bare metal environment. Eventually the work can be done to enable Puppet, Chef, and Ansible.
Note that this code base uses ideas and code snippets from the RabbidManagement project https://github.com/Berico-Technologies/RabbidManagement
This project is a REST service that provides a set of RESTful endpoints protected by OAuth 2. The REST service is based on the Building a RESTful Web Service getting started guide. This project incorporates the new Java-based configuration support, now available in Spring Security OAuth 2.0.
This project builds multiple virtual RabbitMQ clusters in an internal database through a provided resource based REST interface. This set of clusters is a "Project" which has clusters and then nodes. The purpose of this is to have one place where a RabbitMQ Federation or just one RabbitMQ cluster can be stored either through provisioning the changes to the RabbitMQ cluster or provisioning the cluster through:
- BOSH release
- Docker Compose
- Bare Metal (create the RabbitMQ config files)
- Puppet (later)
- Chef (later)
- Ansible (later)
The purpose of the RabbitMQEstimator service is that once the project is provisioned, it will continually collect heuristic information about the cluster. This would be things like
- Drive space and memory used by queues
- Memory used by the system overall
- Number of Exchanges created
- Use of Federation
Using the original template by which the project (and it's clusters) are created the RabbitMQEstimator will have the capability to automatically create the new cluster in the environments and then transition the load to the new cluster(s). An HAProxy instance will be used to to create the no-downtime upgrade/deployment. In the future it should support hardware based load balancers.