Page tree
Skip to end of metadata
Go to start of metadata

To create a VMware virtual server:

Go to your Control Panel's Virtual Servers menu and press the "+" button, or click the Create New Virtual Server button at the bottom of the screen. Fill in the VS creation form step by step:

Step 1 of 5. Templates

  1. Click the required Operating system label (Windows, Linux or FreeBSD) to expand the list of template group.
  2. Distribution - choose a template Distribution
  3. Template - select the template
  4. Click Next.


1. You can use RHEL, Windows and Debian templates to create VMware virtual servers. For details how to create VMware templates, refer to Create Template for VMware Virtual Server section. 

 2. To be able to use Ubuntu templates later than 9 version for VMware virtual server creation, you need to remove the absolute pathnames in /etc/pam.d/vmtoolsd file. For example: /lib/security/ >

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.

Windows Licensing Type

This option only appears if your billing plan 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

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 VMware virtual server without running a sysprep.

Step 2 of 5. Properties

You can create a virtual server having specified only the required parameters and configure it later. Specify the following virtual server properties:

  • Label - the label of the virtual server. The required parameter.
  • Hostname - the hostname of the virtual server. The required parameter. 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.

  • Compute zone - the compute zone to build the VS on.
  • Compute resource - the specific VMware compute resource to build the VS on. 

  • Password - a secure password for the VS. It can consist of 6-99 characters, letters [A-Za-z], digits [0-9], dash [ - ] and lower dash [ _ ], and the following special characters: ~ ! @ # $ * _ - + = ` \\ { } [ ] : ; ' , . ? /. You can use both lower- and uppercase letters.

  • Password confirmation - repeat the password to confirm it.
  • Encrypt password - move the Encrypt Password slider to the right, to encrypt your password, then enter an encryption key in the field that appears.
  • Click Next.

Step 3 of 5. Resources

  • RAM - set the amount of virtual server's RAM.
  • CPU Cores - set the amount of virtual server's CPU cores.
  • CPU Priority - set virtual server's 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 burst over 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.

Primary disk

  • Data Store Zone - choose a data store zone for this VS's primary disk.
  • Primary disk size - Set the primary disk size.

Swap disk

  • Data Store Zone - choose a data store zone for this VS's swap disk.
  • Swap disk size - 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.

 Network configuration

  • Network - choose a customer network from the drop-down list.
  • Port Speed - set virtual server port speed.
  • Click Next.

Step 4 of 5. Recipes

  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 the variable's details:
    • Enter the recipe's name and its value.
    • Move the Enabled slider to the right to allow use of this variable.
  3. Click Next.


Step 5. Confirmation

  • 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.

OnApp must be preconfigured, before VMware VSs can be created. A Vyatta firewall must be configured and available for the cloud before creating any virtual server. As all customer virtual servers are organized into VLAN’s, with Vyatta acting as the VS gateway.

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

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels