|This document applies to Sellers.|
You need to configure your cloud properly to be able to publish compute zones to Federation. For this, follow the listed procedure step by step:
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.
1. Add location group(s)
The first step is to add location group(s) to your cloud. Location groups are the locations registered in OnApp dashboard on the Dashboard Cloud License screen. The location group ties сompute resource, network, data store and backup server zones into the same location group.
2. Configure compute resources
To publish zones to Federation, you need to add compute zones and compute resources to your cloud. When adding a compute zone, select the location group you added in Step 1. After that, attach the newly created compute resource to the compute zone you've added.
You can only publish zones of the virtual type to Federation. For more information refer to Zone Types.
3. Configure data stores
To provide your federated zone with storage space, you need to configure data store zones and data stores. When adding a data store zone, select the location group you added in Step 1. You should also attach the new data store to the data store zone you've added.
Do not select a local compute resource during the creation process. Otherwise, you will not be able to add the data store zone to the compute zone.
4. Configure networks
To provide IP address(es) to your federated zone, you need to perform the necessary network configurations. To do this, create network zones and networks. While creating a network zone, select the location group you added in Step 1. When adding the network, select the network zone you've created. The network will be automatically attached to the network zone you chose during creation.
IP addresses in the network(s) should be public, as only public IPs can be used for Federation.
5. Configure backup servers
You should use a backup server to store templates, ISO and OVA images, and backups of virtual servers. First, you create a backup server and then a backup server zone. Next, you assign the backup server to the backup server zone.
6. Create template store
Next you need to add a template store. The template store enables you to organize individual templates into groups. Users who will subscribe to your federated zone will be able to choose among the templates from this template store to create virtual servers.
Additionally, you need to add the Debian 7.8 x64 Compute Performance Test template to your template store for zone evaluation. Every zone published to the market is automatically tested every two weeks for performance benchmarks regarding CPU, bandwidth and disk operations. The test scores are recalculated into index by comparing the scores of all other zones on the market.
OnApp service will subscribe as a buyer to your zone, deploy a special testing virtual server and conduct a test. After the test virtual server will be deleted and the service will unsubscribe.
The main requirement is that any published zone has a template Debian 7.8 x64 Compute Performance Test. On your CP dashbord menu go to Cloud >Templates > Template list > System Templates > Available, search for the above template and download it. This template should be in the Template Group selected while publishing the zone.
Do not change the name of template Debian 7.8 x64 Compute Performance Test.
Make sure your SSL certificates are valid.
7. Configure relations between entities
You should associate the networks, data stores, and backup servers with the compute zone, not compute resource. Data stores, networks, and backup servers associated with compute resources are not available in Federation.
Once you've added all the necessary resources to your cloud, you need to associate them with the compute zone you've created in Step 2. For this, assign the data store (Step 3), network (Step 4), and backup server (Step 5) to the compute zone (Step 2).
Each data store can be associated with only one compute zone.
8. Ensure 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
9. Configure CloudBoot Integrated Storage
If you want to provide buyers with the Cloud Motion functionality, the zone you publish to Federation should have CloudBoot Integrated Storage configured. The Cloud Motion feature allows users to migrate their virtual servers from one federated compute zone to another. For more information on CloudBoot Integrated Storage, refer to OnApp Storage.
If you have published a zone with CloudBoot Integrated storage prior to OnApp 5.2, it will be automatically marked as suitable for Cloud Motion functionality.