|Application Fee||The fee charged when users import an application that has an associated cost (one-time fee, monthly fee, or a run-time fee). See Application Fee for additional context.|
|Base price||The fee associated with the annual subscription plan.|
Ais a plan type that gives the user a fixed dollar amount of usage or a fixed VM-hour limit.
|Concurrent VMs||The number of simultaneously running VMs permitted to each user under a monthly usage plan|
Every CloudCenter plan requires a. 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.
|Discount rate||Contracts sometimes have a discount rate that provides users an incentive to sign a longer contract. Typically, a longer contract length has a deeper discount rate. This discount is applied to a plan's base one-time fee, annual fee, bundle price, and monthly subscription fee (Cisco does not discount overage and storage fees).|
|Minimum charge||The minimum number of minutes deducted from a plan when a user runs an application.|
|Monthly VM hours||The number of VM hours credited to the user each month.|
|Maximum Running VMs||The number of VMs permitted to the user each month.|
|One-time Fee||The fee is charged each time the user changes from one plan to another.|
|Overage rate||The cost per hour if a user exceeds the Overage Limit.|
Ais 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.
Runtime refers to the number of hours:
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.
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).
If the admin does not set up a contract plan or bundle for a user, then that user cannot deploy any application.
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 thatassigned to any user.
CloudCenter Plan Types
When creating a plan in CloudCenter, the administrator must select one of five possible plan types that are summarized in the following table.
VM Hour Subscription (Default)
Common Options for All Plan Types
The parameters and check box selections that the following table describes are available to all plan types.
|Only Visible to Tenant Admin|
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 and enforces custom plans.
- No labels