Lifecycle management for workloads on heterogeneous infrastructure
US-2023161643-A1 · May 25, 2023 · US
US11936544B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11936544-B2 |
| Application number | US-202217820328-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 17, 2022 |
| Priority date | Jul 20, 2022 |
| Publication date | Mar 19, 2024 |
| Grant date | Mar 19, 2024 |
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 system and method for capturing resource usage information in a network for namespaces in which pods operate are described herein. A data structure specifies a topology that includes a gateway and routing addresses in a network whose usage is to be captured. The data structure is provided to an API of a master node controlling the pods. A controller in the master node enforces the data structure and reports results back to the API.
Opening claim text (preview).
What is claimed is: 1. A method of capturing network usage for one or more namespaces, the method comprising: specifying, in one or more custom resource definitions, information to be captured for a network accessible by entities operating in the one or more namespaces, wherein the network includes a gateway and a set of routing addresses for access to and from the network, and wherein the network usage specifies how many routing addresses in the set of routing addresses are used; providing the one or more custom resource definitions to a management interface in a node that controls the one or more namespaces, wherein the management interface provides create, read, update, and delete operations for one or more of the entities operating in the one or more namespaces; collecting, by one or more controllers in the node, network usage information according to the information specified in the one or more custom resource definitions, from notifications received from the management interface, wherein the management interface is configured to send notifications to the one or more controllers when changes are detected to the network; and receiving a report of network usage from the node according to the information specified in the one or more custom resource definitions to be captured. 2. The method of claim 1 , wherein the node is a master node in a supervisor cluster supporting the one or more namespaces and the management interface is an application programming interface (API) that receives the one or more custom resource definitions. 3. The method of claim 1 , wherein a pod virtual machine is an entity operating in the one or more namespaces. 4. The method of claim 1 , wherein the one or more namespaces are associated with a cluster of nodes that implement a container orchestration system. 5. The method of claim 1 , wherein the one or more custom resource definitions includes a status field for indicating any error condition applying to the network. 6. The method of claim 1 , further comprising providing a controller that resides in the node, wherein the controller performs a watch service for the information specified to be captured. 7. The method of claim 1 , wherein the report of network usage does not reveal any other information about the network. 8. A system comprising: a CPU coupled to a memory; a cluster of servers, the cluster being configured to run a node that controls one or more namespaces, wherein the servers are communicatively connected to the CPU and the memory; and a networking sub-system coupled to the cluster of servers, the networking sub-system accessible by entities operating in the one or more namespaces; wherein one or more custom resource definitions are provided to a management interface in the node, the one or more custom resource definitions being configured to: specify information to be captured for the networking sub-system accessible by the one or more namespaces, wherein the network includes a gateway and a set of routing addresses for access to and from the network, wherein the network usage specifies how many routing addresses in the set of routing addresses are used, wherein one or more controllers in the node collect network usage information according to the information specified in the one or more custom resource definitions, from notifications received from the management interface, wherein the management interface is configured to send notifications to the one or more controllers when changes are detected to the networking sub-system and wherein the management interface provides create, read, update, and delete operations for one or more of the entities operating in the one or more namespaces, and wherein the node provides a report of network usage according to the information specified in the one or more custom resource definitions to be captured. 9. The system of claim 8 , wherein the node is a master node in a supervisor cluster supporting the one or more namespaces and the management interface is an application programming interface (API) that receives the one or more custom resource definitions. 10. The system of claim 8 , wherein a pod virtual machine is an entity operating in one of the one or more namespaces. 11. The system of claim 8 , wherein the one or more namespaces are associated with a cluster of nodes that implements a container orchestration system. 12. The system of claim 8 , wherein the one or more custom resource definitions includes a status field for indicating any error condition applying to the network. 13. The system of claim 8 , wherein the node includes a controller, and the controller performs a watch service for the information specified to be captured. 14. The system of claim 8 , wherein the report of network usage does not reveal any other information about the network. 15. A non-transitory computer-readable medium comprising instructions, which, when executed, cause a computer system to carry out a method for capturing network usage for one or more namespaces accessible by entities operating in the one or more namespaces, the method comprising: specifying, in one or more custom resource definitions, information to be captured for a network accessible by the one or more namespaces, wherein the network includes a gateway and a set of routing addresses for access to and from the network, and wherein the network usage specifies how many routing addresses in the set of routing addresses are used; providing the one or more custom resource definitions to a management interface in a node that controls the one or more namespaces, wherein the management interface provides create, read, update, and delete operations for one or more of the entities operating in the one or more namespaces; collecting, by one or more controllers in the node, network usage information according to the information specified in the one or more custom resource definitions, from notifications received from the management interface, wherein the management interface is configured to send notifications to the one or more controllers when changes are detected to the network; and receiving a report of network usage from the node according to the information specified in the one or more custom resource definitions to be captured. 16. The non-transitory computer-readable medium of claim 15 , wherein the node is a master node in a supervisor cluster supporting the one or more namespaces and the management interface is an application programming interface (API) that receives the one or more custom resource definitions. 17. The non-transitory computer-readable medium of claim 16 , wherein a pod virtual machine is an entity operating in the one or more namespaces. 18. The non-transitory computer-readable medium of claim 16 , wherein the one or more namespaces are associated with a cluster of nodes that implement a container orchestration system. 19. The non-transitory computer-readable medium of claim 16 , wherein the one or more custom resource definitions includes a status field for indicating any error condition applying to the network. 20. The non-transitory computer-readable medium of claim 16 , wherein the report of network usage does not reveal any other information about the network.
Network utilisation, e.g. volume of load or congestion level · CPC title
Hypervisor-specific management and integration aspects · CPC title
Remote procedure calls [RPC]; Web services · CPC title
Network integration; Enabling network access in virtual machine instances · CPC title
the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.