This document summarizes a presentation about automating cloud recovery using OVH's cloud services. It discusses using OVH's private and public cloud along with replication and failover capabilities to ensure workloads are recovered when on-premises infrastructure goes down. The presentation includes a demo of how applications are automatically failed over from an on-premises environment to OVH's public cloud when networking is lost. It also discusses how the "Mother" application was created using the vCloud API to monitor replications and initiate failovers when needed to provide automated cloud recovery without downtime.
Scaling API-first – The story of a global engineering organization
Let OVH Help You Automate your Cloud Recovery for when you are Nuked from Orbit: It’s the only way to be sure
1. Ashley Neely
Sr. Solution Strategist
LHC1951BE
#VMworld #LHC1951BE
Let OVH Help You Automate
your Cloud Recovery for when
you are Nuked from Orbit:
It’s the only way to be sure.
2. 2017 Proprietary and Confidential
AUTOMATE CLOUD RECOVERY
it’s the only way to be sure…
–––
Ashley Neely | Sr. Solution Strategist
With OVH you get access to almost any type of infrastructure you will need. If you are like most businesses you have a large number of Vmware based VMs running on-prem. OVH’s private cloud is based on Vmware’s SDDC stack and with the acquisition of vCloud Air, connecting your on-prem to a private cloud has never been easier.
If you are looking for public cloud burstability OVH has you covered with Public Cloud provided and run on Openstack.
But let’s say you have a workload that has specific requirements and you want access to all parts of the software stack. OVH has Bare Metal servers for you.
OVH not only provides differing product platforms to address specific project needs of customers, we also allow the integration of these resources to allow for easy setup and communication between these platforms with our vRack product.
A customer may have a piece of each of these all combined into a single solution that suites their needs.
Private cloud – vSphere SDDC allowing ease of management by leveraging the same tools you’re used to from VMware.
Public Cloud – Get virtualized machines at a per hour/minute cost by leveraging OVH’s public cloud built with Openstack.
Dedicated Servers – Have full control of every aspect of your environment by starting from bare metal. Have root and BIOs level access to your hardware, and install what you want.
With OVH you get access to almost any type of infrastructure you will need. If you are like most businesses you have a large number of Vmware based VMs running on-prem. OVH’s private cloud is based on Vmware’s SDDC stack and with the acquisition of vCloud Air, connecting your on-prem to a private cloud has never been easier.
If you are looking for public cloud burstability OVH has you covered with Public Cloud provided and run on Openstack.
But let’s say you have a workload that has specific requirements and you want access to all parts of the software stack. OVH has Bare Metal servers for you.
OVH not only provides differing product platforms to address specific project needs of customers, we also allow the integration of these resources to allow for easy setup and communication between these platforms with our vRack product.
A customer may have a piece of each of these all combined into a single solution that suites their needs.
Private cloud – vSphere SDDC allowing ease of management by leveraging the same tools you’re used to from VMware.
Public Cloud – Get virtualized machines at a per hour/minute cost by leveraging OVH’s public cloud built with Openstack.
Dedicated Servers – Have full control of every aspect of your environment by starting from bare metal. Have root and BIOs level access to your hardware, and install what you want.
NIC pulled for VLAN2 / 10.10.10.1/24
Mother app running in vCA loses communication
Csv created to have a Tier for each application
Failover for Tier 1 apps was set at 1 minute
Failover for Tier 2 apps was set at 5 minutes
Failover for Tier 3 apps was set at 10 minutes
Status updates provided during failover, while connectivity is being restored.
NIC pulled for VLAN2 / 10.10.10.1/24
Mother app running in vCA loses communication
Csv created to have a Tier for each application
Failover for Tier 1 apps was set at 1 minute
Failover for Tier 2 apps was set at 5 minutes
Failover for Tier 3 apps was set at 10 minutes
Status updates provided during failover, while connectivity is being restored.
NIC pulled for VLAN2 / 10.10.10.1/24
Mother app running in vCA loses communication
Csv created to have a Tier for each application
Failover for Tier 1 apps was set at 1 minute
Failover for Tier 2 apps was set at 5 minutes
Failover for Tier 3 apps was set at 10 minutes
Status updates provided during failover, while connectivity is being restored.
NIC pulled for VLAN2 / 10.10.10.1/24
Mother app running in vCA loses communication
Csv created to have a Tier for each application
Failover for Tier 1 apps was set at 1 minute
Failover for Tier 2 apps was set at 5 minutes
Failover for Tier 3 apps was set at 10 minutes
Status updates provided during failover, while connectivity is being restored.
Mother/start.py – configure your environment, pull replication data and match it to on premise replication information, then start script to monitor vis ping
Obtain a session & authentication token that are stored
Obtain a session & authentication token that are stored
Obtain a session & authentication token that are stored
Obtain a session & authentication token that are stored
Mother/start.py – configure your environment, pull replication data and match it to on premise replication information, then start script to monitor vis ping
Mother/start.py – configure your environment, pull replication data and match it to on premise replication information, then start script to monitor vis ping
Take replication appliance csv and match it to replication UUIDs in vCloud Air
Mother/start.py – configure your environment, pull replication data and match it to on premise replication information, then start script to monitor vis ping
Background ping and failover process
Background ping and failover process
Successful failover of a VM in the log
Session obtained and logged at failover time
VM name and status of failover displayed
10 GHz CPU base capacity
20 GB RAM
1 TB Basic Storage (DR)
2 TB Basic Storage (VPC)
10 Mbps+ Network
2 Public IP
API management of these resources
Access to modify everything from NAT and FW rules on the edge to modifying IPSec VPNs
In a model like this the customer has scaled out quite a bit with
2 Dedicated Cloud SKUs
1 HCM Enterprise SKU
Additional 420 GHz & 2880 GB RAM
Additional 72 TB Basic storage
Additional 72 TB SSD-Accelerated Storage
Bandwidth upgrade to 10 Gbps
12 additional public IP addresses
10 Gbps Direct Connect
Large sized Dedicated DR environment with HDMZ
Support for 1-1000 replicated VMs, with an additional 1000 VMs in the DMZ SID, 200 VMs in their VPC and another 600 in Dedicated cloud, adding up to 2800 VMs in vCloud Air, all of which can be managed via API, scripting and automation
In a model like this the customer has scaled out quite a bit with
2 Dedicated Cloud SKUs
1 HCM Enterprise SKU
Additional 420 GHz & 2880 GB RAM
Additional 72 TB Basic storage
Additional 72 TB SSD-Accelerated Storage
Bandwidth upgrade to 10 Gbps
12 additional public IP addresses
10 Gbps Direct Connect
Large sized Dedicated DR environment with HDMZ
Support for 1-1000 replicated VMs, with an additional 1000 VMs in the DMZ SID, 200 VMs in their VPC and another 600 in Dedicated cloud, adding up to 2800 VMs in vCloud Air, all of which can be managed via API, scripting and automation
In a model like this the customer has scaled out quite a bit with
2 Dedicated Cloud SKUs
1 HCM Enterprise SKU
Additional 420 GHz & 2880 GB RAM
Additional 72 TB Basic storage
Additional 72 TB SSD-Accelerated Storage
Bandwidth upgrade to 10 Gbps
12 additional public IP addresses
10 Gbps Direct Connect
Large sized Dedicated DR environment with HDMZ
Support for 1-1000 replicated VMs, with an additional 1000 VMs in the DMZ SID, 200 VMs in their VPC and another 600 in Dedicated cloud, adding up to 2800 VMs in vCloud Air, all of which can be managed via API, scripting and automation
In a model like this the customer has scaled out quite a bit with
2 Dedicated Cloud SKUs
1 HCM Enterprise SKU
Additional 420 GHz & 2880 GB RAM
Additional 72 TB Basic storage
Additional 72 TB SSD-Accelerated Storage
Bandwidth upgrade to 10 Gbps
12 additional public IP addresses
10 Gbps Direct Connect
Large sized Dedicated DR environment with HDMZ
Support for 1-1000 replicated VMs, with an additional 1000 VMs in the DMZ SID, 200 VMs in their VPC and another 600 in Dedicated cloud, adding up to 2800 VMs in vCloud Air, all of which can be managed via API, scripting and automation
In a model like this the customer has scaled out quite a bit with
2 Dedicated Cloud SKUs
1 HCM Enterprise SKU
Additional 420 GHz & 2880 GB RAM
Additional 72 TB Basic storage
Additional 72 TB SSD-Accelerated Storage
Bandwidth upgrade to 10 Gbps
12 additional public IP addresses
10 Gbps Direct Connect
Large sized Dedicated DR environment with HDMZ
Support for 1-1000 replicated VMs, with an additional 1000 VMs in the DMZ SID, 200 VMs in their VPC and another 600 in Dedicated cloud, adding up to 2800 VMs in vCloud Air, all of which can be managed via API, scripting and automation