Container-based cloud exchange disaster recovery

Patent metadata

Field	Value
Publication number	US-10892942-B2
Application number	US-201615223740-A
Country	US
Kind code	B2
Filing date	Jul 29, 2016
Priority date	Jan 22, 2016
Publication date	Jan 12, 2021
Grant date	Jan 12, 2021

Abstract

In general, this disclosure describes techniques for coordinating, with a cloud exchange, automated cloud-based disaster recovery across containers from a failed cloud service to a backup cloud service. In some examples, an orchestration engine for a cloud exchange is configured to: detect an indication of a disruption in a first cloud service provided by a first cloud service provider network coupled to the cloud exchange to send and receive data packets via the cloud exchange; provision, in response to detecting the indication of the disruption in the first cloud service, disaster recovery infrastructure layers in containers of a second cloud service provided by a second cloud service provider network coupled to the cloud exchange; obtain code and state from containers of the first cloud service; and communicate the code and state to the disaster recovery infrastructure layers in the containers of the second cloud service.

First claim

What is claimed is:

1. A method comprising:
configuring, by a cloud exchange and in an orchestration engine executed by the cloud exchange, a disaster recovery infrastructure interface layer for an enterprise network coupled to the cloud exchange;
provisioning, by the cloud exchange and in a networking platform of the cloud exchange, a first virtual circuit between the enterprise network and a first cloud service provided by a first cloud service provider network of a plurality of cloud service provider networks coupled to the cloud exchange, wherein the first virtual circuit is configured to transport, via the cloud exchange, data packets between the enterprise network and containers of the first cloud service provided by the first cloud service provider network, and wherein the cloud exchange logically isolates each of the plurality of cloud service provider networks from one another;
provisioning, by the cloud exchange and in the networking platform of the cloud exchange, a second virtual circuit between the enterprise network and a second cloud service provided by a second cloud service provider network of the plurality of cloud service provider networks coupled to the cloud exchange, wherein the second virtual circuit is configured to transport, via the cloud exchange, data packets between the enterprise network and containers of the second cloud service provided by the second cloud service provider network;
receiving, with the cloud exchange and over the first virtual circuit, a service request from the enterprise network and addressed to one of the containers of the first cloud service of the first cloud service provider network;
detecting, with the cloud exchange, an indication of a disruption in the first cloud service provided by the first cloud service provider network; and

in response to detecting the indication of the disruption in the first cloud service:
re-directing, with the cloud exchange, the service request from the enterprise network to the disaster recovery infrastructure interface layer;
provisioning, with the disaster recovery infrastructure interface layer, disaster recovery infrastructure compute layers in the containers of the second cloud service provided by the second cloud service provider network, wherein the disaster recovery infrastructure compute layers in the containers of the second cloud service replicate a network topology of the containers of the first cloud service;
obtaining, with the disaster recovery infrastructure interface layer, code for the first cloud service and state for the first cloud service from the containers of the first cloud service;
communicating, with the disaster recovery infrastructure interface layer, the code and the state for the first cloud service to the disaster recovery infrastructure compute layers in the containers of the second cloud service;
storing, with the disaster recovery infrastructure interface layer and prior to the disaster recovery infrastructure compute layers in the containers of the second cloud service being operational to handle the service request, the service request; and
sending, with the disaster recovery infrastructure interface layer and after the disaster recovery infrastructure compute layers are operational to handle the service request, the service request to the containers of the second cloud service via the second virtual circuit.

2. The method of claim 1 , wherein sending, after the disaster recovery infrastructure compute layers are operational to handle the service request, the service request to the containers of the second cloud service comprises:
determining, by the disaster recovery infrastructure interface layer, that the disaster recovery infrastructure compute layers in the containers of the second cloud service are operational to handle the service request; and
sending, with the disaster recovery infrastructure interface layer and in response to determining the disaster recovery infrastructure compute layers in the containers of the second cloud service are operational to handle the service request, the service request.

3. The method of claim 1 , further comprising: selecting, with the cloud exchange, the second cloud service provided by the second cloud service provider network from among a plurality of available cloud services provided by the plurality of cloud service provider networks to host the disaster recovery infrastructure compute layers, prior to provisioning the disaster recovery infrastructure compute layers in the containers of the second cloud service.

4. The method of claim 1 , wherein provisioning the disaster recovery infrastructure compute layers in the containers of the second cloud service of the second cloud service provider network comprises provisioning, by a disaster recovery manager of the orchestration engine executed by the cloud exchange, the disaster recovery infrastructure compute layers in the containers of the second cloud service of the second cloud service provider network.

5. The method of claim 1 , wherein provisioning the disaster recovery infrastructure compute layers comprises provisioning an interface layer, a storage layer, a compute layer, and a network layer in the containers of the second cloud service, wherein the interface layer, the storage layer, the compute layer, and the network layer in the containers of the second cloud service replicate an interface layer, a storage layer, a compute layer, and a network layer in the containers of the first cloud service.

6. The method of claim 1 , further comprising provisioning, by the cloud exchange and in a networking platform of the cloud exchange, a third virtual circuit between the first cloud service provided by the first cloud service provider network and the second cloud service provided by the second cloud service provider network, wherein the third virtual circuit is configured to transport data packets between the containers of the first cloud service and the containers of the second cloud service.

7. The method of claim 6 ,
wherein obtaining the code for the first cloud service and the state for the first cloud service from the containers of the first cloud service comprises receiving, by the cloud exchange and from the containers of the first cloud service provided by the first cloud service provider network via the third virtual circuit, the code for the first cloud service and the state for the first cloud service, and
wherein communicating, with the disaster recovery infrastructure interface layer, the code and the state for the first cloud service to the disaster recovery infrastructure compute layers in the containers of the disaster recovery infrastructure compute layers of the second cloud service comprises transmitting, by the disaster recovery infrastructure interface layer and to the containers of the second cloud service provided by the second cloud service provider network via the third virtual circuit, the code and the state for the first cloud service.

8. The method of claim 1 , further comprising:
in response to detecting the indication of the disruption in the first cloud service, placing a hold on operations of one or more of the containers of the first cloud service prior to obtaining the code and the state from the containers of the first cloud service; and
re-starting the operations from the one or more of the containers of the first cloud service in the containers of the second cloud service subsequent to communicating the code and the state for the first cloud service to the disaster recovery infrastructure compute layers in the containers of the second cloud service.

9. The method of claim 8 , wherein placing the hold on the operations of the one or more of the containers of the first cloud s

Assignees

• Equinix Inc

Inventors

• Rangasamy Venkatachalam
• Kumar Parveen
• Jeyapaul Jaganathan
• Lillie Brian J

Classifications

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• H04L67/1095

  Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• H04L67/02

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title