-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Luis Mayorga
committed
Aug 29, 2014
1 parent
e130f81
commit a234c67
Showing
1 changed file
with
13 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,21 @@ | ||
Rabbitmq-Cluster-Demo | ||
Rabbitmq Cluster Demo | ||
=============== | ||
|
||
RabbitMQ Server provisioned with Puppet on Ubuntu Trusty | ||
|
||
How Does it Work | ||
Requirements | ||
=============== | ||
|
||
* Start every vagrant machine (`vagrant up rbs1`, `vagrant up rbs2` , `vagrant up rbs3`) | ||
* Verify if they are running in a cluster (`sudo rabbitmqctl cluster_status`) on each server. | ||
* Vagrant 1.6.3 or later | ||
* Virtualbox 4.3.10 or later | ||
|
||
How does it work? | ||
=============== | ||
|
||
* Start the rabbitmq server cluster `vagrant up` | ||
* The **vagrant up** command will create 3 rabbitmq servers and 1 bunny client. | ||
|
||
Issues | ||
====== | ||
|
||
* Still have some issues with puppetlabs/rabbitmq puppet module and the cluster feature |