8.1. Compute and Disk Service Offerings
A service offering is a set of virtual hardware features such as CPU core count and speed, memory, and disk size. The CloudStack administrator can set up various offerings, and then end users choose from the available offerings when they create a new VM. A service offering includes the following elements:
CPU, memory, and network resource guarantees
How resources are metered
How the resource usage is charged
How often the charges are generated
For example, one service offering might allow users to create a virtual machine instance that is equivalent to a 1 GHz Intel® Core™ 2 CPU, with 1 GB memory at $0.20/hour, with network traffic metered at $0.10/GB. Based on the user’s selected offering, CloudStack emits usage records that can be integrated with billing systems. CloudStack separates service offerings into compute offerings and disk offerings. The computing service offering specifies:
The disk offering specifies:
8.1.1. Creating a New Compute Offering
To create a new compute offering:
Log in with admin privileges to the CloudStack UI.
In the left navigation bar, click Service Offerings.
In Select Offering, choose Compute Offering.
Click Add Compute Offering.
In the dialog, make the following choices:
Name: Any desired name for the service offering.
Description: A short description of the offering that can be displayed to users
Storage type: The type of disk that should be allocated. Local allocates from storage attached directly to the host where the system VM is running. Shared allocates from storage accessible via NFS.
# of CPU cores: The number of cores which should be allocated to a system VM with this offering
CPU (in MHz): The CPU speed of the cores that the system VM is allocated. For example, “2000” would provide for a 2 GHz clock.
Memory (in MB): The amount of memory in megabytes that the system VM should be allocated. For example, “2048” would provide for a 2 GB RAM allocation.
Network Rate: Allowed data transfer rate in MB per second.
Offer HA: If yes, the administrator can choose to have the system VM be monitored and as highly available as possible.
Storage Tags: The tags that should be associated with the primary storage used by the system VM.
Host Tags: (Optional) Any tags that you use to organize your hosts
CPU cap: Whether to limit the level of CPU usage even if spare capacity is available.
Public: Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name.
Click Add.
8.1.2. Creating a New Disk Offering
To create a system service offering:
Log in with admin privileges to the CloudStack UI.
In the left navigation bar, click Service Offerings.
In Select Offering, choose Disk Offering.
Click Add Disk Offering.
In the dialog, make the following choices:
Name. Any desired name for the system offering.
Description. A short description of the offering that can be displayed to users
Custom Disk Size. If checked, the user can set their own disk size. If not checked, the root administrator must define a value in Disk Size.
Disk Size. Appears only if Custom Disk Size is not selected. Define the volume size in GB.
(Optional)Storage Tags. The tags that should be associated with the primary storage for this disk. Tags are a comma separated list of attributes of the storage. For example "ssd,blue". Tags are also added on Primary Storage. CloudStack matches tags on a disk offering to tags on the storage. If a tag is present on a disk offering that tag (or tags) must also be present on Primary Storage for the volume to be provisioned. If no such primary storage exists, allocation from the disk offering will fail..
Public. Indicate whether the service offering should be available all domains or only some domains. Choose Yes to make it available to all domains. Choose No to limit the scope to a subdomain; CloudStack will then prompt for the subdomain's name.
Click Add.
8.1.3. Modifying or Deleting a Service Offering
Service offerings cannot be changed once created. This applies to both compute offerings and disk offerings.
A service offering can be deleted. If it is no longer in use, it is deleted immediately and permanently. If the service offering is still in use, it will remain in the database until all the virtual machines referencing it have been deleted. After deletion by the administrator, a service offering will not be available to end users that are creating new instances.
