Rabbitmq Server cluster docker images for openshift origin platform

Build rabbitmq cluster docker images for openshift origin platform.
Down load docker file tarball rabbitmq.tar, and cd rabbitmq, run

docker build -t rabbitmq . 

after build process is done, tag the images built with rabbitmq:v002

docker images

docker tag image-id rabbitmq:v002

and then deploy a rabbitmq-server cluster in openshift origin platform. we should create a serviceaccount rabbitmq, and add it with anyuid scc.

oc create serviceaccount rabbitmq
oc adm policy add-scc-to-user anyuid -z rabbitmq

deploy it

oc create -f rabbitmq.yaml

Openshift origin multi-node installation guide

in this tutorial, i will describe how to deploy an openshift multi-node cluster manually.
before we start, let’s clarify some basic requirements and deployment topology.

one master node, virtual box vm, 2 cores + 2G mem + 20G disk
two nodes, virtual box vm, 2 cores + 2G mem + 20G disk

master hostname: master.openshift.shaunos.com ip address: 192.168.2.49
node1 hostname: node1.openshift.shaunos.com ip address: 192.168.2.50
node2 hostname: node2.openshift.shaunos.com ip address: 192.168.2.56

All three vms with centos 7.2(1511) minimal installation are on the same subnet, static ip address.

for openshift oauth, i use anypassword auth plugin
for openshift network, i use sdn muilti-tenant plugin

Okay, let’s start

Continue reading

Adjust total file descriptors of rabbitmq

The total file descriptors number of rabbitmq is 1024 by default. This value is not big enough obviously when your openstack cluster grows. If the file descriptor or socket descriptor reaches its limit, the rabbitmq server will close incoming connections. and you will see the error below:

AMQP server on controller1:5672 is unreachable: timed out. Trying again in 1 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 2 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 4 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 6 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 8 seconds.
AMQP server controller1:5672 closed the connection. Check login credentials: Socket closed
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 12 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 14 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 16 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 18 seconds.
AMQP server on controller1:5672 is unreachable: timed out. Trying again in 20 seconds.
AMQP server controller1:5672 closed the connection. Check login credentials: Socket closed

To check the current status of file descriptors used, you can run command ‘service rabbitmq-server status’
the result is

Continue reading

Monasca installation and configuration guide

In this tutorial, i will describe how to setup monasca components in detail. Before we start, something needs to be confirmed:

  • All the components of monasca can be installed on one node, such as on openstack controller node, or you can deploy it in multi-nodes. In this tutorial, i will install monasca-api in a new VM created in my openstack cluster, which has a floating ip associated. Monasca-agent was installed on controller node. The agent node post metrics to api node through floating ip. the are in the same sub net.
  • All the user name and password in this tutorial is monasca and qydcos. change it to yours.
  • the installation will be performed on ubuntu 14.04 openstack Mitaka version, for liberty, special settings must be made and be described later.
  • All the file related in this tutorial are here, clone it before you start.

    Continue reading

  • Page 2 of 71234567