Set User Billing Plan Prices And Resource Limits

You can set pricing and limits for cloud resources for each billing plan.

To add a resource limit to a billing plan:

  1. Go to your Control Panel's Billing Plans menu.
  2. The screen that appears shows all billing plans currently available. Click the Actions button next to the plan in question, then click Resources.
  3. The screen loads all the resources currently assigned to this billing plan. Now you can add limits to the following resources. If nothing added, the user gets unlimited resources:

If you delete a resource associated with the billing plan from the cloud, the resource is also deleted from a billing plan. If there are no other resources of this type added to Billing Plan, the resource will become unlimited.

If you remove from the billing plan a resource that has virtual server(s) running on it, the pricing for that resource will be removed for such VSs. This behavior refers to user VS limits, template stores, edge groups, recipe groups, backup server zones, guaranteed minIOPS and instance packages.


User VS limits

To set resource limits for user virtual servers:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the User VS limits.
  3. In the window that pops up, select the resource type from the drop-down menu and click Add Resource.
  4. Set limits foruservirtual servers:

    • Virtual Servers Limits (Max) - the maximum number of virtual servers users can create.

      This parameter affects the number of virtual servers, VSs in Federation and load balancers users can create.

    • Autoscaling Limits (Free, Max, Price) – the number of VSs using Autoscaling that user can create for free as well as the total amount of such VSs. You can also set the price for theVSs using Autoscaling (per VS).
    • Templates, ISOs & Backups Storage (Disk size for free, Disk size, Price) - the amount of free disk space users get for backup, ISO and template storage, and the total amount of disk space they can use for backups, ISOsand templates. Disk space is measured inGB, and priced per hour.
    • Backups Limits (Free, Max, Price) - the number of backups users can create for free as well as the maximum number of backups, according to their template/backup storage space limit. This parameter applies only to manual backups. You can set prices per backup per hour. Alternatively, use Templates & Backups Storage limit to charge per GB of disk space the backup actually takes.

      The limits for Templates, ISOs & Backup Storage and Backup Limits will apply only if you use Compute resources for disk-related actions (basic backup scheme) in your cloud. 

      If there are backup servers in your cloud:

      • set the Backup server zone limits as required;
      • set the Backups Limits and Templates, ISOs & Backups Storage (User VS Limit section) max limit to 0 to prevent creating both manual and auto-backups on compute resources.
    • Template Limits (Free, Max, Price) - the number of user templates which can be created for free as well as the maximum number of user templates, according to their template/backup storage space limit. You can set prices per user template per hour. Alternatively, use Templates & Backups Storage limit to charge per GB of disk space the template actually takes.
    • Customer network limits - (Free, Max, Price) - the number of customer networks users can create for free, and the maximum number of customer networks they can create.
    • ISO Limits (Free, Max, Price) - the number of ISOs users can create for free as well as the maximum number of ISOs, according to their template/ISO/backup storage space limit. You can set prices per ISO per hour. Alternatively, use Templates, ISOs & Backups Storage limit to charge per GB of disk space the ISOs actually take.
    • Acceleration (Free, Max, Price) - the number of virtual servers users can accelerate using an accelerator for free as well as the maximum number of accelerated VSs. You can set prices per accelerated VS per hour. Be aware that billing starts as soon as acceleration is activated for VS.

      If there are accelerated virtual servers in the cloud, these VSs will be still billed for acceleration even if you delete the accelerator.

    • Application Servers (Max) - the maximum number of application servers users can create.
    • DRaaS (Price) -  the additional prices for VSs that have DRaaS enabled: for disk size per GB per hour, for RAM per MB per hour, for CPU core per core per hour, for CPU per percent per hour or CPU per unit per hour.
    Billing plan resource limits are specified per user, not per VS. So, a user assigned to a plan with a maximum available disk size of 500Gb cannot exceed that limit across all of their virtual servers.


Limits for template store 

If you want your users to be able to create application servers, make sure to include the template store that contains the template for application servers into the user's billing plan.

When you add template store limits to a billing plan, you limit the number of preconfigured system templates available to users signed up for this billing plan – they can only choose from templates specified.

To add resource limits for template store:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the Limits for Template Store box.
  3. In the window that pops up, select the target template distribution from the drop-down menu and click Add Resource.  


Limits for recipe groups

When you add a recipe group to a billing plan, you limit the number of preconfigured plug-ins called recipes to users signed up for this billing plan - they can only choose from the recipe groups specified. If nothing added to a billing plan, the users can use all the recipe groups in the system.

User's own recipes will not be included into the billing plan.


To add resource limits for recipe groups:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the Limits for Recipe Groups box.
  3. In the window that pops up, select the target recipe group from the drop-down menu, and click Add Resource.  



Limits for compute zones

The master bucket is added to each billing plan automatically. The master bucket sets the total amount of limits and prices that all compute zones using the bucket will have.  All servers running on a compute resource within this zone will come within these values. You can use custom resource limits for compute zones alongside with master bucket limits.

You can also reset the limits and prices and set them to default (used in master bucket). In this case your current settings will be overridden.

To add limits for Compute zones:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Scroll down to the Limits & Pricing for Compute Zones section and set the following limits for the Master Buckets resource:

    CPU
    • the number of CPU cores that users get for free
    • the maximum number of CPU cores they can request under this plan
    • the price per CPU core per hour, for VSs powered on
    • the price per CPU core per hour for VSs powered off

    CPU Share

    • the CPU share % that users get for free
    • the maximum CPU share % they can request under this plan
    • the prices per CPU share % per hour, for VSs powered on
    • the prices per CPU share % per hour, for VSs powered off

    CPU Units - move the Use CPU Units slider to the right to enable CPU Units instead of CPU shares and CPU cores.

    • the CPU units that users get for free
    • the maximum CPU units they can request under this plan
    • the prices per CPU unit per hour, for VSs powered on
    • the prices per CPU unit per hour, for VSs powered off

      • Currently CPU Units are available for Xen and KVM Compute resources only.

      • Do not use CPU Units for KVM5 Compute resources, Baremetal, VMware servers, and load balancers.

    Memory

    • the amount of RAM users get for free
    • the maximum RAM they can request under this plan
    • the prices for RAM for VSs powered on
    • the prices for RAM for VSs powered off. RAM is measured in MB and priced per hour.

  3. Set the VS creation properties which specify the minimum amount of resources available for users in a server creation wizard form. You can also set the default values for CPU and CPU share resources. Each server created based on this particular Compute zone will be created with these default values and CPU/CPU share parameters won't be shown in a server creation wizard.

    CPU
    • set the minimum number of CPU cores for a server
    • alternatively, configure the default values which set the amount of CPU cores automatically added per each VS (move the Use default values slider and set the values). It is only possible to enable the Use default values option when resource prices and max limit are not set. 

    CPU Priority (refer to Billing Calculation section for details on how CPU priority is calculated)
    • set the minimum CPU priority for a server
    • alternatively, configure the default values which set the CPU Priority automatically assigned when creating a VS (move the Use default values slider and set the values). It is only possible to enable the Use default values option when resource prices and max limit are not set.

    Memory
    • set the minimum RAM available when creating a VS.

      You can set default CPU and CPU priority settings in the billing plan. This option is available only if limits and prices for the CPU and CPU shares are set to zero for the corresponding zone. Specifying the default CPU and/or default CPU priority amount will result in VSs always being created with the corresponding CPU/CPU priority amount for the given Compute zone.

      To prevent users from choosing a Compute resource when creating a VS, but still enable them to select the type of virtualization, use Show Compute resources on Virtual Machine creation permission. For details, refer to  Permissions List section.



  4. Click the "+" button in the upper right corner of the Limits & Pricing for Compute zones box to add a custom Compute zone.
  5. In the window that pops up:

    1. Select the target Compute zone from the drop-down menu.
    2. Specify if this Compute zone should use the limits set for a Master Bucket
    3. Specify if CPU units should replace CPU shares and CPU cores for this Compute zone.
    4. Click the Add resource button. 

  6. Set the limits and pricing. For details, refer to step 2. 
  7. To reset the Compute zone limits and pricing to those specified for Master Bucket, move the slider in the Use Master Bucket? column to the right.


If you'd like to prevent your users from choosing a Compute resource when creating a VS, but still enable them to select the type of virtualization, use Show Compute resources on Virtual Server creation permission. For details, refer to Permissions List section.


Limits for data store zones

The master template is added to each billing plan automatically. When applying the master template zone limits to a data store zone, each data store within this zone will have the same limit type (currently hourly only), limits, and prices as the master template. You can use data store zones with custom limits alongside with master template zone limits.

You can also reset the limits and prices and set them to default (used in master template). In this case your current settings (limit type, resource limits and prices) will be overridden. 

When a data store zone is added to the master template, its limit type (hourly or monthly) is overridden by the master template. If a zone is removed from the master template, it's limit type will become the same as it was before the master template was applied to the zone.

To add limits for data store zones:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Scroll down to the Limits & Pricing for Data Store Zones section and set the following limits for the Master Templates resource:

    • Disk Size - the disk space users get for free, and the maximum disk space they can request under this plan. You can set prices for disk space for VSs powered on and off. Disk size is priced per GB per hour.
    • Data read - set the amount of data read users can send for free, and the price over free units. Data read is measured in GB and priced per GB.
    • Data written - set the amount of data written users can send for free, and the price over free units. Data written is measured in GB and priced per GB.
    • Input requests - specify the number of input requests per hour users can get for free and the price over free units. Input requests are measured in millions and priced per million requests.
    • Output requests- specify the number of output requests per hour users can get for free and the price over free units. Output requests are measured in millions and priced per million requests.

  3. Click the "+" button in the upper right corner of the Limits & Pricing for Data Store zones box to add a custom data store zone.
  4. In the window that pops up:
    1. Select the target data store zone.
    2. Select the limit type: hourly or monthly. 
      When setting hourly resource type, the user will be billed only for the disk size that exceeds the hourly free limit. The next hour, the user will again have the free hourly limit available and will pay only for the overused units.
      When setting monthly resource type, the limits for resources are set per month rather than per hour. After the free limit is exceeded, all the units overused during the month will be billed hourly according to the price set.
      For details on hourly/monthly billing calculation, see Billing Calculation.
    3. Specify if this data store zone should use the limits set for a Master Defaults zone.
    4. Click the Add resource button. 
  5. Set limits and prices for the data store zone. For details, refer to Step 2. 
  6. To reset the data store zone limits and pricing to those specified for Master Template resource, move the slider in the Use Template Master? column to the right. In this case your current settings will be overridden.

 


Limits for network zones

The master template is added to each billing plan automatically. When applying the master template limits to a network zone, each network zone will come under these limit type (currently hourly only), resource limits, and prices as the master template. You can use network zones with custom limits alongside with master template limits.

You can also reset the limits and prices and set them to default (used in master template).

When a network zone is added to the master template, its limit type (hourly or monthly) is overridden by the master template. If a zone is removed from the master template, it's limit type will become the same as it was before the master template was applied to the zone.

To add limits for network zones:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Scroll down to the Limits & Pricing for Network Zones section and set the following for Master Templates zone:

    • IP address (Free, Max, On, Off) - the number of IP addresses users get for free, and the maximum number of IP addresses they can request under this plan. IP addresses are priced per hour.
    • Port speed - set the amount of port speed for each server user gets for free, and the maximum port speed amount user can request. The port speed is measured in MB per second and priced per MB.
    • Data reсeived - set the amount of data received users can send for free, and the price over free units. Data received is priced per GB.
    • Data sent - set the amount of data sent users can send for free, and the price over free units. Data sent is priced per GB.

  3. Click the "+" button in the upper right corner of the Limits & Pricing for Network Zones box to add a custom network zone.
  4. In the window that pops up:

    1. Select the target network zone.
    2. Select the limit type: hourly or monthly. 
      When setting hourly resource type, the user will be billed only for the disk size that exceeds the hourly free limit. The next hour, the user will again have the free hourly limit available and will pay only for the overused units.
      When setting monthly resource type, the limits for resources are set per month rather than per hour. After the free limit is exceeded, all the units overused during the month will be billed hourly according to the price set.
      For details on hourly/monthly billing calculation, see Billing Calculation.
    3. Specify if this network zone should use the limits set for a Master Defaults zone
    4. Click the Add resource button. 

  5. Set limits and prices for the network zone. For details, refer to step 2. 

  6. To reset the network zone limits and pricing to those specified for Master Template resource, move the slider in the  Use Master Template? column to the right. In this case your current settings will be overridden.


    By adding Compute resource, data store and network zone resources to a billing plan, you can add to the overall limits enforced by the billing plan by limiting what amount of resource is available in different zones of your cloud.
    For example: a user is assigned to a billing plan with a total limit of 10 IP addresses. The plan is associated with 2 network zones: NZ1, a high performance zone, which has a limit of 2 IPs; and NZ2, which has a limit of 8 IPs.
    In this case, the user would be able to use a maximum of 10 IPs for all of their VSs - of which, up to 2 may be located in NZ1, and up to 8 located in NZ2.

Limits for edge groups

To add limits for edge groups:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the Limits for edge groups box.
  3. In the window that pops up, select the target edge group from the drop-down menu, and click Add Resource.  
  4. Set the prices for the edge group per GB.


    If no limits or edge groups are specified, no edge groups will be available to this billing plan.

       


Limits for backup server zones

To add limits for backup server zones:

Auto-backups are only billed per disk size. Backup quantity limit is not applied to this backup type.

Manual backups are billed per backups disk size and per backup quantity limit.


  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the Limits for backup server zones box.
  3. In the window that pops up, select the target backup server zone from the drop-down menu, and click Add Resource. 

  4. Set limits and prices for the backup server zone:
    • Backups - set the amount of backups users get for free, and the total amount they may use. You can set prices for backups.
      Quantity backup limit only affects manual backups (created by clicking the Take backup button).
    • Backup Disk Size - set a maximum amount of backup server space users get for free, and total amount of backup server space users can request. When the backup server space is exceeded, you can take a backup, but you cannot restore it unless the size is freed up. You can set prices for backup server space. Backup server space is measured in GB.

      Please also set the Backups max limit to 0 in the User VS limits to prevent creating backups on compute resources.

    • Templates - set the amount of templates users can send for free, and the prices for each template over that limit.
    • Template Disk Size  - set the amount of template disk size users can receive for free, and the prices for each GB over that limit. Template disk size is measured in GB, and priced per GB.
  5. If you specify backup server zone in the billing plan, users will be able to use only the backup servers specified in the backup server zones assigned to their billing plan.
  6. If the billing plan does not contain any assigned backup servers zone, users will be able to use any available Backup Server.

 


Limits for guaranteed minIOPS

(for billing plans with SolidFire data stores added)


To add limits for guaranteed minIOPS:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the Limits for guaranteed minIOPS box.
  3. In the window that pops up, select the target data store zone from the drop-down menu, and click Add Resource.  

    Limits for IOPS are set for a whole data store zone.



Limits for Instance packages
When you add instance packages limits, you enable users signed up for this billing plan to select predefined resource packages in the virtual server creation wizard. If you add compute/data store/network zones to this section, you limit the zones to which the instance package will apply. If no zones are added, the instance packages will be applied to all zones within this billing plan. 
Add limits for Instance packages
To add limits for instance packages:
  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the "+" button in the upper right corner of the Limits for instance packages box.
  3. In the window that pops up, select the target instance package and the compute zone(s), data store zone(s) and network zone(s) the instance package will apply to. Click Add Resource.

  4. Set the price that will be charged per VS powered on/off  for each appropriate instance package. You can also set the pricing for overused bandwidth per GB.
  • If you do not select any compute resource/data store/network zones, the instance package will apply to all compute resource/data store/network zones available for the user.
  • It is advisable that you limit the user's billing plan by the compute zones that have enough resources to support the instance package(s) you add to the user's billing plan. If the user selects a compute zone that does not have enough resources during virtual server creation, they will not see all the instance packages available to them, but only those that have resources compatible with the chosen compute zone.
  • You can update instance package prices in billing plan even if this instance package has been used during virtual server creation. Instance package price update takes effect on VS's price approximately five minutes after updating. Also you can update zones for an instance package in billing plan even if this instance package has been used during virtual server creation.
  • If you have VSs created with the instance package on a particular compute zone, you cannot remove this compute zone from instance packages limits.
  • If no compute zones are added to limits for instance packages, you can  edit limits and add a compute zone, on which instance package VS is already built. Another compute zones can not be added.


For the info on how the instance packages are billed, refer to Billing for Instance Packages document.

Modify/delete Limits for Instance packages

If required, you can edit the zones the instance package applies to:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the Actions button next to the instance package you are interested in and select Edit.
  3. In the window that pops up, edit the compute resource/data store/network zone(s) and click Update.

If there is a VS created on a compute resource/data store/network zone you remove while editing the billing plan, the VS will still be billed according to the instance package.

Also, you can delete instance packages from the billing plan:

  1. Go to the billing plan resources screen (Billing Plans > Resources).
  2. Click the Actions button next to the instance package you are interested in and select Delete. You will be asked for confirmation before the instance package is removed from the billing plan.

Instance packages that have been used during virtual server creation cannot be deleted.