OVA Virtual Server Wizard Beta

OVA virtual servers are created from the OVAs uploaded to the Control Panel and saved as specific OVA  templates . The OVAs are uploaded at the Control PanelCloud > Templates menu. For more information, refer to the Upload OVAs section of this guide. 


Before You Begin


If you do not see OVA template group in the Template store, go to your Profile > Bucket tab and check Limits for template store section. If OVA template group is missing, add it by clicking the "+" button in the upper right corner of this section.


To create a virtual server from the OVA:

  1. Go to your Control Panel > Cloud > Virtual Servers menu and click the "+" button, or click the Create Virtual Server button at the bottom of the screen. This will start a VS creation wizard.
  2. Fill in the wizard 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. Templates


At this step, choose a specific OVA template from which your virtual server will be built. 

To choose a template:

  1. Click the OVA template group.

  2. Select the template. 
  3. Click Next.

Additional information for Windows templates

The Windows Licensing Type box appears for Windows templates and includes license options that you configure for a corresponding template store. You can select one of the following license types:

  • MAK - the default licensing type applicable to all Windows-based virtual servers. If you don't select the licensing type, MAK is set by default.
  • KMS - the licensing type applicable to every virtual server since Windows 7, Windows Server 2008, and the following Windows versions. Click KMS and then select a licensing Server.
  • User license - type your license key

When you create a virtual server from a Windows template, consider the following:

  • You can create Windows-based virtual servers without running Sysprep. Disable the Run Sysprep option while creating or editing a destination compute zone.
  • If multiple virtual servers are deployed from the same template without running Sysprep, they will have identical security identifiers (SIDs) that can result in the system conflict.
  • You can't select KMS or your own license when you create a Windows virtual server from a custom template. As a workaround, you can create a virtual server from a template used for custom template creation.
  • You can build a Windows 10/Windows Server 2016 virtual server on KVM CentOS 6 and CentOS 7 compute resources that run at least on the following processor:



Step 2 of 6. Virtual Server Properties


At this step you need to indicate your virtual server's properties.

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.

    The following symbols are not allowed for Windows-based virtual servers:

    • percent sign [%]
    • double quotation marks [“]
    • brackets [<,>]
    • vertical bar [|]
    • caret [^]
    • ampersand [&]
    • parentheses [(,)]
  • Domain - specify the domain for this VS. For example, in test.onapp.com the test is a hostname and onapp.com is a domain. If you don't enter a domain, the default value localdomain is used as follows test.localdomainThis parameter is not applicable to Windows virtual servers. 

  • 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. If you leave password field blank, it will be generated automatically. 

    The password, set at this step, will overwrite the password specified in OVA file.

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

  • Encryption passphrase - enter a passphrase for encryption

  • Encryption passphrase confirmation - repeat the passphrase for encryption

Click Next to proceed to the following step of the wizard to specify the virtual server resources.


Step 3 of 6. Compute Resources



At this step, you can configure the following compute resources for your OVA VS:

  • RAM - set the amount of virtual server's RAM.The minimum value is the RAM value taken from OVA file. The maximum RAM depends on your bucket's settings. The maximum RAM that can be assigned to a VS is 168 GB regardless of the Max RAM value set in the bucket. 
  • CPU Cores - set the amount of virtual server's CPU cores. The minimum value is the amount of CPU cores specified in OVA file.For KVM compute resources, this parameter sets CPU sockets by default, unless CPU topology is enabled.
  • 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.

  • Use CPU Topology - move the slider to the right, to set the following parameters:
    • CPU Sockets - set the amount of sockets.

  • Compute Zone - the compute zone where the VS should be imported
  • Compute Resource - the specific compute resource where the VS from OVA will be imported. Compute resource may be selected automatically according to the set provisioning type.


Step 4 of 6. Storage Resources


Storage Resources

When you create a VS from the OVA template, you can select different data stores to put disks on them. During the creation process, all disks are imported from the OVA configuration and their size cannot be changed. The first disk becomes primary and the next disks will be numbered in the subsequent order starting from 2 (Disk 2, Disk 3, etc.). When you select a data store for each of your VS`s disks, pay attention to its price and the total free disk capacity. 

Primary Disk

  • Data Store - choose a data store for VS's primary disk. Each data store free space is indicated in brackets.
  • Size - fixed primary disk size imported from OVA configuration

Disk 2

  • Data Store - choose a data store for VS's disk. Each data store free space is indicated in brackets.
  • Size - fixed disk size imported from OVA configuration

Step 5 of 6. Network Resources


Before you apply network configuration, consider the following: (check this out for OVA virtual server)

  • When you create a virtual server in Federation, you cannot set a network port speed to a value greater than indicated by a seller while adding a zone to Federation.
  • Since not every application supports IPv6, at least one IPv4 address must be allocated to a primary network interface. 

  • The Show only my IP addresses checkbox appears only if you select a specific network, not Any network. 
  • The Selected IP address option is available in the wizard if it is enabled via Admin > Settings > Configuration > System > Show IP address selection for new VS.

When you create a VS from the OVA template, you can select in which network the VS will be created. The first network becomes Network Interface 1 and the next networks will be numbered in the subsequent order starting from 2 (Network Interface 2, Network Interface 3, etc.). The amount of network interfaces will be taken from the OVA configuration. If the OVA has several network interfaces, you can change the following parameters for each of them. 

  • Network - choose the network from which the VS should get the IP address
  • IP net - select from the drop-down list the IP net from which the IP address should be assigned
  • IP range - select from the drop-down list the IP range from which the IP address should be assigned
  • IP address - assign an IP address for the VS from the drop-down menu. Indicate compute resource and network to have the list of available IPs.

    Be aware, that you should choose only public IP address. Otherwise VS, built from OVA, will not work properly.

  • Show only my IP address - tick this checkbox to view only own IP addresses in the IP addresses dropbox.
  • Selected IP address - if the option is available, you can also assign an IP address for the VS from the drop-down menu. Indicate Compute resource and network to have the list of available IPs.
  • Port Speed - set the port speed for this VS
  • Selected IP address option is enabled via the "Show IP address selection for new VS" slider on the Settings > Configuration screen (under the System tab).
  • You can't select unlimited port speed if the Network Zone is not selected. In this case the port speed will be 1 by default.
    It's possible to create virtual server with unlimited network speed without selecting a network zone only if you have only one Network Zone assigned to your bucket.

Click Next to proceed to the last step of the wizard.

Step 6 of 6. Confirmation



At this step, configure the automation settings. This is the final step of the virtual server creation wizard.
  • 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.

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, number of cores.

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

When virtual server is created, you will be redirected to VS details page. 

You can view VS creation logs at VS details page (activity log section). If ProvisionGRUB log fails during VS creation, take the following steps:

  1. Go to VS console.
  2. Log in with credentials, created at step 2 of the VS creation wizard.
  3. Run the following command:

    grub2-install /dev/sda || grub-install /dev/sda

    After running the command, reboot the VS.