[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13739299#comment-13739299
 ] 

prashant kumar mishra edited comment on CLOUDSTACK-867 at 8/18/13 4:38 AM:
---------------------------------------------------------------------------

Hi following changes required:

1-

Actual
-----------
  <listitem><para>New VMs that are created
  66                                 after the installation of &PRODUCT; 4.2.
  67                                 If you are upgrading from a previous 
version of &PRODUCT;,
  68                                 your existing VMs created with previous 
versions
  69                                 will not have the dynamic scaling 
capability.</para>


Changes
---------------------------------------
after line/step 69 we should add following:

If you want to make existing vm (created before upgrade ) you need to update 
them ,before update make sure zone level setting  "dynamic scalable" =true 

update vm
---------------
1-install tools (XS tools/VMware tools) if its not already installed 
2-Stop vm
3-mark  isdynamic scalable check box
4-Start vm



2-
Actual
----------
<para>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.</para>


Following should be added
---------------------------------------
if resources are not available on current host, scaling up will fail on VMware 
because  of issue https://issues.apache.org/jira/browse/CLOUDSTACK-1809

-->please  check issue https://issues.apache.org/jira/browse/CLOUDSTACK-2985

                
      was (Author: prashantkm):
    Hi following changes required:

1-

Actual
-----------
  <listitem><para>New VMs that are created
  66                                 after the installation of &PRODUCT; 4.2.
  67                                 If you are upgrading from a previous 
version of &PRODUCT;,
  68                                 your existing VMs created with previous 
versions
  69                                 will not have the dynamic scaling 
capability.</para>


Changes
---------------------------------------
after line/step 69 we should add following:

If you want to make existing vm (created before upgrade ) you need to update 
them ,before update make sure zone level setting  "dynamic scalable" =true 

update vm
---------------
1-install tools (XS tools/VMware tools) if its not already installed 
2-Stop vm
1-mark  isdynamic scalable check box
2-Start vm



2-
Actual
----------
<para>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.</para>


Following should be added
---------------------------------------
if resources are not available on current host, scaling up will fail on VMware 
because  of issue https://issues.apache.org/jira/browse/CLOUDSTACK-1809

-->please  check issue https://issues.apache.org/jira/browse/CLOUDSTACK-2985

                  
> 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