To create a CloudBoot compute resource, use the following request:
XML Request Example
JSON Request Example
hypervisor - an array of compute resource details:
- label* - the name of the compute resource
- pxe_ip_address_id* - the ID of Cloud Boot IP address that will be used for this compute resource
- hypervisor_type - compute resource type:
kvmYou can only specify the KVM type for smart CloudBoot compute resource provisioning.
- segregation_os_type - an operating system type (can be Any OS, Windows only or Non-Windows)
- server_type - specify the type of servers that will be deployed on this compute resource:
- smart - specify the smart server type to use this compute resource for smart server deployment. The server_type is virtual by default.
- backup_ip_address - provisioning network IP address
- enabled - set 1 to enable this compute resource, otherwise set 0
- collect_stats - set 1 to collect statistics for this compute resource, otherwise set 0
- disable_failover - optional parameter. Set true to disable compute resource failover, otherwise false
- failover_recipe_id - the ID of a recipe to run before the failover process
- format_disks - set 1 to format compute resource's disks during creation, otherwise set 0
- passthrough_disks - set 1 if the disks should be passed through to the storage nodes, otherwise set 0. This parameter is for Xen compute resources only.
storage - an array of compute resource disks' details:
- disks - an array of compute resource disks, where:
- scsi - SCSI inquiry product revision number
- selected - set 1 to select a disk , otherwise set 0
- nics - network interfaces that will be used for storage, where:
- mac - network interface MAC address
- type - network interface type:
- 0 - leave the NIC unused
- 1 - SAN subnet - select this option to use this interface for storage network. In this case, the NIC interface will be bonded with the virtual network interface of the Storage Controller Server
- 2 - 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 complete control over this interface
- 3 - passthrough to Guest - this option is available for smart CloudBoot compute resources. The network interface will be added to the smart server
- custom_pcis - an array of custom PCI devices
- pci - NIC PCI
- selected - 1 if the PCI is selected, otherwise false
mtu - maximum transferrable unit value. 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. The utilization of jumbo frames allows to reduce increase throughput and increase CPU utilization during large-size file transfers.
- storage_controller_memory_size - specify the storage controller memory size (minimum 640 MB)
- disks_per_storage_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 - set true if the compute resource does not support the interrupt remapping, otherwise set false. Note: With allow_unsafe_assigned_interrupts parameter enabled, smart server is exposed to the PCI passthrough MSI trap injection.
custom_config - specify any custom commands you want to run when compute resource is booted
XML Output Example
- added the following parameters:
- added the following parameters:
- type (storage parameter)