HYBRID CLOUDS

• US 20180124158A1
• Filed: 10/28/2016
• Published: 05/03/2018
• Est. Priority Date: 10/28/2016
• Status: Active Grant

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: AMENTO, Brian, HALL, Robert J., JOSHI, Kaustubh, PURDY, Kermit Hal
• Granted Patent: US 10,462,212 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5041 characterised by the time relationship between creation and deployment of a service
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• 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/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• 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/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04W 24/02 Arrangements for optimising operational condition
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

Systems and methods are disclosed for creating and managing hybrid clouds including both standard compute nodes and edge devices. Edge devices can be enrolled in a hybrid cloud by deploying a lightweight container to the edge device.

Claims

1. A method, comprising:

identifying an edge device in network communication with a cloud extension component of a managed hybrid cloud;

deploying a lightweight management container to the edge device, the lightweight management container sharing a common control plane with a standard management container used on a traditional compute node in the managed hybrid cloud; and

enrolling the edge device in the managed hybrid cloud using the lightweight management container.

2. The method of claim 1, further comprising:

receiving a resource request associated with the edge device, the resource request associated with a standard management container before deploying the lightweight management container; and

determining requirements of the resource request, the lightweight management container provides functionality to respond to the resource request without duplicating all modules of the standard management container.

3. The method of claim 1, further comprising:

controlling the edge device using a conductor component associated with the cloud extension component of the managed hybrid cloud; and

controlling the traditional compute node using the conductor component, the conductor component compatible for both edge device control and traditional compute node control.

4. The method of claim 1, the edge device is identified based on a constraint.

5. The method of claim 4, the constraint is one of a geographic location, velocity, acceleration, sensor capability, processing capability, memory capability, or verification of affirmative participation in the managed hybrid cloud.

6. The method of claim 1, further comprising managing communication in the managed hybrid cloud to or from the edge device, communication being transmitted using a long range technique or an ad hoc technique.

7. The method of claim 1, further comprising running an application on an edge device using the lightweight management container.

8. The method of claim 7, the application is distributed among a plurality of edge devices having the lightweight management container.

9. The method of claim 1, the lightweight management container and the standard management container communicate within the managed hybrid cloud using a common messaging protocol.

10. The method of claim 1, further comprising monitoring the edge device for changes using a monitor component.

11. A system, comprising:

a cloud extension component of a managed hybrid cloud, the cloud extension component configured to communicate with edge devices and traditional compute nodes,

the cloud extension component deploys a standard management container to traditional compute nodes,

the cloud extension component deploys a lightweight management container to the edge devices, the lightweight management container sharing a common control plane with the standard management container used on a traditional compute node in the managed hybrid cloud, the lightweight management container enrolls the edge device in the managed hybrid cloud.

12. The system of claim 11, further comprising a conductor component of the cloud extension component, the conductor component controls the edge devices, and the conductor component controls the traditional compute nodes.

13. The system of claim 11, the edge devices communicate in the managed hybrid cloud using a long range technique or an ad hoc technique.

14. The system of claim 11, a cloud application is run on the edge devices using the lightweight management container.

15. The system of claim 11, the lightweight management container and the standard management container communicate using a common messaging protocol.

16. The system of claim 11, further comprising a monitor component that monitors the edge devices for changes.

17. A system comprising a processor and computer readable media storing instructions configured to:

identify an edge device in network communication with a cloud extension component of a managed hybrid cloud;

deploy a lightweight management container to the edge device, the lightweight management container sharing a common control plane with a standard management container used on a traditional compute node in the managed hybrid cloud; and

enroll the edge device in the managed hybrid cloud using the lightweight management container.

18. The system of claim 17, the instructions further configured to:

receive a resource request associated with the edge device, the resource request associated with a standard management container before deploying the lightweight management container; and

determine requirements of the resource request, the lightweight management container provides functionality to respond to the resource request without duplicating all modules of the standard management container.

19. The system of claim 17, the instructions further configured to monitor the edge devices for changes using a monitor component.

20. The system of claim 19, the instructions further configured to identify the edge device based on a constraint, the constraint is monitored as one of the changes.