Skip to content

Commit a1b1ad8

Browse files
authored
Merge pull request #806 from stackhpc/rabbitmq-use-systemd-units
Use systemctl in RMQ hammer playbook and docs
2 parents 372beee + 654625c commit a1b1ad8

File tree

2 files changed

+5
-6
lines changed

2 files changed

+5
-6
lines changed

doc/source/operations/rabbitmq.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ Stop all the OpenStack services which use RabbitMQ.
9898

9999
.. code-block:: console
100100
101-
kayobe overcloud host command run --command "docker ps -a | egrep '(barbican|blazar|ceilometer|cinder|cloudkitty|designate|heat|ironic|keystone|magnum|manila|masakari|neutron|nova|octavia)' | awk '{ print \$NF }' | xargs docker stop"
101+
kayobe overcloud host command run -b --command "systemctl -a | egrep '(barbican|blazar|ceilometer|cinder|cloudkitty|designate|heat|ironic|keystone|magnum|manila|masakari|neutron|nova|octavia)' | awk '{ print \$1 }' | xargs systemctl stop"
102102
103103
Upgrade RabbitMQ.
104104

@@ -136,7 +136,7 @@ procedure.
136136

137137
.. code-block:: console
138138
139-
kayobe overcloud host command run --command "docker ps -a | egrep '(barbican|blazar|ceilometer|cinder|cloudkitty|designate|heat|ironic|keystone|magnum|manila|masakari|neutron|nova|octavia)' | awk '{ print \$NF }' | xargs docker start"
139+
kayobe overcloud host command run -b --command "systemctl -a | egrep '(barbican|blazar|ceilometer|cinder|cloudkitty|designate|heat|ironic|keystone|magnum|manila|masakari|neutron|nova|octavia)' | awk '{ print \$1 }' | xargs systemctl start"
140140
141141
Check to see if the expected queues are durable.
142142

@@ -170,7 +170,7 @@ such as the following when other OpenStack services start::
170170
vhost '/': received 'true' but current is 'false'
171171

172172
This may happen if a host is not in the inventory, leading to them not being
173-
targeted by the ``docker stop`` command. If this does happen, look for the
173+
targeted by the ``systemctl stop`` command. If this does happen, look for the
174174
hostname of the offending node in the queues created after the RabbitMQ reset.
175175

176176
Once the rogue services have been stopped, reset the RabbitMQ cluster again to

etc/kayobe/ansible/rabbitmq-reset.yml

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@
1212
- container_name: rabbitmq
1313
tasks:
1414
- name: Checking timedatectl status
15-
become: true
1615
command: timedatectl status
1716
register: timedatectl_status
1817
changed_when: false
@@ -32,7 +31,7 @@
3231
register: inspection
3332

3433
- name: Ensure the {{ container_name }} container is running
35-
command: "docker start {{ container_name }}"
34+
command: "systemctl start kolla-{{ container_name }}-container.service"
3635
when: inspection.stdout == 'false'
3736

3837
- name: Wait for the {{ container_name }} container to reach state 'Running'
@@ -69,4 +68,4 @@
6968
# The following services can have problems if the cluster gets broken.
7069
- name: Restart OpenStack services
7170
shell: >-
72-
docker ps -a | egrep '(cinder|heat|ironic|keystone|magnum|neutron|nova)' | awk '{ print $NF }' | xargs docker restart
71+
systemctl -a | egrep '(cinder|heat|ironic|keystone|magnum|neutron|nova)' | awk '{ print $1 }' | xargs systemctl restart

0 commit comments

Comments
 (0)