CI Resource Types
Resource types represent a variety of resources that your Virtualization nodes can provide: containers, virtual machines, their CPU and RAM, disk space, backups, as well as some other resources. Resource types are grouped into classes, depending on their role.
The default resource types are automatically set up when you install the Cloud Infrastructure module on the CloudBlue Commerce management node (their name has CI prefix). These resources are used in Cloud Infrastructure service templates and subscriptions. You can find CI resources in Operations control panel > Products > Resources.
Note: Some resource types have running or stopped at the end of their names. Using these resource types, you can charge customers for using Cloud Infrastructure resources differently, depending on the state of their servers. For example, you can charge customers $0.10 per hour for using 1 GB of RAM when their servers are running and reduce the price to $0.01 when their servers are stopped.
Resource Class |
Resource Type |
Description |
Provisioning Attributes |
Limit |
Unit of Measure |
---|---|---|---|---|---|
CI Virtual Environment Limit | CI Virtual Environments Limit |
Limits the number of servers customers are allowed to create. |
Unlimited |
Unit |
|
CI Virtual Environments
|
CI Free Linux VE |
Enables customers to create and use servers with free Linux distributions, such as CentOS, Fedora, or Ubuntu. |
|
Unlimited |
Hour |
CI Commercial Linux VE |
Enables customers to create and use servers with commercial Linux distributions, such as Red Hat Enterprise Linux. |
|
Unlimited |
Hour |
|
CI Windows VE |
Enables customers to create and use servers with Windows operating systems, such as Windows Server 2008 R2, or Windows Server 2012. |
Unlimited |
Hour |
||
CI CPU Time Used | CI Virtual Machine CPU Usage running |
Charges customers for using CPU resources in virtual machines when they are running. |
ci_running |
Unlimited |
MHzh |
CI Virtual Machine CPU Usage stopped |
Charges customers for using CPU resources in virtual machines when they are stopped. |
ci_stopped |
Unlimited |
MHzh |
|
CI Container CPU Usage running |
Charges customers for using CPU resources in containers when they are running. |
ci_running |
Unlimited |
MHzh |
|
CI Container CPU Usage stopped |
Charges customers for using CPU resources in containers when they are stopped. |
ci_stopped |
Unlimited |
MHzh |
|
CI RAM Used | CI RAM usage running |
Charges customers for using memory in servers when they are running. |
ci_running |
Unlimited |
MBh |
CI RAM usage stopped |
Charges customers for using memory in servers when they are stopped. |
ci_stopped |
Unlimited |
MBh |
|
CI Storage Used
|
CI VE disk usage |
Charges customers for the amount of local disk space used for storing the content of their servers. |
ci_stopped, ci_running |
Unlimited |
GBh |
CI network disk usage running |
Charges customers for the amount of disk space used for storing the content of their running servers in Virtuozzo storage cluster. |
ci_running |
Unlimited |
GBh |
|
CI network disk usage stopped |
Charges customers for the amount of disk space used for storing the content of their stopped servers in Virtuozzo storage cluster. |
ci_stopped |
Unlimited |
GBh |
|
CI image space usage |
Calculates disk space occupied by the customer's server images. |
Unlimited |
GBh |
||
CI backup space usage |
Calculates disk space occupied by the customer's backups. |
Unlimited |
MBh |
||
CI Backups Used | CI daily backup |
Allows customers to back up their servers on a daily basis. |
Unlimited |
Hour |
|
CI weekly backup |
Allows customers to back up their servers on a weekly basis. |
Unlimited |
Hour |
||
Network Bandwidth Limit for CI | CI bandwidth limit running |
Limits network bandwidth for running servers. |
ci_running |
Unlimited |
Kbpsh |
CI bandwidth limit stopped |
Limits network bandwidth for stopped servers. |
ci_stopped |
Unlimited |
Kbpsh |
|
Traffic
|
CI internal incoming traffic |
Counts the traffic received by the customer's servers from other servers on the customer's private network. |
ci_incoming, ci_internal |
Unlimited |
KB |
CI internal outgoing traffic |
Counts the traffic sent by the customer's servers to other servers on the customer's private network. |
ci_outgoing, ci_internal |
Unlimited |
KB |
|
CI external incoming traffic |
Counts the traffic received by the customer's servers from locations outside of the customer's private network. |
ci_incoming, ci_external |
Unlimited |
KB |
|
CI external outgoing traffic |
Counts the traffic sent by the customer's servers to locations outside of the customer's private network. |
ci_outgoing, ci_external |
Unlimited |
KB |
|
CI Load Balancers | CI Load Balancers |
Enables customers to add load balancers to balance incoming traffic among their servers. |
Unlimited |
Hour |
|
CI Cloud Hosting | CI Cloud Hosting |
Enables customers to use and manage Cloud Infrastructure resources. |
Unlimited |
Unit |
Please note that:
- Limits for the Disk space, CPU, and RAM resource types in Cloud Infrastructure service template should be non-zero, otherwise creation of a new cloud server fails.
- You can use the "CPU Usage"-based resource types to offer customers only specific types of servers: containers or virtual machines. For example, to sell only containers, you don't have to include the resource types CI Virtual Machine CPU Usage running and CI Virtual Machine CPU Usage stopped in your service template. Similarly, if you want to offer only virtual machines, you don't have to include the resource types CI Container CPU Usage running and CI Container CPU Usage stopped in your service template.
- The CI internal incoming traffic, CI internal outgoing traffic, CI external incoming traffic, and CI external outgoing traffic resource types are based on the Traffic resource class that is not specific to Cloud Infrastructure.
- If you change the disk space limit activation parameters for CI image space usage and CI backup space usage resource types, the changes will be applied only to the new subscriptions. The existing subscriptions should be synchronized manually. Refer to Billing Provider's Guide >> Managing Subscriptions > Operations with Subscriptions > Synchronizing Subscriptions for details.