Persistent data storage for a microservices application
US-10360009-B2 · Jul 23, 2019 · US
US11513865B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11513865-B2 |
| Application number | US-202017035219-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 28, 2020 |
| Priority date | Jun 30, 2017 |
| Publication date | Nov 29, 2022 |
| Grant date | Nov 29, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Methods and apparatus are disclosed to deploying a distributed system using operating system or container virtualization. An example apparatus includes a management container including a configuration manager and a container manager. The example configuration manager to is receive an instruction for a desired deployment state and is to apply a first change to a first current deployment state of the management container based on the desired deployment state. The example container manager is to apply a second change to a second current deployment state of a deployed container based on the desired deployment state. The container manager is to return information indicative of the desired deployment state to the configuration manager when the second change from the second current deployment state to the desired deployment state is achieved.
Opening claim text (preview).
What is claimed is: 1. A method comprising: a) when a desired deployment state of a container is not equal to a current deployment state of the container, applying, by a configuration manager upon a trigger to interact with a container manager, a first change to the current deployment state of the configuration manager and the container manager of the container to form an updated deployment state, wherein the configuration manager and the container manager are both located in the container; b) executing, by the container manager, a first command in the container to adjust the container in the updated deployment state; c) evaluating, by at least one of the container manager or the configuration manager, the updated deployment state with respect to the desired deployment state; and d) repeating a)-c) until the desired deployment state of the container is equal to the updated deployment state of the container. 2. The method of claim 1 , wherein the first command is a lifecycle command, and further including executing, by the container manager, the first command with respect to the container in a container host environment. 3. The method of claim 1 , further including determining, using the configuration manager, a runtime environment based on applying the first change. 4. The method of claim 3 , further including triggering execution of the first command based on the runtime environment. 5. The method of claim 4 , further including reporting runtime information to the container manager. 6. The method of claim 1 , further including triggering, by a browser, an instruction for the desired deployment state. 7. The method of claim 1 , wherein the container includes a first container, and further including executing a second command with respect to a second container. 8. A tangible computer readable storage medium comprising instructions which, when executed, cause at least one processor to at least: a) when a desired deployment state of a container is not equal to a current deployment state of the container, applying, by a configuration manager upon a trigger to interact with a container manager, a first change to the current deployment state of the configuration manager and the container manager of the container to form an updated deployment state, wherein the configuration manager and the container manager are both located in the container; b) executing, by the container manager, a first command in the container to adjust the container in the updated deployment state; c) evaluating, by at least one of the container manager or the configuration manager, the updated deployment state with respect to the desired deployment state; and d) repeating a)-c) until the desired deployment state of the container is equal to the updated deployment state of the container, the updated deployment state forming a runtime environment for execution of additional commands in the container. 9. The computer readable storage medium of claim 8 , wherein the first command is a lifecycle command, and wherein the instructions, when executed, further cause the at least one processor to trigger executing, by the container manager, the first command with respect to the container in a container host environment. 10. The computer readable storage medium of claim 8 , wherein the instructions, when executed, further cause the at least one processor to trigger determining, using the configuration manager, a runtime environment based on applying the first change. 11. The computer readable storage medium of claim 10 , wherein the instructions, when executed, further cause the at least one processor to trigger execution of the first command based on the runtime environment. 12. The computer readable storage medium of claim 11 , wherein the instructions, when executed, further cause the at least one processor to trigger reporting runtime information to the container manager. 13. The computer readable storage medium of claim 8 , wherein the instructions, when executed, further cause the at least one processor to trigger, by a browser, the desired deployment state. 14. The computer readable storage medium of claim 8 , wherein the container includes a first container, and wherein the instructions, when executed, further cause the at least one processor to trigger executing a second command with respect to a second container. 15. An apparatus comprising: memory to store instructions; and at least one processor to execute the instructions to at least: a) when a desired deployment state of a container is not equal to a current deployment state of the container, applying, by a configuration manager upon a trigger to interact with a container manager, a first change to the current deployment state of the configuration manager and the container manager of the container to form an updated deployment state, wherein the configuration manager and the container manager are both located in the container; b) executing, by the container manager, a first command in the container to adjust the container in the updated deployment state; c) evaluating, by at least one of the container manager or the configuration manager, the updated deployment state with respect to the desired deployment state; and d) repeating a)-c) until the desired deployment state of the container is equal to the updated deployment state of the container. 16. The apparatus of claim 15 , wherein the at least one processor is to trigger determining, using the configuration manager, a runtime environment based on applying the first change. 17. The apparatus of claim 16 , wherein the at least one processor is to trigger execution of the first command based on the runtime environment. 18. The apparatus of claim 17 , wherein the at least one processor is to trigger reporting runtime information to the container manager. 19. The apparatus of claim 15 , further including a browser to trigger the desired deployment state. 20. The apparatus of claim 15 , wherein the container includes a first container, and wherein the at least one processor is to trigger executing a second command with respect to a second container.
Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements · CPC title
Policy-based network configuration management · CPC title
characterised by the conditions triggering a change of settings · CPC title
considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration (scheduling strategies G06F9/4881 and subgroups) · CPC title
the resource being a machine, e.g. CPUs, Servers, Terminals · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.