Set reserved_host_memory_mb to zero for vCenter deployment

Bug #1382539 reported by Andrey Danin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Low
Alexander Arzhanov
5.0.x
Won't Fix
Low
Partner Centric Engineering
5.1.x
Won't Fix
Low
Partner Centric Engineering
6.0.x
Won't Fix
Low
Partner Centric Engineering
6.1.x
Won't Fix
Low
Partner Centric Engineering
7.0.x
Won't Fix
Low
Partner Centric Engineering
8.0.x
Won't Fix
Low
Partner Centric Engineering

Bug Description

Affecting 5.0, 5.0.1, 5.1, and 6.0 releases.

Vmware recommends [0] to set nova-scheduler’s option ‘reserved_host_memory_mb’ to 0 (Fuel uses a default value which is 512). That’s because vCenter is already doing a memory reservation and there is no valuable reason to do it twice. vCenter provides an aggregated memory from all ESXi’s in a vSphere cluster, and this option is applied to a cumulative value not to each individual ESXi node. So, actually, we looses 512MB for each vSphere cluster.

But because it’s a global configuration option it potentially can cause some problems in a multi-HV environment. We can look for a better solution in this case. For instance, set ‘reserved_host_memory_mb’ to 0 anyway, but force non-vCenter nova-computes provide an already adjusted memory value.

[0] http://docs.openstack.org/trunk/config-reference/content/vmware.html#VMwareVCDriver_configuration_options

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/131140

Changed in fuel:
assignee: Fuel Partner Integration Team (fuel-partner) → Igor Zinovik (izinovik)
status: Confirmed → In Progress
Changed in fuel:
milestone: 6.0 → 6.1
Changed in fuel:
status: In Progress → Triaged
Changed in fuel:
assignee: Igor Zinovik (izinovik) → Igor Gajsin (igajsin)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on fuel-library (master)

Change abandoned by Igor Zinovik (<email address hidden>) on branch: master
Review: https://review.openstack.org/131140

Tatyana Dubyk (tdubyk)
Changed in fuel:
importance: Medium → Low
Igor Gajsin (igajsin)
Changed in fuel:
milestone: 6.1 → 7.0
Igor Gajsin (igajsin)
Changed in fuel:
status: In Progress → Won't Fix
milestone: 7.0 → 6.1
no longer affects: fuel/7.0.x
Revision history for this message
Igor Gajsin (igajsin) wrote :

We can't fix it due to soft code freeze. Postpone to 8.0.

Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 6.1 → 8.0
status: Won't Fix → Confirmed
no longer affects: fuel/8.0.x
Dmitry Pyzhov (dpyzhov)
tags: added: area-partners
Changed in fuel:
milestone: 8.0 → 9.0
tags: added: area-pce-vcenter
Revision history for this message
Bug Checker Bot (bug-checker) wrote : Autochecker

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

tags: added: need-info
Changed in fuel:
assignee: Igor Gajsin (igajsin) → Alexander Arzhanov (aarzhanov)
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-library (master)

Fix proposed to branch: master
Review: https://review.openstack.org/301550

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-library (master)

Reviewed: https://review.openstack.org/301550
Committed: https://git.openstack.org/cgit/openstack/fuel-library/commit/?id=43eadba18974b93cb3a89e6611237a4902c57592
Submitter: Jenkins
Branch: master

commit 43eadba18974b93cb3a89e6611237a4902c57592
Author: Alexander Arzhanov <email address hidden>
Date: Tue Apr 5 09:51:47 2016 +0000

    Set reserved host memory to 0MB for nova-compute with VCDriver

    The reserved_host_memory_mb option value is 512 MB by default.
    However, VMware recommends that you set this option to 0 MB
    because the vCenter driver reports the effective memory
    available to the virtual machines.
    Link to review for openstack doc(VMware recommends):
    https://review.openstack.org/#/c/73450/2

    Change-Id: I9ab240820740ed3ecd09fc7ccdc5109875baf453
    Closes-bug: #1382539

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
Ilya Bumarskov (ibumarskov) wrote :

Verified on Fuel 9.0 mos-iso#465

root@node-5:~# grep -r "reserved_host_memory_mb" /var/log
/var/log/puppet.log:2016-06-14 18:11:24 +0000 /Stage[main]/Nova::Compute/Nova_config[DEFAULT/reserved_host_memory_mb]/ensure (notice): created
/var/log/nova/nova-compute.log:2016-06-14 18:12:50.133 26361 DEBUG oslo_service.service [req-0429de39-c9b5-4ed9-957d-4dd50e1be67c - - - - -] reserved_host_memory_mb = 0 log_opt_values /usr/lib/python2.7/dist-packages/oslo_config/cfg.py:2517
/var/log/nova/nova-compute.log:2016-06-14 18:13:11.823 29054 DEBUG oslo_service.service [req-1bf53aa7-a9af-4da7-a9e4-0a176ab748d7 - - - - -] reserved_host_memory_mb = 0 log_opt_values /usr/lib/python2.7/dist-packages/oslo_config/cfg.py:2517
/var/log/nova-all.log:<183>Jun 14 18:12:50 node-5 nova-compute: 2016-06-14 18:12:50.133 26361 DEBUG oslo_service.service [req-0429de39-c9b5-4ed9-957d-4dd50e1be67c - - - - -] reserved_host_memory_mb = 0 log_opt_values /usr/lib/python2.7/dist-packages/oslo_config/cfg.py:2517
/var/log/nova-all.log:<183>Jun 14 18:13:11 node-5 nova-compute: 2016-06-14 18:13:11.823 29054 DEBUG oslo_service.service [req-1bf53aa7-a9af-4da7-a9e4-0a176ab748d7 - - - - -] reserved_host_memory_mb = 0 log_opt_values /usr/lib/python2.7/dist-packages/oslo_config/cfg.py:2517

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.