CONTAINER-BASED CLOUD EXCHANGE DISASTER RECOVERY

• US 20170244593A1
• Filed: 07/29/2016
• Published: 08/24/2017
• Est. Priority Date: 01/22/2016
• Status: Active Grant

• Current Assignee: Equinix Incorporated
• Original Assignee: Equinix Incorporated
• Inventors: Rangasamy, Venkatachalam, Kumar, Parveen, Jeyapaul, Jaganathan, Lillie, Brian J.
• Granted Patent: US 10,892,942 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 2009/4557 Distribution of virtual machine instances; Migration and load balancing
• CPC Class Codes: G06F 2009/45595 Network integration; Enabling network access in virtual machine instances
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/45558 Hypervisor-specific management and integration aspects
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: H04L 12/4679 Arrangements for the registration or de-registration of VLAN attribute values, e.g. VLAN identifiers, port VLAN membership
• CPC Class Codes: H04L 12/4683 characterized by the protocol used
• CPC Class Codes: H04L 41/0654 using network fault recovery ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5045 Making service definitions prior to deployment
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 45/021 Ensuring consistency of routing table updates, e.g. by using epoch numbers
• CPC Class Codes: H04L 61/3015 Name registration, generation or assignment
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/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 Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/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

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.

Claims

1. A method comprising:

detecting, with a cloud exchange, 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;

provisioning, with the cloud exchange, 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 to send and receive data packets via the cloud exchange;

obtaining, with the cloud exchange, code and state from containers of the first cloud service; and

communicating, with the cloud exchange, the code and state to the disaster recovery infrastructure layers in the containers of the second cloud service.

2. The method of claim 1, further comprising:

receiving, with the cloud exchange, cloud service traffic from an enterprise network coupled to the cloud exchange to send and receive data packets via the cloud exchange; and

re-directing, with the cloud exchange, in response to detecting the indication of the disruption in the first cloud service, the cloud service traffic from the containers of the first cloud service to the containers of the second cloud service.

3. The method of claim 1, further comprising:

provisioning, with the cloud exchange, in response to detecting the indication of the disruption in the first cloud service, a disaster recovery infrastructure interface layer for execution by the cloud exchange, in response to detecting the indication of the disruption in the first cloud service;

receiving, with the cloud exchange, a service request from an enterprise network coupled to the cloud exchange to send and receive data packets via the cloud exchange, wherein the service request is addressed to the first cloud service; and

storing, with the cloud exchange, prior to the disaster recovery infrastructure layers in the containers of the second cloud service being operational to handle the service request, the service request.

4. The method of claim 3, further comprising:

sending, with the cloud exchange, in response to determining the disaster recovery infrastructure layers in the containers of the second cloud service are operational to handle the service request, the service request to the second cloud service.

5. The method of claim 1, further comprising:

selecting, with the cloud exchange, the second cloud service from among a plurality of available cloud services to host the disaster recovery infrastructure layers, prior to provisioning the disaster recovery infrastructure layers in the containers of the second cloud service.

6. The method of claim 1, wherein provisioning the disaster recovery infrastructure interface layer and provisioning the disaster recovery infrastructure layers are performed by a disaster recovery manager of the orchestration engine.

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

8. The method of claim 1, further comprising provisioning, in a networking platform of the cloud exchange, a virtual circuit to transport data packets between the containers of the first cloud service and the containers of the second cloud service.

9. The method of claim 8, further comprising communicating, with the cloud exchange, the code and state from the containers of the first cloud service to the containers of the disaster recovery infrastructure layers of the second cloud service via the virtual circuit.

10. The method of claim 1, further comprising:

placing a hold on operations of one or more of the containers of the first cloud service prior to obtaining the code and 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 state to the disaster recovery infrastructure layers in the containers of the second cloud service.

11. The method of claim 10, wherein placing the hold on the operations of the one or more of the containers of the first cloud service comprises locking state stored to an in-memory data store at the first cloud service.

12. The method of claim 1, wherein the state from containers of the first cloud service comprises one or more of:

application data, application stack configuration data, microservices state, memory data, commands, process information, and instruction pointers.

13. The method of claim 1, wherein the code comprises executable instruction code for one or more of:

applications, application specific libraries, microservices, and microservice specific libraries.

14. The method of claim 1, wherein copying the state from the containers in the first cloud service is performed while the containers in the first cloud service are executing one or more applications.

15. The method of claim 1, wherein detecting the indication of the disruption in the first cloud service comprises detecting an indication of a qualifying disruption in accordance with disaster recovery configuration settings selected via user inputs to the cloud exchange.

16. The method of claim 15, wherein the disaster recovery configuration settings comprise:

criteria to define disruptions in the first cloud service that qualify as the qualifying disruption; and

criteria for selecting the second cloud service.

17. The method of claim 15, further comprising providing, with the cloud exchange, an interface for receiving the user inputs to select the disaster recovery configuration settings.

18. The method of claim 1, further comprising:

associating, with the cloud exchange, a container identifier and a network address of a first container of the first cloud service with a container identifier and a network address of a second container of the disaster recovery infrastructure layer; and

communicating code and state from the first container to the second container based on the association.

19. The method of claim 1, further comprising:

placing a hold on service requests to the containers of the first cloud service, subsequent to detecting the indication of the disruption in the first cloud service; and

re-directing the service requests to the disaster recovery infrastructure layers in the containers of the second cloud service, subsequent to the code and state being communicated to the disaster recovery infrastructure layers.

20. The method of claim 1, further comprising updating, in a routing table of the orchestration engine, routes to the containers of the first cloud service with routes to the containers of the disaster recovery infrastructure layers, subsequent to communicating the code and state to the disaster recovery infrastructure layers in the containers of the second cloud service.

21. A computing system comprising:

at least one processor operably coupled to a memory; and

an orchestration engine for a cloud exchange, the orchestration engine configured for execution by the at least one processor, wherein the orchestration engine 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 to send and receive data packets via 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.

22. A computer-readable medium comprising instructions for causing at least one programmable processor of a cloud exchange 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 to send and receive data packets via 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.