CloudBoot compute resources are created in Control Panel's Settings menu. To add a compute resource:
- Configure the IP range which the Control Panel will assign to compute resources.
- Add specific compute resources to the Control Panel itself.
On this page:
Create an IP range
To create an IP range:
- Go to your Control Panel’s Settings menu and click the Compute resources icon.
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.
- 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).
- 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:
- Go to your Control Panel's Settings > Compute Resources menu.
- Click the Add New CloudBoot Compute Resource button at the bottom of the screen.
- Fill in the wizard step by step. Each of these steps is described in the corresponding sections below.
- 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, where you can deploy VSs
- Xen 3 - Xen 3 CloudBoot Compute Resource, based on CentOS 5
Xen 4 - Xen 4 CloudBoot Compute Resource, based on CentOS 6
Backup - KVM CloudBoot Provisioning and Backup Resource, for backups maintenance
Smart - KVM Cloudboot Compute Resource, where you can deploy a smart server
Baremetal - XEN CloudBoot Compute Resource, where you can deploy a baremetal server
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
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
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)
- 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
- 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
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, network interfaces and PCI devices. 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. To assign a device to a particular task, click on the required task near the device. Devices can be assigned to different tasks:
Disks can be assigned to Storage (typical option when disk is connected to Integrated Storage) or to Cache (as cache 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 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.
- Network interfaces can be assigned to SAN
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.