[ https://issues.apache.org/jira/browse/CLOUDSTACK-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224193#comment-14224193 ]
ASF subversion and git services commented on CLOUDSTACK-6465: ------------------------------------------------------------- Commit eae733817b3670b0151410c027325f78013392ad in cloudstack's branch refs/heads/4.5 from [~harikrishna.patnala] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=eae7338 ] CLOUDSTACK-6465: vmware.reserve.mem is missing from cluster level settings Signed-off-by: Rajani Karuturi <rajanikarut...@gmail.com> > 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, 4.5.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.3.4#6332)