Allocating Resources

Resources are allocated to a machine from the Cluster based on the Template instructions. If you create a VM from the Instance menu, it will instantiate based on predefined Template parameters; however, if you work the creation via the Template menu, after clicking Instantiate, you are given the opportunity to adjust these resource allocations prior to fully standing up the machine. If it is found to require more resources, these values can be updated, but an outage will be necessary.

Memory

When initially instantiating a machine, it is necessary to allocate enough RAM to sufficiently process the tasks the box will handle; therefore, if you have a base Template with the desired OS and any Appliances pre-loaded, etc. you can navigate to the Template menu and click VM and select the base Template.

From here you assign the desired Memory allocation, making sure that the units (e.g. GB vs MB) are correctly selected from the dropdown list beside the input field.

To adjust the Memory, select the desired Instance that is running, from this pane you can Power Off the machine, which can be found at the top of the screen in the Power Button dropdown list. You will need to wait a short time for the system to power off the machine and may need to hit the Refresh button at the top of the pane after a few moments.

Navigate to the Capacity view and you should see that the Resize button is now available. Click this button to pull up the Resize VM Capacity pop-up and adjust as desired. When adjustments are complete, press the Resize button at the bottom of the pop-up window and then you can restart the machine by pressing the now highlighted Resume button.

CPU

CPU cycle allocation is scheduled by the hypervisor, and when instantiating a VM, you are required to provide two fields with information, Physical CPU, that will be reserved for the VM, and Virtual CPU, that will be available to the machine. The steps required to alter the CPU allocation are the same as adjusting the Memory, the device will need to be powered off and resumed after the adjustment is made as laid out above.

Important

Allocation of the Physical CPU is weighted by 100 for each thread of the CPU and an ideal ratio for desired Virtual CPU resources vs Physical CPU resources is 10:1; therefore, if the desired vCPUs are 4, the input for physical CPU allocation should be 0.4. This allows for oversubscription of the physical resources among multiple virtual devices and prevents one device from over utilizing the cloud's resources.

Disk

The disk(s) associated with the VM can be set by the Template and additional disks can be added during instantiation; however, if the need arises to alter the capacity of the VM, the option to add storage to them is available when the VM is in the "Running" State. Disks are created from Images and a Generic Storage Datablock can be created or imported to add to the VM.

Danger

Volatile disks should never be used in a HyperCloud instance.