A plan is an agreement determined by the admin and assigned to a user to determine the capacity or allowed usage for that user.
Users must accept plans assigned to them by their admins to start using CloudCenter.
A bundle is like a prepaid phone card that allows users to run applications based on the capacity specified in the bundle.
Every CloudCenter plan requires a contract. CloudCenter administrators can enforce the user to accept a Terms of Contract agreement that dictates how long this agreement should last. A CloudCenter contract does not automatically renew when the contract ends. Once a contract ends, users have the option to switch to another contract.
A contract and a plan work together – when you assign a plan you must assign a contract.
If you change a user's plan and also check the Renew Contract check box, it resets the contract period (see Usage Plan for additional context).
If you assign a plan to a user, the user signs a contract for a period of time.
If the user cancels the contract before the contract period ends, the user might be subject to a One-Time Fee.
You can change your plan at any time. However, when you change your plan, you renew your contract period, and will be back to being on the new plan for the entire span of your contract. For example:
You sign a contract for 2 years.
- You change your plan a year after the contract period starts (and you still have a year of your contract remaining).
- As you changed your plan before your contract period ended (2 years), your contract period restarts and you will be on the new plan for 2 more years (NOT one year).
Who Creates Contract, Bundles, or Plans?
The root or tenant admin can create contract, bundles, and plans. The tenant admin can belong to an enterprise or to Cisco depending on the deployment. The CloudCenter documentation generally refers to both as the administrator (or admin). See People for additional context.
If the admin does not set up a contract plan or bundle for a user, then that user can deploy any application.
If the admin sets stipulates that the user requires a payment profile to be setup, then when the user logs into the CCM and accepts the terms of agreement, this user must manually set up a Payment Profile.
Admins have the following flexibility when creating contract dependencies:
- Restrict certain contracts, bundles, and plans to just admins so it is not available to all users.
- Edit or delete contract, bundles, and plans if no users have signed up. If users have signed up, the admin must create a new , , or and revise the required settings.
- Reset the contract start date for an active user.
- Delete a bundle if that assigned to any user.
CloudCenter Subscription Types
The financial controls for each deployment in available in the form of plans and bundles that provide budget and capacity details, charges for each VM, cloud time cost and so forth.
See Finance for related terminology and definition.
VM Hour Subscription (Default)
Prepaid VM-Hour Bundle
Prepaid Budget Bundle
Common Options for All Subscription Types
The following parameters and check box selections are available to all subscription types:
|Only Visible to Tenant Admin|
Bill me for my users cloud usage
|Payment profile is required|
The granular chargeback control provided by CloudCenter compliment its management infrastructure:
- The User Activity Report provides reports and enforces usage at the application level, aggregated across multiple clouds with governance around licensing chargeback. As reports provide a granular level of usage for each tenant, you can enforce departmental chargebacks for the applicable tenants. See Application Deployments Report for additional context.
- You can create plans on a per-customer basis and make these plans visible to particular customers or to all customers for self-service scenarios. The administrator can set up billing cycles and contract lengths, as well as manage chargebacks for these customers. See Plan Configuration for additional context.
- Tenants get complete independence with respect to enforcing chargebacks and generating billing. Admins/tenant admins can use the CCM UI to allow businesses to modify the user interface such as show/hide chargeback to each tenant/departments. See Tenant Billing for additional context.
A payment profile specifies how the user pays for supported services. The cost of the services includes one-time fees, annual fees, monthly subscription, overage fee, storage cost, and other charges agreed to in the CloudCenter contract.
A user can pay for cost of services using the following methods:
|Credit card||Requires a valid credit card number, expiration date, and billing address (Visa, MasterCard, American Express, and Discover).|
|Purchase Order (PO)||Requires a valid billing address for the monthly invoices and allows 30 days for the payment.|
Integrated metering, reporting, and billing ensure that users are always aware of their consumption and are charged appropriately for what they use.
- The Management Agent. Monitoring and metering data is sent to the for reporting purposes. The continues to enforce deployment policies created by the user. For example, a user may have associated a deployment with an auto-scaling policy. The continues to monitor the deployed application and orchestrates scaling as specified by the user in the policy. monitors and meters deployed applications through the
- IT can meter usage and issue departmental chargebacks, so that the users get the immediacy they need but IT controls and enforces the required mechanisms.
- CloudCenter meters end user activity, enforces custom plans, and optionally bills the end user's credit card.
- You can create plans on a universal basis or on a per-application basis for published Marketplace applications. Tenants can create the following types of pricing plans:
- Pre-paid bundles metered by the consumption of compute-hours on the cloud. For example, a vendor can create a 3,000 compute hours/month bundle for application A and a 10,000 compute hours/month bundle for application B.
- Pre-paid bundles metered by the number of application jobs or instances.
- No labels