Manage Virtual Servers

Virtual servers are based on templates and are deployed on сompute resources. Compute resources give them access to CPU, disk and network resources. OnApp supports two kinds of storage for virtual servers: traditional centralized SANs, and the new distributed block storage functionality introduced with OnApp Storage, in which local disks in сompute resources provide the physical storage space allocated to virtual servers. In each case, the OnApp platform creates virtual data stores from the physical resources and uses these to provide virtual servers with virtual disks. This document provides information on how you can manage virtual servers in your OnApp сloud. 

View Virtual Servers


To view all virtual servers deployed in the cloud:

  1. Go to your Control Panel's Virtual Servers menu to see an overview of all virtual servers in the cloud.

  2. The page that loads will show the list of VSs together with their: 

    • operating system

    • label. Click the label to see the VS details.

    • VIP status (enabled or disabled). Click the icon to enable/disable VIP status of a particular VS.

    • IP addresses

    • allocated disk size

    • RAM

    • backups - the number of backups and the space these backups take.

    • compute resource - the label of compute resource with which VS is associated

    • user - the owner of this VS. Click the user name to see the owner details.

    • power status. Click the on/off buttons to change the status.

  3. Click the Actions button next to the VS for the quick access to the list of VS actions (the list of actions displayed depends on the VS status):

    • Recovery reboot
    • Power off a VS
    • CPU usage
    • Backups
    • Shutdown
    • Start up
    • Recovery start up
    • Unlock

If you are viewing the VSs list on a narrow screen, you can customize the way the table is displayed by clicking the actions icon at the top of the table. In the drop-down list that appears, check the columns you want to be displayed and click Apply. The narrower your screen is, the more unchecked columns will be hidden from the table. If your screen is too narrow to fit all the columns you have checked, a scrollbar will appear at the bottom of the VSs list. You can always alter you column selection later. Note that by default the VIP and Backups columns are not visible in the table on narrow screens.

Column selection is currently set for one browser. If you have checked some columns in one browser and open the list in some other browser, the column selection will be the default one for that other browser.


To search for a particular virtual server, click the Search icon at the top of the VS list. When the search box appears, type the text you want to search for and click the Search button.



View Virtual Server Details



To view details of a specific virtual server:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you're interested in.
  3. The screen that appears loads the VS propertiesnotesactivity log and tools for managing your VS.

VS Properties

VS properties page gives a general overview of the VS details:

  • Template this VS is built on
  • Power status & On/Off/Reboot buttons.

    Clicking the OFF button performs a graceful shutdown and then powers off the virtual server after the timeout set in configuration settings.

  • Segregated VS. This field appears if the VS is segregated from another virtual server. Click the label of the virtual server to view the details of the VS from which the current server is segregated. 
  • FQDN (fully qualified domain name)
  • Compute resource. Click the compute resource name to see its details
  • Location group. Click the location to view the details of the location group with which the VS is associated.
  • Login credentials
  • Owner. Click the owner name to see its details.
  • VIP status (on/off). Click the icon to change the status.
  • Estimated Price per hour. This sum does not take into consideration the free limits for resources set in the bucket. Therefore, the final price for the server might differ from the sum indicated here.

  • Memory
  • CPU(s)
  • Sockets
  • Cores per socket
  • CPU priority or CPU units
  • Disk Size
  • Disk backups
  • Network usage
  • IP Addresses. Only the first five IP addresses are displayed on the virtual server properties page. To view the list of all virtual server IP addresses, mouse over IP addresses area or go to the Networking > IP addresses tab.
  • Autoscale - move the slider to enable/disable the autoscaling rules set for this VS.
  • Until the autoscaling rules are configured the autoscaling itself will not start working.
  • If the Autoscale slider is greyed out that means that you have reached the autoscaling limit in bucket (or the max is set as 0).


  • Auto-backups - move the slider to enable/disable automatic backups for this VS. If the incremental backups are enabled in your cloud, you can set auto-backups per VS rather than per disk.

    If the automation options weren’t enabled during this virtual server creation, you’ll be redirected to the form where you can configure them.
  • Acceleration allowed - move the Acceleration allowed slider to the right to allow acceleration for this VS or move this slider to the left to prohibit acceleration for this VS. Acceleration status of the VS will be changed on the next CDN Sync Runner run (default value 20 minutes). To edit CDN Sync Runner delay, refer to Edit Infrastructure Configuration section of this guide. If VS is accelerated, you can also view the actual Acceleration Status - active or inactive.

    Ensure that Accelerate any Virtual Server/Accelerate own Virtual Servers permissions are on before enabling acceleration for the VS. For more information about permissions refer to the List of all OnApp Permissions section of this guide.

Notes

The Notes section lists brief comments or reminders for a VS. You can add either Admin's or User's notes. The Admin's note will be available to cloud administrators. Click the Actions button in the Notes section of the page to add admin's or user's note.

Service Add-ons

If you have the service add-on functionality enabled and service add-on is assigned to the VS, you can view it at the VS overview page together with the following details:

  • Label - the service add-on name (by clicking on it you can edit the service add-on)
  • Price - the service add-on price, set for this service add-on in the Service Add-on Store
  • Status - whether the service add-on is active or not
  • Actions icon - you can unassign the Service Add-on from this Virtual Server by clicking the Delete icon.

To assign more service add-ons to the VS, click the "+" button at the upper right corner of the section. You will be redirected to the VS OverviewService Add-ons section of the VS options.

VS Management

  • Click the Tools button to expand the Tools menu with the VS management options.
  • Use the top menu to manage your virtual servers' statistics/networking/storage options.


Rebuild/Build Virtual Server Manually



To build/rebuild virtual server Build/rebuild virtual server and Manage public templates permissions must be enabled.

If you haven't checked the Build Virtual Server option during the VS creation process, you will have to do this manually after the VS has been created. Building a virtual server is the process of allocating physical resources to that VS.

To build a virtual server manually or rebuild the VS on the same (or another) template:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you're interested in.
  3. On the screen that appears, click the Tools button and then click Rebuild Virtual Server.
  4. On the screen that pops up, use the drop-down menu to choose a template with which to build the VS.

    It is not possible to rebuild a Linux-based virtual server to FreeBSD templates.

  5. Move the Start VS after rebuild slider to the right if you want to have your VS started automatically after it is built.
  6. Select the following options if you selected Windows or Linux
    Windows
    • Windows Licensing type - KMS, MAK, or OWN
    • Licensing key - input license if you selected OWN licensing type
    • Select Server for KMS licensing type
  7. Click the Rebuild Virtual Server button to finish.


After you rebuild your template all data will be lost!



Edit Virtual Server



You can edit resources for all VSs. Depending on the template it is built on, some VSs can have their CPU or RAM or both resized without needing to be powered off ("resize without reboot"). If the VS template allows resizing of the required resource without the reboot, the resize should be completed automatically: you will be returned to the VS details screen and see a message indicating the resize was successful. If the template does not allow this, you will be asked to confirm that the VS will need rebooting so that the resize can take place. On how to determine whether the template you are interested in supports resizing without the reboot of RAM or CPU, refer to the Hot resize document.

  • Windows virtual servers cannot be resized without the reboot.
  • It is not possible to increase the VSs RAM beyond its max_memory value without rebooting the server. For more information refer to Hot resize.
  • If the template on which the VS is built on has the value 'YES' for the resize without reboot option, it might denote that either CPU or RAM can be changed without rebooting the server. Some templates support the resize without reboot only for either CPU or RAM while in other templates both CPU and RAM can be changed without rebooting the server. The virtualization type also influences the resize without reboot option. For more information refer to Hot resize.

The Edit Virtual Server screen will differ depending on the way the VS resources were selected: either manually or using an instance package. To adjust VS resources:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the server you want to resize, to show its details screen.
  3. Click the Tools button and select the Edit Virtual Server link.

    For virtual servers built by selecting resources manually:

    • Change CPU cores, CPU priority/units and RAM values.

      If you are editing a VS in Federation, there are the following resources ratios for VSs built on public federated zones:

      • a 4:1 ratio for CPU cores and RAM. For example, if you are building a VS with 8 CPU cores, you need to allocate at least 2 GB of RAM to it.
      • a 20:1 ratio for storage and RAM. For example, if you are building a VS with 5 GB of storage, you need to allocate at least 256 MB of RAM to it.
    For VSs based on KVM Compute resources only, providing the Enable CPU topology permission is switched on for the user:
    • Change the number of CPU sockets.

Setting the correct amount of CPU sockets

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




For virtual servers built using instance packages:

    • Choose the new instance package for your virtual server. Click the instance package to select it. After that, the instance package you have chosen will be highlighted in green.
    • Those instance packages that have resources incompatible with the compute zone, on which the VS is built, will be greyed out. Greyed out instance packages cannot be selected.
    • You can only choose from those instance packages that offer more disk size than the VS currently uses.
    • After you select a new instance package you can use the extra disk size to create a new disk for the VS or make the existing VS disk larger.

You can also edit the Time Zone parameter for all Windows KVM and Xen virtual servers. After you edit the server's time zone, you need to stop and then start up the VS. 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.

After changing VS resources you can see two prices per this VS per hour, depending on VS power status (on/off).

    • Click the Save button.


Migrate Virtual Server



OnApp allows hot and cold migration of virtual servers:

  • Hot migration - the migration of virtual servers between compute resources that share common data stores (or data store zones)
  • Cold migration - the migration of virtual servers and disks between compute resources with local storage or across compute zones

Virtual Server Hot Migration

The Hot Migrate VS feature allows you to migrate an online VS from one compute resource to another compute resource live that are both utilizing local/shared/IS storage or across zones. There are two types of hot migration: Compute Resource - migration between compute resource and Compute Resource and Storage (Hot) - VS and disk migration. 

Hot Migration Between Compute Resources


To hot migrate a virtual server:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to migrate.
  3. Click the Tools button and click the Migrate Virtual Server button.
  4. In the window that appears, choose the migration type - Compute Resource.
  5. Choose the target compute resource from the drop-down menu.
  6. Move the Cold-migrate when hot-migration fails slider to the right if you want to apply cold migration in case of the hot migration failure.
  7. Move the Are you sure you want to migrate? slider to the right to confirm the hot migration. 
  8. Click the Start Migration button.

After migration, the power status of your virtual server remains the same as before the migration. If you migrate a virtual server that's running, the whole process is almost unnoticeable.

  • To check if your Windows template supports hot migration, see the Windows templates list.
  • Note that migration VSs to a compute resource without a specific Operating System Type has the following implications. It won’t be possible to set the Windows only type for a compute resource if there are any Linux or FreeBSD VSs residing on it. Likewise, it won't be possible to set the non-Windows type for a compute resource, if there are Windows-based VSs residing on it.

VS and Disks Hot Migration


Prerequisites

There are several prerequisites for the migration:

  • The current and the target compute resources and data stores should be in the same location. Migration between locations is not possible.

  • Networks must be the same across the zones. That means that compute zones should have the same network attached.

  • The bandwidth from compute resource to compute resource should be sufficient enough to allow transferring of virtual servers.

  • This feature is suitable for VSs with local storage. Be aware, that migration will take much more time if you want to perform it between shared data stores.
  • Be aware, that disk migration is better than full VS migration in case you want to migrate the disks within the same compute zone and if the advanced backup scheme is used. Such scenario is applicable only for the shared data stores within the same compute zone.

  • The hot migration will work only when the VS is running on CentOs 7 KVM compute resources and they can be migrated only to CentOs 7 KVM compute resources.
  • The hot migration option appears only if the VS is online and your Quick Emulator (QEMU) version is later than 2.6

To hot migrate a virtual server:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to migrate.
  3. Click the Tools button and click the Migrate Virtual Server link.
  4. In the window that appears, choose migration type - Compute Resource and Storage (Hot).
  5. Choose the target compute zone and compute resource from the drop-down menu. The list will include the other zones that you have access to within the same network (i.e. KVM to KVM migration but not KVM to XEN migration). 
  6. Also, you can see each disk associated with the virtual server with a drop-down menu. Choose the data stores where you wish to move each disk. The list will include available data stores associated with the compute zone and compute resource, selected in the previous step.
  7. Move the Are you sure you want to migrate? slider to the right to confirm the hot migration. 
  8. Click the Start Migration button.

  • Hot migration is not performed if VS has temporary disks (attached to or from other VS).

  • Hot migration is not performed for Integrated Storage data stores if any of the disks has snapshots.

  • Hot migration is not applicable for federated VSs, which are built in compute zones submitted to the Marketplace.

  • If you have local backups on the source compute resource, please move them manually to a target compute resource or backup server.

  • If you change the compute resource or data store zone, the billing will be changed according to the prices set for that new zone in the bucket.

  • Go to Control Panel's Settings menu > ConfigurationDefaults tab > Migration options if you want to set migration rate limit and limit of transactions which can be run simultaneously on the target compute resource when migrating a VS.
  • The following disk migration scenarios are applicable:
    • From LVM data store to LVM data store
    • From Integrated Storage data store to Integrated Storage data store
    • From LVM data store to Integrated Storage data store
    • From Integrated Storage data store to LVM data store
      This feature is not applicable for SolidFire storage.
  • Disks that are migrated from one LVM data store to another, will be renamed in the source data store. In case of Integrated Storage, disks will remain with the same name at source data store and will be marked as offline zombie disks. You need to delete them manually, otherwise, you will get an error during backward migration.

OnApp administrators can control user access over virtual server migration. Using OnApp permissions, you can allow/forbid users to perform migration of all virtual servers, or their own servers only. This is handled via the Control Panel's Roles menu.


VS and Disks Cold Migration

Prerequisities

There are several prerequisites for the migration:

  • The virtual server should be shut down to perform migration.
  • The current and the target compute resources and data stores should be in the same location. Migration between locations is not possible.

  • Networks must be the same across the zones. That means that compute zones should have the same network attached.

  • The bandwidth from compute resource to compute resource should be sufficient enough to allow transferring of virtual servers.

  • This feature is suitable for VSs with local storage. Be aware, that migration will take much more time if you want to perform it between shared data stores.
  • Be aware, that disk migration is better than full VS migration in case you want to migrate the disks within the same compute zone and if the advanced backup scheme is used. Such scenario is applicable only for the shared data stores within the same compute zone.

To cold migrate a virtual server:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to migrate.
  3. Click the Tools button and click the Migrate Virtual Server link.
  4. In the window that appears, choose the migration type - Compute Resource and Storage (Cold).
  5. Choose the target compute zone and compute resource from the drop-down menu. The list will include the other zones that you have access to within the same network (i.e. KVM to KVM migration but not KVM to XEN migration). 
  6. Also, you can see each disk associated with the virtual server with a drop-down menu. Choose the data stores where you wish to move each disk. The list will include available data stores associated with the compute zone and compute resource, selected in the previous step.
  7. Move the Are you sure you want to migrate? slider to the right to confirm the cold migration. 
  8. Click the Start Migration button.
  • Cold migration is not applicable for federated VSs, which are built in compute zones submitted to the Marketplace.

  • You cannot migrate a virtual server from a compute resource that is offline.

  • If you have local backups on source compute resource, please move them manually to a target compute resource or backup server.

  • If you change the compute resource or data store zone, the billing will be changed according to the prices set for that new zone in the bucket. The new estimated price per hour for a VS is displayed at the bottom of the VS migration screen.

  • Go to Control Panel's Settings menu > ConfigurationDefaults tab > Migration options if you want to set migration rate limit and limit of transactions which can be run simultaneously on the target compute resource when migrating a VS.
  • The following disk migration scenarios are applicable:
    • From LVM data store to LVM data store
    • From Integrated Storage data store to Integrated Storage data store
    • From LVM data store to Integrated Storage data store
    • From Integrated Storage data store to LVM data store
      This feature is not applicable for SolidFire data stores.
  • Disks that are migrated from one LVM data store to another will be renamed in the source data store. In case of Integrated Storage, disks will remain with the same name in the source data store and will be marked as offline zombie disks. You need to check if the transaction is completed and delete them manually, otherwise, you will get an error during the backward migration.

OnApp administrators can control user access to the virtual server migration. Using OnApp permissions, you can allow/forbid users to perform migration of all virtual servers, or their own servers only. This is handled via the Control Panel's Roles menu.


Autoscale Virtual Server



VS autoscaling allows you to change the RAM, CPU and disk size settings of a virtual server automatically. VS resources scaling is based on rules you specify. For example, you can set up a rule that will add 1000MB of memory to a VS if RAM usage has been above 90% for the last 10 minutes - but add no more than 5000MB in total in 24 hours. You can set autoscaling down settings alongside with autoscaling up.

  • For Linux-based VSs and VS primary disks only.
  • Disk usage autoscaling is applicable for VS primary disk only.
  • Autoscaling for CPU cores is currently not implemented, it is implemented only for CPU units and CPU shares. 
  • If the VS is based on a template that allows resizing without the reboot - see the Edit Virtual Server section – then the VSs RAM or CPU or both can be increased without rebooting the VS. The resources that can be resized without reboot depend on the template and the virtualization type. Some templates support the resize without reboot only for either CPU or RAM. Disk space autoscaling requires a VS reboot.
  • If you autoscale a VS's memory to a value greater than current VS RAM x 16 (which is a max_memory parameter in a configuration file and database), the VS will be rebooted anyway, regardless of the template it is built on.
  • Make sure a VS can be reached via SSH. Otherwise, the autoscaling client installation will fail.
  • Starting with version 4.2, OnApp uses Zabbix for autoscaling. Monitis will be used for autoscaling of servers built using OnApp versions previous to 4.2 until you switch autoscaling off for such server(s). If you decide to switch autoscaling back on, autoscaling will be implemented using Zabbix. Zabbix also will be used for autoscaling of newly created VSs.
  • When autoscaling down is enabled, it will reduce the VS memory and disk size to the minimum, indicated in a template, on which this VS is built. CPU usage can be reduced to the minimum CPU priority allowed by the system(1%).

To configure autoscaling settings:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the appropriate VS.
  3. On the page that follows, click the Overview tab, and then click Autoscaling.
  4. Press the required tab - Memory Usage, Disk Usage or CPU Usage - to see the statistics for each type of resources.
  5. Below you will see UP and DOWN autoscaling options. Move the slider to the right to add the autoscaling rule or move it to the left to remove the rule.
  6. Add autoscaling rules as explained below:

    Set autoscale up options:
    • Time - select a specific time period in which scaling will be executed. 
    • If RAM usage is above X% for a specific time period, add Y MB – but no more than Z MB in a 24 hour period.
    • If CPU usage is above X % for a specific time period, add Y% - but no more than Z% in a 24 hour period.
    • If disk usage is above X % for a specific time period, add Y GB - but no more than Z GB in a 24 hour period.

    Set autoscale down options:
    • Time - select a specific time period in which scaling will be executed
    • If RAM usage is below X% for a specific time period, remove Y MB.
    • If CPU usage is below X % for a specific time period, remove Y%.
    • If disk usage is below X % for a specific time period, remove Y GB.
  7. Click Apply.


Clicking the Apply button does not activate autoscaling if the Autoscale slider at VS overview page is disabled. You can configure autoscaling rules, press the Apply button, these rules will be saved and will start working only after the Autoscale slider at VS overview page is enabled. Also, you can disable the Autoscale slider, autoscaling will stop working, but the configuration of rules will be saved in case you will want to activate them in future.

Set VIP Status for Virtual Server



If a compute resource fails or reboots, the system migrates virtual servers to another compute resource, one VS at a time. The order VSs are migrated in is random. However, you can give a virtual server "VIP" status, and this will give that VS priority in the migration queue. 

To set or remove VIP status for a VS:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Use the icon in the VIP column next to a required virtual server to change switch on/off the VIP status.


Segregate Virtual Server



If required, you can instruct OnApp to make sure a VS is never booted on the same compute resource as another specific VS. This may be important if, for example, you have two name servers or a load balanced web server, and you need to keep VSs on separate physical servers. You can also remove segregation if required.

  • Virtual servers can only be segregated from other VSs built by its owner.
  • Virtual servers can only be segregated from VSs within the same compute zone.
  • Virtual servers cannot be segregated from VSs running on the same compute resource.
  • The segregated VS is not automatically migrated to another compute resource.

To isolate one VS from another:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to segregate.
  3. On the screen that appears, click the Tools button, then click Segregate Virtual Server.
  4. In the dialogue box that pops up, use the drop-down menu to choose a VS you want to keep away from.
  5. Click the Segregate Virtual Server button to finish.

To remove segregation:

  1. Go to your Control Panel's Virtual Servers menu.
  2. Click the label of the virtual server you want to segregate.
  3. On the screen that appears, click the Tools button, then click Desegregate Virtual Server.
  4. In the dialogue box that pops up, click the OK button to finish.


Delete Virtual Server



Shut down the virtual server before destroying it. If you are deleting a VS that is running, the VS will be deleted after the time set in Timeout Before Shutting Down VSs configuration parameter.
To remove the virtual server from the cloud:

  1. Go to your Control Panel's Virtual Servers menu.
  2. On the screen that appears, you'll see the list of all virtual servers in the cloud. Click the label of the virtual server you want to delete.
  3. On the virtual server's screen, click the Tools button, then select Delete Virtual Server.
  4. Move the Move Last Backup to My Templates if it is present slider to the right if you want to save the last VS's backup as a template.
  5. Move the Destroy All Existing Backups slider to the right if you want to remove all existing backups of this virtual server.

IMPORTANT:

  • You won't be able to restore a virtual server after deleting it.
  • Deleting a virtual server removes all data stored on that virtual server. To save the data stored on the virtual server, back up your virtual server and tick the Destroy All Existing Backups box when following the instructions described in this section.
  • To delete a virtual server together with its backups, the user needs to have the Destroy any backup or Destroy own backup permission enabled. Otherwise, the backups of the VS deleted by the user will remain in the system.