Nitin,
Thanks for the quick response.

Jessica T.


On Tue, Aug 20, 2013 at 10:35 PM, Nitin Mehta <nitin.me...@citrix.com>wrote:

>  LGTM.
> Thanks very much Jessica :)
>
>   From: Jessica Tomechak <jessica.tomec...@gmail.com>
> Date: Tuesday 20 August 2013 2:55 PM
> To: Nitin Mehta <nitin.me...@citrix.com>
> Cc: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>, "
> us...@cloudstack.apache.org" <us...@cloudstack.apache.org>, Sudha
> Ponnaganti <sudha.ponnaga...@citrix.com>
>
> Subject: Re: [Doc] Please review: CPU and RAM scaling for running VMs doc
>
>   I have incorporated not only Nitin's comments in this email thread, but
> also others in the bug itself. Please check and verify the fix so I may
> close the doc bug for 4.2.0. This is checked in to both 4.2 and master.
>
>  Diff:
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=2796f01
>
>  Bug:
> https://issues.apache.org/jira/browse/CLOUDSTACK-867
>
>  Thanks for your help,
> Jessica T.
>
>
> On Thu, Aug 8, 2013 at 9:46 PM, Nitin Mehta <nitin.me...@citrix.com>wrote:
>
>> Jessica ­ Thanks for the draft. Looks good. Some minor modifications.
>>
>>
>> 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<http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&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<https://www.vmware.com/support/vsphere5/doc/vsphere-esx-vcenter-server-50-release-notes.html>
>>
>>
>>
>>
>> Thanks,
>> -Nitin
>>
>>
>> From:  Jessica Tomechak <jessica.tomec...@gmail.com>
>> Date:  Friday 9 August 2013 6:41 AM
>> To:  "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
>> Cc:  "us...@cloudstack.apache.org" <us...@cloudstack.apache.org>, Sudha
>> Ponnaganti <sudha.ponnaga...@citrix.com>, Nitin Mehta
>> <nitin.me...@citrix.com>
>> Subject:  Re: [Doc] Please review: CPU and RAM scaling for running VMs doc
>>
>>
>> +cc Nitin
>>
>>
>> On Thu, Aug 8, 2013 at 6:08 PM, Jessica Tomechak
>> <jessica.tomec...@gmail.com> wrote:
>>
>> Hi,
>>
>> CPU and RAM scaling for running VMs doc is ready for review. You can view
>> the updated text at the link below. This is checked in to both master and
>> 4.2 branch.
>>
>> Please provide your feedback.
>>
>> Diff:
>> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=535e74d
>>
>>
>> Bug:
>> https://issues.apache.org/jira/browse/CLOUDSTACK-867
>>
>>
>> Regards,
>> Jessica T.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>

Reply via email to