Self-service provisioning in Intelligent Infrastructure (II)

On this page:


About the new model

To enable self-service provisioning within the Intelligent Infrastructure (II) environment, CPU, RAM, and Disk resources will be associated with a pool of resources rather than an individual virtual machine (VM). This model will allow II VM admins to create, modify, expand, clone, and destroy VMs at their own discretion.

This new resource pool model will require fiscal approvers to approve resource pools rather than individual VMs. Teams can then manage additions, deletions and other changes to their VMs via self-service as long as they do not exceed the approved resource limits. As UITS transitions to this new model, resource pools will be created for existing VMs that will require fiscal approval.

Pricing

In January 2017, the Storage and Virtualization (SAV) team introduced a simplified costing model as the first step toward self-service VM administration.

Changes involved replacing the "base VM" concept with cost recovery purely on CPU, RAM, and DISK allocations, and consumed storage used for Data Protection Services (DPS).

  • $95/vCPU/year – Allocated CPU
  • $25/GB/year – Allocated RAM
  • $0.79/GB/year – Allocated DISK
  • $0.55/GB/year – Consumed DPS space

See Rates and costs of UITS services.

Pools

Moving forward, II will treat VMs as belonging to a resource pool. This pool will represent a collection of resources (CPU/Memory/Storage) to use across as many different VMs as one wishes. This will enable VM admins to create VMs, allocate resources to them, adjust resources as needed to meet performance demands, and when desired, destroy VMs. The capacity of the pool allows for this self-service within a known maximum expenditure.

Note:
You will only be charged for the resources you use. Costs will fluctuate based upon actual usage each month, with an absolute maximum of the approved pool size.

Resource pools

Resource pools are a method of grouping VMs together. They represent a quota of resources (CPU/Memory/Storage) which can be used for VMs. In addition, resource pools are distinct per data center and per account. As such, you will need a separate resource pool for each account to which various VMs in your group will be billed.

For example, if you have two different accounts to cover your VMs, and VMs for each account exist in both IUDC and ICTC, you will need four resource pools (IUDC Acct 1, IUDC Acct 2, ICTC Acct 1, ICTC Acct 2) in order to contain all VMs. You will need to plan resources accordingly for each resource pool to contain the VMs associated with it.

Note:
Once you reach the capacity of a particular resource (e.g., CPU, RAM, Disk), you will not be able to add any more of that resource to any VMs in that pool unless and until you either reduce/retire resources on another VM in the pool or request that the pool quota limits be increased.

Requests

A member of a particular organization will request resource pools be created and modified; see more about organizations in the Resource Allocation Center (RAC) system. Requesters will specify their estimate of the maximum resource use for the year in terms of number of CPUs, GB of memory, and TB of storage. Requesters should anticipate potential growth over the course of the year in order to avoid having to expand the capacity of the pool during the year. Expansion will require a new request and fiscal approval. Within the RAC system, fiscal approvers will be provided the maximum cost for that pool assuming all resources are consumed; however, you will only be charged for the resources that are actually consumed. For example, if you approve a pool for 10 CPUs and only actually use two, you will only be charged for two.

Requests will consist of the following:

Label: This is a name that will be easily identifiable by your group. At a minimum, we recommend that it contain the data center on which this pool will reside and the funding source (i.e., account) to which VMs in this pool will be billed.

Data Center: A pool must be tied to a specific data center. This allows you to control where the VM is hosted.

CPUs: Maximum number of CPUs that should be available for various VMs in this pool to use.

Memory: Maximum amount of memory in gigabytes (GB) that should be available for various VMs in this pool to use.

Storage: Maximum amount of storage in terabytes (TB) that should be available for various VMs in this pool to use.

VLAN IDs: Comma-separated list of VLAN IDs that your organization manages that should be available for VMs in this pool to use.

Data Protection Services (DPS): Indicate whether the VMs in this pool are eligible for CommVault AllDisk backup services; see How do I determine the type of data protection used for my Intelligent Infrastructure virtual machines?

Cost summary calculations

On the request form and the fiscal approval page, there is a section that presents a cost summary for the request. This "Maximum Annual Cost Summary" represents the maximum annual potential cost that this pool could represent.

CPUs: CPU cost is calculated by taking the number of CPUs requested * the current annual rate per CPU.

Memory: Memory cost is calculated by taking the number of GB of memory requested * the current annual rate per GB.

Storage: Storage cost is calculated by taking the number of GB of storage requested * the current annual rate per GB.

Data protection (DPS): DPS cost is calculated by estimating the likely usage using the following formula:

(((S * 0.8 * 2) + (S * 0.8 * 0.08 * 12)) / 2) * Sr

Where S is the number of GB of storage requested and Sr is the rate per GB of storage. This formula is created by assuming backup data will constitute 80% of total requested storage (in GB), will increase at an 8% growth rate, and can be stored at a 2:1 deduplication rate. In addition, UITS keeps two full and twelve incremental backup instances.

See Example for a demonstration of how this calculation would be carried out with actual numbers. Costs will fluctuate based upon actual usage each month, with an absolute maximum of the approved pool size.

Example

The following example uses 2017/2018 charge rates.

A request is submitted for a pool consisting of 20 CPUs, 50 GB of memory, and 1 TB (1024 GB) of storage, with DPS enabled.

The resulting Maximum Annual Cost Summary would look like this:

Item Subtotal
CPUs $1900.00
Memory $1,250.00
Storage $808.96
Data protection $666.83
Estimated total $4,625.79
CPUs: 
  20 CPUs * $95/CPU = $1900

Memory: 
  50 GB memory * $25/GB = $1250

Storage: 
  1 TB (1024 GB) storage * $0.79/GB = $808.96

DPS:
  1 TB (1024 GB) storage
  (((1024 GB * 0.8 * 2) + (1024 GB * 0.8 * 0.08 * 12)) / 2) * $0.55/GB/yr
  ((1638.4) + (786.432) / 2) * $0.55
  (2424.832 / 2) * $0.55
  1212.416 * $0.55
  $666.83

The estimate reflects the maximum cost if all requested resources are fully utilized within the pool. This estimate also assumes the entire storage capacity is using DPS. This estimate should be treated as an absolute maximum, where costs will fluctuate based on actual usage each month.

Approval

All new resource pool requests as well as changes to existing pools must be approved by the appropriate fiscal officer prior to the pool being created or modified. Fiscal officers will be notified by the Kuali Enterprise Workflow system that they have action items to approve. An approval page similar to the RAC resource pool will be displayed, listing all the resource maximums as well as maximum annual cost summary, but will contain Approve and Disapprove buttons at the bottom. The cost summary reflects the maximum cost if all requested resources are fully utilized within the pool. This estimate also assumes the entire storage capacity is using DPS. As such, the estimate should be treated as an absolute maximum where costs can/will fluctuate below that maximum based on actual usage each month.

Billing

Each month, the current VMs associated with your organization will be tallied. The resources allocated to each VM (as well as any storage used by VM backups) will be calculated, and the resulting charges will be billed against the account associated with the resource pool in which each VM resides. This total should never represent a sum greater than the maximum cost estimate.

Annual renewal

In an effort to keep fiscal officers informed about the charges hitting their accounts, resource pools will require annual approval. The RAC system will automatically generate a new workflow approval action. This renewal should take place in January.

Questions

If you have additional questions or concerns, contact the Storage and Virtualization team.

This is document apjh in the Knowledge Base.
Last modified on 2017-12-07 12:41:56.

  • Fill out this form to submit your issue to the UITS Support Center.
  • Please note that you must be affiliated with Indiana University to receive support.
  • All fields are required.

Please provide your IU email address. If you currently have a problem receiving email at your IU account, enter an alternate email address.

  • Fill out this form to submit your comment to the IU Knowledge Base.
  • If you are affiliated with Indiana University and need help with a computing problem, please use the I need help with a computing problem section above, or contact your campus Support Center.

Please provide your IU email address. If you currently have a problem receiving email at your IU account, enter an alternate email address.