Cluster capacity management for hyper converged infrastructure updates
Abstract
Disclosed are various implementations of cluster capacity management for infrastructure updates. In some examples, cluster hosts for a cluster can be scheduled for an update. A datacenter level workload can invoke an enter cluster maintenance mode component of a datacenter level resource scheduler by identifying a specified cluster of a datacenter. The datacenter level workload can receive an add host command to add a host for the host level update. Once the host level update is performed on hosts of the specified cluster, the datacenter level workload invokes an exit cluster maintenance mode component and implements a cluster scaling decision.
Claims
exact text as granted — not AI-modifiedWhat is claimed is :
1 . A system, comprising:
at least one computing device comprising at least one processor; instructions stored in at least one memory, wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
invoke, by the datacenter level workload, an enter cluster maintenance mode component of the datacenter level resource scheduler using a parameter that identifies a particular cluster of a plurality of clusters of a datacenter;
receive, by the datacenter level workload from a datacenter level resource scheduler, an add host command that causes the datacenter level workload to add a host for a host level update;
perform, by the datacenter level workload, the host level update on a plurality of hosts corresponding to the particular cluster;
invoke, by the datacenter level workload, an exit cluster maintenance mode component of the datacenter level resource scheduler using a parameter that identifies the particular cluster; and
implement, by the datacenter level workload, a cluster scaling decision comprising one of: a scale out decision to increase a total number of hosts in the specified cluster, or a cluster ready decision.
2 . The system of claim 1 , wherein the update command comprises instructions to block datacenter level functionalities and cluster level functionalities that interfere with the schedule of updates prior to performing the update.
3 . The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by the datacenter level workload from the datacenter level resource scheduler, a datacenter update command that specifies the update for a plurality of clusters of the datacenter.
4 . The system of claim 1 , wherein the enter cluster maintenance mode component is invoked based at least in part on the datacenter update command.
5 . The system of claim 1 , wherein the host level update comprises a firmware update.
6 . The system of claim 1 , wherein the enter cluster maintenance mode component corresponds to an enter cluster maintenance mode application programming interface (API), and the exit cluster maintenance mode component corresponds to an exit cluster maintenance mode API.
7 . The system of claim 1 , wherein the datacenter level workload performs the host level update for a plurality of hosts of the specified cluster, and iteratively performs the host level update for a respective plurality of hosts of a respective one of the plurality of clusters of the datacenter.
8 . A method comprising:
invoking, by the datacenter level workload, an enter cluster maintenance mode component of the datacenter level resource scheduler using a parameter that identifies a particular cluster of a plurality of clusters of a datacenter; receiving by the datacenter level workload from a datacenter level resource scheduler, an add host command that causes the datacenter level workload to add a host for a host level update; performing, by the datacenter level workload, a host level update on a plurality of hosts corresponding to the particular cluster; invoking, by the datacenter level workload, an exit cluster maintenance mode component of the datacenter level resource scheduler using a parameter that identifies the particular cluster; and implementing, by the datacenter level workload, a cluster scaling decision comprising one of: a scale out decision to increase a total number of hosts in the specified cluster, or a cluster ready decision.
9 . The method of claim 8 , wherein the update command comprises instructions to block datacenter level functionalities and cluster level functionalities that interfere with the schedule of updates prior to performing the update.
10 . The method of claim 8 , further comprising:
receiving, by the datacenter level workload from the datacenter level resource scheduler, a datacenter update command that specifies the update for a plurality of clusters of the datacenter.
11 . The method of claim 8 , wherein the enter cluster maintenance mode component is invoked based at least in part on the datacenter update command.
12 . The method of claim 8 , wherein the host level update comprises a firmware update.
13 . The method of claim 8 , wherein the enter cluster maintenance mode component corresponds to an enter cluster maintenance mode application programming interface (API), and the exit cluster maintenance mode component corresponds to an exit cluster maintenance mode API.
14 . The method of claim 8 , wherein the datacenter level workload performs the host level update for a plurality of hosts of the specified cluster, and iteratively performs the host level update for a respective plurality of hosts of a respective one of the plurality of clusters of the datacenter.
15 . A non-transitory computer-readable medium comprising machine readable instructions, wherein the instructions, when executed by at least one processor, cause at least one computing device to at least:
invoke, by the datacenter level workload, an enter cluster maintenance mode component of the datacenter level resource scheduler using a parameter that identifies a particular cluster of a plurality of clusters of a datacenter; receive, by the datacenter level workload from a datacenter level resource scheduler, an add host command that causes the datacenter level workload to add a host for a host level update; perform, by the datacenter level workload, a host level update on a plurality of hosts corresponding to the particular cluster; invoke, by the datacenter level workload, an exit cluster maintenance mode component of the datacenter level resource scheduler using a parameter that identifies the particular cluster; and implement, by the datacenter level workload, a cluster scaling decision comprising one of: a scale out decision to increase a total number of hosts in the specified cluster, or a cluster ready decision.
16 . The non-transitory computer-readable medium of claim 15 , wherein the update command comprises instructions to block datacenter level functionalities and cluster level functionalities that interfere with the schedule of updates prior to performing the update.
17 . The non-transitory computer-readable medium of claim 15 , wherein the instructions, when executed by the at least one processor, cause the at least one computing device to at least:
receive, by the datacenter level workload from the datacenter level resource scheduler, a datacenter update command that specifies the update for a plurality of clusters of the datacenter.
18 . The non-transitory computer-readable medium of claim 15 , wherein the enter cluster maintenance mode component is invoked based at least in part on the datacenter update command.
19 . The non-transitory computer-readable medium of claim 15 , wherein the host level update comprises a firmware update.
20 . The non-transitory computer-readable medium of claim 15 , wherein the datacenter level workload performs the host level update for a plurality of hosts of the specified cluster, and iteratively performs the host level update for a respective plurality of hosts of a respective one of the plurality of clusters of the datacenter.Join the waitlist — get patent alerts
Track US2023155955A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.