Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3BBC41087E for ; Sun, 5 Jan 2014 21:34:51 +0000 (UTC) Received: (qmail 66687 invoked by uid 500); 5 Jan 2014 21:34:51 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 66624 invoked by uid 500); 5 Jan 2014 21:34:50 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 66612 invoked by uid 500); 5 Jan 2014 21:34:50 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 66609 invoked by uid 99); 5 Jan 2014 21:34:50 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Jan 2014 21:34:50 +0000 Date: Sun, 5 Jan 2014 21:34:50 +0000 (UTC) From: "Nitin Mehta (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-4881) Both Running and stopped vm can be scaled up using old API changeServiceForVirtualMachine that too above host capacity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-4881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13862662#comment-13862662 ] Nitin Mehta commented on CLOUDSTACK-4881: ----------------------------------------- Marcus - To your question - "Who decided it was right to only allow editing the offering while the VM was off?" - Let me just tell you what the behavior is. changeServiceForVirtualMachine - should change the service offering of a stopped vm and has been in CS since 3.0.x or before. Recently there was a bug introduced where it was allowing to change the service offering of a running vm as well. That was never intended and breaks compatibility and tests and has been fixed with this bug. This api will be deprecated in 5.0 scaleVirtualMachine - introduced in 4.2, this should allow changing the service offering of a running as well as stopped vm. You can use this api to edit the offering whenever you want. If you were using changeServiceForVirtualMachine for changing the offering of a running and stopped vm, I would say please change that and start using scaleVirtualMachine instead because changeServiceForVirtualMachine has been since ages only supporting editing the offering for 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 > 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)