May 2018
Intermediate to advanced
256 pages
7h 6m
English
Most of the OpenStack API services are designed to be run on more than one system simultaneously. This configuration, the active/active configuration, requires a load balancer to spread traffic across each of the active services. The load balancer manages the VIP for the service and ensures that the backend systems are listening before forwarding traffic to them. The cluster manager ensures that the VIP is only active on one node at a time. The backend services may or may not be managed by the cluster manager in the active/active configuration. Service or system failure is detected by the load balancer and failed services are brought out of rotation.
There are a few different advantages to the active/active ...
Read now
Unlock full access