tripleo-image-elements/elements/rabbitmq-server
Kiall Mac Innes 24fdfe9369 Leave symlinks for RabbitMQ state paths
As an operator, we instinctively expect e.g. logs to be
in /var/log while debugging. Placing a symlink allows
us to make debugging easier.

Change-Id: I86cfea07230ee3554f792b0b00ab366a60779d64
2014-08-26 18:28:11 +01:00
..
install.d Leave symlinks for RabbitMQ state paths 2014-08-26 18:28:11 +01:00
os-apply-config Prefer rabbit.host over rabbit.nodes 2014-08-04 11:41:50 +02:00
os-refresh-config PEP8 on the doc and elements files 2014-08-19 10:02:00 +02:00
README.md Move rabbitmq-server cluster port 2014-07-14 12:07:01 -07:00
element-deps Move rabbitmq-server cluster port 2014-07-14 12:07:01 -07:00

README.md

Install RabbitMQ server package and optionally configure it using Heat metadata.

Heat

We will create a random password and feed it to a Heat wait condition if directed by Metadata. The relevant Metadata would look something like this in Heat:

Metadata:
  rabbit:
    users:
      guest:
        username: guest
        tags: administrator
      nova:
        username: nova
        password: SuperSecret
        tags: 
          - administrator
          - monitoring
        permissions:
          conf: .*
          write: .*
          read: .*
    password_handle: {Ref: RabbitMQPasswordHandle}
    keepalive_disabled: true/false
    - Enable/Disable TCP keepalive on rabbitmq sockets (default is
    for keepalive to be enabled).

Using cfn-signal, we will feed back a generated password into the handle for use by other resources.

RabbitMQ Cluster

Additional parameters in heat template are required for each clustered node:

Metadata:
  rabbit:
    cookie: some_cookie
      - make sure same cookie is set for all nodes in cluster
    nodes:
      node0,node1

'rabbit.nodes' contains short hostnames of all nodes in RabbitMq cluster.

If a node has 'rabbit.nodes' set to true, this node is added into cluster with other nodes listed in 'rabbit.nodes'.

RabbitMQ inter-node communication is restricted to port 61000 only in config file (otherwise random ports would be used) to make sure this port can be enabled in firewall.

Due to bug http://bugzilla.redhat.com/show_bug.cgi?id=1105850, we must use a port within the ephemeral port range (32768-61000).

Port 61000 is reserved by using sysctl to set net.ipv4.ip_local_reserved_ports to 61000.

Sample 2-node cluster definition:

node0:
  rabbit:
    cookie: some_cookie
    nodes:
      Fn::Join:
      - ','
      - - Fn::Select:
          - name
          - Fn::GetAtt:
            - node0
            - show
        - Fn::Select:
          - name
          - Fn::GetAtt:
            - node1
            - show

node1:
  rabbit:
    cookie: some_cookie
    nodes:
      Fn::Join:
      - ','
      - - Fn::Select:
          - name
          - Fn::GetAtt:
            - node0
            - show
        - Fn::Select:
          - name
          - Fn::GetAtt:
            - node1
            - show