Create VS in Federated Zone

This document applies to end users. Otherwise refer to the Sellers or Buyers sections of this guide.

For users, creating a virtual server in Federation is almost the same procedure as creating a VS on local buyer's compute zones. Virtual servers are created from templates. Depending on the location chosen (remote seller's location or local buyer's), the virtual server will be created locally or in Federation. The system automatically checks this and the VS creation wizard alters accordingly.

Starting with OnApp 5.5 you can create vCenter virtual servers if you are subscribed to a private vCenter compute zone. To create such a VS, select a template of the  'VCENTER' virtualization type in the server creation wizard. The creation process for a vCenter VS is the same as for regular OnApp virtual servers.

When a virtual server is provisioned, the public keys of the Control Panel and your public SSH keys (if you have SSH keys added) are set for the server. 

To create a virtual server on a federated compute zone:

  1. Go to your Control Panel > AdminVirtual Servers menu and press the "+" button, or click the Create New Virtual Server button at the bottom of the screen.

  2. Fill in the VS creation form step by step. Each of these steps is described in the corresponding sections below.

  3. Click the Create Virtual Server button to start the creation process. You will be taken to the virtual server details screen.

Step 1 of 6. Cloud Locations

If you face the problem with viewing the maps, refer to the Add Google Map API Key section of Administrator guide.

At this step you choose cloud location for VS creation. The location predefines the available configurations of VS resources in the following steps of the wizard. If the chosen location is associated with a local compute zone, the VS creation procedure will be standard. Refer to Create VS section of OnApp User Guide for details. If the selected location is provided in Federation, the VS will be created remotely. Below are the instructions for completing the wizard if the chosen location is associated with a federated compute zone:

  1. If you want to use Cloud Motion functionality, click the Cloud Motion checkbox. The map will then show only the zones which are configured for Cloud Motion.
  2. Indicate your virtual server's cloud location: country and city.
  3. Click Next to proceed to the following step of the wizard.

If there is only one location available this step will be skipped. The wizard will start with the Templates step.

  • It is required to click the Cloud Motion checkbox when selecting a location for the VS if you want to be able to move this VS later, otherwise you will not be able to use Cloud Motion for the VS.
  • If you select a dashboard location at this step, only local buyer templates will be available in the VS creation wizard. If you select a federated location, only the templates that come with the federated zone you have selected will be available for selection.

Step 2 of 6. Templates

At this step, specify the template from which your virtual server will be built. 

To choose a template:

  1. Click the required group icon on the right (Windows, Linux, FreeBSD etc.) to expand the list of templates on the left. Every template contains the following info:
    • Template's label
    • Min memory size, required to create a VS from this template
    • Min disk size, required to create a VS from this template
    • Virtualization type (XEN, KVM, VCENTER)

      To create a vCenter VS, select a 'VCENTER' virtualization type template. This applies only if you are subscribed to a vCenter compute zone.

    • Price per hour
  2. Select the template.
  3. Click Next.

Only the templates that come with the federated zone you have selected at Step 1 are available for selection.

Note that the template group associated with the selected location will be present in the wizard only if all the resources (template group, data store zone, compute zone, network zone, backup server zone) of that compute zone are added to the bucket of the current user.

Step 3 of 6. Virtual Server Properties

At this step you need to:

  • Give your virtual server a label. 
  • Give your virtual server a hostname. The hostname should consist of letters [A-Z a-z], digits [0-9] and dash [ - ]. For more info on hostname validation, refer to RFC standard documentation.
  • Specify the domain for this VS. The default value is localdomain. This parameter is not applicable for Windows virtual servers. 

    For example: - specify 'test' as hostname, ''-  as domain. If you leave the domain field blank, the default value 'localdomain' will be used and you will get the following -
  • Give your virtual server a secure password. It can consist of 6-99 characters, letters [A-Za-z], digits [0-9], dash [ - ] and lower dash [ _ ]. You can use both lower- and uppercase letters.
  • Click Next. 

Step 4 of 5. Resources

Set the resources needed for this VS: RAM, CPU cores, CPU priority.

Primary disk

  • Set the primary disk size

Swap disk

  • Set the swap disk size.  There is no swap disk for Windows-based VSs. In all other cases, swap disk size must be greater than zero. There is no swap disk for vCenter virtual servers.

 Network configuration

  • Set the port speed for this VS or choose unlimited
  • Click Next.

  • Be aware, that during VS creation you can not set greater network port speed than indicated by seller when adding zone to federation.
  • There are the following resources ratios for VSs built on public federated zones:
    • a 4:1 ratio for CPU cores and RAM. For example, if you are building a VS with 8 CPU cores, you need to allocate at least 2 GB of RAM to it. The RAM value in the wizard will be adjusted automatically according to the number of CPU cores you set.
    • a 20:1 ratio for storage and RAM. For example, if you are building a VS with 5 GB of storage, you need to allocate at least 256 MB of RAM to it. The RAM value in the wizard will be adjusted automatically according to the storage size you set.
    • a 20:1 ratio for primary and swap disks, if swap disks apply to your VS. For example, if you set a 1GB swap disk for a VS, the primary disk cannot exceed 19GB.

Step 5 of 6. Recipes

  • The recipes step will be missing in the wizard if there are no recipes created in the cloud. For information on adding recipes to the cloud refer to the Recipes section of the User Guide.
  • Recipes on the disk resize event are supported only if the seller who provides the resources runs OnApp version 5.4 and up. Recipes on the network interface added event are not supported for VSs in Federation.

At this step you need to indicate the recipes you want to assign to your virtual server. This step is optional. You can create a virtual server without choosing recipes and add them later if required.

  1. Choose a recipe you want to assign to this virtual server by dragging the required recipe to the Assigned recipes pane. 
  2. To add a custom variable, click the "+" button next to the Custom recipe variables title bar, then specify variable details:
    • Specify the recipe name and its value.
    • Move the Enabled slider to the right to allow use of this variable.
  3. Click Next to proceed to the next step of the wizard that completes the virtual server creation process.

Step 6 of 6. Confirmation

At the Confirmation step you can find the configuration summary of VS, which will be created. You can view template's name, RAM size, number of networks, primary disk and swap disk size, number of cores.

Move the Boot Virtual Server slider to the right if you want the system to automatically build the VS. If you leave this box blank, you will have to build your server manually after it is created.

After you set up these parameters, click the Create Virtual Server button to start the creation process.