[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jessica Tomechak updated CLOUDSTACK-867:
----------------------------------------

    Assignee: Jessica Tomechak  (was: prashant kumar mishra)
      Status: Open  (was: Ready To Review)

Some minor modifications requested by Nitin.

Correction 1 (check for "*") ----> Make it vmware tools instead of vmtools
<listitem><para>VM*Ware* Tools or XenServer Tools must be installed on the
virtual machine.</para></listitem>


Correction 2 (check for "*") ----> Remove the decrease word.
t is not always possible to accurately predict the CPU and RAM requirements
+                       when you first deploy a VM.
+                       You might need to increase or *decrease* these
resources at any time during the life of a VM.
+                       You can dynamically modify CPU and RAM levels to
+                       change these resources for a running VM without
incurring any downtime.



Addition 1 ---->
For dynamic scaling to work virtual machine should have XS tools / VMware
tools installed on it. To ensure this Admin/User can do it in two ways :-
* Admin/User while registering the template provides an input whether
tools are installed on the template(or can be done using update template
API).
* If the user deploys a virtual machine with a template that does not have
XS tools / VMware tools and later if he/she installs the tools on the VM
then he can inform Cloudstack using using updatevirtualmachine API. After
installation of tools and updating the virtual machine, user needs to stop
and start the vm from cloudstack in order for dynamic scaling of CPU and
RAM for that VM.


Addition 2 ---->

Some vmware caveats
Limitation - 1 - After dynamically scaling memory user "might" need to run
a couple of commands on Linux OS for new memory to take affect. Further
reading below
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=di
splayKC&externalId=1012764
Limitation - 2 - If a VM is initially assigned a RAM of less than 3gb then
it cannot be dynamically scaled beyond 3gb. Holds true for for Linux 64
bit and windows 7 32 bit guest os. Further reading below.
https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-50-r
elease-notes.html
                
> Document Scaling up CPU and RAM for running VMs 
> ------------------------------------------------
>
>                 Key: CLOUDSTACK-867
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-867
>             Project: CloudStack
>          Issue Type: Sub-task
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Doc
>            Reporter: Radhika Nair
>            Assignee: Jessica Tomechak
>             Fix For: 4.2.0
>
>
> Document Scaling up CPU and RAM for running VMs 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to