To add a new compute zone, use the following request:

POST /settings/hypervisor_zones.xml
POST /settings/hypervisor_zones.json

XML Request Example

curl -i -X POST http://onapp.test/settings/hypervisor_zones.xml -d '<pack><label>zaza</label><server_type>virtual</server_type><location_group_id>38</location_group_id><release_resource_type>memory_guarantee</release_resource_type><max_vms_start_at_once>5</max_vms_start_at_once><recovery_type>roundrobin</recovery_type><failover_timeout>15</failover_timeout><run_sysprep>1</run_sysprep><default_gateway></default_gateway><cpu_units>1000</cpu_units></pack>' -u user:userpass -H 'Accept: application/xml' -H 'Content-type: application/xml'

JSON Request Example

curl -i -X POST http://onapp.test/settings/hypervisor_zones.json -d '{"pack":{"label":"zaza", "server_type":"virtual","location_group_id":"38", "release_resource_type":"memory_guarantee", "max_vms_start_at_once":"5", "recovery_type":"roundrobin",
"failover_timeout":"15", "run_sysprep":"1", "default_gateway":"", "cpu_units":"1000"}}' -u user:userpass -H 'Accept: application/json' -H 'Content-type: application/json' 


label* - title of a new compute zone

server_type - specify the type of servers that will reside within this compute zone:

  • virtual  - choose the virtual type to create a Xen, KVM, VMware or CloudBoot zone
  • smart - choose the smart server type to create a smart server zone
  • baremetal - choose the baremetal server type to create a baremetal server zone

location_group -  specify the location group to which the compute zone will be assigned

release_resource_type - specify the release resource type. Release resource option allows to free up compute resources by over-committing RAM, CPU and CPU shares of virtual servers that are shut down.  By default, the compute zone is created with the Memory Guarantee option enabled. In this case the release resources option is not used. Then, to enable resource over-committing you should choose either the Ballooning or Only Started VS option.

  • memory_guarantee - the actual free compute memory is calculated. All virtual servers residing on the compute resource will be able to start. 

  • ballooning - free compute memory is calculated with the ability to use memory over-committing. The ballooning option is only available for KVM compute resources. NOTE: Virtual server may be migrated to another compute resource if there is not enough memory for it to start up on the compute resource with the ballooning option enabled. 

     Do not use the ballooning option if there is at least one edge or storage server within the compute zone. 


  • only_started_vms - only the memory of running virtual servers is calculated.

max_vms_start_at_once - the maximum number of virtual servers that can be started simultaneously within this compute zone

recovery_type - specify the compute resource selection algorithm, which will be used on virtual server provisioning and recovery, per compute zone:

  • roundrobin - set the roundrobin type to select the compute resource with maximum free RAM during the VS recovery

    Note: this option behaves in different ways, depending on the event:

    • On provisioning, the round-robin algorithm will be used on compute resource selection.
    • On recovery, the compute resource with maximum free RAM will be selected.
  • fillnext - select the fillnext type to select the compute resource with minimum required free RAM. This option allows to fill compute resource as tightly as possible before starting to use next appliance in the zone

failover_timeout - time period for which the iterations will run during the failover if the compute resource does not respond

- set 1 to minimise the network throughput dependency for read heavy workloads. When this option is enabled, reads go over the local software bridge to a local replica of the data rather than traverse a physical NIC + switch.

run_sysprep - set 1 to enable Windows virtual server deployment without running sysprep

NOTE: It is not possible to set VS password when creating a Windows-based VMware virtual server without running a sysprep.

cpu_units - set the number of cpu units for applied to each compute resource in this compute zone

VMware parameters:

default_gateway - external gateway IP address. All virtual servers within the compute zone will be rerouted to this gateway.

Page History

v. 3.3:

  • added cpu_units parameters

v. 3.1:

  • added the following parameters:
    • server_type
    • release_resource_type
    • recovery_type
    • run_sysprep
    • failover_timeout