Persistent data storage for a microservices application

Patent metadata

Field	Value
Publication number	US-10360009-B2
Application number	US-201715462142-A
Country	US
Kind code	B2
Filing date	Mar 17, 2017
Priority date	Mar 17, 2017
Publication date	Jul 23, 2019
Grant date	Jul 23, 2019

Abstract

A device can receive a specification identifying information associated with a stateful microservices application. The device can provide a request for storage information associated with the stateful microservices application based on the information included in the specification. The device can receive the storage information based on providing the request. The device can execute a storage installation procedure to provide the stateful microservices application with a storage volume based on receiving the storage information. The storage volume can be capable of providing persistent data storage. The device can provide a notification that the stateful microservices application is available for deployment on the device based on executing the storage installation procedure.

First claim

What is claimed is:

1. A device in a microservices management platform, comprising:
a memory; and

one or more processors to:
receive, at a client manager or client-side data manager, a specification identifying
information associated with a stateful microservices application;
generate a request for storage information, including a microservices application identifier associated with the stateful microservices application based on the information included in the specification;
provide the request, to a server-side data manager within the microservices management platform, for the storage information associated with the stateful microservices application based on the information included in the specification,
the storage information including information associated with mounting a storage volume, the information including a port identifier associated with a storage node, of a set of storage nodes, to provide data storage for the stateful microservices application and metadata indicating a quantity of data available for storage,
the request to cause the server-side data manager to determine that the stateful microservices application is requesting storage information for a first time by comparing the microservices application identifier with a data structure comprising a plurality of microservices application identifiers,

the server-side data manager obtaining the storage information from the storage node;
receive, from the server-side data manager, the storage information based on providing the request;
execute a storage installation procedure to provide the stateful microservices application with the storage volume based on receiving the storage information,
the storage volume to allow traffic to flow from the device to the storage node; and

provide a notification that the stateful microservices application is available for deployment on the device based on executing the storage installation procedure.

2. The device of claim 1 , where the information included in the specification include at least one of:
a microservices application identifier, a host internet protocol (IP) address,
a value indicating a quantity of data for supporting the stateful microservices application, a file path,
information identifying a storage volume driver, or
a storage location within a container.

3. The device of claim 1 , where the storage information includes at least one of:
an internet protocol (IP) address of the storage node that has been selected to provide storage, or
a storage networking protocol for managing data associated with the storage volume.

4. The device of claim 1 , where the one or more processors are further to:
provide another request for additional storage information to a storage management node, the server-side data manager hosted by the storage management node
the other request to cause the storage management node to determine that the stateful microservices application is deployed on another node and detach the storage volume from the other node based on determining that the stateful microservices application is deployed on the other node; and
receive, from the storage management node, an indication that the storage volume is detached from the other node; and
provide, to the storage management node, a request to attach to the storage volume, the request to attach to cause the storage management node to obtain the storage information.

5. The device of claim 1 , where the one or more processors, when executing the storage installation procedure, are to:
establish a path between the device and the storage node that is hosting the storage volume, and
mount the storage volume based on establishing the path.

6. The device of claim 1 , where the one or more processors, when executing the storage installation procedure, are to:
attach the storage volume to the device,
generate a file system on the storage volume based on attaching the storage volume to the device,
mount the storage volume to an operating system of the device based on generating the file system, and
mount the storage volume to a container of the device based on mounting the storage volume to the operating system of the device.

7. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors in a microservices management platform, cause the one or more processors to:
generate, at a client manager or client-side data manager, a request for storage information, including a microservices application identifier, associated with a stateful microservices application,
provide the request, to a server-side data manager within the microservices managements platform, for the storage information associated with the stateful microservices application based on information included in a specification,
the storage information including information associated with mounting a storage volume, the information including a port identifier associated with a storage node, from a set of storage nodes, to provide data storage for the stateful microservices application and metadata indicating a quantity of data available for storage,
the request to cause a storage management node to obtain the storage information, the request to cause the server-side data manager to determine that the stateful microservices application is requesting storage information for a first time by comparing the microservices application identifier with a data structure comprising a plurality of microservices application identifiers,
the server-side data manager obtaining the storage information from the storage node;

receive, from the storage management node, the storage information based on providing the request;
execute a storage installation procedure to provide the stateful microservices application with storage based on receiving the storage information,
the storage installation procedure to use the storage information to mount the storage volume that is capable of providing persistent data storage;

and provide a notification, to the stateful microservices application, that the storage volume is mounted based on executing the storage installation procedure.

8. The non-transitory computer-readable medium of claim 7 , where the stateful microservices application includes a plugin to allow the stateful microservices application to interact with a client-side data manager, and where the specification includes at least one of:
a microservices application identifier, a host internet protocol (IP) address,
a value indicating a quantity of data for supporting the stateful microservices application,
or a file path.

9. The non-transitory computer-readable medium of claim 7 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
receive an indication that the stateful microservices application has been deployed; receive traffic associated with a client device writing data to the storage volume; determine that the traffic satisfies a threshold;
provide another request, to the storage management node, for additional storage information, the other request to cause the storage management node to obtain additional storage information from the set of storage nodes;
receive, from the storage management node, the additional storage information; and execute another storage installation procedure to attach another storage volume to a device associated with the one or more processors and to mount the other storage volume.

10. The non-transitory computer-readable medium of claim 7 , where the one or more instructions, that cause the one or more processors to provide the request

Assignees

• Verizon Patent & Licensing Inc

Inventors

• Holman Candace
• Apte Aniket
• Jain Kapil
• Chugtu Manish
• Tahir Rehan

Classifications

• G06F9/5011

  the resources being hardware resources other than CPUs, Servers and Terminals · CPC title

• G06F9/5077

  Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title

• G06F8/60 Primary

  Software deployment · CPC title

• G06F8/61 Primary

  Installation · CPC title

• G06F9/5072

  Grid computing · CPC title