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

ASF subversion and git services commented on CLOUDSTACK-2987:
-------------------------------------------------------------

Commit f7f826d4f516144069e26b3bb112e8c22414123e in branch refs/heads/master 
from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=f7f826d ]

CLOUDSTACK-2987: UI > Templates menu > register template action: add 
Dynamically Scalable field.

                
> Ensure XStools to be there in template inorder to enable dynamic scaling of vm
> ------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2987
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2987
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> XS tools need to be installed on the guest vm for Xenserver for memory 
> dynamic scaling and over provisioning to work.
> XStools contain baloon drivers that are required to dynamically manipulate 
> the memory attributes (dynamic max/min). If they are altered at run time 
> without these tools, it can lead to unstable behavior for vm and  potential 
> crash. Both for memory dynamic scaling and over provisioning this is 
> required. 
> So we need to be able to ensure whether xstools are installed on the template 
> based on the user inputs while registering the template and use the same to 
> set different memory/cpu values to make dynamic scaling work. 

--
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