Auto-Start deployment
For auto-start deployment, there are four basic types of OS/VM cluster environment and software configurations:
- Active-Passive
In this configuration, node1 is hosting Cloverleaf and node2 is designated as a standby node, waiting for node1 to fail. When a failover happens, Cluster takes this action:
- Moves the application data files to the secondary node
- Moves application IP address to the secondary node
- Starts application on the secondary node; clients may see a brief interruption in service and may require a refresh/reconnect.
- Active-Test
In this configuration, node1 is hosting production instance of Cloverleaf. Node2 is designated as standby node, and hosts the test instance. When a failover happens, Cluster takes this action:
- Moves the production data files to the secondary/test node.
- Moves production IP address to the secondary/test node.
- Starts production application on the secondary node; clients may see a brief interruption in service and may require a refresh/reconnect.
- Active-Active
In this configuration, node1 is hosting production instance of Cloverleaf. Node2 is hosting second instance of Cloverleaf. Both nodes act as secondary to each other, also known as mutual take-over. When a failover happens, node2 becomes double-active. Cluster takes this action:
- Moves the production data files to the secondary node.
- Moves production IP address to the secondary node.
- Starts production application on the secondary node; clients may see a brief interruption in service and may require a refresh/reconnect.
- Geo-Cluster
In this configuration, the cluster is configured across two data centers. This provides a greater level of availability and protection of storage by having a second copy of the data at the secondary location. When a primary data center fails, application is relocated to secondary/remote data center. Cluster takes this action:
- Remote data center is designated as a primary location.
- Moves the application IP to remote data center.
- Starts the application at remote data center; clients may see a brief interruption in service and may require a refresh/reconnect.