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 80BB810382 for ; Mon, 1 Jul 2013 16:54:25 +0000 (UTC) Received: (qmail 5020 invoked by uid 500); 1 Jul 2013 16:54:25 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 2903 invoked by uid 500); 1 Jul 2013 16:54:22 -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 2154 invoked by uid 500); 1 Jul 2013 16:54:22 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 2080 invoked by uid 99); 1 Jul 2013 16:54:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Jul 2013 16:54:21 +0000 Date: Mon, 1 Jul 2013 16:54:21 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-3279) Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware. 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-3279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696956#comment-13696956 ] ASF subversion and git services commented on CLOUDSTACK-3279: ------------------------------------------------------------- Commit 265c00dcfc9d57a85e94f72ea769588df54abf35 in branch refs/heads/4.2 from [~sateeshc] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=265c00d ] CLOUDSTACK-3279 Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware. Signed-off-by: Sateesh Chodapuneedi > Need mechanism to detect if hotadd for cpu/memory is supported per a specific guest OS supported by VMware. > ----------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-3279 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3279 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: VMware > Affects Versions: 4.2.0 > Reporter: Sateesh Chodapuneedi > Assignee: Sateesh Chodapuneedi > Priority: Critical > Fix For: 4.2.0 > > > Vmware publishes a list for vmware guest os and their supported capabilities for each vmware release. Example for guest OS Ubuntu 10.04 and ESX some release 4.x we only support hot add of vcpu (and not hot add memory) > GuestOS Release > Ubuntu 10.04 Desktop > Supported Releases > ESX 4.1 U31, 2, 3, 4, 5, 6, 4.1 U21, 2, 3, 4, 5, 6, 4.1 U11, 2, 3, 4, 5, 6, 4.12, 1, 6, 5, 4, 3 > Support Details > Hot Add vCPU etc.... > More info @ http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf > Vmware says that the attributes hot add cpu and memory should be turned on during deployment of vm (i.e. As part of deployvm api) so that in future the user can dynamically scale cpu and memory(scale vm api). Now I wanted to understand how to enforce this check in Cloudstack. The best would be Vmware providing a method to check whether hot add cpu and memory is enabled for the current GuestOS version in the vmware release. Need such mechanism. > This is related to dynamic scaling of cpu/memory in case of VMware environments. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira