Add missing information that Openvswitch agent supports now
both ingress and egress direction for QoS bandwidth limit rule.
Support for ingress bandwidth limit was added in
I9d94e27db5d574b61061689dc99f12f095625ca0
TrivialFix
Change-Id: I70058d1d8f16c58e41dab08fc66d5d3f5fcefa4b
Leading spaces before item lists leads to vertical line
on the left side. They are completely unnecessary.
Change-Id: I08c3f077e470aa593076a525de1445bc5d0bdb9a
openstackdocstheme generates the toc tree in the left sidebar
based on the page hierarchy from the top page.
The previous developer guide hirarchy is a bit deep, and
this commit reorganizes the devref pages for better navigation
with openstackdocstheme.
Change-Id: I1412b047efc1c268b34ef97e78073da7bcbb6d7e
The docs reorganization proposed in the docs-specs [1],
we will migrate our sphinx theme to openstackdocsthems.
This commit switches our docs theme to it,
Also ajust title levels. openstackdocstheme assume one title (first
level) per page. Second or later first-level titles are not shown.
This changes title levels to match openstackdocsthem requirements.
Note that oslosphinx is used by releasenotes build,
so it is not dropped from test-requirements.txt.
[1] https://review.openstack.org/#/c/472275/
Change-Id: I72d55c26401ae9bfd06626d1b1584a368bbd9f86
Added devref documentation related to the "default" behaviour
for QoS policies.
Change-Id: Ic3b149ec5dfdc732a4b5851237389abaef8992b7
Closes-Bug: #1694298
Add support for QoS ingress bandwidth limiting in
openvswitch agent.
It uses default ovs QoS policies on bandwidth limiting
mechanism.
DocImpact: Ingress bandwidth limit in QoS supported by
Openvswitch agent
Change-Id: I9d94e27db5d574b61061689dc99f12f095625ca0
Partial-Bug: #1560961
html_last_updated_fmt option is interpreted as a
byte string in python3, causing Sphinx build to break.
This patch makes it utf-8 string.
Changing Popen to .check_output because of 3 reasons:
1. check_output() will raise CalledProcessError if
the called process returns a non-zero return code.
2. For consistency with keystone [1] and cinder [2]
3. It makes the code look much better.
[1] https://review.openstack.org/#/c/457142/
[2] https://review.openstack.org/#/c/433081
Change-Id: Ifeff184b71a83b78de751dfd0c2f43a33cd409ee
Removed one orphan reference of unclear value (pudb), and moved another
one into the text itself. This allows to pass gate with new sphinx.
Change-Id: I943d9b0904731ebcc4d3fd3a9b686fd08b03c48b
Closes-Bug: #1694614
This method allows to update matching resources with requested values
without doing full fetch/set/update cycle. This is also handy to "lock"
records in database with UPDATE WHERE.
Change-Id: I2347fedbecef823babe3d8038f5a74b21fc0a602
Partially-Implements: blueprint adopt-oslo-versioned-objects-for-db
Added create, update and delete precommit calls for QoS
driver, to be used by some out-of-tree backends.
Co-Authored-By: Miguel Angel Ajo <mangelajo@redhat.com>
Co-Authored-By: Rodolfo Alonso Hernandez <rodolfo.alonso.hernandez@intel.com>
Closes-Bug: #1657381
Change-Id: I44dd7e049eab054363063021f07ade81ef2d1a90
Added a table in devref documentation to define which
QoS rules are supported by the network backends.
Change-Id: Ie536a05d19cab28eb48bad66b3bc204d017a1ebd
This patch changes way how neutron calculates which QoS rules
are available to use. It now returns all rule types which are
supported by at least one loaded QoS driver.
If user will want to apply policy with rule unsupported by driver
used by port then it will be catched on port/network update event.
This validation mechanism was introduced in
I75bd18b3a1875daa5639dd141fb7bbd6e1c54118
DocImpact: list of returned available QoS rule types is changed
Change-Id: Ia00d349625db358ab486802fc0ff2e69eaa3895e
Closes-Bug: #1686898
The callback modules have been available in neutron-lib since commit [1]
and are ready for consumption.
As the callback registry is implemented with a singleton manager
instance, sync complications can arise ensuring all consumers switch to
lib's implementation at the same time. Therefore this consumption has
been broken down:
1) Shim neutron's callbacks using lib's callback system and remove
existing neutron internals related to callbacks (devref, UTs, etc.).
2) Switch all neutron's callback imports over to neutron-lib's.
3) Have all sub-projects using callbacks move their imports over to use
neutron-lib's callbacks implementation.
4) Remove the callback shims in neutron-lib once sub-projects are moved
over to lib's callbacks.
5) Follow-on patches moving our existing uses of callbacks to the new
event payload model provided by neutron-lib.callback.events
This patch implements #1 from above, shimming neutron's callbacks and
removing devref + UTs. Rather than shimming using debtcollector, this
patch leaves callback constants as-is, and simply references the lib
class/function in its respective neutron callback module. This allows
consumers to test callback types without changing code. For example,
an except block block like that below continues to work even though
the raised exception now lives in lib::
try:
neutron_cb_registry.notify(...)
except neutron_cb_exceptions.CallbackFailure:
handle_exception()
In addition this patch contains minor UT updates to support the shim
approach.
NeutronLibImpact
[1] fea8bb64ba7ff52632c2bd3e3298eaedf623ee4f
Change-Id: Ib6baee2aaeb044aaba42a97b35900d75dd43021f
Prior to this commit, the number of flows can be prohibitively large
in some cases.
Closes-bug: #1628819
Change-Id: I194e7f40db840d29af317ddc2e342a1409000151
Those are against the spirit of the tool, and were introduced by
mistake. Sanity checks should validate actual features not version
numbers, because distributions can ship an older version of a package
that still has the needed patches backported to support features needed
for neutron; in which case the sanity check tool should not fail on
those deployments.
Updated 'effective neutron' guide to reflect the unspoken rule.
Since the tool is supposed to be consumed by operators, and not (just)
developers, we can't remove those CLI arguments immediately, and so we
follow deprecation process instead. In Queens, we will completely remove
those checks and options.
Change-Id: I2df8b7b39bca6d548a6f17466c26ffa688eb1d59
[1] has been merged for supporting use floating IP to cross scopes.
The devref should be updated for it, due to the discussion in [1].
[1] https://review.openstack.org/#/c/283134/
Change-Id: I5c330ba5d5446ec985b628d8bc3b37d65fa7d53d
Related-Bug: #1543885
neutron-server and ovs-agents are stopped with SIGTERM since a while ago.
DHCP HA tests have been written.
Change-Id: I93361e641bb07eaee92b2c60d7e0adf3fafed657
In order to get a better habit on how to recheck gate failures, this
patch introduces a new policy and howto related to usage of recheck on
gerrit.
Change-Id: Iaef998108de80fffcf5400e357a51e2f70dc047a
The sriov_nic_agent added qos support with the following
patches[1][2][3], and the document was not updated to reflect that.
The bandwidth limit rule was added by [1]
The minimum bandwidth rule was added by [2] and [3]
This commit removes QoS from the "to be supported in the future"
part of the body and adds a partially supported part to the body.
[1] I364fc8158e502d4dcc3510d6157f12969961a11d
[2] Iefe5e698e99d186202d6ef170f84e93bfbba46dd
[3] I6b619a96a2bfde164646c71409b671352bc6ce7d
Change-Id: Ia5e90307795683679a92214786e8d8021eb9ff57
Neutron-lib 1.1.0 is now out and contains the portbindings
API definition (as per commit [1]). This patch moves neutron
references over to the neutron-lib version.
NeutronLibImpact
- Consumers using the public constants within neutron's
portbindings API extension must now use the values
from neutron-lib.
[1] 87e42f993c07ae320159d5123662ee9f3bd4d903
Change-Id: I669af9b4c712877772d91a03857ab108714001d4
