Create Virtual Server

Virtual servers are created from templates. To create a virtual server:

  1. Go to your Control Panel's 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.

OnApp must be configured properly before VSs can be created. You must have:

At least one data store configured and assigned to a data store zone

At least one network configured and assigned to a network zone

At least one compute resource configured and online

At least one compute resource assigned to a compute zone

At least one data store attached to a compute resource

At least one network attached to a compute resource

Assigned a bucket to the user creating the VS

On this page:

Step 1 of 6. Cloud Locations
Step 2 of 6. Templates
Step 3 of 6. Virtual Server Properties
Step 4 of 6. Resources
Step 5 of 6. Recipes or Service Add-ons
Step 6 of 6. Confirmation


See also:

Virtual Servers - the information on managing virtual servers
Configure Resource Allocation And Prices - bucket configuration
Template Software Licenses- how to enable MAK or KMS
Set up Instance Packages for Cloud - the walk-through for using packages of resources
Recipes - recipes creation and management
Virtual Servers (API) - the list of available API requests

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 this guide.

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 with 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


Make sure that the selected template is located on a backup server attached to the compute resource on which you wish to built the VS, otherwise, the creation of the VS will fail.

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

  1. Click the required template store icon on the left (Windows, Linux, FreeBSD etc.) to expand the list of templates on the right. 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)
    • Price per hour
  2. Select the template.
  3. Click Next.

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

If you don't specify the licensing type, MAK licensing will be set by default.

Consider the following when creating a VS on Windows templates:

  • 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.
  • If there are several virtual servers simply deployed from the same template in the cloud, they will have identical SIDS. This will result in the system conflict.
  • It is not possible to select KMS or own licensing type when creating a Windows virtual server from custom template. As a workaround, you can create a virtual server from the template used for custom template creation.

Proceed to the following step of the wizard and specify the virtual server properties.

Template extraction is performed during server provisioning  or taking a backup when using a particular template. To prevent template from being used in other transactions during extraction, template is locked during the extraction and unlocked on accomplishment. If other transaction tries to use the locked template, it will fail after 5 minutes of standby. Transaction which locked template and failed, means that extracted template is broken.

Storing scheme:

  • template /onapp/templates/your_template.tgz
  • extracted template /onapp/backups/templates/your_template
  • locked template /onapp/backups/templates/your_template.lock

Windows 10/Windows Server 2016 Virtual Servers

If you want to build Windows 10/Windows Server 2016 VSs, the following limitations apply to KVM compute resources:

  • Windows 10/Windows Server 2016 VSs can be built on the CentOS 6/CentOS 7 compute resources with the following CPU models:
    • at least Ivy-Bridge-based Intel Xeon E series v2

    • Opteron G2, G3, G4, G5, and G6

  • CPU flag 'fsgsbase' is required. For more information on CPU flags refer to Manage Extended CPU Configuration for Compute Zone.

The above limitations do not apply to XEN compute resources.

Step 3 of 6. Virtual Server Properties



At this step you need to indicate your virtual server's properties, such as label, password and other. 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.

    Particular characters 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. The default value is localdomain. This parameter is not applicable for Windows virtual servers. 

    For example:
    test.onapp.com - specify ' test' as hostname, ' onapp.com'-  as domain. If you leave the domain field blank, the default value ' localdomain' will be used and you will get the following - test.onapp.com.localdomain.
  • Time zone - set the time zone for the virtual server. This parameter is applicable only to Windows XEN and KVM virtual servers. Currently, the time zone is set at the Compute resource side only. Therefore, users need to set the target time zone inside a Windows VS manually. Setting correct time zone at the Compute resource side helps to keep correct time inside a VS after starting it if time synchronization is not completed for some reason.

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

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

    For more information on the VS password encryption, refer to the FAQ.

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


Step 4 of 6. Resources



At this step, you can choose to create the virtual server either by selecting a predefined instance package or by setting your virtual server's resources, such as disk size, network configuration and other manually.

  • A VS created using instance packages is called an instance package VS.
  • A VS created by setting resources manually is called a custom virtual server.

Depending on the permissions, this step will display either Instance Packages or Create your own tabs, or both of them.

You are forwarded to the next step from the tab you are currently on. If you select an instance package and then click on the Create Your Own tab and proceed to the next step, the system will set the resources from the Create Your Own tab even if you did not configure any resources there.

Resources

Instance packages

If the selected instance package applies to certain compute zones only, as indicated in the user's bucket, the VS will be created on one of the compute resources within one of those zones. Otherwise, the compute zone and compute resource for the VS will be selected automatically from the zones available to the user.

Note that instance package VSs can only be created on compute resources within compute zones where all compute resources are assigned the same amount of CPU units. If there are compute resources with different amount of CPU units set in a zone, it will not be possible to create instance package VSs in such zones. The reason is that CPU priority for instance package VSs in this configuration cannot be set to 100%, which is the default value for such virtual servers.

If there are no available IP addresses during VS creation, all instance packages will be grayed out in the wizard. 

From this tab, you can choose one of the predefined Instance Packages for your virtual server.

You will see all instance packages available to you, but those that have resources incompatible with the available compute zone(s) will be grayed out. Grayed out instance packages cannot be selected.

For each of the instance packages the following details are displayed:

  • Memory - the RAM size (GB) available in the instance package
  • CPUs - the number of CPU cores available in this instance package
  • Disk Size - the disk size available in this instance package
  • Bandwidth - the bandwidth available in this instance package
  • Price per Hour:
    • Mode ON - hourly instance package price for the VS powered on
    • Mode OFF - hourly instance package price for the VS powered off
  • Price per Month:
    • Mode ON - monthly instance package price for the VS powered on
    • Mode OFF - monthly instance package price for the VS powered off

Note that estimated price per hour may be displayed inaccurately under such conditions:

  • When you do not have the required permissions. Ensure that Show Compute Zones on VirtualServer creation and Show compute resources on virtual server creation permissions are on before setting your virtual server's resources.
  • When you leave some resources with Any option selected. Since estimated price includes only those prices that are known, specify the compute zone, data store, and network resources in the wizard.


Click the instance package to select it. After that, the instance package you have chosen will be highlighted in green.

Virtual servers created using instance packages do not support autoscaling.

Create Your Own

Using this tab you can define the resources for your virtual server manually:

Compute Resources

  • Compute Zone - the Compute zone to build the VS on
  • Compute Resource - the specific Compute resource to build the VS on. Compute resource may be selected automatically according to the set Virtual Server Provisioning.

    When the Show Compute resources on Virtual Machine creation permission is disabled (so that user cannot select the Compute resource, but can choose the virtualization type), the Compute resource that meets the virtualization type and the resources set will be automatically selected. The data store will be set according to the compute zone selected.

Resources

  • RAM - set the amount of virtual server's RAM. The maximum RAM depends on your bucket's settings, virtualization type, and virtual server OS. 

    Set RAM to 512MB if you are creating a FreeBSD based virtual server. The RAM value can be later increased after the VS creation when editing the VS.

  • CPU Cores - set the amount of virtual server's CPU cores. For KVM Compute resources, this parameter sets CPU sockets by default, unless CPU topology is enabled. When the CPU topology is enabled, this amount specifies how many virtual cores the virtual server will have.
  • 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 following options are available for VSs based on KVM Compute resources only, providing the Enable CPU topology permission is switched on for the user.

  • Use CPU Topology - move the slider to the right, to set the following parameters:
    • CPU Sockets - set into how many sockets the CPU cores should be arranged. This value will affect the amount of cores_per_socket.

Setting the correct amount of CPU sockets

If the CPU topology is enabled, the CPU cores will mean a number of vCPUs, which is the maximum value that can be arranged into cpu sockets and cores per socket. If the CPU topology is disabled, the CPU cores will actually mean the CPU sockets value with 1 core_per_socket.

  • Set the total amount of virtualized CPUs and the number of sockets.
  • The value of cores_per_socket will be calculated automatically by the formula vCPUs  = cpu_sockets x cores_per_socket.
  • Thus, if you set the vCPU value 8, and the CPU sockets 2, this means that the cores_per_socket value will be set 4. 



Primary Disk

  • Data Store - choose a data store for VS's primary disk.
  • Primary disk size -  set the primary disk size.

Swap Disk

  • Data Store - choose a data store for 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 Interface 1

  • Network - select 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 - select an IP address to be assigned from the drop-down box
  • Show only my IP address - tick this checkbox to view only own IP addresses in the IP addresses dropbox.

How the checkbox works

It becomes visible after you select the network from which the VS should get the IP address. Next, three options are available:

  1. You tick the checkbox. In this case, you retrieve only your IP addresses for selected network.
  2. You tick the checkbox and then untick it. In this case, you retrieve all available IP addresses for selected network. 
  3. You don't tick the checkbox. In this case, follow the network configuration process steps described above.
  • 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
  • For federated VSs: be aware, that during VS creation you cannot set the network port speed greater than indicated by seller when adding zone to federation.

  • Since not every application supports IPv6, at least one IPv4 address must be allocated to a VS's primary network interface. 

  • 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 if you have only one Network Zone assigned to your bucket.

Click Next to proceed to the following step of the wizard where you can specify the virtual server recipes.


Step 5 of 6. Recipes or Service Add-ons



This step can be either Recipes or Service Add-ons depending on the cloud configuration. If service add-on functionality is not available, you will get Recipes step.

Recipes

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.

The recipes step can be missing in the wizard if there are no recipes created in the cloud.

If mentioned below prerequisites are met, the Recipes step will be replaced with the Service Add-ons step.

Service Add-ons

Prerequisites

Ensure that the following requirements are met to be able to assign service add-on to VS during its creation:

  • Replace Recipes with Service Add-ons on VS creation permission is enabled
  • Service add-on groups are available in your bucket
  • The On Provisioning option is enabled for all or some of the service add-ons available to you within bucket. 

In case there are no available service add-ons, this step of the wizard will be skipped.

At this step you need to indicate the service add-ons 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.

  1. 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:
    • Label
    • VS's types, with which this service add-on is compatible
    • description of the service add-on
    • Price per hour. You will be charged only after the VS is built and the transaction status is complete.
  2. 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.
  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 this step, configure the automation settings. This is the final step of the virtual server creation wizard.
  • 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 to allow acceleration for this VS or move this slider to the left to prohibit acceleration for this VS. 

The Acceleration allowed slider is available if the following conditions are met:

  • Accelerator is available in the network
  • IP Address, selected during VS creation, is in the same network as Accelerator
  • VS is created by setting own virtual server's resources, not by selecting a predefined instance package
  • The Show IP address selection for new VS slider is activated in the Control Panel Settings menu > Configuration
  • Only HTTP is supported. Other protocols, including HTTPS, will be passed through to the VS directly.
  • In order to route the VS’s traffic, the VS must be on the same network with the Accelerator.

At the Confirmation step you can find the configuration summary of VS, which will be created, including the info on how many cores/cores per socket/sockets the VS will have.

 You can view template's name, RAM size, number of networks, primary disk and swap disk size, number of cores.

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