Usage Collection

 
 
 

In order for CPBM to accurately bill a customer for usage of resources from an underlying cloud service, CPBM needs to periodically collect usage from the cloud service and be able to understand and mediate it. Mediation is the process by which CPBM identifies the product corresponding to usage received from an underlying cloud service. CPBM does this based on a set of mediation rules attached to a product. A usage record is matched to a product based on its usage type and matching discriminator values between what is collected for the usage record and what is specified in a mediation rule for the product.

As described earlier, in order for this to happen, CPBM periodically collects usage in a well-defined format that is understood by CPBM's mediation engine. It is the responsibility of the Usage collector implementation to transform usage from the underlying resource to the standard format recognized by CPBM.

A connector must implement a Usage collector for its underlying cloud service. The connector (i.e., the Usage collector implementation) shall return usage in terms of UsageData objects. Each UsageData object describes a distinct usage record and should include values for all discriminators described in the product metadata (this includes resource type, filter and additional discriminator values).

UsageData

UsageData is defined as follows:
public class UsageData {    /* the usage type for this resource. Should match the type specified in the metadata      */    String getUsageType();    /* The tenant handle if any. Should match the handle for owning tenant associated        in the account lifecycle handler */    String getTenantHandle();    /* The user handle if any. Should match the handle for the owning user associated        in the user lifecycle handler */    String getUserHandle();    /* The resource handle, if any. Should match the handle for this tenant        associated in the subscription lifecycle handler */    String getResourceHandle();    /* Start date/time for this usage record */    Date getStartDate();    /* End Date/Time for this usage record */    Date getEndDate();    /* service specific reference id for this usage record. This should be the same        format used by the markers. */    String getReferenceId();    /* Discriminator values for *all* declared discriminators for this usage. This        includes resouce type ids, filter values and other discriminators declared for       this usage type in the metadata */    Map<String, String> getDisriminators ();    /* Raw usage. Actual usage consumed, in the unit of measure described in metadata */    Double getUsage();  }

UsageCollector

The UsageCollector SPI defines the protocol which CPBM uses to collect usage from the underlying service on a periodic basis. It is defined as follows:
public interface UsageCollector {    /* Returns a batch of usage data collected from the cloud service. */    public UsageResultSet collect(String startMarker, Date endDate);  }
The UsageCollector is called periodically to collect data from the underlying cloud service. CPBM will schedule a job to collect this data at an operator defined frequency. In any given run CPBM will repeatedly call the UsageCollector to collect usage, until it exhausts available data. The startMarker and endDate determines the range of usage data to collect. When collect is called, the returned usage data:
  • should start from after the startMarker and it must be generated on or before the passed endDate. For better performance, we recommend all implementations of the UsageCollector return usage data in small batches. The batch size should typically be in hundreds. Any subsequent call to UsageCollector.collect() should return the next batch of usageData. In case there is no usageData left, return UsageResultSet with the input startMarker as the marker and null usageData list. CPBM will continuously call UsageCollector.collect() for a given endDate, until all data is exhausted for this time range.
  • In case of conflicting usageData (i.e., duplicate referenceId) CPBM will resolve the conflict by using the first record received.
  • The UsageResultSet object contains List of UsageData. This list should be sorted by UsageData.endDate from oldest to newest. Also, for any two calls to UsageCollector.collect, all of UsageData collected in the later call should be newer (have later UsageData.endDate, than the data collected in the earlier call).

The interaction between CPBM and Cloud Service for collecting usage is shown the figure below

Figure 1. Usage Collection Process


 
또 다른 질문이 있으십니까? 문의 등록

댓글

 
Adding comment, please wait....

Provide Feedback on Article:

Subject:
Comments:*
Zendesk 제공