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 97C2D104C7 for ; Mon, 30 Dec 2013 18:00:09 +0000 (UTC) Received: (qmail 4648 invoked by uid 500); 30 Dec 2013 18:00:07 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 4500 invoked by uid 500); 30 Dec 2013 18:00:00 -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 4476 invoked by uid 500); 30 Dec 2013 17:59:58 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 4310 invoked by uid 99); 30 Dec 2013 17:59:54 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Dec 2013 17:59:54 +0000 Date: Mon, 30 Dec 2013 17:59:54 +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=13858960#comment-13858960 ] Nitin Mehta commented on CLOUDSTACK-4881: ----------------------------------------- Marcus - I do not get what you meant here. Can you please explain the functionality again and if it is still broken because the reporter closed it saying fixed ? Also please explain the solution you give with an example so that I can understand it better. > 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)