Providing high availability for a thin-provisioned container cluster
US-10447614-B2 · Oct 15, 2019 · US
US11463374B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11463374-B2 |
| Application number | US-202117244400-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 29, 2021 |
| Priority date | Jun 23, 2017 |
| Publication date | Oct 4, 2022 |
| Grant date | Oct 4, 2022 |
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 providing high availability for a thin-provisioned container cluster includes a memory, one or more processors in communication with the memory, a scheduler executing on the one or more processors, and a spot instance market monitor. The spot instance market monitor receives market information about spot instances in a cloud system at a first time. The spot instances are available to a client at the first time. The spot instance market monitor determines, based on the market information, a respective reliability value for each of the spot instances at the first time. Then, the scheduler selects one spot instance among the spot instances based on the reliability value of the spot instance. In response to the selection of the spot instance, the scheduler schedules a container on the spot instance and executes the container on the spot instance.
Opening claim text (preview).
The invention is claimed as follows: 1. A system comprising: a memory; one or more processors in communication with the memory; a scheduler executing on the one or more processors; and a spot instance market monitor configured to: receive market information about a first plurality of available spot instances in a cloud system; and determine, based on the market information, a respective reliability value of each of the first plurality of available spot instances, wherein each respective reliability value corresponds to a respective likelihood of a respective spot instance being terminated by a predetermined time; wherein the scheduler is configured to select a first spot instance in the first plurality of available spot instances based on a first reliability value of the first spot instance. 2. The system of claim 1 , wherein the system is configured to execute a stateful workload on the first spot instance. 3. The system of claim 2 , wherein the stateful workload comprises a web application or a database service. 4. The system of claim 1 , wherein the cloud system comprises a public cloud system or a hybrid cloud system. 5. The system of claim 1 , wherein the scheduler is configured to select a spot instance whose purchase price is the lowest among available spot instances whose reliability value is greater than a predetermined value. 6. The system of claim 1 , wherein the scheduler is configured to schedule a service on the first spot instance, wherein responsive to being scheduled on the first spot instance, the service executes on the first spot instance. 7. The system of claim 6 , wherein the spot instance market monitor is configured to determine a respective reliability value of each of a second plurality of spot instances in the cloud system, and wherein the scheduler is configured to: select a second spot instance in the second plurality of spot instances based on a second reliability value of the second spot instance; and migrate the service from the first spot instance to the second spot instance. 8. The system of claim 7 , wherein the scheduler is configured to perform the migration when the first reliability value of the first spot instance becomes less than a predetermined reliability value. 9. The system of claim 7 , wherein the scheduler is configured to select the second spot instance responsive to detecting that the first spot instance is terminated. 10. The system of claim 6 , wherein the service comprises a payment processing service or a video service. 11. The system of claim 1 , wherein the spot instance market monitor is configured to: determine the respective reliability value of each of the first plurality of spot instances periodically at a predetermined frequency; and increase the predetermined frequency when a fluctuation of purchase prices of spot instances in the cloud system becomes greater than a predetermined level. 12. A method comprising: receiving, by a spot instance market monitor, market information about a first plurality of available spot instances in a cloud system; determining, by the spot instance market monitor, based on the market information, a respective reliability value of each of the first plurality of available spot instances, wherein each respective reliability value corresponds to a likelihood of a respective spot instance being terminated by a predetermined time; and selecting, by a scheduler executing on one or more processors in communication with a memory, a first spot instance in the first plurality of available spot instances based on a first reliability value of the first spot instance. 13. The method of claim 12 , further comprising executing a stateful workload on the first spot instance. 14. The method of claim 13 , wherein the stateful workload comprises a web application or a database service. 15. The method of claim 12 , further comprising selecting, by the scheduler, a spot instance whose purchase price is the lowest among available spot instances whose reliability value is greater than a predetermined value. 16. The method of claim 12 , further comprising scheduling, by the scheduler, a service on the first spot instance, wherein responsive to being scheduled on the first spot instance, the service executes on the first spot instance. 17. The method of claim 16 , further comprising: determining, by the spot instance market monitor, a respective reliability value of each of a second plurality of spot instances in the cloud system; selecting, by the scheduler, a second spot instance in the second plurality of spot instances based on a second reliability value of the second spot instance; and migrating, by the scheduler, the service from the first spot instance to the second spot instance. 18. The method of claim 16 , wherein the service comprises a payment processing service or a video service. 19. The method of claim 12 , further comprising: determining, by the spot instance market monitor, the respective reliability value of each of the first plurality of spot instances periodically at a predetermined frequency; and increasing, by the spot instance market monitor, the predetermined frequency when a fluctuation of purchase prices of spot instances in the cloud system becomes greater than a predetermined level. 20. A non-transitory machine readable medium storing instructions, which when executed by one or more processors, cause the one or more processors to: receive, by a spot instance market monitor, market information about a first plurality of available spot instances in a cloud system; determine, by the spot instance market monitor, based on the market information, a respective reliability value of each of the first plurality of available spot instances, wherein each respective reliability value corresponds to a likelihood of a respective spot instance being terminated by a predetermined time; and select, by a scheduler executing on the one or more processors, a first spot instance in the first plurality of available spot instances based on a first reliability value of the first spot instance.
Allocation of resources, e.g. of the central processing unit [CPU] · CPC title
Payments according to the detected use or quantity · CPC title
Grid computing · CPC title
by checking availability · CPC title
using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.