HP CloudSystem Foundation Uživatelský manuál stáhnout pdf (Strana 4)

Technical white paper | Integrated Billing Solutions with HP CSA 4.00

• Organization In HP CSA terminology an organization contains a set of persons. HP CSA service catalogs and pricing are

assigned to specific organizations. Like HP CSA persons, organizations are defined in LDAP. For private HP CSA

installations, organizations can include departments such as marketing, R&D, and payroll. For public HP CSA installations,

organizations are independent customer organizations. Billing solutions also need to access the internal organization

information.

• Groups

HP CSA does not maintain any internal group relationships. Instead, it relies on directory services to identify

members of groups referenced by HP CSA.

Part 2. Billable Service Conditions

Before costs can be associated with a service order, several criteria must be met:

• Any required approval steps must complete. If a request is denied explicitly or through a time-out, no service instance is

created, and no records are made available.

• After a service request has been approved, a service instance is created. This service instance goes through the

initializing, reserving, and deploying stages before the requested service is online. Status information on service

instances is available during all deployment stages. A billing solution should only bill for a service after it has been fully

deployed.

After a service reaches the deployed stage, valid billing information is made available.

Be aware that in the deployed state, the following service state changes can occur:

• The subscription can expire.

• The subscription can be cancelled by a subscriber or an operator.

• A subscriber may choose to “flex” (modify) the service instance by adding or deleting resources such as disk space,

memory, or CPUs. These resources may have associated costs that need to be tracked and billed.

Part 3. Billable Intervals

When a HP CSA service instance reaches the Deployed state, a billing solution can collect an initial snapshot of the service

instance information. The billing solution must then periodically collect subsequent snapshots of the service instance. As

long as the service continues to run, a billing solution can calculate the cost of those intervals and add them to the customer

billing report.

This high-level flowchart shows how service records can be used to build chargeback reports.

Figure 6. Example of how to create billable intervals

The service costs, currency, and billing interval are specified within the service instance. Figure 7 shows many of the billing-

related fields that are contained in a service instance. Part 4 of this document describes how to collect this information with

API calls.

1 2 3 4 5 6 7 8 9 ... 15 16

Žádné komentáře

HP CloudSystem Foundation Uživatelský manuál Strana 4