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
This is a followup from [1]. which missed
the example for update and get_object.
[1]. https://review.openstack.org/336518
Change-Id: I0cc91e3070bd466bcccbdb2bcd4505a24924884f
The feature classification matrix will provide information about
plugins and the features they support.
Acts as a launching point for users to read about the intent
of the matrix before reviewing the matrix to find features and plugins
that meet their needs.
Will implement a page where users can view Neutron features
and plugins and their status.
Similar to Nova's implementation here:
http://docs.openstack.org/developer/nova/feature_classification.htmlhttp://docs.openstack.org/developer/nova/support-matrix.html
Co-Authored-By: Darek Smigiel <dariusz.smigiel@intel.com>
Closes-Bug: #1580327
Change-Id: I67f4dc67883623decdbf136c598eb9e2d0bc24c4
To introduce to every neutron developer the concept of using objects,
this dev ref is describing the ecosystem of Oslo VersionedObjects
and its modification for neutron project, how to create or use the objects.
Co-Authored-By: Dariusz Smigiel <smigiel.dariusz@gmail.com>
Change-Id: If25060feb77f35873a2b6a4ecfe639a284e7f677
Partially-Implements: blueprint adopt-oslo-versioned-objects-for-db
Sadly, Nate is no longer with the team. Also Doug left us a while ago.
However we may like to blame others for all faults, it's time to free
those two from responsibility for the code.
Also, new infra liaisons were added.
Change-Id: Ief906ef64922acb4d3e7370c3d1e3ed75fe92a04
Basically, the commit removes the file encoding - since jenkins is fine
with it, means it was really unnecessary and the change makes sense.
Change-Id: Id0821c9b11b9efad1836596c407566c9eb4dc11a
This reverts commit 84b3ae3ae9111e241352bdccad238c9fd37b83df.
The logic was incorrect[1]. We cannot achieve QoS egress minimum bandwidth of Linuxbridge by the patch. I also think that the issue is not solved by small patch and we must consider deeply.
[1]: https://bugs.launchpad.net/neutron/+bug/1662582
Change-Id: Id4703b5c63876f16e31b6805cd147b5840a4a591
The devref describes tag mechanism supports network only but
now it supports subnet, port, subnetpool, and router.
This patch updates the description about supported resources.
Change-Id: I1a4b02e253157154218bfe63a18891083178f55a
Closes-Bug: #1662102