Bug 1228448 - [Docs] [Nova] Add a description of updates to the NUMATopologyFilter
Summary: [Docs] [Nova] Add a description of updates to the NUMATopologyFilter
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 7.0 (Kilo)
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ga
: 7.0 (Kilo)
Assignee: Radek Bíba
QA Contact: Don Domingo
URL:
Whiteboard:
Depends On: 1193287
Blocks: 1234669
TreeView+ depends on / blocked
 
Reported: 2015-06-05 01:42 UTC by Andrew Dahms
Modified: 2015-12-02 12:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-12-02 12:04:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Dahms 2015-06-05 01:42:30 UTC
In RHEL-OSP 7.0, the NumaTopologyFilter used to filter instances as part of scheduling now has PCI device awareness. The description of this filter in "3.5.1. Configure Scheduling Filters" in the Administration Guide must be updated to include some brief details of the new functionality.

BluePrint - https://blueprints.launchpad.net/nova/+spec/input-output-based-numa-scheduling

Comment 4 Andrew Dahms 2015-06-05 03:25:39 UTC
Assigning to Radek for review.

Radek - this is another Nova bug, and the changes can be applied to the content in the Administration Guide for now.

Comment 5 Radek Bíba 2015-06-05 12:20:03 UTC
While reading the relevant part of the Administration Guide, I found the following bullet point:

* The nova boot command, see the "Command-Line Interface Reference" in https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/. 

I believe it would be quite convenient if the link led to https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux_OpenStack_Platform/6/html/Command-Line_Interface_Reference_Guide/novaclient_commands.html#novaclient_subcommand_boot directly. (The OSP version in the URL would depend on the particular version described in the Administration Guide.)

Comment 6 Radek Bíba 2015-06-08 08:54:53 UTC
Stephen,

Could you please check if the following description is technically correct?

With I/O (PCIe) based NUMA scheduling, the filter allows for locality of
PCI devices passed to the guest and ensures that the guest is scheduled on
the requested host NUMA node, thus improving performance and latency.

(I'm thinking of appending that to the current description of the NUMATopologyFilter.)

Comment 7 Stephen Gordon 2015-06-17 15:38:31 UTC
Close, more accurately:

With I/O (PCIe) based NUMA scheduling, when attaching PCI devices to guests their NUMA locality is stored - where the hardware chipset supports NUMA locality of PCI devices. The NUMATopologyFilter filter uses this information to ensure that the guest is scheduled on the host NUMA node associated with PCI device(s) it has been passed, thus improving performance and latency.

Comment 9 Andrew Dahms 2015-06-19 00:13:14 UTC
Assigning Don as the QA contact.

Don, could you take a look at the newly added content?

Comment 10 Radek Bíba 2015-06-24 09:36:03 UTC
Edited and merged (although it wasn't that simple due to a strange merge conflict in gitlab).

Comment 11 Andrew Dahms 2015-12-02 12:04:42 UTC
This content is now live on the Customer Portal.

Closing.


Note You need to log in before you can comment on or make changes to this bug.