You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/05/07 12:25:16 UTC

[jira] [Updated] (CLOUDSTACK-2298) Dynamic scaleup of CPU/Memory of instance is not updating Accout/Domain resources usage

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

Sudha Ponnaganti updated CLOUDSTACK-2298:
-----------------------------------------

    Fix Version/s: 4.2.0
    
> Dynamic scaleup of CPU/Memory of instance is not updating Accout/Domain resources usage
> ---------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2298
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2298
>             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: Sailaja Mada
>             Fix For: 4.2.0
>
>
> Setup:  Advanced Networking Zone, Xen 6.1 , MS- RHEL 6.3
> Steps:
> 1. Deploy  instance as ROOT admin with 2 GB memory offering
> 2. Scaleup the VM to 6000 MB offering
> 3. Verify the resources usage of account after scale up
> Observation:
> Dynamic scaleup of CPU/Memory of instance is not updating Accout/Domain resources usage
> 1) Resources usage before scaleup:
> <cpulimit>Unlimited</cpulimit><cputotal>2</cputotal><cpuavailable>Unlimited</cpuavailable><memorylimit>Unlimited</memorylimit><memorytotal>2048</memorytotal><memoryavailable>Unlimited</memoryavailable>
> 2) Resources usahe after scaleup
> <cpulimit>Unlimited</cpulimit><cputotal>2</cputotal><cpuavailable>Unlimited</cpuavailable><memorylimit>Unlimited</memorylimit><memorytotal>2048</memorytotal><memoryavailable>Unlimited</memoryavailable>

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