cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitin Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7154) CLONE - Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine that too above host capacity
Date Fri, 25 Jul 2014 20:50:38 GMT

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

Nitin Mehta commented on CLOUDSTACK-7154:
-----------------------------------------

4.2.1 is already out. Closing this wrongly cloned bug.

> CLONE - Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine
that too above host capacity
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7154
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7154
>             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.2.1
>
>
> 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.2#6252)

Mime
View raw message