Manage Compute Resources

Compute resources are based on Xen or KVM virtualization and run on bare metal with CentOS Linux as the management operating system or VMware ESXi servers. Compute resources are used to provide hardware resources for virtual servers, ensuring highly-efficient use of available hardware and complete isolation of virtual server processes. Each virtual server in the cloud is hosted on a specific physical compute resource server, from which it receives CPU, RAM and storage capacity from the data stores attached to that compute resource. In this document, you can find information on how to manage compute resources. 

For more information on how to manage a specific compute resource, refer to the Compute Resource Settings section.


View Compute Resources



The Control Panel provides a quick way to see a summary of compute resources available in your cloud. In the Admin tab, click All Compute Resources to see a list of all compute resources and the following details:

  • Status
  • Label
  • IP Address
  • Type (Xen, KVM, etc)
  • Zone
  • Location Group
  • Operating System
  • Failover
  • VS (the number of deployed virtual servers) 
  • CPU
    • Cores
    • Used
    • Available
    • MHZ
  • RAM (based on the compute resource type)
    • Total 
    • Free 

If you are viewing the compute resources 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, select the columns you want to see and click Apply. The narrower your screen is, the more deselected columns will be hidden from the table. If your screen is too narrow to fit all the columns you have selected, a scrollbar will appear at the bottom of the compute resources list. You can always change the selection of columns. Note that by default the VS, Used and MHz columns are not visible in the table on narrow screens.

The selection of columns is currently set for one browser. If you select some columns in one browser and open this page in another browser, the column selection will be the default one for that other browser.



View Compute Resource Details



To view detailed information on a particular compute resource, follow the next steps: 

  1. In the Admin tab, click a label of a compute zone where a target compute resource runs.
  2. Click a label of a compute resource.
  3. On the screen that appears, you will see a list of all virtual servers hosted on the compute resource along with the following details:
    • OS - the operating system of the virtual server
    • Label - the name of the virtual server
    • Type - the type of the virtual instance, for example, VS (virtual server), AS (application server), Fed VS (federated virtual server), Smart Server, etc.
    • VIP - the icon that indicates whether the VIP status is enabled for the virtual server. If theicon is dimmed, the VIP status is not enabled. Click the icon to enable the VIP status for the VS.
    • IP Addresses - the IP address of the virtual server
    • Disk size - the disk size of the virtual server in GB
    • RAM - the amount of RAM allocated to the virtual server in MB
    • Backups - the number of backups and the space these backups take
    • Compute Resource - the compute resource on which the virtual server runs 
    • User - the user who created the virtual server
    • Power - the power status of the virtual server that can be powered on or powered off
    • Actions - the list of actions available for the virtual server that includes: 
      • Startup 
      • Shutdown
      • Reboot
      • Recovery Reboot
      • Recovery Startup
      • CPU Usage
      • Backups

      The list of available actions for the virtual server depends on the VS power status. For more information, refer to the Virtual Server Power Options guide.

  4. To view details of a specific VS, click its label.

Power On/Off Virtual Servers



At the compute resource details page, you can power on and power off virtual servers that are run on this compute resource. To power on/off virtual servers, follow the next steps: 

  1. In the Admin tab, click a label of a compute zone where a target compute resource runs.
  2. Click a label of a compute resource. On the screen that appears, you will see a list of all virtual servers hosted on the compute resource.
  3. Choose virtual servers that you want to power on or power off by selecting the required checkboxes in the first column of the table. 

    • To select all virtual servers residing on the compute resource, click the first checkbox. To cancel the selection of all virtual servers, click this checkbox again.

    • If you select all virtual servers, only the powered-off VSs will be powered on, while the already powered-on VSs will be skipped and vice versa.

Depending on the current power status of the selected VSs, one of the following options become available. 

Power On

To power on the selected VSs: 

    • Click the Power On button.
    • In the pop-up box, click the YES button to confirm your action.


Power Off 

To power off the selected VSs: 

    • Click the Power Off button.
    • In the pop-up box, select one of the following methods: 
      • Gracefully shutdown - to run a graceful shutdown of VSs
      • Power Off - to run a forceful shutdown of VSs
    • Click the Submit button to confirm your action.
  • The bulk power on/off actions are available only to virtual servers that are run on KVM and Xen compute resources.
  • For more information on the VS Power Options, refer to the linked guide.



Migrate Virtual Servers 



You can migrate multiple virtual servers at once from one compute resource to another compute resource of the same type (KVM to KVM or Xen to Xen). The mass migration is available within compute resources that belong to the same compute zone. To migrate virtual servers, follow the next steps: 

  1. In the Admin tab, click a label of a compute zone where a target compute resource runs.
  2. Click a label of a compute resource. On the screen that appears, you will see a list of all virtual servers hosted on the compute resource.
  3. Select checkboxes next to the virtual servers that you want to migrate and click the Migrate button. 

    To select all virtual servers residing on the compute resource, click the first checkbox. To cancel the selection of all virtual servers, click this checkbox again.
  4. In the pop-up box, select the following options:
    • Target compute resource - select a destination compute resource to migrate the virtual servers to
    • Cold-migrate when hot-migration fails - select the checkbox if you want to apply cold migration in case of the hot migration failure

      If some of the selected virtual servers have disks that run as a local storage on this compute resource, these virtual servers could not be migrated. After the migration, these virtual servers remain on the previous compute resource, while other VSs are migrated to the destination compute resource.

  5. When you are finished, click the Submit button. 

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

To check if your Windows template supports hot migration, see the Windows templates list.

Note that migration of virtual servers to a compute resource without a specific Operating System Type has the following implications:

    • You won't be able to set the Windows only type for a compute resource if there are any Linux or FreeBSD virtual servers on it.
    • You won't be able to set the non-Windows type for a compute resource if there are Windows-based virtual servers on it.



Edit Compute Resource Details



You can edit a compute resource at the compute resource details page or through the Settings > Compute Resources menu (see Compute Resource Settings section for details: the editing functionality is the same whichever method you choose).

To edit compute resource details:

  1. In the Admin tab, click a label of a compute zone where a target compute resource runs.
  2. Click a label of a compute resource.
  3. Click the Tools button and then click Edit Compute Resource.
  4. On the screen that follows, change details as required:
    • Label - the name of the compute resource
    • Operating System Type - choose an operating system type (Any OS, Windows only or Non-Windows)
    • IP Address - the IP address of the compute resource
    • Backup IP Address - the provisioning network IP address
    • CPU Units - the amount of CPU units assigned to this compute resource

      Mind that setting a different amount of CPU units will affect your cloud configuration. It will not be possible to create Instance Package VSs in the compute zone to which you assign this compute resource.

    • Enabled - enable or disable the ability to install/boot virtual servers on this compute resource
    • Collect Stats - enable or disable the ability to collect statistics for this compute resource
    • Disable Failover - enable or disable the VS migration to another compute resource if this compute resource is marked as offline by the Control Panel server

      • When you assign the compute resource to the new compute zone without any compute resources, the disable failover zone’s parameter automatically takes the value of the compute resource.

      • When all compute resources within the zone have the same value, the compute zone’s disable failover status will be the same, otherwise, the compute resources zone’s failover status will be set to disabled.

      • When you change the compute zone’s disable failover value, this change will be applied to all compute resources within this zone.

    • Failover recipe - select a recipe to run before the failover process

    • Power Cycle Command - arbitrary command string to be executed by IPMI from the CP server. If the command is entered, a new option "Power Cycle Compute Resource", which will execute the entered command, will appear in the Tools menu at the Settings > Compute resources > Compute resource page.

      Currently, a command or commands should be written in one line separated by semicolon. If the command is written in two lines you will receive a "fail" response, although the transaction will be performed. The power cycle command is executed on Control Panel under the onapp user and it can be any bash script.

  5. Click the Save button to apply changes.


Reboot Compute Resource



You can reboot a compute resource and set a logic to apply to virtual servers during the reboot. To reboot a compute resource:

  1. Go to your Control Panel > AdminCompute Resources menu.
  2. Click a label of the compute resource that you want to reboot.
  3. On the compute resource details page, click Tools and then click Reboot Compute Resource.
  4. In the pop-up box, you can select the following options:

    • Do not migrate powered off VSs 
      Select this checkbox to prevent the migration of powered off virtual servers to another compute resource while the source compute resource is being rebooted. 

    • Start running virtual servers after reboot? 
      Select this checkbox to initiate the failover process to start running virtual servers after the reboot. 

      The failover process will be initiated despite the Disable Failover configuration for Compute resource or Compute zone.

    • Stop all virtual servers that cannot be migrated to another compute resource? 
      Select this checkbox to power off virtual servers that cannot be migrated
      . When a compute resource is scheduled for the reboot, OnApp first attempts to hot migrate all virtual servers on a compute resource. If hot migration is not possible for a VS, OnApp attempts to cold migrate the VS. If you select this checkbox and cold migration fails, the VS is stopped so that the reboot may continue. If you don't select this checkbox, OnApp first attempts to hot and then cold migrate all VSs hosted on the compute resource but stops the migration process if any VS cannot be migrated.

    • Are you sure you want to reboot this compute resource? 
      Select this checkbox to confirm that you want to reboot the compute resource.


  5. When you are certain that you want to proceed with the reboot, click the Reboot button.

The reboot option is not available for VMware compute resources.
If your backups disappear after rebooting the CloudBoot compute resource with LVM storage which is used as a backup server, add mount command to CloudBoot backup server custom config after the reboot. This is a known issue which will be fixed in the future release.

To fix your custom config settings, use one of the following options provided in the examples below (you will have to specify your own device names):
  1. If you have a separate partition for backups and templates (/dev/sda1 and /dev/sda2)

    mkdir-p /onapp/backups

    mkdir-p /onapp/template

    s mount /dev/sda1 /onapp/backups

    mount /dev/sda2 /onapp/templates

  2. If you current array is detected as /dev/sda1 and currently everything is located in /onappwithin templates and backup directories within:

    mkdir-p /onapp

    mount /dev/sda1 /onapp