RAMWeigher and CPUWeigher docs don't link properly to config options

Bug #1767192 reported by Matt Riedemann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Medium
Matt Riedemann

Bug Description

I don't know why the sphinx build doesn't fail for this, but the oslo config option links for the RAMWeigher and CPUWeigher don't work:

https://docs.openstack.org/nova/latest/user/filter-scheduler.html#weights

RAMWeigher Compute weight based on available RAM on the compute node. Sort with the largest weight winning. If the multiplier, :oslo.config:opt:`filter_scheduler.ram_weight_multiplier`, is negative, the host with least RAM available will win (useful for stacking hosts, instead of spreading).

CPUWeigher Compute weight based on available vCPUs on the compute node. Sort with the largest weight winning. If the multiplier, :oslo.config:opt:`filter_scheduler.cpu_weight_multiplier`, is negative, the host with least CPUs available will win (useful for stacking hosts, instead of spreading).

===

Those should be using ":oslo.config:option:".

Tags: docs
Matt Riedemann (mriedem)
Changed in nova:
importance: Medium → Low
assignee: nobody → Matt Riedemann (mriedem)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in nova:
status: Triaged → In Progress
Matt Riedemann (mriedem)
Changed in nova:
importance: Low → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/564631
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=3c95254b1cd0f41e1a1efaf125de1749cc19310c
Submitter: Zuul
Branch: master

commit 3c95254b1cd0f41e1a1efaf125de1749cc19310c
Author: Matt Riedemann <email address hidden>
Date: Thu Apr 26 17:30:08 2018 -0400

    Fix tox -e docs

    This was missed in I90ee8a2081c2a0465441a8d81d161f4887b4e1fb
    presumably because we no longer get warnings as errors, or
    some such wickedness. Anyway, this fixes docs build using tox.

    Change-Id: Ic8ec0c54a7c6502a0a4ea91d034fa9c1ae5e59d4
    Closes-Bug: #1767192

Changed in nova:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/nova 18.0.0.0b2

This issue was fixed in the openstack/nova 18.0.0.0b2 development milestone.

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.