Deploying and managing containers to provide a highly available distributed file system

• US 10,341,438 B2
• Filed: 03/17/2017
• Issued: 07/02/2019
• Est. Priority Date: 03/17/2017
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Inventors: Jain, Kapil, Chugtu, Manish, Mukherjee, Subhajit
• Primary Examiner(s): Hussain, Tauqir
• Assistant Examiner(s): Grijalva Lobos, Boris D
• Application Number:
  US15/462,153
• Publication Number:
  US 20180270125A1
• Time in Patent Office: 837 Days
• CPC Class Codes: G06F 11/07 Responding to the occurrence of a fault, e.g. fault tolerance
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• 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/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/122 of virtualised topologies, e.g. software-defined networks [SDN] or network function virtualisation [NFV]
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• 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]

Abstract

A device can receive information indicating a set of instructions associated with a microservices application, where the microservices application is associated with one or more microservices. The device can generate a deployment specification. The device can deploy one or more containers and one or more replicate containers. The one or more containers and the one or more replicate containers are associated with the one or more microservices. The one or more containers and the one or more replicate containers can be associated with a distributed file system. The device can receive information associated with modifying the one or more microservices. The device can modify the one or more microservices, as one or more modified microservices, based on receiving the information associated with modifying the one or more microservices. The device can deploy the one or more modified microservices.

Claims

1. A device, comprising:

one or more processors, implemented at least partially in hardware, to;

receive information indicating a set of instructions associated with a microservices application,

the microservices application being associated with one or more microservices;

generate a deployment specification based on receiving the information indicating the set of instructions;

deploy one or more containers and one or more replicate containers based on generating the deployment specification,

the one or more containers and the one or more replicate containers being associated with the one or more microservices, and

the one or more containers and the one or more replicate containers being associated with a distributed file system;

provide an instruction to one or more computing nodes that are associated with the one or more replicate containers,

the instruction causing the one or more replicate containers to manage traffic flow associated with the one or more microservices, and

the instruction causing the one or more replicate containers to synchronize to the one or more containers to provide the one or more containers with metadata and data associated with the traffic flow;

receive information associated with modifying the one or more microservices based on deploying the one or more containers and the one or more replicate containers;

modify the one or more microservices, as one or more modified microservices, based on receiving the information associated with modifying the one or more microservices; and

deploy the one or more modified microservices.

2. The device of claim 1, where the one or more processors, when deploying the one or more containers and the one or more replicate containers, are to:

determine information relating to a network topology, and

deploy the one or more containers and the one or more replicate containers based on the information relating to the network topology.

3. The device of claim 1, where the one or more processors, when deploying the one or more containers and the one or more replicate containers, are to:

deploy the one or more containers in a first fault zone, and

deploy the one or more replicate containers in one or more second fault zones that are different than the first fault zone.

4. The device of claim 1, where the one or more processors, when receiving information associated with modifying the one or more microservices, are to:

receive, from a computing node that hosts a microservice of the one or more microservices, information indicating a result of a health check,

the result of the health check identifying a performance issue associated with the microservice; and

where the one or more processors, when modifying the one or more microservices, are to;

modify the microservice, of the one or more microservices, to resolve the performance issue identified by the information indicating the result of the health check.

5. The device of claim 1, where the one or more processors, when receiving the information associated with modifying the one or more microservices, are to:

receive a request to upgrade a microservice of the one or more of microservices; and

where the one or more processors, when modifying the one or more microservices, are to;

obtain a first container associated with hosting the upgraded microservice,

shut down a second container associated with the microservice based on obtaining the first container, and

deploy the first container based on shutting down the second container.

6. The device of claim 1, where the one or more processors, when receiving the information associated with modifying the one or more microservices, are to:

receive a request to downgrade a microservice of the one or more microservices; and

where the one or more processors, when modifying the one or more microservices, are to;

obtain a first container associated with hosting the downgraded microservice,

shut down a second container associated with the microservice based on obtaining the first container, and

deploy the first container based on shutting down the second container.

7. The device of claim 1, where the one or more processors, when receiving the information associated with modifying the one or more microservices, are to:

receive information associated with adding an amount of capacity available for a microservice of the one or more microservices; and

where the one or more processors, when modifying the one or more microservices, are to;

obtain one or more additional containers and one or more additional replicate containers,

apply a load balancing technique to the one or more containers, the one or more replicate containers, the one or more additional containers, and the one or more additional replicate containers to balance a distribution of resources, and

deploy the one or more additional containers and the one or more additional replicate containers based on applying the load balancing technique.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors implemented at least partially in hardware, cause the one or more processors to;

determine to host a microservices application,

the microservices application being associated with one or more microservices;

deploy one or more containers and one or more replicate containers based on determining to host the microservices application,

the one or more containers and the one or more replicate containers being associated with a distributed file system, and

the one or more containers to be deployed in a first fault zone and the one or more replicate containers to be deployed in one or more second fault zones that are different than the first fault zone;

provide an instruction, to one or more computing nodes that are associated with the one or more replicate containers,

the instruction causing the one or more replicate containers to manage traffic flow associated with the one or more microservices, and

the instruction causing the one or more replicate containers to synchronize to the one or more containers to provide the one or more containers with metadata and data associated with the traffic flow;

receive information associated with modifying the one or more microservices after deploying the one or more containers and the one or more replicate containers;

modify the one or more microservices, as one or more modified microservices, based on receiving information associated with modifying the one or more microservices; and

deploy the one or more modified microservices.

9. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive the information associated with modifying the one or more microservices, cause the one or more processors to:

receive a request to upgrade the one or more microservices; and

where the one or more instructions, that cause the one or more processors to modify the one or more microservices, cause the one or more processors to;

obtain one or more first containers associated with hosting the one or more microservices,

shut down one or more second containers that are associated with the one or more microservices based on obtaining the one or more first containers, and

deploy the one or more first containers based on shutting down the one or more second containers.

10. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive the information associated with modifying the one or more microservices, cause the one or more processors to:

receive information associated with downgrading the one or more microservices; and

where the one or more instructions, that cause the one or more processors to modify the one or more microservices, cause the one or more processors to;

obtain one or more different containers associated with hosting the one or more microservices,

shut down the one or more containers that are associated with the one or more microservices based on obtaining the one or more different containers, and

deploy the one or more different containers based on shutting down the one or more containers.

11. The non-transitory computer-readable medium of claim 10, where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:

provide an instruction to one or more computing nodes that are associated with the one or more replicate containers,

the instruction to cause the one or more replicate containers to manage traffic flow associated with the one or more microservices,

the instruction to cause the one or more replicate containers to synchronize to the one or more different containers to provide the one or more different containers with information associated with the traffic flow.

12. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive information associated with modifying the one or more microservices, cause the one or more processors to:

receive information associated with adding an amount of capacity available for a different microservice,

the different microservice being separate from the one or more microservices; and

where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to;

obtain one or more different containers and one or more different replicate containers;

apply a load balancing technique to the one or more containers, the one or more replicate containers, the one or more different containers, and the one or more different replicate containers to balance a distribution of resources; and

deploy the one or more different containers and the one or more different replicate containers based on applying the load balancing technique.

13. The non-transitory computer-readable medium of claim 8, where the one or more instructions, that cause the one or more processors to receive the information associated with modifying the one or more microservices, cause the one or more processors to:

receive a request to deploy one or more additional replicate containers at a first geographic location that is different than a second geographic location associated with the one or more containers and the one or more replicate containers; and

where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to;

deploy the one or more additional replicate containers at the first geographic location.

14. A method, comprising:

receiving, by a device, information indicating a set of instructions associated with a microservices application,

the microservices application being associated with one or more microservices;

determining, by the device, information relating to a network topology;

deploying, by the device, one or more containers and one or more replicate containers based on the information indicating the set of instructions associated with the microservices application and based on determining the information relating to the network topology,

the one or more containers and the one or more replicate containers being associated with a distributed file system that provides data storage for the one or more microservices;

providing an instruction, by the device, to one or more computing nodes that are associated with the one or more replicate containers,

the instruction causing the one or more replicate containers to manage traffic flow associated with the one or more microservices, and

the instruction causing the one or more replicate containers to synchronize to the one or more containers to provide the one or more containers with metadata and data associated with the traffic flow;

determining, by the device, to modify one or more microservices based on deploying the one or more containers and the one or more replicate containers;

modifying, by the device, the one or more microservices, as one or more modified microservices, based on determining to modify the one or more microservices; and

deploying, by the device, the one or more modified microservices.

15. The method of claim 14, where deploying the one or more containers and the one or more replicate containers comprises:

deploying the one or more containers in a first fault zone, and

deploying the one or more replicate containers in one or more second fault zones that are different than the first fault zone.

16. The method of claim 14, where determining to modify the one or more microservices comprises:

determining to upgrade a first microservice of the one or more microservices, and

determining to downgrade a second microservice of the one or more microservices; and

where modifying the one or more microservices comprises;

obtaining a first set of containers associated with hosting the upgraded first microservice and a second set of containers associated with hosting the downgraded second microservice,

shutting down a subset of the one or more containers that are associated with the first microservice and shutting down another subset of the one or more containers that are associated with the second microservice based on obtaining the first set of containers and the second set of containers, and

deploying the first set of containers and the second set of containers based on shutting down the subset of the one or more containers associated with the first microservice and the other subset of the one or more containers associated with the second microservice.

17. The method of claim 16, further comprising:

providing, to a subset of the one or more replicate containers that are associated with the first microservice, an instruction to manage traffic flow associated with the first microservice,

the instruction to cause the subset of the one or more replicate containers to manage the traffic flow associated with the first microservice, and

the instruction to cause the subset of the one or more replicate containers to provide the first set of containers with information associated with the traffic flow; and

providing, to another subset of the one or more replicate containers that are associated with the second microservice, a different instruction to manage traffic flow associated with the second microservice,

the different instruction to cause the other subset of the one or more replicate containers to manage the traffic flow associated with the second microservice, and

the different instruction to cause the other subset of the one or more replicate containers to provide the second set of containers with information associated with the traffic flow.

18. The method of claim 14, where determining to modify the one or more microservices comprises:

receiving information associated with adding an amount of capacity available for a microservice of the one or more microservices; and

where modifying the one or more microservices comprises;

obtaining one or more additional containers and one or more additional replicate containers,

applying a load balancing technique to at least one of the one or more containers, the one or more replicate containers, the one or more additional containers, or the one or more additional replicate containers to balance a distribution of network resources, and

deploying the one or more additional containers and the one or more additional replicate containers based on applying the load balancing technique.

19. The method of claim 14, where determining to modify the one or more microservices comprises:

receiving information associated with adding an amount of capacity available for a first microservice, of the one or more microservices; and

where modifying the one or more microservices comprises;

shutting down a first container, and a first replicate container,

the first container and the first replicate container being associated with a second microservice, of the one or more microservices, and

applying a load balancing technique to reallocate resources associated with the second microservice to the first microservice.

20. The method of claim 14, further comprising:

receiving a request to deploy one or more additional replicate containers at a geographic location that is different than the geographic location associated with the one or more containers and the one or more replicate containers; and

providing the one or more additional replicate containers to another device associated with a different distributed file system.