Edit Compute Zone

To edit Compute zones:

  1. Go to your Control Panel > Admin > Settings menu, and click the Compute Zones icon.
  2. The screen that appears will show all zones currently set up in the cloud.
  3. Click the Actions button next to the required Compute zone, then click Edit. You can edit the following Compute zone details:

See also:

Properties

  • Label -  Compute zone's name
  • Location group - location group to which the Compute zone is assigned. You can change the already set location if there are no virtual servers built on Compute resources of this zone.

  • Release resource type - Compute zone's resource type. This option allows you to free up the Compute resource resources and over-commit RAM, CPU and CPU shares by means of the virtual servers that are shut down. By default, the Compute zone is created with the Memory Guarantee option enabled. In this case, the over-committing cannot be used. To enable resource releasing, choose either the Ballooning or Only Started VS option.

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

    • Ballooning (KVM Compute resources only) - free Compute resource memory is calculated with the ability to use memory over-committing.  

      • A 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. 
      • When using ballooning option it is impossible to monitor the exact free compute resource memory as it is a floating value. Therefore some VS edit or start actions may fail.

    • Only started VS - only the memory of running virtual servers is calculated.

  • Max VS to start at once - the maximum number of virtual servers that can be started simultaneously on this Compute resource (5 recommended). This option ensures that virtual servers with VIP status will be booted prior to other servers.

  • Placement type - specify the Compute resource selection algorithm, that will be used on virtual server provisioning and recovery, per Compute zone: 

    • Take HV with maximum free RAM (Sparse) - set this type to select the Compute resource with maximum free RAM during the VS recovery. This option allows performing faster migration of virtual servers with the lesser (sparse) number of iterations during the failover.

      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.

    • Take HV with minimum free RAM (Dense) - with this type the system selects the Compute resource with the minimum required free RAM. This option allows filling Compute resource as densely as possible before starting to use next Compute resource in the zone. 

  • Failover timeout - the time period in minutes for which the iterations will run during the failover if the Compute resource does not respond. To manage failover, refer to Manage Failover section of this guide.
  • CPU Units - edit a number of CPU units assigned to each Compute resource in this zone by default.
  • Set max memory (appears only if ballooning release resource type is chosen)  - move the slider to the right to enable max memory parameter for every VS within the compute zone. The max memory parameter will be set as 90% of free compute resource memory.
  • CPU guarantee - move the slider to the right to ensure there is enough CPU on the Compute zone to create a new VS. 
  • Update Compute resource CPU units - move the slider to apply the edited number of CPU units to all the Compute resources in this zone.

    • Run Sysprep -  enable or disable Windows virtual server deployment without running sysprep.

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

    • CPU Model Configuration - select the type of CPU model configuration

      • Default KVM - regular CPU model configuration with no default CPU flags
      • Extended CPU Configuration - CPU model with a set of extended CPU flags that can be applied to new and existing VSs in a zone
      • Passthrough Host CPU - CPU model with a set of default and additional flags automatically applied to existing and new VSs

    • Instance Package VSs - move the slider to the right if you want the zone to be used when creating Instance Package VSs only. If you enable this option, the zone will not be available in the virtual server creation wizard's Resources step for custom VSs (VSs built by setting resources manually). If this slider does not appear, this zone is inappropriate for creating Instance Package VSs.

      Note that Instance Package VSs can only be created on compute resources within compute zones where all compute resources are assigned the same amount of CPU units. If there are compute resources with different amount of CPU units set in a zone, it will not be possible to create Instance Package VSs in such zones. The reason is that CPU priority for Instance Package VSs in this configuration cannot be set to 100%, which is the default value for such virtual servers.

    • Custom Config - add or edit any custom commands you want to run when a compute zone is booted.

      The custom configs are only applicable to Virtual, Smart, and Baremetal compute zones.

      Integrated Storage

    • Use local reads path - minimize the network throughput dependency for read-heavy workloads. When the Use Local Read Path option is enabled, reads go over the local software bridge to a local replica of the data rather than traverse a physical NIC + switch.

4.  Click the Save button to save your changes.