Dynamic cloud native cluster construction using under-utilized machines

US11996979B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11996979-B2
Application numberUS-202117205681-A
CountryUS
Kind codeB2
Filing dateMar 18, 2021
Priority dateJan 29, 2020
Publication dateMay 28, 2024
Grant dateMay 28, 2024

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

One example method includes connecting to a server component, transmitting, to the server component, information concerning a hardware configuration associated with an asset having a capability that is fully utilized during a first time period and the capability is idle during a second time period, receiving, from the server component, cluster connection information, and using the cluster connection information to temporarily connect the asset to the cluster as a node of the cluster so that the capability is available during idle time to perform a workload of the cluster.

First claim

Opening claim text (preview).

What is claimed is: 1. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising: receiving, from an agent component associated with an asset, information concerning a hardware configuration associated with the asset, wherein the asset has a capability, and the capability of the asset is fully utilized during a first time period and the capability of the asset is idle during a second time period; predicting a timeslot throughout which the asset may be available to serve as a node of a cluster by using time-series data associated with the asset; generating a policy concerning the asset based on the information received from the agent component, wherein the policy includes an identifier of the asset and the timeslot; accessing the policy concerning the asset; connecting to the agent component based on the policy; and transmitting cluster connection information to the agent component, and the cluster connection information is usable by the agent component to connect the asset to the cluster. 2. The non-transitory storage medium as recited in claim 1 , wherein a server component connects to the agent component at a time specified in the policy. 3. The non-transitory storage medium as recited in claim 1 , wherein the operations are performed by a server component. 4. The non-transitory storage medium as recited in claim 1 , wherein the operations further comprise notifying the agent component that a time period specified in the policy has ended. 5. The non-transitory storage medium as recited in claim 1 , wherein the policy specifies (i) a unique identifier of the asset, and (ii) a timeslot during which the asset is available to execute a cluster workload. 6. The non-transitory storage medium as recited in claim 1 , wherein the cluster is a virtualized cluster, and the operations further comprise a server component notifying the agent component to create a virtual machine (VM) based on the asset. 7. The non-transitory storage medium as recited in claim 1 , wherein the cluster is a cloud-native cluster. 8. A method, comprising: receiving, from an agent component associated with an asset, information concerning a hardware configuration associated with the asset, wherein the asset has a capability, and the capability of the asset is fully utilized during a first time period and the capability of the asset is idle during a second time period; predicting a timeslot throughout which the asset may be available to serve as a node of a cluster by using time-series data associated with the asset; generating a policy concerning the asset based on the information received from the agent component, wherein the policy includes an identifier of the asset and the timeslot; accessing the policy concerning the asset; connecting to the agent component based on the policy; and transmitting cluster connection information to the agent component, and the cluster connection information is usable by the agent component to connect the asset to the cluster. 9. The method as recited in claim 8 , wherein a server component connects to the agent component at a time specified in the policy. 10. The method as recited in claim 8 , wherein the operations are performed by a server component. 11. The method as recited in claim 8 , wherein the operations further comprise notifying the agent component that a time period specified in the policy has ended. 12. The method as recited in claim 8 , wherein the policy specifies (i) a unique identifier of the asset, and (ii) a timeslot during which the asset is available to execute a cluster workload. 13. The method as recited in claim 8 , wherein the cluster is a virtualized cluster, and the operations further comprise a server component notifying the agent component to create a virtual machine (VM) based on the asset. 14. The method as recited in claim 8 , wherein the cluster is a cloud-native cluster. 15. A system, comprising: one or more hardware processors; and a non-transitory storage medium having stored therein instructions that are executable by the one or more hardware processors to perform operations comprising: receiving, from an agent component associated with an asset, information concerning a hardware configuration associated with the asset, wherein the asset has a capability, and the capability of the asset is fully utilized during a first time period and the capability of the asset is idle during a second time period; predicting a timeslot throughout which the asset may be available to serve as a node of a cluster by using time-series data associated with the asset; generating a policy concerning the asset based on the information received from the agent component, wherein the policy includes an identifier of the asset and the timeslot; accessing the policy concerning the asset; connecting to the agent component based on the policy; and transmitting cluster connection information to the agent component, and the cluster connection information is usable by the agent component to connect the asset to the cluster. 16. The system as recited in claim 15 , wherein the policy specifies (i) a unique identifier of the asset, and (ii) a timeslot during which the asset is available to execute a cluster workload. 17. The system as recited in claim 15 , wherein the cluster is a virtualized cluster, and the operations further comprise a server component notifying the agent component to create a virtual machine (VM) based on the asset. 18. The system as recited in claim 15 , wherein a server component connects to the agent component at a time specified in the policy, and the operations are performed by the server component. 19. The system as recited in claim 15 , wherein the operations further comprise notifying the agent component that a time period specified in the policy has ended. 20. The system as recited in claim 15 , wherein the cluster is a cloud-native cluster.

Assignees

Inventors

Classifications

  • specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks · CPC title

  • the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV · CPC title

  • for predicting network behaviour · CPC title

  • for prediction of maintenance · CPC title

  • Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11996979B2 cover?
One example method includes connecting to a server component, transmitting, to the server component, information concerning a hardware configuration associated with an asset having a capability that is fully utilized during a first time period and the capability is idle during a second time period, receiving, from the server component, cluster connection information, and using the cluster conne…
Who is the assignee on this patent?
Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification H04L41/0816. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue May 28 2024 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 5 related publications on this page (citations in our corpus or others sharing the same primary CPC).