9.4.2. Restarting the Red Hat Ceph Storage 5 Alertmanager service
After migrating from ceph-ansible to cephadm, you can restart the Alertmanager service before continuing with the process. Restarting the Alertmanager service requires restarting the HAProxy service as well.
Restarting the HAProxy service introduces downtime to the Red Hat OpenStack Platform control plane. The downtime lasts as long as is required for the HAProxy service to restart.
Procedure
Log in to the OpenStack Controller node.
참고Confirm that you are logged into a node that is hosting the Ceph Manager service. In default deployments, this is the OpenStack Controller node. You must be logged into a Controller node that is running the Ceph Manager service.
View the current Alertmanager specification file:
$ sudo cephadm shell -- ceph orch ls --export alertmanagerCreate a specification file for the Alertmanager service based on the output from the previous step.
The following is an example of a specification file:
service_type: alertmanager service_name: alertmanager placement: count: 3 label: monitoring networks: - 10.10.10.0/24 - 10.10.11.0/24참고The IP addresses in the
networkslist should correspond with the Storage/Ceph public networks in your environment.-
Save the specification file as
/root/alertmanager.spec. Stop the HAProxy service:
# pcs resource disable haproxy-bundleStop the Alertmanager service:
# cephadm shell -k /etc/ceph/<stack>.client.admin.keyring -- ceph orch rm alertmanager-
Replace
<stack>with the name of your stack.
-
Replace
Start the Alertmanager service:
# cephadm shell -k /etc/ceph/<stack>.client.admin.keyring -m /root/alertmanager.spec -- ceph orch apply -i /mnt/alertmanager.spec-
Replace
<stack>with the name of your stack.
-
Replace
Start the HAProxy service:
# pcs resource enable haproxy-bundle
Perform this procedure again if the Alertmanager service does not restart, adding a port definition to the specification file. The following is the previous specification file example with a port definition added:
service_type: alertmanager
service_name: alertmanager
placement:
count: 3
label: monitoring
networks:
- 10.10.10.0/24
- 10.10.11.0/24
spec:
port: 4200
- 1
- Custom port definition. Use a port that corresponds to your deployment environment.