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 903B511252 for ; Mon, 21 Apr 2014 09:43:18 +0000 (UTC) Received: (qmail 38983 invoked by uid 500); 21 Apr 2014 09:43:17 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 38772 invoked by uid 500); 21 Apr 2014 09:43:16 -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 38753 invoked by uid 500); 21 Apr 2014 09:43:15 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 38741 invoked by uid 99); 21 Apr 2014 09:43:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2014 09:43:14 +0000 Date: Mon, 21 Apr 2014 09:43:14 +0000 (UTC) From: "Harikrishna Patnala (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-6465) vmware.reserve.mem is missing from cluster level settings 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-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harikrishna Patnala updated CLOUDSTACK-6465: -------------------------------------------- Status: Reviewable (was: In Progress) > vmware.reserve.mem is missing from cluster level settings > ---------------------------------------------------------- > > Key: CLOUDSTACK-6465 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6465 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Management Server > Affects Versions: 4.4.0 > Reporter: Harikrishna Patnala > Assignee: Harikrishna Patnala > Priority: Critical > Fix For: 4.4.0 > > > vmware.reserve.mem is missing from cluster level settings > steps > ======= > infrastructure->cluster->select a cluster->setting you should vmware.reserver.mem > DB: > === > mysql> select name from configuration where scope ="cluster"; > +----------------------------------------------------------+ > | name | > +----------------------------------------------------------+ > | cluster.cpu.allocated.capacity.disablethreshold | > | cluster.cpu.allocated.capacity.notificationthreshold | > | cluster.memory.allocated.capacity.disablethreshold | > | cluster.memory.allocated.capacity.notificationthreshold | > | cluster.storage.allocated.capacity.notificationthreshold | > | cluster.storage.capacity.notificationthreshold | > | cpu.overprovisioning.factor | > | mem.overprovisioning.factor | > | vmware.reserve.cpu | > | xen.vm.vcpu.max | > +----------------------------------------------------------+ > 10 rows in set (0.00 sec) -- This message was sent by Atlassian JIRA (v6.2#6252)