CloudBoot functionality is a method of compute resource installation without the presence of a local disk or other local storage, utilizing the PXE and DHCP servers. In other words, Cloudboot refers to a type of compute resource that is booted from an image generally hosted on the Control Panel server.
This allows users to both lower their hardware requirements on the compute resources (no local storage is required to boot a compute resource) as well as make the process of adding new compute resources to the cloud more efficient:
- No manual admin work required to boot compute resources
- No local storage needed to boot compute resources
- Self-discovery of new compute resources added to the cloud
- Ability to move compute resources quickly between zones
Cloudboot compute resources are required for the use of OnApp Integrated Storage.
To start using CloudBoot, you must enable CloudBoot and Storage in the system configuration first (Admin > Settings > Configuration > CloudBoot). Visit the Configuration Settings chapter for more details.
It’s recommended that you create a separate network for compute resources when using the CloudBoot system to prevent errors of other servers (not compute resources) on the cloud to boot into the CloudBoot network. All Compute resources must reside on the same VLAN (this concerns compute resources only, not the VS’s themselves).
Since CloudBoot compute resources are booted from an image, some configurations will not be saved after reboots. You can use the Custom Config option to effectively save configurations. The custom config executes as a script on the compute resource any time it is booted.
The following CloudBoot features are not currently available (they will be introduced in future releases):
- Bonded NICs for the management/boot interface
For details on how to create a CloudBoot compute resource, refer to the Create CloudBoot Compute Resource section.