Information
This article describes Resource Classes, Resource Types and basic hints on Service Template creation to provide Cloud Infrastructure services to customers.
Resource Classes
According to Provider's Guide > Cloud Infrastructure Hosting > Exploring Resource Classes in Cloud Infrastructure:
- CI backups used: Allow customers to create backups of their servers at specified intervals.
- CI CPU time used: Charge customers for using CPU resources in a specific type of servers.
- CI Load Balancers: Allow customers to use load balancers to balance incoming traffic among their servers.
- CI RAM used: charge Customers for using memory in their servers.
- CI storage used: charge Customers for disk space used by their servers.
- CI Virtual Environments: Charge customers for running different groups of operating systems in their servers.
- CI Virtual Environment limit: Limit the maximum number of servers customers are allowed to create.
- Network bandwidth limit for CI: Charge customers for network bandwidth allocated to their servers.
- CI Cloud Hosting: Allow customers to use and manage Cloud Infrastructure resources (this resource class was added in POA 5.5)
Resource Types
For your convenience there are pre-defined default Resource Types for Cloud Infrastructure. According to Provider's Guide > Cloud Infrastructure Hosting > Exploring Default Resource Types in Cloud Infrastructure:
- CI Virtual Environments Limit: To limit the number of servers customers are allowed to create.
- CI Free Linux VE: To charge customers for using servers that run free Linux distributions, such as CentOS, Fedora, or Ubuntu.
- CI Commercial Linux VE: To charge customers for using servers that run commercial Linux distributions, such as Red Hat Enterprise Linux.
- CI Windows VE: To charge customers for using servers that run Windows operating systems, such Windows 7 or Windows Server 2008 R2.
- CI Virtual Machine CPU Usage running: To charge customers for using CPU resources in virtual machines when they are running.
- CI Virtual Machine CPU Usage stopped: To charge customers for using CPU resources in virtual machines when they are stopped.
- CI Container CPU Usage running: To charge customers for using CPU resources in Containers when they are running.
- CI Container CPU Usage stopped: To charge customers for using CPU resources in Containers when they are stopped.
- CI RAM Usage running: To charge customers for using memory in servers when they are running.
- CI RAM Usage stopped: To charge customers for using memory in servers when they are stopped.
- CI VE disk usage: To charge customers for using disk space in their servers.
- CI image space usage: To charge customers for using disk space occupied by their images.
- CI daily backup: To allow customers to back up their servers on a daily basis.
- CI weekly backup: To allow customers to back up their servers on a weekly basis.
- CI bandwidth limit running: To charge customers for using network bandwidth when their servers are running.
- CI bandwidth limit stopped: To charge customers for using network bandwidth when their servers are stopped.
- CI internal incoming traffic: To charge customers for the amount of internal traffic coming into their servers.
- CI internal outgoing traffic: To charge customers for the amount of internal traffic outgoing from their servers.
- CI external incoming traffic: To charge customers for the amount of external traffic coming to their servers.
- CI external outgoing traffic: To charge customers for the amount of external traffic outgoing from their servers.
- CI Load Balancers: To allow customers to use load balancers to balance incoming traffic among their servers.
The following resource types were added in POA 5.5:
- *CI network disk usage running: To charge customers for the amount of disk space used for storing the content of their running servers in a Parallels Cloud Storage cluster.
- CI network disk usage stopped: To charge customers for the amount of disk space used for storing the content of their stopped servers in a Parallels Cloud Storage cluster.
- CI backup space usage: To charge customers for using disk space occupied by their backups.
- CI Cloud Hosting: To allow customers to use and manage Cloud Infrastructure resources.
Minimum set of resources in PACI Service Template
According to Provider's Guide > Cloud Infrastructure Hosting > Minimum Set of Resource Types for Cloud Infrastructure Service Templates:
- CI Virtual Machine CPU Usage running
- CI Virtual Machine CPU Usage stopped
- CI Container CPU Usage running
- CI Container CPU Usage stopped
- CI RAM usage running
- CI RAM usage stopped
- CI VE disk usage
- CI image space usage
- CI bandwidth limit running
- CI bandwidth limit stopped
- CI internal incoming traffic
- CI internal outgoing traffic
- CI external incoming traffic
- CI external outgoing traffic
- CI Load Balancers
- CI Virtual Environments Limit
- Additional Staff Members
- IP addresses
- IPv6 addresses
NOTE: If you plan to provision only virtual machines, then include only CI Virtual Machine CPU Usage running and CI Virtual Machine CPU Usage stopped resources into a service template. If you want to provide containers only, then include CI Container CPU Usage running and CI Container CPU Usage stopped.
The following changes took place in POA 5.5:
- CI Cloud Hosting is required.
- CI VE disk usage can be replaced or complimented by CI network disk usage running and CI network disk usage stopped depending on what type of storage you want to use: local disk, Parallels Cloud Storage clusters, or both.
- Additional Staff Members resource is no longer required.
Also see
112633 How to create new OS group for Cloud Infrastructure
112636 Public IP assignments for Online Store-created CI servers
113218 How to change default values displayed on PACI Screen in Online Store
113188 PACI Load Balancers accounting logic
114072 Overselling PACI resources
113553 Cloud Infrastructure: IP Address resource usage accounting