To create a vCenter virtual server:
Go to your Control Panel > Cloud > Virtual Servers menu and click the + button or click the Create New Virtual Server button at the bottom of the page. Fill in the VS creation form step by step:
Step 1 of 6. Cloud Locations
The Cloud Locations step applies to those users who have compute zones assigned to location groups in their bucket. This step will be present in the wizard if both of the following requirements are met:
- all compute resources available to the user are assigned to location groups
- compute resources are assigned to different locations
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.
- Indicate your virtual server's cloud location:
- 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.
- Click Next to proceed to the following step of the wizard to specify the virtual server templates
Step 2 of 6. Templates
- Click the required group icon on the right (vCenter) to expand the list of templates on the left. Every template contains the following info:
- Min memory size that is required to create a VS from this template
- Min disk size that is required to create a VS from this template
- Virtualization type
- Price per hour
- Select the template.
- To be able to use Ubuntu templates later than 9 version for vCenter virtual server creation, you need to remove the absolute pathnames in /etc/pam.d/vmtoolsd file. For example: /lib/security/pam_unix.so > pam_unix.so
- 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.
- OnApp supports templates with no more than one disk.
- Sometimes, vCenter VS creation may fail if it is based on OVA template with NVRAM file. For more details about the causes of the issue, refer to VMware article Unable to deploy an OVF from a 6.7 environment. To check one of the possible solutions, refer to vCenter 6.5 fails to boot OVA (Linux). If the issue persists, make sure that you have equal version on vSphere and ESXI.
Windows Licensing Type
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 this option is available, choose the license type you require:
- For the KMS type, choose the licensing server
- For your own license, type your license key
Please note that for the Windows templates imported from vCenter it is impossible to select the MAK license during the VS creation. Instead, select the Your own license option and manually indicate the License Key.
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. Seesection for details.
It is not possible to set VS password when creating a Windows-based vCenter virtual server without running a sysprep.
Step 3 of 6. Properties
You can create a virtual server having specified only the required parameters and configure it later. Specify the following virtual server properties:
Label - enter the label of the virtual server
Hostname - enter the host name of the virtual server
- Hostname may contain letters (A-Z), numbers(0-9) and hyphens (-) but no spaces or periods (.). The name may not consist entirely of digits.
- For Windows-based VSs, the hostname length should be between 1 and 15 characters.
- Domain - enter the domain name of the virtual server
- Password - enter the password of the virtual server or leave black for the password to be auto generated
- Password confirmation - enter the password again to confirm it
- Click Next.
Step 4 of 6. Resources
Compute Resource - select the compute resource
vCenter Resource Pool - select the resource pool
If you pick Resources from the dropdown menu, the virtual server will be placed into the default resource pool, so it will not be shown at any user resource pool, just under the cluster.
- 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.
- The amount of CPU resource a VS is given is the CPU priority (you can think of this as its "share percentage") multiplied by the number of cores allocated to that VS. This is a minimum number – clients can exceed it, up to 100% multiplied by the number of cores. For example, on a compute resource with 3GHz CPU cores:
- 100% x 1 core = 3GHz (burstable to 3GHz)
- 10% x 2 cores = 600MHZ (burstable to 6GHz)
- 5 % x 4 cores = 600MHz (burstable to 12GHz)
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.
- Note that CPU priority amount does not reflect the number of VMware CPU Resource Shares. It is calculated as follows: CPU Resource Shares (VMware) = CPU Priority (OnApp) *20. For example, 25% of CPU Priority (in OnApp) transforms into 500 CPU Resource shares (in VMware):
- 25% x 20 = 500 CPU Resource Shares (low)
- 50% x 20 = 1000 CPU Resource Shares (normal)
- 100% x 20 = 2000 CPU Resource Shares (high)
- 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.
Select the following properties for a swap disk:
- Size - enter a size for a swap disk
- Data Store Zone - select a data store zone for a swap disk
- Data Store - select a data store for a swap disk
- Disable - select the checkbox to disable swap disk creation
Only enabled data stores will be available for selection at this step. You can enable or disable a data store at Control Panel > Admin > Settings menu by clicking the Actions button next to the data store you want to change, and then clicking Edit. Move the Enabled slider to the right to enable a data store.
Network Interface 1
- Network group - select the network zone or leave Any
- Network - select the network from which the VS should get the IP address or leave Any
- IP net - select from the drop-down list the IP net from which the IP address should be assigned or leave Any
- IP range - select from the drop-down list the IP range from which the IP address should be assigned or leave Any
- IP address - select an IP address to be assigned from the drop-down box or leave Any
- Port Speed - set the port speed for this VS
Please note that it is possible to create a vCenter virtual server from a vCenter template with only one network interface added.
Since VSS networks cannot be managed on OnApp side, it will not be possible to configure traffic shaping for them, so the Port speed field at the Edit NIC page and the Resources step of the VS Creation wizard will be disabled.
Step 5 of 6. Add-ons
During this step, you can assign service add-ons or recipes to your vCenter virtual server using Service Addons or Recipes sub-tabs.
You can create a vCenter virtual server either with Service Addons or Recipes, not with both at the same time. From which sub-tab you click Next, that option is applied. For example, if you select some recipes, then go to the Service Addons sub-tab and select some service add-ons and then click Next, service add-ons will be applied not recipes.
The Recipes step is available in the wizard if Manage recipes joins for all virtual servers permission or Manage recipes joins for own virtual servers permission is enabled. To assign a recipe to your vCenter virtual server in the wizard, click Recipe under Add-ons and then follow the next steps:
- Select a recipe that you want to assign to this virtual server by dragging the required recipe to the Assigned recipes pane.
- 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.
- 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.
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.
Service add-ons are available if Manage Service Add-ons for all virtual servers permission or Manage Service Add-ons for own virtual servers permission is enabled.
- Click the service add-on group icon on the left to expand the list of service add-ons on the right. Every service add-on contains the following info:
- VS types with which this service add-on is compatible
- Description of the service add-on
- Price per hour
- 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.
Step 6. Confirmation
- Move the Enable Automated Backup slider to the right if you want this VS to be backed up automatically (according to the backup settings configured in the Settings/Auto-backup Presets menu)
- 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 Edge 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.