This spec outlines the Implementation plan of ECMP in neutron.
Patch for this spec:
https://review.opendev.org/#/c/743661
Related-Bug: #1880532
Change-Id: I67ebf642fbb130a7701792d66629dbab2d76181b
sphinx seems to not finding paths for images files, but adding a symlink
to doc/source make the doc build work again.
Change-Id: Icf8e867c21252e0d098e45630dcb8399eb6386ab
Closes-Bug: #1916332
In python3, all strings are considered as unicode strings
and the unicode prefix ("u") for string is no longer needed.
This commit cleans up "u" prefix in the repository.
Change-Id: I30a9f5314aef1160766af608043c073d333f1bff
Extend the current floating IP port forwarding API to handle a
range of ports instead of a one-to-one mapping.
Change-Id: Iee88c2d36eeb600a9b75fc21f4fb5b0a707898f4
Implements: blueprint floatingips-portforwarding-ranges
Closes-Bug: #1885921
UPPER_CONSTRAINTS_FILE is old name and deprecated
This allows to use upper-constraints file as more
readable way instead of UPPER_CONSTRAINTS_FILE=<lower-constraints file>.
Change-Id: I2c450c25cb8f97575df3f4f518ca179c4cf2dffd
This specification proposes to add functionality that allows users to
associate floating IPs to ports of routed networks
Partial-Bug #1667329
Change-Id: Id07f52da9fff321827aff8be11614a347030bb04
Since the conversation reported in [1], the information to be reported
to Nova will not be stored in the port "resource_request" and the
NUMA affinity policies will not be considered as resource provider
traits.
NUMA is going to be modeled in Placement soon, but until this feature
does not land in a stable version, Neutron will only provide this
information via an extension.
Related-Bug: #1886798
[1]https://review.opendev.org/#/c/739961/
Change-Id: I2a96e5ba394f4476121cbc916634e1c4d4b4212f
This spec should be merged to victoria directory but was by mistake
proposed to the Ussuri. So this fixes it.
Change-Id: I15877081f685832d9fc71c2ed167968910c4ee57
This specification describes how to support address groups in
security group rules.
Change-Id: Ib58afde9ed58092ffbc94f7d522d5f5d034b832b
Related-Bug: #1592028
Switch to openstackdocstheme 2.2.1 version. Using
this version will allow especially:
* Linking from HTML to PDF document
* Allow parallel building of documents
* Fix some rendering problems
Update Sphinx version as well.
Change pygments_style to 'native' since old theme version always used
'native' and the theme now respects the setting and using 'sphinx' can
lead to some strange rendering.
openstackdocstheme renames some variables, so follow the renames
before the next release removes them. A couple of variables are also
not needed anymore, remove them.
See also
http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014971.html
Change-Id: I61c96d3f8479b6ab5eef993a769f1fc7df78c6ad
It was merged recently in [1] but by mistake we merged it to the
Ussuri branch.
[1] https://review.opendev.org/#/c/724207/
Change-Id: I604956217d2370b72cd6825289fac9e79fafeda3
This specification describes how to allow sharing security groups as
read-only.
Change-Id: If2dcec379d4c874df97af12da44aec7060f0abc2
Related-Bug: #1875516
Make a few cleanups:
- Remove obsolete sections from setup.cfg
- Cleanup doc/source/conf.py to remove now obsolete content.
- Use newer openstackdocstheme version
- Remove install_command from tox.ini, the default is fine;
cleanup tox.ini for python3
Change-Id: I306fe1dd080839004e206ac08f3526812e406f19
added section explicitly calling out a lock on certain
variables in the classification resources to prevent
updating.
This avoids an issue with the classifications being
updated but the classifier having no way to inform its
consumers.
Change-Id: If937e343484387ecce4a3709bed3ca74cc52b9bc
This is the Spec to propose and describe the integration
between the Neutron Quality of Service extension and
the Neutron Classifier service plugin.
Change-Id: I5bfd7dfab8061debd6fb86470c874098cfc48a0b
Implements: blueprint neutron-classifier-neutron-qos
This spec outlines the rationale, justification, and plans for
OVN and ML2+OVS+DVR convergence in neutron.
Change-Id: I82a2bae8c250e6a5749450131c0d602b134fb3a4
Related-Bug: #1828607
Some options are now automatically configured by the version 1.20:
- project
- html_last_updated_fmt
- latex_engine
- latex_elements
- version
- release.
Change-Id: Iae624665505cc5948756318ecf2914678c103461
As we discovered during implementation it wasn't a good idea of mine to
make the request and response body a list on the top level. Neither the
documentation tools nor python-neutronclient were prepared for non-dict
request/response bodies.
Another reason I suspect to always have dict-wrapped bodies is that it
makes possible future changes to the request/response format a bit easier.
Yet another reason is that the request/response body format in this change
is now the exact same as it was used in the PUT /v2.0/routers/router-id
request/response. Therefore clients wishing to use the new API only have
to change the URL, but not the body of their requests.
Since the api-def was already merged, this change just retroactively
updates the spec to avoid possible future confusion between the spec
and the api-ref.
Change-Id: I3c7e9ab4ab6518eb1d30e3711a2d9571dfc2fa15
Partial-Bug: #1826396
Introduce the OpenStack tooz distributed lock to the
ipam module. In the scenario of large-scale port
creation, avoid ip allocation exceeding the maximum
retry limit failure and improve ip allocation efficiency.
Implements: blueprint introduce-distributed-locks-to-ipam
Change-Id: I1483a6474d5f5a7530a2b2e9e369f712b591fec4
This change adds a specification for the change to add control for
custom ethertypes.
Change-Id: I158b1be16fba7b3eb8d53a51625eb3d9b2a26773
Related-Bug: #1832758
There are several cases in the Nova/Neutron/os-vif interaction
where the knowledge of the neutron core plugin or ML2 driver
would be useful to facilitate a more robust handling of guest
networking.
For example, in Icehouse, a external event mechanism was
introduced to allow neutron to notify Nova of network changes
and VIF plugging. As the occasion on which these events are
emitted is dependent on the driver that bound the port and Nova
does not have knowledge of that. Therefore, Nova cannot rely on
the event to synchronize the operation between Nova and neutron,
which has lead to a race condition in the past.
Change-Id: I57f4df31bee83b818f2c0123577d11a8e07c0191
Related-Bug: #1821058
As discussed in an openstack-discuss thread [1] we could improve the
extraroute API to better support Neutron API clients, especially Heat.
The problem is that the current extraroute API does not allow atomic
additions/deletions of particular routing table entries. In the current
API the routes attribute of a router (containing all routing table
entries) must be updated at once. Therefore additions and deletions
must be performed on the client side. Therefore multiple clients race
to update the routes attribute and updates may get lost.
[1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005121.html
Change-Id: I10407a74102bfd16e3a0b8d2bd08c92acb4cc27f
Partial-Bug: #1826396
