Maintaining VM High Availability Using OpenStack Masakari

With organizations running increasing numbers of critical systems over private clouds, there is a greater need than ever for reliable, highly available infrastructure.  VM high availability allows for maximum uptime when running in the cloud, while shielding the user from any unplanned downtime of the infrastructure.

In broad terms, both Cloud Native apps and traditional applications rely on high availability to maintain maximum uptime.  However, while Cloud Native apps are designed to tolerate failures of an availability zone by auto scaling to another server within the zone, traditional apps cannot tolerate such infrastructure failures, as they assume that the underlying infrastructure is fully functioning.  OpenStack Masakari provides VM high availability to these apps by automatically recovering VMs from compute host failure events.

Read Blog Post:

Transcript of Video: 

Pushkar: [00:18] Today, we are going to talk about high availability for virtual machines. What is high-availability? Availability in computing terms refers to the amount of time a particular service is available, functionally available during any given amount of time.

Pushkar: [00:32] As more and more workloads are deployed to the private cloud, the need for reliable infrastructure has gone up significantly. VM high availability
 refers to the ability of the cloud to tolerate infrastructure failures without affecting a user's virtual machine, which means that the VM keeps it on running fine and the user does not see any downtime to his work. 

Pushkar: [00:52] In broad terms, today's applications can be categorized into two types - Cloud Native apps and traditional apps.

Pushkar: [01:00] Cloud Native apps are designed to tolerate failures of an availability zone. In OpenStack, these applications can be deployed using the open stack heat service in the auto-scaling groups. So whenever there is an infrastructure failure the HEAT service will auto-scale the app to a different availability zone and the app keeps running fine.

Pushkar: [01:21] Traditional apps are not designed to tolerate such failures. They require a reliable infrastructure. This is where OpenStack Masakari comes into picture. OpenStack Masakari uses Pacemaker and Corosync for creating a cluster on the host and detecting host failures.

Pushkar: [01:37] Here the administrator now needs to deploy and monitor and configure not just where Pacemaker and Corosync but also open stack Masakari. And after detecting host failures, if the host needs to be removed he needs to make sure that the cluster is healthy again before starting the workloads.

Pushkar: [01:56] So how does Platform9 Manage OpenStack help in a VM high-availability. Platform9 uses Hasicorp Consul for creating a cluster instead of Pacemaker and Corosync. This cluster of Consul hosts will be used for detecting host failure event.

Pushkar: [02:13] So when an administrator wants to enable high availability and Platform9 Managed OpenStack, all he needs to do is create a host aggregate and select enable HA. Platform9 will then install, configure and monitor the console services on the host and it will also install and configure Masakari on the controllers.

Pushkar: [02:34] This takes out a lot of complexity from enabling HA for virtual machines. Enabling VM high-availability should not be a challenge and Platform9 Managed OpenStack and OpenStack Masakari can make that simple for you.

Previous Video
Kubernetes Upgrades with Low/No Downtime
Kubernetes Upgrades with Low/No Downtime

Next Video
OpenStack Ironic: Enabling Bare Metal as a Service
OpenStack Ironic: Enabling Bare Metal as a Service