Add Zones to Federation


This document applies to Sellers. If you're a Buyer, refer to the Buyers section of this guide.


To add zones to Federation, at first you need to configure all the necessary resources in your cloud. After that you can proceed to adding compute zones to Federation.

When publishing a zone, you indicate the backup, network and data store zones that will supply storage and IP address to you federated compute zone. You also indicate the limits for the zone's compute, network, backup and data store resources. After you publish a zone, buyers will be able to subscribe to your federated zone and use its resources.

If you are adding a public zone to the Federation, the pricing for the zone's resources are set according to the pricing tier you select. If required, you can later switch your zone from public to private

If you wish to set your own pricing for the zone you add to the Federation, you can publish a private zone. In this case, only the buyers you provide with a trust token will be able to subscribe to your zone. Other buyers will not see this zone in Federation. Note that you can not change the zone from private to public after you publish the zone. However, if required you can remove the zone from Federation and publish it again as public.

After yo publish a zone you can change pricing and resource limits for private zones. For public zones, you can only change resource limits. Fore more information refer to Edit Federated Zone.

  • You need to be running OnApp 5.0 or higher to add compute zones to Federation. Sellers running on versions prior to OnApp 5.0 can no longer publish new zones.
  • You can only publish zones of the virtual type to Federation. For more information refer to Zone Types.
  • vCenter compute zones can only be published as private federated zones.
  • If you want to disable prices completely you can do so by enabling the Disable billing slider at the Edit System Configuration page. It is possible to disable billing only if there are no compute zones that are added to Federation or any compute zones subscribed from the Federation on your OnApp CP.



Add Zone to Federation



To sell a compute zone to Federation:

Before you add a zone, please ensure you have reviewed the Seller Pricing Tiers for Compute Zones section.

  1. Configure your cloud.

  2. When the compute zone is created, the list of all compute zones will be displayed at Control PanelSettings > Compute Zones. Click Actions > Add to federation next to a required zone.
  3. Configure the federated zone in the wizard that appears: 


Step 1 of 5. Start




Fill in the following fields:

  • Provider - enter the provider name
  • Data store zone - select a data store zone from the drop-down box. Make sure that selected data store zone has no data stores attached to compute resources directly. The data stores should be attached to compute zones.
  • Backup server zone - select a backup server zone from a drop-down box. 
  • Network zone - select a network zone from a drop-down box. Make sure that selected network zone has no networks attached to compute resources directly. The networks should be attached to compute zones.
  • Template group - select a template group from the drop-down box. All the templates which are added to this group will be available to buyers who sign up for this federated zone. Later you can add templates to this template group after the zone is published to buyer. In this situation the templates will be synchronized and appear in respective buyer's template group. If a seller deletes a template from a group, the template will not be removed from buyer's federated template group.
  • Move the Private slider to the right if you want to make this Federated zone private. Otherwise, the zone will be pubic and all buyers in the Federation will be able to view and subscribe to this zone. If the zone is made private, only those buyers who have received a trust token from the seller can access the zone. For more information see Make Federated Zone Private. vCenter compute zones can only be published as private federated zones.
  • Note that you will not be able to switch a private zone to public once it is published.
  • Description - add a necessary description.


Step 2 of 6. Tiers




Select the pricing tier for your zone if you are adding a public zone:

  • DEV - a tier for non-critical workload
  • PRO - a tier for production environments
  • ENTERPRISE - a tier for enterprise workloads and/or mission critical data. This tier is currently unavailable.

For public zones, this step also displays the pricing for the zone's resources depending on the selected tier:

  • CPU (Cores) - the price per CPU core/per hour, for VSs powered on/off
  • RAM (MB) - the price per RAM (MB) per hour, for VSs powered on/off
  • Disk (GB) - the price per GB of disk space per hour for VSs powered on/off
  • IP - the price per IP address/per hour for VSs powered on/off
  • Data sent (GB) - the price per GB of data sent/per hour for VSs 
  • Data received (GB) - the price per GB of data received/per hour for VSs


For both public and private zones, configure the following options for you zone. The configuration of tier options does not influence the pricing for the public zones. The default value for the tier options is 'NO'.

  • HA - whether HA is available for the compute zone. For the DEV tier you can select HA meaning that HA is available, or Local indicating that High Availability is not provided for the zone. For PRO and ENTERPRISE tiers HA is available by default.
  • SLA - this parameter indicates the number by which the cost of the resources provided to the buyer will be multiplied in case of downtime. You will need to compensate the cost of resource multiplied by this number to your buyers in case of downtime. This option applies only to public zones.
  • Storage Performance - select the storage that will be provided for the federated zone: SSD or HDD.
  • Backups - whether backups will be available in the federated zone. For PRO and ENTERPRISE tiers backups are available by default. You can select whether backups are available or not for the DEV tier.
  • Templates - the templates that will be available in the federated zone. For the DEV tier, buyers will have access to the templates you have selected. For the PRO tier, buyers will have access to all templates from the OnApp repository. For the PRO tier, buyers will have access to all templates from the OnApp repository and can also request custom templates.
  • Windows licence - whether Windows licence will be available in the federated zone. For PRO and ENTERPRISE tiers Windows licence is available by default. You can select whether Windows licence will be available or not for the DEV tier.
  • DDOS protection - whether DDOS protection will be available for the federated zone.
  • IPv6 - whether IPv6 will be available for the federated zone.
  • DNS - whether DNS will be available for the federated zone.
  • Cloud Motion - whether your zone has CloudBoot Integrated storage. By publishing zones with CloudBoot Integrated storage you can provide your users with the ability to migrate their virtual servers between locations. If customers subscribe to two or more Cloud Motion compatible federated zones they can later move their VSs from one such zone to another. The Cloud Motion option applies only to zones with CloudBoot Integrated storage. For more information refer to How Cloud Motion Works.

  • Cross Location Replication - whether cross location replication will be available for the federated zone. This option is not available for the DEV and PRO tiers.
  • Network & Compute resource uptime - the uptime provided by the federated zone. 100% uptime is indicated for all three tiers. This option applies only to public zones.

For more information on pricing tiers refer to Seller Pricing Tiers for Compute Zones.














Step 3 of 6: Certificates



For both private and public zones you can indicate the certificates you have and their expiration date. Click in the date field next to the required certificate to indicate its expiration date. You will be required to present your certificates to our support team or your account manager before your zone is available for buyers to subscribe. You can indicate the following certificates:

  • ISO 27001 - an information security standard which is published by the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC).
  • HIPAA -  the federal Health Insurance Portability and Accountability Act of 1996. The primary goal of the law is to make it easier for people to keep health insurance, protect the confidentiality and security of healthcare information and help the healthcare industry control administrative costs.
  • PCI/DSS - a proprietary information security standard for organizations that handle branded credit cards from the major card schemes including Visa, MasterCard, American Express, etc.
  • SOX - a United States federal law that set new or expanded requirements for all U.S. public company boards, management and public accounting firms.
  • Ssae16 - a regulation created by the Auditing Standards Board (ASB) of the American Institute of Certified Public Accountants (AICPA) for redefining and updating how service companies report on compliance controls
  • Tier 1/Tier 2/ Tier 4/ Tier 4 - levels in a thorough, quantifiable manner published by Telecommunications Infrastructure Standard for Data Centers in the ANSI/TIA-942 or Uptime Institute independent certifications


Step 4 of 6. Limits




Note that when you set limits for resources, you indicate the quantity of resources that will be available to all buyers who subscribe to the zone. For example, if you set the Memory limit to 1024, the combined RAM of all VSs in the zone authored by all the buyers who have subscribed to the zone cannot exceed 1024.

Set the following limits for resources:

Compute Resource Limits

  • CPU - the maximum number of CPU cores the users can request when signed up for this federated zone
  • CPU share - the maximum CPU share % the users can request when signed up for this federated zone
  • Memory - the maximum RAM (MB) they can request when signed up for this federated zone

Data Store Limits

  • Disk Size - the maximum disk size the users can request when signed up for this federated zone


Network Limits

  • IP Address - the maximum number of IP addresses the users can request when signed up for this federated zone.
  • Port Speed - the maximum port speed (Mbps) the users can request when signed up for this federated zone.


Backup Limits

  • Backups - the maximum amount of backups the users can request when signed up for this federated zone.
  • Backup Disk Size - the maximum backup disk size the users can request when signed up for this federated zone


Step 5 of 6. Pricing



If you are adding a public zone, review the pricing for the resources in the federated zone. The prices are not editable and are set according to the pricing tier you have selected at the Tiers step.

If you are adding a private zone, set the pricing for the resources in the federated zone.

Compute Resource Pricing

  • CPU - the price per CPU core/per hour, for VSs powered on/off
  • CPU share - the prices per CPU share % per hour, for VSs powered on/off
  • Memory - the price per RAM (MB) per hour, for VSs powered on/off


Data Store Pricing

  • Disk Size - the price per GB of disk space per hour for VSs powered on/off
  • Data Read - the price for data read per GB/per hour
  • Data Written - the price for data written per GB/per hour
  • Input Requests - the price for input requests per hour. Input requests are measured in millions and priced per million requests.
  • Output Requests - the price for output requests per hour. Output requests are measured in millions and priced per million requests.


Network Pricing

  • IP Address - the price per IP address/per hour for VSs powered on/off
  • Port Speed - the price for Mbps/per hour of port speed
  • Data Received - the price per GB of data received/per hour for VSs
  • Data Sent - the price per GB of data sent/per hour for VSs 


Backup Pricing

  • Backups - the price per backup per hour
  • Backup Disk Size - the price per GB of backup disk space per hour


Step 6. Confirmation



Review the details of the federated zone.

If you want to change any of the details click the Previous button to edit the data you added on the previous steps of the wizard.

If you are satisfied with your federated zone configuration click Add to Federation.

The OnApp Dashboard will list all the transactions/logs related to Federation. Use the Hide Successful Market Notifications button to remove successful items from the list. Click the button again to show the full list.

Make sure your SSL certificates are valid

If you're using SSL certificates, make sure that they are valid. Otherwise, the Control Panel may be inaccessible. You must ensure that SSL is valid and is renewed when prompted by the SSL provider. 

Invalid SSL certificates mean:

  • New Buyers will not be able to access your resources 
  • Buyers already accessing your resources will be unable to manage their Virtual Servers 
  • OnApp cannot collect usage, meaning you may lose revenue for loss of billing
  • The Cloud Score cannot be measured