Infrastructure driven auto-scaling of workloads
US-2024419470-A1 · Dec 19, 2024 · US
US2024152404A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2024152404-A1 |
| Application number | US-202218052993-A |
| Country | US |
| Kind code | A1 |
| Filing date | Nov 7, 2022 |
| Priority date | Nov 7, 2022 |
| Publication date | May 9, 2024 |
| Grant date | — |
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.
A method, computer program product, and computer system are provided for container cross-cluster capacity scaling. The method includes broadcasting local capacity information of capacity availability or capacity requirement for the local cluster and receiving broadcasts from each of one or more other clusters providing capacity information including capacity availability or capacity requirements. The method may map the received capacity information with the local capacity information and may determine a suitable cross-cluster capacity sharing when a capacity requirement of the local cluster maps to a capacity availability of another cluster or when a capacity availability of the local cluster maps to a capacity requirement of another cluster. The method may coordinate the deallocation of a node from the cluster having the capacity availability and reallocation of the node to the cluster having the capacity requirement.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method for container cross-cluster capacity scaling, said method is carried at a local cluster having one or more current nodes in the form of physical or virtual machines running containers and comprises: broadcasting local capacity information of capacity availability or capacity requirement for the local cluster; receiving broadcasts from each of one or more other clusters providing capacity information including capacity availability or capacity requirement; mapping the received capacity information with the local capacity information; determining a suitable cross-cluster capacity sharing when a capacity requirement of the local cluster maps to a capacity availability of another cluster or when a capacity availability of the local cluster maps to a capacity requirement of another cluster; and coordinating the deallocation of a node from the cluster having the capacity availability and reallocation of the node to the cluster having the capacity requirement. 2 . The method of claim 1 , wherein the local capacity information and the received capacity information include temporary periods of availability or requirement, and wherein the mapping is based on the temporary periods of availability and requirement. 3 . The method of claim 1 , including: storing metadata of workflow patterns for the local cluster; capturing capacity utilization trends for the local cluster; and applying predictive modeling based on the utilization trends to the mapping. 4 . The method of claim 1 , including: when a capacity requirement of a local cluster is not met by received capacity availability of other clusters within a defined time frame, coordinating allocation of a node to the local cluster by local cluster scaling. 5 . The method of claim 1 , wherein determining a suitable cross-cluster capacity sharing includes applying supply and demand algorithms used to understand the capacity availability and capacity requirements and using a rules-based scheduler to match the supply and demand algorithms. 6 . The method of claim 1 , including gathering local capacity information from an agent running at each node at the local cluster. 7 . The method of claim 1 , including updating account billing and providing billing sharing beyond account boundaries when coordinating a node deallocation and reallocation. 8 . The method of claim 1 , wherein the method is carried out in a control plane of a cluster including defined custom resource application programming interfaces (APIs) providing at least some of the method functions. 9 . The method of claim 8 , wherein the defined custom resource APIs on each cluster communicate with similar peer defined custom resource APIs on other clusters and the defined custom resource APIs communicate with each other and other components using container orchestration APIs. 10 . A system for container cross-cluster capacity scaling, comprising: a processor and a memory configured to provide computer program instructions to the processor to execute the functions of the components of a cross-cluster capacity component including: a capacity broadcast component for broadcasting local capacity information of capacity availability or capacity requirement for the local cluster; a broadcast receiving component for receiving broadcasts from each of one or more other clusters providing capacity information including capacity availability or capacity requirements; a capacity mapping component for mapping the received capacity information with the local capacity information; and a capacity allocation component for determining a suitable cross-cluster capacity sharing when a capacity requirement of the local cluster maps to a capacity availability of another cluster or when a capacity availability of the local cluster maps to a capacity requirement of another cluster and coordinating the deallocation of a node from the cluster having the capacity availability and reallocation of the node to the cluster having the capacity requirement. 11 . The system of claim 10 , wherein the local capacity information and the received capacity information include temporary periods of availability or requirement, and wherein the capacity allocation component includes a temporary node period component for applying the temporary periods of availability and requirement. 12 . The system of claim 10 , including: a metadata component for storing metadata of workflow patterns for the local cluster; a capacity trend component for capturing capacity utilization trends for the local cluster; and a predictive modeling component for applying predictive modeling based on the utilization trends to the mapping. 13 . The system of claim 10 , including: a node scaling component for, when a capacity requirement of a local cluster is not met by received capacity availability of other clusters within a defined time frame, coordinating allocation of a node to the local cluster by local cluster scaling. 14 . The system of claim 10 , including a supply/demand component for applying supply and demand algorithms used to understand the capacity availability and capacity requirements and a rules-based scheduler component for using a rules-based scheduler to match the supply and demand algorithms. 15 . The system of claim 10 , including a gathering component for gathering local capacity information from an agent running at each node at the local cluster. 16 . The system of claim 10 , including a capacity metering component for updating account billing and providing billing sharing beyond account boundaries when coordinating a node deallocation and reallocation. 17 . The system of claim 10 , wherein the capacity allocation component includes using a custom resource definition application programming interface (API) for deallocating nodes from a cluster and reallocating nodes to a cluster. 18 . The system of claim 10 , wherein the cross-cluster capacity component is configured in a control plane of a cluster including defined custom resource application programming interfaces (APIs) providing at least some of the method functions. 19 . The system of claim 18 , wherein the defined custom resource APIs on each cluster communicate with similar peer defined custom resource APIs on other clusters and the defined custom resource APIs communicate with each other and other components using container orchestration APIs. 20 . A computer program product for container cross-cluster capacity scaling, the computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to: broadcast local capacity information of capacity availability or capacity requirement for the local cluster; receive broadcasts from each of one or more other clusters providing capacity information including capacity availability or capacity requirement; map the received capacity information with the local capacity information; determine a suitable cross-cluster capacity sharing when a capacity requirement of the local cluster maps to a capacity availability of another cluster or when a capacity availability of the local cluster maps to a capacity requirement of another cluster; and coordinate the deallocation of a node from the cluster having the capacity availability and reallocation of the node to the cluster having the capacity requirement.
Clust · CPC title
Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title
involving task migration · CPC title
Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues · CPC title
via adapters, e.g. between incompatible applications · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.