You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nitin Mehta (JIRA)" <ji...@apache.org> on 2014/01/08 19:10:55 UTC

[jira] [Resolved] (CLOUDSTACK-4881) Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine that too above host capacity

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

Nitin Mehta resolved CLOUDSTACK-4881.
-------------------------------------

    Resolution: Fixed

Closing this...based on the discussion

> Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine that too above host capacity
> ----------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4881
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4881
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.3.0
>            Reporter: Gaurav Aradhye
>            Assignee: Nitin Mehta
>            Priority: Blocker
>             Fix For: 4.3.0
>
>
> changeServiceForVirtualMachine API can be used to scale up a running vm also (It should be effective against only stopped vm)
> More over, using this API, VM can be scaled up above host capacity (both CPU and RAM) without any over-provisioning of resources.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)