Systems and methods for proactively and reactively allocating resources in cloud-based networks
US-2018302340-A1 · Oct 18, 2018 · US
US10846079B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10846079-B2 |
| Application number | US-201816191377-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 14, 2018 |
| Priority date | Nov 14, 2018 |
| Publication date | Nov 24, 2020 |
| Grant date | Nov 24, 2020 |
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.
Systems and method for expanding a cluster with nodes before an upgrade so that the cluster can handle a failover event during an upgrade and still continue operating. The system and method includes receiving, at a processor, a signal indicating a cluster is about to commence an upgrade; computing, by the processor, a first number of nodes; adding, by the processor, the first number of nodes from a network to the cluster before the upgrade is performed on the cluster; receiving, at the processor, a signal indicating the cluster finished the upgrade; and removing a second number of nodes that is no greater than the first number of nodes from the cluster after the processor receives the signal indicating the upgrade is complete.
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, by a processor that executes computer-readable instructions stored on a memory, a first signal indicating a disaster recovery cluster is about to commence an upgrade; upon receiving the first signal, determining, by the processor, a total amount of computing resource needed by the disaster recovery cluster to receive migrated entities from a second cluster during the upgrade, wherein determining the total amount of the computing resource comprises: determining, by the processor, a number of the entities of the second cluster to be migrated to the disaster recovery cluster during the upgrade; identifying, by the processor, which of the number of the entities require a maximum amount of the computing resource; computing, by the processor, an initial computing resource requirement by aggregating the maximum amount of the computing resource of each of the number of the entities requiring the maximum amount of the computing resource; and determining, by the processor, the total amount of the computing resource based on the initial computing resource requirement; adding, by the processor, a first number of compute only nodes to the disaster recovery cluster before the upgrade, wherein adding the first number of the compute only nodes comprises: comparing, by the processor, the total amount of the computing resource with an available amount of the computing resource at the disaster recovery cluster to determine an extra amount of the computing resource needed by the disaster recovery cluster to satisfy the total amount of the computing resource; determining, by the processor, the available amount of the computing resource at each compute only node; and adding, by the processor, the first number of the compute only nodes to the disaster recovery cluster based upon the available amount of the computing resource at each compute only node to satisfy the extra amount of the computing resource; receiving, by the processor, a second signal indicating the upgrade of the disaster recovery cluster is complete; and removing, by the processor, a second number of the compute only nodes from the disaster recovery cluster upon receiving the second signal, wherein removing the second number of the compute only node comprises: identifying, by the processor, which ones of the first number of the compute only nodes added to the disaster recovery cluster are dormant; and removing, by the processor, the dormant ones of the compute only nodes. 2. The method of claim 1 , further comprising adding, by the processor, an additional computing resource requirement to the initial computing resource requirement to obtain the total amount of the computing resource. 3. The method of claim 1 , wherein the second number of nodes is no greater than the first number of nodes. 4. The method of claim 1 , further comprising determining that the compute only nodes are insufficient to satisfy the extra amount of the computing resource. 5. The method of claim 4 , further comprising adding at least one node with storage upon determining that the compute only nodes are insufficient to satisfy the extra amount of the computing resource. 6. The method of claim 1 , wherein determining the number of the entities comprises multiplying a percentage by a total number of the entities in the second cluster. 7. The method of claim 1 , wherein the computing resource comprises at least one of amount of memory or central processing unit core resources. 8. The method of claim 7 , wherein the total amount of the computing resource needed by the disaster recovery cluster comprises a first total amount of the memory needed by the disaster recovery cluster and a second total amount of the central processing unit core resources needed by the disaster recovery cluster. 9. The method of claim 8 , wherein the first number of nodes comprises enough number of nodes to satisfy the first total amount of the memory as well as the second total amount of the central processing unit core resources. 10. The method of claim 1 , wherein identifying the dormant ones of the compute only nodes comprises identifying the compute only nodes that are not in use. 11. A system comprising: a processor that executes computer-readable instructions stored on a memory to: receive a first signal indicating a disaster recovery cluster is about to commence an upgrade; upon receiving the first signal, determine a total amount of computing resource needed by the disaster recovery cluster to receive migrated entities from a second cluster during the upgrade, wherein to determine the total amount of the computing resource, the processor: determines a number of the entities of the second cluster to be migrated to the disaster recovery cluster during the upgrade; identifies which of the number of the entities require a maximum amount of the computing resource; computes an initial computing resource requirement by aggregating the maximum amount of the computing resource of each of the number of the entities that require the maximum amount of the computing resource; and determines the total amount of the computing resource based on the initial computing resource requirement; add a first number of compute only nodes to the disaster recovery cluster before the upgrade, wherein to add the first number of the compute only nodes, the processor: determines an available amount of the computing resource at the disaster recovery cluster; compares the total amount of the computing resource with the available amount of the computing resource to determine an extra amount of the computing resource needed by the disaster recovery cluster to satisfy the total amount of the computing resource; determines the available amount of the computing resource at each compute only node; and adds the first number of the compute only nodes to the disaster recovery cluster based upon the available amount of the computing resource at each compute only node to satisfy the extra amount of the computing resource; receive a second signal indicating the upgrade of the disaster recovery cluster is complete; and remove a second number of the compute only nodes from the disaster recovery cluster upon receiving the second signal, wherein to remove the second number of the compute only node, the processor: identifies which ones of the first number of compute only nodes added to the disaster recovery cluster are dormant; and removes the dormant ones of the compute only nodes. 12. The system of claim 11 , wherein the processor further executes the computer-readable instructions to determine that the compute only nodes are insufficient to satisfy the extra amount of the computing resource. 13. The system of claim 12 , wherein the processor executes the computer-readable instructions to add at least one node with storage upon determining that the compute only nodes are insufficient to satisfy the extra amount of the computing resource. 14. The system of claim 11 , wherein the processor executes the computer-readable instructions to determine the number of the entities by multiplying a percentage by a total number of the entities in the second cluster. 15. The system of claim 11 , wherein the computing resource comprises at least one of memory or central processing unit core resource. 16. The system of claim 11 , wherein to identify the dormant ones of the compute only nodes, the processor executes the computer-readable instructions to identify the compute only nodes that are not in use. 17. A non-transitory computer readable media compr
where the redundant components share neither address space nor persistent storage · CPC title
Network integration; Enabling network access in virtual machine instances · CPC title
without idle spare hardware · CPC title
Updates (security arrangements therefor G06F21/57) · CPC title
Responding to the occurrence of a fault, e.g. fault tolerance · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.