Set reserved_host_memory_mb to zero for vCenter deployment
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_
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_
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 |
Changed in fuel: | |
importance: | Medium → Low |
Changed in fuel: | |
milestone: | 6.1 → 7.0 |
Changed in fuel: | |
status: | In Progress → Won't Fix |
milestone: | 7.0 → 6.1 |
no longer affects: | fuel/7.0.x |
Changed in fuel: | |
milestone: | 6.1 → 8.0 |
status: | Won't Fix → Confirmed |
no longer affects: | fuel/8.0.x |
tags: | added: area-partners |
Changed in fuel: | |
milestone: | 8.0 → 9.0 |
tags: | added: area-pce-vcenter |
Changed in fuel: | |
assignee: | Igor Gajsin (igajsin) → Alexander Arzhanov (aarzhanov) |
status: | Confirmed → In Progress |
Fix proposed to branch: master /review. openstack. org/131140
Review: https:/