OnApp’s ‘cloudboot’ diskless boot system enables admins to swiftly add additional compute and backup nodes to an OnApp cloud without having to install a local OS on each server.
After adding a cloudboot compute node to your cloud, you can create bonded interfaces for storage traffic and appliance (virtual server) traffic.
To create a storage bond, assign two or more NICs to the SAN at the edit devices page:
The bonding mode can be selected in the edit compute resource page under ‘advanced settings’ (from OnApp v5.0 onwards):
By adding five commands to the custom config section, you can create an appliance bond from two NICs.
Here is an example:
nic0=`ifconfig -a | grep -i 18:66:DA:6E:1D:32 | cut -f1 -d " " `
nic1=`ifconfig -a | grep -i 18:66:DA:6E:1D:34 | cut -f1 -d " " `
echo -e 'DEVICE=appbond\nTYPE=BOND\nBONDING_OPTS="mode=1"'>/etc/sysconfig/network-scripts/ifcfg-appbond
ifenslave appbond $nic0 $nic1
In this example, the bond device name is appbond, the bonding mode is 1 (active-backup) and the MAC addresses of the slave NICs are 18:66:DA:6E:1D:32 and 18:66:DA:6E:1D:34.
I hope that helps – if you need more advice with your OnApp cloud, open a ticket and the cloud architecture team will be happy to help!