You are here: Supporting Documents > Reference Topics > High Availability in the Cloud > High Availability Overview

High Availability Overview

High Availability seeks to eliminate system downtime and data loss. High Availability provides a set of failure detection and failure recovery mechanisms that can be grouped into various availability-related policies by an IT administrator. The policies are available to application owners to manage the availability-related characteristics of their applications. Additionally, High Availability connects to workload management and workload placement.

Features include KVM-FT, Orchestration Proactive Monitoring, and awareness of infrastructure redundancies; for example, network paths, storage RAIDs, and others. The Stratus Cloud Solution leverages High Availability as protection from compute node failures, and ensures continuous workload operations. High Availability manages the cloud in a holistic method which includes network, storage, and other infrastructure aspects for maintaining your service levels. High Availability in a networking deployment helps mitigate the impact of individual node failures.

Availability Levels

The Stratus Cloud Solution provides three pre-defined High Availability levels:

The availability levels can be changed at any time.

Support for the IT Administrator

To support the IT administrator, High Availability provides the ability to:

Support for the Application Owner

To support the application owner, High Availability provides the ability to:

High Availability Usage Scenarios

High Availability levels are based on the infrastructure components being monitored; for example, compute, network, and storage. High Availability capabilities apply to all hypervisors supported by OpenStack including KVM, ESX, and HyperV.

Usage scenarios for High Availability include:

Key benefits of Stratus Cloud Solution High Availability technology are:

High Availability images connect to shared storage and prohibit them from using direct-attached storage (DAS). Therefore, there is no waiting period for a failed hypervisor or failed DAS to return to service.

of