You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/12/03 02:27:36 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13837208#comment-13837208 ]
ASF subversion and git services commented on CLOUDSTACK-4881:
-------------------------------------------------------------
Commit d5e497859f770d6e11f603f4c12a041251dbce93 in branch refs/heads/master from [~nitinme]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d5e4978 ]
CLOUDSTACK-4881:
changeServiceForVirtualMachine API should be used to scale up a stopped vm only
> 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
> 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#6144)