Measuring resource consumption in a multi-tenant platform-as-a-service (PAAS) system

• US 10,256,984 B2
• Filed: 07/10/2017
• Issued: 04/09/2019
• Est. Priority Date: 08/22/2013
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: McPherson, Daniel, Sankar Penta, Ravi
• Primary Examiner(s): Cheema, Umar
• Assistant Examiner(s): Tolchinsky, Gregory P
• Application Number:
  US15/646,069
• Publication Number:
  US 20170310494A1
• Time in Patent Office: 638 Days
• Field of Search: None
• CPC Class Codes: H04L 12/1432 Metric aspects
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less

Abstract

Implementations for measuring resource consumption in a cloud provider system are disclosed. A method of the disclosure includes determining that a resource of an application of a cloud provider system is initializing, determining whether each operation in a list of initialization operations used in the initialization of the resources is performed successfully, prior to a create usage record operation in the list of initialization operations, in response to determining that each of the initialization operations prior to the create usage record operation in the list of initialization operations is performed successfully, creating a usage record for the resource using the create usage record operation based on a threshold usage level associated with the application, and in response to determining that at least one of the initialization operations prior to the create usage record operation in the list of initialization operations has failed, performing a roll-back operation or a re-try operation for the at least one of the initialization operations that has failed.

Claims

1. A method, comprising:

determining, by a processing device, that a resource of an application of a cloud provider system is initializing;

determining whether each operation in a list of initialization operations used in the initialization of the resources is performed successfully, prior to a create usage record operation in the list of initialization operations;

in response to determining that each of the initialization operations prior to the create usage record operation in the list of initialization operations is performed successfully, creating, by the processing device, a usage record for the resource using the create usage record operation based on a threshold usage level associated with the application; and

in response to determining that at least one of the initialization operations prior to the create usage record operation in the list of initialization operations has failed, performing, by the processing device, a roll-back operation or a re-try operation for the at least one of the initialization operations that has failed.

2. The method of claim 1, wherein the resource comprises at least one of a gear, a cartridge, or storage, wherein the gear comprises a resource-constrained process space of a node executing at least a portion of the application, and wherein the cartridge comprises support software providing a functionality of the application.

3. The method of claim 1, wherein the usage record comprises a user identifier (ID) associated with the application, a resource ID of the resource, a usage type of the resource, a duration of a usage of the resource, and a time stamp of a most recent update to the duration of the usage.

4. The method of claim 1, further comprising:

determining that a synchronization time interval for the usage record has expired; and

calling, in response to the expiration, an integration component of the cloud provider system to communicate data of the usage record to a billing provider.

5. The method of claim 4, further comprising sending, to the billing provider, the data of the usage record and a current time stamp identifying when the data was sent from the cloud provider system, the data comprising usage of the resource tracked since a previous successful synchronization of the usage record.

6. The method of claim 5, further comprising:

receiving, from the billing provider, an indication of successful receipt of the data sent to the billing provider; and

updating the usage record to reflect the indication of successful receipt and to include the time stamp identifying when the data was sent.

7. The method of claim 5, further comprising, prior to the sending the data:

determining whether a previous synchronization of the usage record is indicated to be successful; and

responsive to determining that the previous synchronization is not indicated to be successful, querying the billing provider for a sent time stamp associated with usage record identifier (ID) of the usage record.

8. The method of claim 7, further comprising:

comparing the sent time stamp received from the billing provider with a sent time stamp in the usage record;

in response to determining that the sent time stamps match;

updating the usage record to reflect that the previous synchronization was successful and to include the sent time stamp; and

performing the sending the data; and

in response to determining that the sent time stamps do not match, sending the data of the usage record comprising usage of the resource tracked since the previous synchronization of the usage record and the current time stamp identifying when the data was sent from the PaaS system.

9. The method of claim 5 wherein tracking of the usage of the resource is enabled prior to determining that a tracked resource usage type is initialized.

10. The method of claim 9 wherein determining that the tracked resource usage type is initialized comprises determining that a threshold of usage for the tracked resource usage type is exceeded.

11. The method of claim 1 wherein the cloud provider system is a multitenant Platform-as-a-Service (PaaS) system comprising a client layer, a broker layer and a node layer.

12. The method of claim 11 wherein:

the client layer comprises a set of command tools to create, launch and manage applications;

the broker layer acts as middleware between the client layer and the node layer; and

the node layer comprises a plurality of nodes on which applications are provisioned and executed.

13. The method of claim 12 wherein each of the plurality of nodes is associated with a cartridge library that maintains cartridges used by the applications.

14. The method of claim 13 wherein a cartridge is to execute in gears dispersed on the plurality of nodes.

15. A method, comprising:

determining, by a processing device, that a resource of an application of a multitenant Platform-as-a-Service (PaaS) system is initializing, the resource marked for usage tracking, wherein usage of the resource is tracked in view of a cost rate determined based on a state of the application;

determining whether each operation in a list of initialization operations is initialized successfully, prior to a create usage record operation in the list of initialization operations;

creating, by the processing device, a usage record for the resource using the create usage record operation in response to determining that each of the initialization operations prior to the create usage record operation in the list of initialization operations has performed successfully; and

responsive to determining that at least one of the initialization operations prior to the create usage record operation in the list of initialization operations has failed, perform, by the processing device, a roll-back operation or a re-try operation for the failed initialization operation.

16. The method of claim 15, wherein the resource comprises at least one of a gear, a cartridge, or storage, wherein the gear comprises a resource-constrained process space of a node executing at least a portion of the application, wherein the cartridge comprises support software providing a functionality of the application, and wherein the usage record comprises a user identifier (ID) associated with the application, a resource ID of the resource, a usage type of the resource, a duration of a usage of the resource, and a time stamp of a most recent update to the duration of the usage.

17. The method of claim 15, wherein the usage record comprises a user identifier (ID) associated with the application, a resource ID of the resource, a usage type of the resource, a duration of a usage of the resource, and a time stamp of a most recent update to the duration of the usage.

18. A non-transitory machine-readable storage medium including data that, when accessed by a processing device, cause the processing device to:

determine, by the processing device, that a resource of an application of a multi tenant Platform-as-a-Service (PaaS) system is initializing, the resource marked for usage tracking;

determine whether each operation in a list of initialization operations is performed successfully, prior to a create usage record operation in the list of initialization operations;

in response to determining that each of the initialization operations prior to the create usage record operation in the list of initialization operations has performed successfully;

create, by the processing device, a usage record for the resource using the create usage record operation, and

synchronize a created usage record with a billing provider; and

responsive to determining that at least one of the initialization operations prior to the create usage record operation in the list of initialization operations has failed, perform a roll-back operation or a re-try operation for the failed initialization operation.

19. The non-transitory machine-readable storage medium of claim 18, wherein the resource comprises at least one of a gear, a cartridge, or storage, wherein the gear comprises a resource-constrained process space of a node executing at least a portion of the application, and wherein the cartridge comprises support software providing a functionality of the application.

20. The non-transitory machine-readable storage medium of claim 18, the processing device further to:

responsive to a synchronization time interval for the usage record expiring, send data of the usage record.