4 Commits

Author SHA1 Message Date
Sahid Orentino Ferdjaoui
d52ceaf269 virt: reserved number of mempages on compute host
Users need to mark as reserved some amount of pages for third party
components.

The most common use case for using huge/large pages is NFV. In the
current state of that feature we can't guarantee the necessary amount
of pages to allow OVS-DPDK to run properly on the compute node, which
result in the instance failing to boot on a well selected
compute-node. OVS-DPDK needs 1 GB hugepages reserved. Since Nova does
not take into account that page reserved for OVS-DPDK it results in
the process not being able to acquire the necessary memory which
results in a failed boot.

This commit adds a new option 'reserved_huge_pages' which takes a list
of string format to select on which host NUMA nodes and from which
pagesize we want to reserve a certain amount of pages. It also updates
NUMAPageTopology to contain a reserved memory pages attribute, which
helps compute the available pages size on host for scheduling/claiming
resources.

Change-Id: Ie04d6362a4e99dcb2504698fc831a366ba746b44
Closes-Bug: #1543149
2016-05-12 06:32:00 -04:00
Sylvain Bauza
7b1fb84f68 Fix reno for RC1
This is a bus for all reno problems we see with the relnotes :

* Change Id25bd4870c6e2fda08dc0177b7ed61a8a6091838 was having
a formatting problem with not retaining the newlines, and also
was mentioning "Nove" :-)

* Change I43ddc5164f88fb049fe49ad4672fbf09b2b1987e was using a
prelude section that is not needed because we will provide a
general prelude section (and commenting that) in the next change.

* Change I2dba71e71b1ed7cf8476e8bfe9481e84be5df128 was incorrectly
using the upgrades section while it was a deprecation.

* Change Ia6f1d8f9c7d700498b6441a6ba37fa25b2611ef8 is no longer
valid because Id7936be290b6febd18deb4c2db8ea4d678d4d9b1 has been
merged during Mitaka too.

* Change I2465e1bee618a552132d659014ea96cdbda161d6 was reverting
a reno file but due to a reno bug (see
https://review.openstack.org/#/c/293078/), the release note is
still kept in the output. Consequently, the workaround I found
is to reintroduce the same reno file with an empty content to
drop the previous content.

Note that I used the prelude section for "dropping" notes, that
prevents us to provide empty bullets for upgrade or features sections.

Change-Id: I1535aff80850fa3666da739133fc43e8579aa19b
2016-03-16 11:17:28 +01:00
Nikola Dipanov
56d12936d9 Revert "virt: reserved hugepages on compute host"
This reverts commit 70604db8dacd1d8ea8a054a9f548b24dcffc292c.

The commit adds a config option that is required on both the scheduler
and the compute hosts which is not the direction we want to be going
in, and want to make sure that compute hosts are exclusively
responsible for the data that the scheduler service uses.

Change-Id: I2465e1bee618a552132d659014ea96cdbda161d6
2016-03-14 10:26:23 +00:00
Sahid Orentino Ferdjaoui
70604db8da virt: reserved hugepages on compute host
For some use cases we may need to reserved an amount of pages for
third part components.

This commit adds new option 'reserved_memory_pages' which takes a list
of string format to select on which host NUMA node and from which
pagesize we want to reserve a certain amount of pages.

Change-Id: I9d4c07da3594847917c9dc67e6663717d9ab4ba2
Closes-Bug: #1543149
DocImpact: reserved_memory_pages
2016-03-08 07:29:26 -05:00