Chapter 8. Investigating the RHOSO High Availability services You can use the following command to list all the Red Hat OpenStack Services on OpenShift (RHOSO) High Availability Galera, RabbitMQ, and memcached services, which provides their name, their type, whether they are a ClusterIP or LoadBalancer service, and their ports: You can use the following command to investigate the configuration of a service in more detail: Replace <service-name> with the name of the service from the list of services that you want more information about. In the following example the rabbitmq service is being investigated: 8.1. Testing the resilience of the RHOSO High Availability services You can simulate a failure to test how resilient the Red Hat OpenStack Services on OpenShift (RHOSO) High Availability services are to container failures. For example, you can use the following command to delete the rabbitmq-server-1 pod: After you delete the pod, you can use the following command the monitor the rescheduling process of the rabbitmq-server-1 pod: After a few seconds, the rabbitmq-server-1 pod should have the status of Running :

Commands:
oc get svc |egrep -e "rabbit|galera|memcache" memcached ClusterIP None <none> 11211/TCP openstack-cell1-galera ClusterIP None <none> 3306/TCP openstack-galera ClusterIP None <none> 3306/TCP rabbitmq LoadBalancer 172.30.21.129 172.17.0.85 5672:31952/TCP,15672:30111/TCP,15692:30081/TCP rabbitmq-cell1 LoadBalancer 172.30.97.190 172.17.0.86 5672:30043/TCP,15672:30645/TCP,15692:32654/TCP rabbitmq-cell1-nodes ClusterIP None <none> 4369/TCP,25672/TCP rabbitmq-nodes ClusterIP None <none> 4369/TCP,25672/TCP
oc describe svc/<service-name>
oc describe svc/rabbitmq Name: rabbitmq Namespace: openstack Labels: app.kubernetes.io/component=rabbitmq app.kubernetes.io/name=rabbitmq app.kubernetes.io/part-of=rabbitmq Annotations: dnsmasq.network.openstack.org/hostname: rabbitmq.openstack.svc metallb.universe.tf/address-pool: internalapi metallb.universe.tf/ip-allocated-from-pool: internalapi metallb.universe.tf/loadBalancerIPs: 172.17.0.85 Selector: app.kubernetes.io/name=rabbitmq Type: LoadBalancer IP Family Policy: SingleStack IP Families: IPv4 IP: 172.30.21.129 IPs: 172.30.21.129 LoadBalancer Ingress: 172.17.0.85 Port: amqp 5672/TCP TargetPort: 5672/TCP NodePort: amqp 31952/TCP Endpoints: 192.168.16.43:5672,192.168.20.69:5672,192.168.24.53:5672 Port: management 15672/TCP TargetPort: 15672/TCP NodePort: management 30111/TCP Endpoints: 192.168.16.43:15672,192.168.20.69:15672,192.168.24.53:15672 Port: prometheus 15692/TCP TargetPort: 15692/TCP NodePort: prometheus 30081/TCP Endpoints: 192.168.16.43:15692,192.168.20.69:15692,192.168.24.53:15692 Session Affinity: None External Traffic Policy: Cluster Events: <none>
oc delete pod/rabbitmq-server-1 pod "rabbitmq-server-1" deleted
oc get pods |grep rabbit rabbitmq-cell1-server-0 1/1 Running 0 4h20m rabbitmq-cell1-server-1 1/1 Running 0 4h20m rabbitmq-cell1-server-2 1/1 Running 0 4h20m rabbitmq-server-0 1/1 Running 0 4h20m rabbitmq-server-1 0/1 Init:0/1 0 2s rabbitmq-server-2 1/1 Running 0 4h20m
oc get pods |grep rabbit rabbitmq-cell1-server-0 1/1 Running 0 4h23m rabbitmq-cell1-server-1 1/1 Running 0 4h23m rabbitmq-cell1-server-2 1/1 Running 0 4h23m rabbitmq-server-0 1/1 Running 0 4h23m rabbitmq-server-1 1/1 Running 0 3m8s rabbitmq-server-2 1/1 Running 0 4h23m