If you face the problem with viewing the maps, refer to the Add Google Map API Key section of this guide.
If the user's bucket has several compute zones, some of which are assigned to location groups, whereas others are not - the cloud locations screen will not be available in the wizard. Also if all compute zones are assigned to the same location this step will be skipped. In this case the wizard will start from the Templates step.
Country - choose the country, where the cloud is located, from the drop-down menu.
City - specify the city, where the cloud is located, from the drop-down menu.
1. You can use RHEL, Windows and Debian templates to create vCenter virtual servers. For details how to create vCenter templates, refer to Create Template for vCenter Virtual Server section.
3. Please make sure that the Windows password policy defined inside the template is compliant with the password policy set in the OnApp CP. This will ensure that there are no password related issues when provisioning Windows.
4. OnApp supports templates with no more than one disk.
This option only appears if your bucket allows it, and if the relevant licensing options have been configured for the template group this template belongs to.
If you don't specify the licensing type, MAK licensing will be set by default.
It is possible to deploy Windows virtual servers without running sysprep. To do so, you need to disable the Run Sysprep option for the compute zone the virtual server will be built on. See Create Compute Zone section for details.
It is not possible to set VS password when creating a Windows-based vCenter virtual server without running a sysprep.
Compute Zone - the compute zone to build the VS on.
Compute Resource - the specific vCenter compute resource to build the VS on.
Datacenter - select the data center for the data store.
Cluster - select the cluster to import networks and data stores from.
RAM - set the amount of virtual server's RAM.
CPU Cores - set the amount of virtual server's CPU cores.
CPU Priority (or CPU Units) - set virtual server's CPU priority. If the CPU units are switched on in the bucket for this user, then CPU priority is replaced with CPU units. Refer to Billing Calculation section for details on CPU units and CPU priority.
By default, OnApp allows overselling of cloud resources. For example, OnApp will allow users to create 5 VSs with 100% CPU priority/1 CPU core on a compute resource with a 4-core CPU. In this example, OnApp would reduce the guaranteed CPU for each VS.
If you build a VS on a KVM compute resource running CentOS5, the CPU priority settings will be disabled and CPU priority value will be 100 by default.
Data Store Zone - choose a data store zone for this VS's primary disk.
Primary data store - select a primary data store for this VS's primary disk.
Primary disk size - set the primary disk size.
You can select recipes that 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.
Select a recipe that you want to assign to this virtual server by dragging the required recipe to the Assigned recipes pane.
Move the Enabled slider to the right to allow use of this variable.
Click Next to proceed to the next step of the wizard that completes the virtual server creation process.
The recipes step can be missing in the wizard if there are no recipes created in the cloud.
The On Provisioning option is enabled for all or some of the service add-ons available to you within a bucket.
In case there are no available service add-ons, this step of the wizard is not available.
You can select the service add-ons that you want to assign to your virtual server. This step is optional. You can create a virtual server without choosing service add-ons and add them later if required.
Select the service add-on by clicking on it. You can select several add-ons from different service add-on groups. Click View Selected Add-ons to see the list of selected service add-ons. You can remove the selected service add-on from the list by clicking the button near the add-on.
Click Next to proceed to the next step of the wizard that completes the virtual server creation.
Move the Build 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.
Move the Boot Virtual Server slider to the right, if you want the virtual server to be started up automatically.
Move the Enable Autoscale slider to the right to set autoscaling for this VS.
Until the autoscaling rules are configured the autoscaling itself will not start working.
If the Enable Autoscale slider is grayed out that means that you have reached the autoscaling limit in the bucket (or the max is set as 0).
Move the Acceleration allowed slider to the right to enable accelerator for this VS. For more information, see Accelerator.
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 size, and number of cores.
After you set up all parameters, click the Create Virtual Server button to start the creation process.