cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CLOUDSTACK-4881) Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine that too above host capacity
Date Mon, 30 Dec 2013 17:54:51 GMT

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

Marcus Sorensen reopened CLOUDSTACK-4881:
-----------------------------------------


This actually breaks functionality that we (and probably others) have relied on.  We can change
the offering, and then restart the vm at our leisure to apply it.

It might be nice to instead have a value in the vm information that states whether the service
offering listed has been applied yet. This is cleared any time the VM is started, and set
any time the service offering is changed.

> 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.5#6160)

Mime
View raw message