Multi-component consent-based virtual machine migration
US-9558026-B2 · Jan 31, 2017 · US
US9929918B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9929918-B2 |
| Application number | US-201313953197-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 29, 2013 |
| Priority date | Jul 29, 2013 |
| Publication date | Mar 27, 2018 |
| Grant date | Mar 27, 2018 |
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.
Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving performance metrics from at least one device within the cloud network; analyzing the performance metrics to generate at least one application requirement, wherein the at least one application requirement indicates a recent performance associated with a resource provisioned for a customer, wherein the resource is supported by a first device within the cloud network; identifying a second device within the cloud network to support the resource based on the at least one application requirement; and migrating the resource from the first device to the second device.
Opening claim text (preview).
What is claimed is: 1. A method performed by a cloud controller for migrating resources within a cloud network, the method comprising: receiving performance metrics from at least one device within the cloud network; determining a resource to be migrated, wherein the resource is supported by a first device within the cloud network; after determining the resource to be migrated, analyzing the performance metrics to generate at least one application requirement, wherein the at least one application requirement indicates a recent performance associated with the resource; identifying a second device within the cloud network to support the resource based on the at least one application requirement; determining that migration of the resource to the second device will preserve the at least one application requirement; and migrating the resource from the first device to the second device based upon the determination. 2. The method of claim 1 , wherein identifying the second device within the cloud network to support the resource is further based on an explicit service level agreement (SLA) associated with a customer. 3. The method of claim 1 , wherein the at least one application requirement comprises a device-level performance metric. 4. The method of claim 1 , wherein the at least one application requirement comprises an application-level performance metric. 5. A cloud controller for migrating resources within a cloud network, the cloud controller comprising: a network interface; a memory; and a processor in communication with the memory, the processor being configured to: receive, via the network interface, performance metrics from at least one device within the cloud network, determine a resource to be migrated, wherein the resource is supported by a first device within the cloud network, after determining the resource to be migrated, analyze the performance metrics to generate at least one application requirement, the at least one application requirement indicates a recent performance associated with the resource, identify a second device within the cloud network to support the resource based on the at least one application requirement, determine that migration of the resource to the second device will preserve the at least one application requirement, and migrate the resource from the first device to the second device based upon the determination. 6. The cloud controller of claim 5 , wherein, in identifying the second device within the cloud network to support the resource, the processor is configured to further base identification of the second device on an explicit service level agreement (SLA) associated with a customer. 7. The cloud controller of claim 5 , wherein the at least one application requirement comprises a device-level performance metric. 8. The cloud controller of claim 5 , wherein the at least one application requirement comprises an application-level performance metric. 9. A non-transitory machine-readable storage medium encoded with instructions for execution by a cloud controller for migrating resources within a cloud network, the medium comprising: instructions for receiving performance metrics from at least one device within the cloud network; instructions for determining a resource to be migrated, wherein the resource is supported by a first device within the cloud network; instructions for, after determining the resource to be migrated, analyzing the performance metrics to generate at least one application requirement, wherein the at least one application requirement indicates a recent performance associated with the resource; instructions for identifying a second device within the cloud network to support the resource based on the at least one application requirement; instructions for determining that migration of the resource to the second device will preserve the at least one application requirement; and instructions for migrating the resource from the first device to the second device based upon the determination. 10. The non-transitory machine-readable storage medium of claim 9 , wherein the instructions for identifying the second device within the cloud network to support the resource are further based on an explicit service level agreement (SLA) associated with a customer. 11. The non-transitory machine-readable storage medium of claim 9 , wherein the at least one application requirement comprises at least one of: a device-level performance metric, and an application-level performance metric. 12. The method of claim 1 , wherein the cloud controller is configured to generate an implicit service level agreement (SLA) associated with a customer. 13. The method of claim 1 , wherein the cloud controller is configured to store both explicit service level agreements (SLA) agreed to between a cloud provider and a customer and implicit SLAs generated by the cloud controller. 14. The method of claim 1 , wherein the cloud controller is configured to offer a service upgrade to a customer that brings an explicit service level agreement (SLA) closer to an implicit SLA.
Active monitoring, e.g. heartbeat, ping or trace-route · CPC title
Jitter · CPC title
Delays · CPC title
by checking functioning · CPC title
wherein the managed service relates to distributed or central networked applications · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.