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

• US 9,705,686 B2
• Filed: 08/22/2013
• Issued: 07/11/2017
• 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): Whipple, Brian
• Assistant Examiner(s): Tolchinsky, Gregory P
• Application Number:
  US13/973,285
• Publication Number:
  US 20150058471A1
• Time in Patent Office: 1,419 Days
• 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 multi-tenant Platform-as-a-Service (PaaS) system are disclosed. A method of the disclosure includes determining, by a 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, accessing a list of initialization operations used in the initialization of the resource, determining that each of the initialization operations prior to a create usage record operation in the mapping are performed successfully, and creating a usage record for the resource using the create usage record operation.

Claims

1. A method, comprising:

determining, by a 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;

accessing a list of initialization operations used in the initialization of the resource;

performing initialization operations from the list until reaching a create usage record operation in the list;

determining that each of the initialization operations prior to a 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 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.

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 PaaS 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 PaaS 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

when 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;

when 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

when 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. A system, comprising:

a memory; and

a first processing device communicably coupled to the memory, the first processing device to;

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

access a list of initialization operations used in the initialization of the resource;

perform initialization operations from the list until reaching a create usage record operation in the list;

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

create 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

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, perform a roll-back operation or a re-try operation for the failed initialization operation.

10. The system of claim 9, 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.

11. The system of claim 9, wherein the first processing device further to:

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

call, in response to the expiration, a second processing device of the PaaS system to communicate data of the usage record to a billing provider, wherein the second processing device is communicably coupled to the first processing device.

12. The system of claim 11, wherein the second processing device to send, to the billing provider, the data of the usage record and a current time stamp identifying when the data was sent from the PaaS system, the data comprising usage of the resource tracked since a previous successful synchronization of the usage record.

13. The system of claim 12, wherein the second processing device further to:

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

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

14. The system of claim 12, wherein the second processing device further to, prior to the sending the data:

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

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

15. The system of claim 14, wherein the second processing device further to:

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

when the sent time stamps match;

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

perform the sending the data; and

when the sent time stamps do not match, send 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.

16. 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;

access a list of initialization operations used in the initialization of the resource;

perform initialization operations from the list until reaching a create usage record operation in the list;

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

create, 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, wherein the usage record comprises at least one of 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;

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; and

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

17. The non-transitory machine-readable storage medium of claim 16, 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.

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

send, to a billing provider, the data of the usage record and a current time stamp identifying when the data was sent from the PaaS system, the data comprising usage of the resource tracked since a previous successful synchronization of the usage record;

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

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

19. The non-transitory machine-readable storage medium of claim 18, prior to the sending the data, the processing device further to:

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

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

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

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

when the sent time stamps match;

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

perform the sending the data; and

when the sent time stamps do not match, send 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.