Resource management for cloud computing platforms

US9595054B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9595054-B2
Application numberUS-201113169890-A
CountryUS
Kind codeB2
Filing dateJun 27, 2011
Priority dateJun 27, 2011
Publication dateMar 14, 2017
Grant dateMar 14, 2017

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.

A system for managing allocation of resources based on service level agreements between application owners and cloud operators. Under some service level agreements, the cloud operator may have responsibility for managing allocation of resources to the software application and may manage the allocation such that the software application executes within an agreed performance level. Operating a cloud computing platform according to such a service level agreement may alleviate for the application owners the complexities of managing allocation of resources and may provide greater flexibility to cloud operators in managing their cloud computing platforms.

First claim

Opening claim text (preview).

What is claimed is: 1. A method comprising: receiving a specification of at least one performance level for execution of a software application by a cloud computing platform; executing the software application via resources of the cloud computing platform; checking whether the at least one performance level is met; based at least in part on the checking, determining whether failure to meet the at least one performance level is attributable to the cloud computing platform or the software application; when the failure is attributable to the cloud computing platform, allocating additional resources to the software application; and when the failure is attributable to the software application, refraining from allocating additional resources to the software application. 2. The method of claim 1 , further comprising: billing an application owner of the software application for the execution of the software application an amount determined based at least in part on whether the failure to meet the at least one performance level is attributable to the cloud computing platform or the software application. 3. The method of claim 2 , wherein the billing further comprises: billing the application owner for the execution of the software application at a first billing rate when the failure to meet the at least one performance level is attributable to the cloud computing platform; and billing the application owner for the execution of the software application at a second billing rate that is less than the first billing rate when the failure to meet the at least one performance level is attributable to the software application. 4. The method of claim 1 , further comprising: analyzing functionality of the software application to identify a first logical part and a second logical part, the first logical part comprising a first portion of the functionality of the software application and the second logical part comprising a second portion of the functionality of the software application, the first portion being different from the second portion and being independently executable from the second portion, wherein the failure to meet the at least one performance level is determined via analysis of a first expected execution time of the first logical part and a second expected execution time of the second logical part. 5. A system comprising: a computing device; and a storage device storing computer-executable instructions that, when executed by the computing device, cause the computing device to: receive a service-level agreement (SLA) specified performance level relating to execution by a cloud computing platform of a software application provided by an application owner, execute the software application provided by the application owner via resources of the cloud computing platform, perform a comparison between a first actual operational characteristic of the software application and an expected operational characteristic for the software application, based at least in part on the comparison, determine whether failure to meet the SLA specified performance level is attributable to the software application or to the cloud computing platform, when the failure is attributable to the cloud computing platform, allocate additional resources to the software application, and when the failure is attributable to the software application, refrain from allocating the additional resources to the software application. 6. The system of claim 5 , wherein: the first actual operational characteristic is an actual execution time for operation of at least one logical part of the software application, and the expected operational characteristic is an expected execution time for the operation of the at least one logical part. 7. The system of claim 6 , wherein the computer-executable instructions further cause the computing device to: determine the actual execution time by logging a start and an end of the execution of the at least one logical part in one or more logs. 8. The system of claim 5 , wherein the computer-executable instructions further cause the computing device to: determine an amount to bill the application owner for the execution of the software application based at least in part on the failure being attributable to the software application or the cloud computing platform. 9. The system of claim 5 , wherein the computer-executable instructions further cause the computing device to: determine that the failure to meet the SLA specified performance level is attributable to the software application by determining that the first actual operational characteristic does not meet the expected operational characteristic. 10. The system of claim 5 , wherein the computer-executable instructions further cause the computing device to: receive the expected operational characteristic from the application owner. 11. The system of claim 5 , wherein the computer-executable instructions further cause the computing device to: identify the expected operational characteristic. 12. The system of claim 5 , wherein the computer-executable instructions further cause the computing device to: send a report to the application owner when the software application is not executing within the expected operational characteristic for at least one logical part of the software application for at least a threshold amount of time, the report including a notification that the cloud computing platform is not allocating additional resources to the execution of the software application. 13. A system comprising: at least one processor; and at least one memory device or storage device storing computer-executable instructions which, when executed by the at least one processor, cause the at least one processor to: receive a specification of at least one performance level of a service-level agreement (SLA) between an application owner and a cloud operator of a cloud computing platform, the at least one performance level relating to execution by the cloud computing platform of a software application provided by the application owner, execute the software application provided by the application owner via resources of the cloud computing platform, check whether the at least one performance level is met, based at least in part on the checking, determine whether failure to meet the at least one performance level is attributable to the software application or the cloud computing platform, and when the failure is attributable to the software application, refrain from allocating additional resources to the software application. 14. The system of claim 13 , wherein the at least one performance level comprises an execution time for operation of the software application provided by the application owner. 15. The system of claim 14 , wherein the at least one performance level comprises an upper limit on acceptable execution times. 16. The system of claim 15 , wherein the computer-executable instructions further cause the at least one processor to: when an actual execution time exceeds the upper limit on the acceptable execution times, determine whether an actual operational characteristic of a logical part of the software application deviates from an expected operational characteristic for the logical part, when the actual operational characteristic deviates from the expected operational characteristic, select a first billing rate to bill the application owner for the execution of the software application, and when the actual operational characteristic does not deviate from the expected operational characteristic, select a second

Assignees

Inventors

Classifications

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 US9595054B2 cover?
A system for managing allocation of resources based on service level agreements between application owners and cloud operators. Under some service level agreements, the cloud operator may have responsibility for managing allocation of resources to the software application and may manage the allocation such that the software application executes within an agreed performance level. Operating a cl…
Who is the assignee on this patent?
Jain Navendu, Menache Ishai, Microsoft Technology Licensing Llc
What technology area does this patent fall under?
Primary CPC classification G06Q30/04. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Mar 14 2017 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 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).