Systems and methods for containerized information technology resource management based on customization of kubernetes pods
AssigneeEdjx, Inc.
InventorsDelano Seymour, Douglas Steele, John Cowan
Life of this patent
Estimating the term…
Abstract
Systems and methods for containerized IT intelligence and management. In one embodiment, a system for containerized IT financial management comprises at least one collector, at least one meter, at least one connector, and a reporting dashboard. The at least one collector is customized and connected to at least one container platform. The at least one collector sends capacity and consumption metrics to the at least one meter for processing and aggregation.
Claims14
A system for containerized Information Technology (IT) resource management, comprising:
- a Kubernetes node;
- wherein the Kubernetes node is a physical machine;
- wherein the Kubernetes node comprises at least one collector, at least one meter application programing interface (API), and at least one connector;
- wherein the at least one collector is a first Kubernetes pod;
- wherein the at least one collector comprises an inventory collector container;
- wherein the at least one collector is customized for at least one container application platform with information comprising a unique name to be applied to a container cluster in a container environment, a domain name for a dedicated cluster in the container environment, a log level indicating a verbosity of a collector log, whether to use an Secure Sockets Layer (SSL), whether to verify the SSL, an age period of data for clean cache, a fallback value for Local Area Network (LAN) Input/Output (I/O) speed per node if the at least one collector cannot determine an actual LAN speed, a fallback value for Wide Area Network (WAN) I/O speed per node if the at least one collector cannot determine an actual WAN speed, and a fallback value for disk I/O speed per node if the at least one collector cannot determine an actual disk speed;
- wherein the at least one meter API is configured with information comprising an organization ID, a host address, and a port;
- wherein the inventory collector container is operable to retrieve a list of application containers for metering from each of the at least one container application platform;
- wherein the inventory collector container is operable to store a metered state of each application container in the list of application containers;
- wherein the at least one meter API is further configured to measure consumption of the at least one container application platform, thereby creating meter data;
- wherein the list of application containers is operable to be updated based on the consumption;
- wherein the at least one connector is configured to extract, transform, and load the meter data;
- wherein computer resource usage of the at least one container application platform is tracked and optimized in real time;
- and
- wherein the at least one connector is a second Kubernetes pod of the Kubernetes node.
A system for containerized Information Technology (IT) resource management, comprising:
- a Kubernetes node, including at least one collector, at least one meter, at least one meter application programing interface (API), and at least one connector;
- wherein the Kubernetes node is a physical machine;
- wherein the at least one collector is a first Kubernetes pod;
- wherein the at least one collector comprises an inventory collector container;
- wherein the at least one collector is customized for at least one container application platform with information comprising a unique name to be applied to a container cluster in a container environment, a domain name for a dedicated cluster in the container environment, a log level indicating a verbosity of a collector log, whether to use an Secure Sockets Layer (SSL), whether to verify the SSL, an age period of data for clean cache, a fallback value for Local Area Network (LAN) Input/Output (I/O) speed per node if the at least one collector cannot determine an actual LAN speed, a fallback value for Wide Area Network (WAN) I/O speed per node if the at least one collector cannot determine an actual WAN speed, and a fallback value for disk I/O speed per node if the at least one collector cannot determine an actual disk speed;
- wherein the at least one meter API is configured with information comprising an organization ID, a host address, and a port;
- wherein the inventory collector container is operable to retrieve a list of application containers for metering from each of the at least one container application platform;
- wherein the inventory collector container is operable to store a metered state of each application container in the list of application containers;
- wherein the at least one meter is configured to measure consumption of the at least one container application platform, thereby creating meter data;
- wherein the list of application containers is operable to be updated based on the consumption;
- wherein the at least one connector is configured to extract, transform, and load the meter data;
- wherein computer resource usage of the at least one container application platform is tracked and optimized in real time;
- and
- wherein the at least one connector is a second Kubernetes pod of the Kubernetes node.
A method for containerized Information Technology (IT) resource management, comprising:
- providing a Kubernetes node, including at least one collector, at least one meter, at least one meter application programming interface (API), at least one connector, and at least one analytics platform for at least one container application platform, wherein the Kubernetes node is a physical machine, wherein the at least one collector is a first Kubernetes pod, wherein the at least one collector comprises an inventory collector container and a metrics collector container, and wherein the at least one collector is customized for at least one container application platform with information comprising a unique name to be applied to a container cluster in a container environment, a domain name for a dedicated cluster in the container environment, a log level indicating a verbosity of a collector log, whether to use an Secure Sockets Layer (SSL), whether to verify the SSL, an age period of data for clean cache, a fallback value for Local Area Network (LAN) Input/Output (I/O) speed per node if the at least one collector cannot determine an actual LAN speed, a fallback value for Wide Area Network (WAN) I/O speed per node if the at least one collector cannot determine an actual WAN speed, and a fallback value for disk I/O speed per node if the at least one collector cannot determine an actual disk speed;
- configuring the at least one meter API with information comprising an organization ID, a host address, and a port;
- the inventory collector container retrieving a list of application containers for metering from the at least one container application platform;
- storing a metered state of each application in the list of application containers, and updating the metered state of each application container in the list of application containers;
- the metrics collector container collecting sample data of computing resource usage by application containers not metered yet;
- the at least one meter measuring consumption of the at least one container application platform based on the sample data, thereby creating meter data;
- the list of application containers updating based on the consumption;
- the at least one connector extracting, transforming, and loading the meter data;
- wherein computer resource usage of the at least one container application platform is tracked and optimized in real time;
- and
- wherein the at least one connector is a second Kubernetes pod of the Kubernetes node.
Dependencies are inferred from the claim text.