Create and Manage CloudBoot Compute Resources

Compute resources are a critical part of the cloud. Compute resources have types which they inherit from the zone to which they belong. You can select the type of CloudBoot compute resource during the creation process. Also, this section provides information on how to edit CloudBoot compute resources for different types of servers and how to delete them.

Create CloudBoot Compute Resources


CloudBoot compute resources are created in Control Panel's Settings menu. To add a compute resource:

  1. Configure the IP range which the Control Panel will assign to compute resources.
  2. Add specific compute resources to the Control Panel itself.

After you create a compute resource you need to add it to a compute zone of the required type. For more information on compute zone types, refer to Zone Types.

Create IP Range


To create an IP range:

  1. Go to your Control Panel’s Settings menu and click the Compute resources icon.
  2. Click the CloudBoot IPs tab – this is where you add an IP address or range for the compute resource management interfaces, which Compute resources will acquire via DHCP when they boot. It is recommended to locate Compute resources management interfaces on a separate subnet with a NIC on the CP server also attached. In this configuration, the management subnet can use private address space and does not need to be externally addressable.

  3. Next, power on your Compute resources. As they boot, the Control Panel will detect and record their MAC addresses. 

    • Click the New IP Address button. On the page that loads, fill in the following information:
    • IP Address - enter a single address or a range of addresses to be used by the PXE server- e.g. 192.168.1.100-192.168.1.200 (see the note below)
    • Netmask - enter a netmask
    • Gateway - enter a default gateway address (see the note below)

  4. Click the Submit button to finish.

The dynamic range should be quite a bit larger than the actual IPs that will get assigned. This allows space for reassigning new nodes that come online, without creating address collisions.

Compute resource management interfaces must be on the same subnet as the Control Panel server, and addresses must be valid for that addressable subnet. The Compute resource management interface must also have PXE boot enabled.



Create CloudBoot Compute Resource


To create a CloudBoot compute resource:

  1. Go to your Control Panel's Settings > Compute Resources menu.
  2. Click the Add New CloudBoot Compute Resource button at the bottom of the screen.
  3. Fill in the wizard step by step. Each of these steps is described in the corresponding sections below.
  4. Click the Create CloudBoot Compute Resource button to start the creation process.


Step 1 of 5. Type


At this step, select the type of CloudBoot compute resource you want to create:

  • KVM - KVM CloudBoot Compute Resource, based on CentOS 6

  • KVM - KVM CloudBoot Compute Resource, based on CentOS 7
  • Xen 4 - Xen 4 CloudBoot Compute Resource, based on CentOS 6

  • Xen 4 - Xen 4 CloudBoot Compute Resource, based on CentOS 7
  • Backup - CloudBoot Provisioning and Backup Resource, for backups maintenance, based on CentOS 6

  • Backup -  CloudBoot Provisioning and Backup Resource, for backups maintenance, based on CentOS 7
  • Smart - KVM Cloudboot Compute Resource with hardware pass-through, based on CentOS 6

  • Smart - KVM Cloudboot Compute Resource with hardware pass-through, based on CentOS 7

  • Baremetal - XEN CloudBoot Compute Resource, where you can deploy a baremetal server based on CentOS 6 (legacy provisioning)

  • Baremetal - KVM CloudBoot Compute Resource, where you can deploy a baremetal server based on CentOS 7 (new provisioning)

Click Next to proceed to the following step of the wizard to specify the MAC Address.


Step 2 of 5. MAC Address


At this step, select MAC IP Address of the new compute resource. It will be picked up automatically when you first PXE boot a new server on your cluster using the Control Panel. 

Should you receive the "No available Compute Resources discovered" message, you can wait (this step is auto-refreshed every 30 seconds) or click the Refresh button until MAC IP Address appears.

Click Next to proceed to the following step of the wizard to specify the properties.


Step 3 of 5. Properties


At this step, specify the CloudBoot compute resource properties:

  • Label - give the compute resource a name
  • Pxe IP address - select an IP address for this compute resource from the address pool available
  • Enabled - move the slider to the right to allow VSs to be installed/booted on this compute resource
  • Compute Zone - select the compute zone, to which this compute resource will be assigned, from the drop-down list

  • Apply Compute Zone Custom Config - move this slider to the right to apply a compute zone custom config

    If this check box is selected, a compute zone custom config is applied before a compute resource custom config.

  • Custom Config - specify any custom commands you want to run when compute resource is booted

    Centos now defaults to NFSv4. This is known to cause compatibility issues so we strongly recommend that you use NFSv3 for all mounts. This can be done by passing  -t nfs -o vers=3 in any mount commands.

    We strongly recommend that you recheck if custom config doesn't brake any functionality. So before putting in production, the server with changed custom config should be rebooted, and the server behaviour rechecked. We recommend to perform the Storage Health Check and Network Health Check.


  • Show Advanced settings - move this slider to the right to specify advanced compute resource settings:
    • Backup IP address - add a provisioning network IP address
    • CPU Units - set the number of CPU units which will be assigned to the compute resource
    • Collect Stats - move the slider to the right to collect statistics for this compute resource
    • Disable Failover - move the slider to the right to disable VS migration to another compute resource if this compute resource is marked as offline by the Control Panel server

      • Failover option is not available for baremetal servers.
      • If you use automatic failover with write-back caching you may lose some data in the event of a failover.
    • MTU - specify the maximum transportation unit size. You can set the frame size from 1500 to 9000 bytes

      The maximum transportation unit (MTU) is the maximum size of a unit that can be transmitted transferred via ethernet traffic. Any data that exceed the specified MTU value will be divided into smaller units before being transferred. Utilization of jumbo frames allows you to reduce/increase throughput (depending on a set frame size) and increase CPU utilization during large size file transfers. 

    • SAN bonding mode - choose bonding mode type from the dropdown menu

      After editing the SAN bonding mode option, it is required to reboot your Compute Resource to apply the settings.

      Please note, that using more than one NIC for SAN subnet requires switch support. Please ensure that your network infrastructure supports the utilized NIC bonding and is configured correctly. By default, the utilized NICs bonding mode is  IEEE 802.3ad Dynamic link aggregation which requires grouping appropriate ports together according to the section 5 Switch Configuration of Linux Ethernet Bonding Driver guide.

    • Storage Controller RAM - specify the storage controller RAM value (minimum 640 MB, maximum 4096 MB)
    • Storage Controller DB size - select the storage controller DB size value (minimum 128 MB, maximum 256 MB) 
    • Drives per Controller -  specify the number of disks per controller virtual server. You can specify from 1 to 4 disks. By default, the controller virtual server is created per 4 disk drives.
    • Dom0 RAM - allocate the amount of memory in MB for Dom0 on Xen compute resources. You need to allocate at least 3072 MB of Dom0 RAM. 
    • 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 Tools menu at Settings > Compute resources > Compute resource page.

      Currently, a command or commands should be written in one line separated with semicolon. If the command(s) is written in two lines you will receive a "fail" response, although the transaction will be performed.

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


Step 4 of 5. Devices


At this step the compute resource is rebooted and the new configuration, set in step 3, is applied. It can take some time (the wizard makes 10 attempts with 1 minute interval). Once the compute resource comes back online you will be shown a list of devices that it contains - currently these are disks, cache settings and network interfaces. After the compute resource is created these devices can be further managed from the Control Panel (Settings > Compute Resources > label of compute resource > Tools > Manage devices).

Devices are unassigned by default. You can assign disks and network interfaces to a particular task.

Disks 

Disks can be assigned to Storage (typical option when disk is connected to Integrated Storage) or to Cache (as cache device). To assign disks to one of these tasks, click on the required task near the device. Move the Format all assigned disks slider to the right to enable formatting for all disks, which are assigned to a particular task. You will get a confirmation pop-up window before formatting disks.

When you assign disk to Cache, then SSD caching is enabled. This feature increases disk I/O performance. There are two basic cache modes of operation:

  • Write-through: improves read I/O performance, no impact on reliability
  • Write-back: improves both read and write I/O performance, small chance of data loss.

Caching can be configured on two levels: per data store and per disk. For more information, refer to the SSD Caching section of OnApp Storage guide.

Cache Settings

Cache settings include the following options: 

  • Number of cache mirrors - specify the number of cache mirrors for the compute resource
  • Number of cache stripes - specify the number of cache stripes for the compute resource

Network Interfaces

Network interfaces can be assigned to SAN. Using more than one NIC for SAN subnet requires switch support. Ensure that your network infrustructure supports the utilized NIC bonding and is configured correctly. 

Ensure that the Compute Resource Devices permissions are on before managing devices. For more information, refer to the List of all OnApp Permissions section of this guide.

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


Step 5 of 5. Finalize


At this step, wait until compute resource devices configuration is applied. Then you will be indicated that compute resource is successfully configured and ready for operation. Click the Complete button. The compute resource will be added to the system. You can view it under the Compute resources menu. You do not need to power cycle the Compute resource manually, the Control Panel handles this remotely and takes care of the configuration automatically.


Edit CloudBoot Compute Resource



To edit a CloudBoot compute resource:

  1. Go to your Control Panel's Settings menu.
  2. Click the Compute Resources icon.
  3. Click the Actions button next to the CloudBoot compute resource you want to edit and then click Edit.
  4. On the screen that follows, change details as required:

    Properties

    • Label - the compute resource's name
    • MAC - the MAC address of the compute resource
    • Backup IP address - provisioning network IP address
    • CPU Units - set the amount of CPU units assigned to 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. 

      • The Failover option is not available for baremetal servers.
      • If you use automatic failover with write-back caching, you may lose some data in the event of a failover.
    • Failover Recipe - select a recipe to run before the failover process

    • Pxe IP address - select a new IP address for this compute resource from the address pool

      • When you change the Pxe IP address, you should reboot the CloudBoot compute resource immediately after saving the new settings. If you do not reboot the resource immediately, the Control Panel will fail to connect to the new IP address, causing failover transactions. You can reboot the compute resource manually from the console or use the Power Cycle command (if configured).
        You cannot use the Reboot option on the CP UI to reboot the resource after changing the IP address.
        You can also change the IP address of a CloudBoot compute resource that is offline and once the resource is booted, it will be available on the new IP Address.

      • If InfiniBand is enabled for CloudBoot, you should change a value of the cloud_boot pxe config after changing the Pxe IP address.


      Advanced

      Move the Advanced slider to the right to edit advanced Compute resource settings:

    • MTU - specify the maximum transportation unit size. You can set the frame size from 1500 to 9000 bytes

      The maximum transportation unit (MTU) is the maximum size of a unit that can be transmitted transferred via ethernet traffic. Any data that exceed the specified MTU value will be divided into smaller units before being transferred. Utilization of jumbo frames allows you to reduce increase throughput and increase CPU utilization during large size file transfers.

    • SAN bonding mode - choose bonding mode type from the drop-down menu

      After editing the SAN bonding mode option, it is required to reboot your compute resource to apply the settings.

      Please note that using more than one NIC for SAN subnet requires switch support. Please ensure that your network infrastructure supports the utilized NIC bonding and is configured correctly. By default, the utilized NICs bonding mode is  IEEE 802.3ad Dynamic link aggregation which requires grouping appropriate ports together according to the section 5 Switch Configuration of Linux Ethernet Bonding Driver guide.

    • Storage Controller RAM - specify the storage controller RAM value (minimum 640 MB, maximum 4096 MB)
    • Storage Controller DB size - select the storage controller DB size value (minimum 128 MB, maximum 256 MB) 
    • Drives per Controller - specify the number of disks per controller virtual server. You can specify from 1 to 4 disks. By default, the controller virtual server is created per 4 disk drives.
    • Dom0 RAM - allocate the amount of memory in MB for Dom0 on Xen compute resources. You need to allocate at least 3072 MB of Dom0 RAM. 
    • Storage VLAN - select VLAN for Integrated Storage Network

      After editing the Storage VLAN, it is required to reboot your compute resource to apply settings. By default, Storage VLAN is set to 0 that is equal to no VLAN. If you already use a VLAN parameter in onappstore.conf that was added manually, please change the Storage VLAN parameter for each compute resource and save the CP configuration after editing to regenerate boot configuration. These requirements do not apply to VLAN used by means of a custom config script.

    • Apply Compute Zone Custom Config - move this slider to the right to apply a Compute Zone custom config

      If this check box is selected, a Compute Zone custom config is applied before a CloudBoot compute resource custom config.

    • Сustom Config - specify any custom commands you want to run when a compute resource is booted
    • 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 Settings > Compute resources > Compute resource page.

      Currently, a command or commands should be written in one line separated by a semicolon. If the command(s) 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 user onapp, this may be any script created in bash.
    5. Click the Save button to save your changes.

You can manage CloudBoot compute resource devices (disks, network interfaces, and PCI devices) on the Devices page. For more information, refer to Manage CloudBoot Compute Resource Devices.



Edit Baremetal CloudBoot Compute Resource



To edit a Baremetal CloudBoot compute resource:

  1. Go to your Control Panel's Settings menu.
  2. Click the Compute resources icon.
  3. Click the Actions button next to the CloudBoot compute resource you want to edit and then click Edit.
  4. On the screen that follows, change details as required:
    • Label - the compute resource's name
    • CPU units - the amount of CPU units assigned to this compute resource
    • Enabled - enable or disable the ability to install/boot virtual servers on this compute resource
    • Pxe IP address - select a new IP address for this compute resource from the address pool

      • When you change the Pxe IP address, you should reboot the CloudBoot compute resource immediately after saving the new settings. If you do not reboot the resource immediately, the Control Panel will fail to connect to the new IP address. You can reboot the compute resource manually from the console or use the Power Cycle command (if configured).
        You cannot use the Reboot option on the CP UI to reboot the resource after changing the IP address.
        You can also change the IP address of a CloudBoot compute resource that is offline and once the resource is booted, it will be available on the new IP Address.

      • If InfiniBand is enabled for CloudBoot, you should change a value of the cloud_boot pxe config after changing the Pxe IP address.
    • Apply Compute Zone Custom Config - move this slider to the right to apply a Compute Zone custom config

      If this check box is selected, a Compute Zone custom config is applied before a CloudBootcomputeResource custom config.

    • Сustom Config - specify any custom commands you want to run when a compute resource is booted
    • 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 Settings > Compute resources > Compute resource page.

      Currently, a command or commands should be written in one line separated by semicolon. If the command(s) 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 user onapp, this may be any script created in bash.
  5. Click the Save button to save your changes.

Edit Smart CloudBoot Compute Resource


To edit a Smart CloudBoot compute resource:

  1. Go to your Control Panel's Settings menu.
  2. Click the Compute resources icon.
  3. Click the Actions button next to the CloudBoot compute resource you want to edit and then click Edit.
  4. On the screen that follows, change details as required:

    Properties

    • Label - the Compute resource's name
    • Backup IP address - provisioning network IP address
    • CPU units - the amount of CPU units assigned to 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

      If you use automatic failover with write-back caching you may lose some data in the event of a failover.

    • Pxe IP address - select a new IP address for this compute resource from the address pool

      • If you change the Pxe IP address, you should perform a manual reboot of a Smart CloudBoot compute resource after saving new settings.
      • If InfiniBand is enabled for CloudBoot, you should change a value of the cloud_boot pxe config after changing the Pxe IP address.

    Storage disks

    • Move the slider next to the available disk to the right to select it for this Compute resource.

    Storage NICs

    For each Compute resource NIC, you can use one of the following options:

    • Unassigned - leave the NIC unused.
    • SAN subnet - select this option to use this interface for the storage network. In this case, the NIC interface will be bonded with the virtual network interface of the Storage Controller Server.
    • Passthrough to storage - this option is available for Xen CloudBootcompute resources. The network interface will be added to the Storage Controller Server without the bond and the Storage Controller Server will have the complete control over this interface. 
    • Passthrough to Guest - this option is available for smart CloudBoot compute resources. The network interface will be added to the smart server.

    Advanced

    Move the Advanced slider to the right to edit advanced compute resource settings:

    • MTU - specify the maximum transportation unit size. You can set the frame size from 1500 to 9000 bytes

      The maximum transportation unit (MTU) is the maximum size of a unit that can be transmitted transferred via ethernet traffic. Any data that exceed the specified MTU value will be divided into smaller units before being transferred. Utilization of jumbo frames allows you to reduce increase throughput and increase CPU utilization during large size file transfers.


    • Storage controller RAM - specify the storage controller RAM value (minimum 640 MB)
    • Storage Controller DB size - select the storage controller DB size value (minimum 128 MB, maximum 256 MB) 
    • Drives per controller - specify the number of disks per controller virtual server. You can specify from 1 to 4 disks. By default, the controller virtual server is created per 4 disk drives.
    • Allow unsafe assigned interrupts - move this slider to the right to allow/restrict unsafe assigned interruptsThis parameter is enabled automatically during the smart CloudBoot Compute resource creation if the Compute resource does not support interrupt remapping.

    • Storage VLAN - select VLAN for Integrated Storage Network 

      After editing the Storage VLAN, it is required to rebootyourcomputeresource to apply settings. By default, Storage VLAN is set to 0 that is equal to no VLAN. If you already use a VLAN parameter inonappstore.conf that was added manually, please change the Storage VLAN parameter for eachcomputeresource andsavethe CP configuration after editing to regenerate boot configuration. These requirements do not apply to VLAN used by means of a custom config script.

    • Apply Compute Zone Custom Config - move this slider to the right to apply a Compute Zone custom config

      If this check box is selected, a Compute Zone custom config is applied before a CloudBootcomputeresource custom config.

    • Сustom config - specify any custom commands you want to run when Compute resource is booted
    • 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 Tools menu at Settings > Compute resources > Compute resource page.

      Currently, a command or commands should be written in one line separated by semicolon. If the command(s) 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 user onapp, this may be any script created in bash.

Delete Compute Resource


Compute resources can be removed from your cloud if required. A Compute resource cannot be removed until all of the virtual servers assigned to it are migrated to another Compute resource. 

To remove a Compute resource:

  1. Go to your Control Panel's Settings menu.
  2. Click the Compute resources icon.
  3. Click the Actions button next to the Compute resource you want to delete, then click Delete.