[ https://issues.apache.org/jira/browse/CLOUDSTACK-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14283671#comment-14283671 ]
ASF subversion and git services commented on CLOUDSTACK-7571: ------------------------------------------------------------- Commit bf8db0c743c94c4540dab2f069d253f1a859eb10 in cloudstack's branch refs/heads/4.5 from [~bharat.kumar] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=bf8db0c ] CLOUDSTACK-7571 changing value of cpu/mem.overprovisioning.factor for xen cluster is not affecting total memory at zone level (cherry picked from commit 476733cb92634c8494fe64762d7fbc178292a754) Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com> > changing value of cpu/mem.overprovisioning.factor for xen cluster is not > affecting total memory at zone level > ------------------------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-7571 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7571 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server > Affects Versions: 4.5.0 > Reporter: Bharat Kumar > Assignee: Bharat Kumar > Fix For: 4.5.0 > > > steps to reproduce > ================== > 1-prepare a CS3.6 setup with vmware and xen cluster > 2-set mem.overprovisioning.factor=3 and cpu.overprovisioning.factor=2 > 2-upgrade it to CCP4.3 > 3-record total memory and cpu at zone level > 4-change cpu/memory overprovisioning for xen server cluster to some valid > value > expected > ========= > at zone level total memory should get changed , depends on overprovisioning > value > Actual > ======= > 1-total memory is not getting changed at zone level > 2-but total memory/cpu of xen cluster is getting changed with > overprovisioning factor > My observation > ============== > 1-if i change overspovisioning factor of vmware cluster total memory is > getting changed > 2-In fresh setup with one xen cluster i did not see this problem -- This message was sent by Atlassian JIRA (v6.3.4#6332)