Compute resources are a critical part of the cloud. Compute resources have types which they inherit from the zone to which they belong. This section provides information on how to edit CloudBoot compute resources for different types of servers and how to delete them.


Edit CloudBoot Compute Resource

To edit a CloudBoot compute resource:

  1. Go to your Control Panel > Admin > 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. If you edit a Backup CloudBoot resource type, the Disable Failover parameter is not available
    • 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 edit a Backup CloudBoot resource type, the Disable Failover and Failover Recipe parameters are not available. 
      • 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. You may calculate the amount of memory needed for a storage controller as DB size (128 MB by default) + 10 MB x vDisk parts at the controller.
    • 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

  1. The Dom0 RAM parameter is applicable only to Xen compute resources. Starting from OnApp 6.5, Xen virtualization type is not supported. 

    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 Power Cycle compute resource option, which will execute the entered command will appear at Admin > Settings > Compute Resources > label of a compute resource > Actions > Resource Options

      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 > Admin > 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 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 Power Cycle compute resource option which will execute the entered command, will appear at Admin > Settings > Compute Resources > label of a compute resource > Actions > Resource Options

      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 > Admin > 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 CloudBoot compute 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
  1. The Passthrough to storage option is applicable only to Xen compute resources. Starting from OnApp 6.5, Xen virtualization type is not supported. 

    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. You may calculate the amount of memory needed for a storage controller as DB size (128 MB by default) + 10 MB x vDisk parts at the controller.
    • 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 disabled by default during the smart CloudBoot Compute resource creation

    • 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 inonappstore.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 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 Power Cycle compute resource option, which will execute the entered command will appear at Admin > Settings > Compute Resources > label of a compute resource > Actions > Resource Options

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

See also:

Leave feedback