Reviewed: https://review.openstack.org/501342
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=a76277f81a005cb48088fd9452637b4e7ee1b9f5
Submitter: Jenkins
Branch: master
commit a76277f81a005cb48088fd9452637b4e7ee1b9f5
Author: Stephen Finucane <sfinu...@redhat.com>
Date: Wed Sep 6 16:44:53 2017 +0100
doc: Split flavors docs into admin and user guides
There are currently two docs describing flavors in 'admin', which
contain a lot of overlapping information. Fix this by keeping the
configuration guide (how to create, delete, modify flavors) in
'admin', while moving the reference-style parts into 'user'. We
cross-reference the two internally.
Given that large chunks of this needed to be rewritten, we've taken the
opportunity to fix a poor description for the RXTX factor, closing a
longstanding bug in the process.
Change-Id: Ia57c93ef1e72ccf134ba6fc7fcb85ab228d68a47
Closes-Bug: #1688054
** Changed in: nova
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1688054
Title:
Flavors in Administrator Guide - confusing description for rxtx factor
Status in OpenStack Compute (nova):
Fix Released
Bug description:
- [x] This doc is inaccurate in this way: ______
The RXTX Factor description currently states:
"Optional property allows created servers to have a different
bandwidth cap than that defined in the network they are attached to.
This factor is multiplied by the rxtx_base property of the network.
Default value is 1.0. That is, the same as attached network. This
parameter is only available for Xen or NSX based systems."
The compute API reference has a better and more accurate description:
https://developer.openstack.org/api-ref/compute/?expanded=create-
flavor-detail#create-flavor
"The receive / transmit factor (as a float) that will be set on ports
if the network backend supports the QOS extension. Otherwise it will
be ignored. It defaults to 1.0."
The admin guide description is really talking about nova-network and
the xen virt driver, which is not untrue, but is a bit confusing (I
don't know where the NSX part comes from).
But the way this is used with neutron in nova is on the port if the
QOS extension is enabled. Nova will likely deprecate this field in the
flavor resource since nova-network is deprecated and if you're doing
QOS on ports you should be doing that via the networking service, not
the compute service flavors.
-----------------------------------
Release: 15.0.0 on 2017-05-03 11:19
SHA: 991820bc90e3f08a7ddfd1a649bc78a12a9406ab
Source:
https://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/admin-guide/source/compute-flavors.rst
URL: https://docs.openstack.org/admin-guide/compute-flavors.html
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1688054/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
