Changing the Service Offering for a VM

Committed: Thu Aug 29 14:22:10 2013 +0530 ---------------------------------------------------------------------- docs/en-US/changing-service-offering-for-vm.xml | 288 +++++++++++-------- 1 file changed, 166 insertions(+), 122 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cloudstack/blob/3077c992/docs/en-US/changing-service-offering-for-vm.xml ---------------------------------------------------------------------- diff --git a/docs/en-US/changing-service-offering-for-vm.xml b/docs/en-US/changing-service-offering-for-vm.xml index 9458b38..f4e2ceb 100644 --- a/docs/en-US/changing-service-offering-for-vm.xml +++ b/docs/en-US/changing-service-offering-for-vm.xml @@ -22,125 +22,169 @@ under the License. -->

- Changing the Service Offering for a VM - To upgrade or downgrade the level of compute resources available to a virtual machine, you can change the VM's compute offering. - - Log in to the &PRODUCT; UI as a user or admin. - In the left navigation, click Instances. - Choose the VM that you want to work with. - (Skip this step if you have enabled dynamic VM scaling; see .) - Click the Stop button to stop the VM. - - - - - - StopButton.png: button to stop a VM - - - - Click the Change Service button. - - - - - ChangeServiceButton.png: button to change the service of a - VM - - - The Change service dialog box is displayed. - Select the offering you want to apply to the selected VM. - Click OK. - -

- - CPU and Memory Scaling for Running VMs - (Supported on VMware and XenServer) - It is not always possible to accurately predict the CPU and RAM requirements - when you first deploy a VM. - You might need to increase these resources at any time during the life of a VM. - You can dynamically modify CPU and RAM levels to - scale up these resources for a running VM without incurring any downtime. - Dynamic CPU and RAM scaling can be used in the following cases: - - User VMs on hosts running VMware and XenServer. - System VMs on VMware. - VMware Tools or XenServer Tools must be installed on the virtual machine. - The new requested CPU and RAM values must be within the constraints allowed by the hypervisor - and the VM operating system. - New VMs that are created - after the installation of &PRODUCT; 4.2 - can use the dynamic scaling feature. - If you are upgrading from a previous version of &PRODUCT;, - your existing VMs created with previous versions - will not have the dynamic scaling capability - unless you update them using the following procedure. - - -

- Updating Existing VMs - If you are upgrading from a previous version of &PRODUCT;, - and you want your existing VMs created with previous versions - to have the dynamic scaling capability, - update the VMs using the following steps: - - Make sure the zone-level setting enable.dynamic.scale.vm is set to true. - In the left navigation bar of the &PRODUCT; UI, click Infrastructure, then click Zones, click the zone you want, and click the Settings tab. - Install Xen tools (for XenServer hosts) or VMware Tools (for VMware hosts) on each VM - if they are not already installed. - Stop the VM. - Click the Edit button. - Click the Dynamically Scalable checkbox. - Click Apply. - Restart the VM. - -

- Configuring Dynamic CPU and RAM Scaling - To configure this feature, use the following new global configuration variables: - - enable.dynamic.scale.vm: Set to True to enable the feature. By default, the feature is turned off. - scale.retry: How many times to attempt the scaling operation. Default = 2. - -

- How to Dynamically Scale CPU and RAM - To modify the CPU and/or RAM capacity of a virtual machine, - you need to change - the compute offering of the VM to a new compute offering that has the - desired CPU and RAM values. You can use the same steps - described above in , but skip the step where you - stop the virtual machine. Of course, you might have to create a new compute offering first. - When you submit a dynamic scaling request, - the resources will be scaled up on the current host if possible. - If the host does not have enough resources, the VM will be live migrated - to another host in the same cluster. - If there is no host in the cluster that can fulfill the requested level of CPU and RAM, - the scaling operation will fail. - The VM will continue to run as it was before. -

- Limitations - - You can not do dynamic scaling for system VMs on XenServer. - &PRODUCT; will not check to be sure that the new CPU and RAM levels are compatible - with the OS running on the VM. - When scaling memory or CPU for a Linux VM on VMware, you might - need to run scripts in addition to the other steps mentioned above. - For more information, see - Hot adding memory in Linux (1012764) - in the VMware Knowledge Base. - (VMware) If resources are not available on the current host, - scaling up will fail on VMware because of a known issue where &PRODUCT; and vCenter calculate the available capacity differently. - For more information, see - https://issues.apache.org/jira/browse/CLOUDSTACK-1809. - On VMs running Linux 64-bit and Windows 7 32-bit operating systems, - if the VM is initially assigned a RAM of less than 3 GB, - it can be dynamically scaled up to 3 GB, but not more. - This is due to a known issue with these operating systems, which will freeze - if an attempt is made to dynamically scale from less than 3 GB to more than 3 GB. - - -

\ No newline at end of file + Changing the Service Offering for a VM + To upgrade or downgrade the level of compute resources available to a virtual machine, you + can change the VM's compute offering. + + + Log in to the &PRODUCT; UI as a user or admin. + + + In the left navigation, click Instances. + + + Choose the VM that you want to work with. + + + (Skip this step if you have enabled dynamic VM scaling; see .) + Click the Stop button to stop the VM. + + + + + StopButton.png: button to stop a VM + + + + + + Click the Change Service button. + + + + + ChangeServiceButton.png: button to change the service of a VM + + + The Change service dialog box is displayed. + + + Select the offering you want to apply to the selected VM. + + + Click OK. + + +

+ + CPU and Memory Scaling for Running VMs + (Supported on VMware and XenServer) + It is not always possible to accurately predict the CPU and RAM requirements when you + first deploy a VM. You might need to increase these resources at any time during the life of a + VM. You can dynamically modify CPU and RAM levels to scale up these resources for a running VM + without incurring any downtime. + Dynamic CPU and RAM scaling can be used in the following cases: + + + User VMs on hosts running VMware and XenServer. + + + System VMs on VMware. + + + VMware Tools or XenServer Tools must be installed on the virtual machine. + + + The new requested CPU and RAM values must be within the constraints allowed by the + hypervisor and the VM operating system. + + + New VMs that are created after the installation of &PRODUCT; 4.2 can use the dynamic + scaling feature. If you are upgrading from a previous version of &PRODUCT;, your existing + VMs created with previous versions will not have the dynamic scaling capability unless you + update them using the following procedure. + + +

+ Updating Existing VMs + If you are upgrading from a previous version of &PRODUCT;, and you want your existing VMs + created with previous versions to have the dynamic scaling capability, update the VMs using + the following steps: + + + Make sure the zone-level setting enable.dynamic.scale.vm is set to true. In the left + navigation bar of the &PRODUCT; UI, click Infrastructure, then click Zones, click the zone + you want, and click the Settings tab. + + + Install Xen tools (for XenServer hosts) or VMware Tools (for VMware hosts) on each VM + if they are not already installed. + + + Stop the VM. + + + Click the Edit button. + + + Click the Dynamically Scalable checkbox. + + + Click Apply. + + + Restart the VM. + + +

+ Configuring Dynamic CPU and RAM Scaling + To configure this feature, use the following new global configuration variables: + + + enable.dynamic.scale.vm: Set to True to enable the feature. By default, the feature is + turned off. + + + scale.retry: How many times to attempt the scaling operation. Default = 2. + + +

+ How to Dynamically Scale CPU and RAM + To modify the CPU and/or RAM capacity of a virtual machine, you need to change the compute + offering of the VM to a new compute offering that has the desired CPU and RAM values. You can + use the same steps described above in , but + skip the step where you stop the virtual machine. Of course, you might have to create a new + compute offering first. + When you submit a dynamic scaling request, the resources will be scaled up on the current + host if possible. If the host does not have enough resources, the VM will be live migrated to + another host in the same cluster. If there is no host in the cluster that can fulfill the + requested level of CPU and RAM, the scaling operation will fail. The VM will continue to run + as it was before. +

+ Limitations + + + You can not do dynamic scaling for system VMs on XenServer. + + + &PRODUCT; will not check to be sure that the new CPU and RAM levels are compatible + with the OS running on the VM. + + + When scaling memory or CPU for a Linux VM on VMware, you might need to run scripts in + addition to the other steps mentioned above. For more information, see Hot adding memory in Linux (1012764) in the VMware Knowledge Base. + + + (VMware) If resources are not available on the current host, scaling up will fail on + VMware because of a known issue where &PRODUCT; and vCenter calculate the available + capacity differently. For more information, see https://issues.apache.org/jira/browse/CLOUDSTACK-1809. + + + On VMs running Linux 64-bit and Windows 7 32-bit operating systems, if the VM is + initially assigned a RAM of less than 3 GB, it can be dynamically scaled up to 3 GB, but + not more. This is due to a known issue with these operating systems, which will freeze if + an attempt is made to dynamically scale from less than 3 GB to more than 3 GB. + + +

+ +