This extension makes it possible to add subnetpools to RBAC policies.
Change-Id: I1238430c40fe7132bad4eea573a638c0c47a5e78
Depends-On: https://review.openstack.org/707407
Partial-Bug: #1862032
In api-ref dns_assignment parameter was listed as dict but in fact it
is list of dicts.
This patch fixes api-ref to reflect what is actually in neutron's code.
Change-Id: I898633cd360cd9619f5e9a87acb718e01e99b647
Closes-Bug: #1861027
Problem Description
===================
As users create and update theirs floating ip rules, the reason
behind those rules might get lost throughout time. Moreover, in
an environment with many people writing rules, it is important
to track down the reason behind each one of the rules
created/added in a floating IP port forwarding configuration.
The addition of a description field would allow operators to
determine the reason why a rule was created and help the users
to know if the existence of a rule is still reasonable.
Proposed Change
===============
To address the described scenario, we propose to create a new
“description” field in the Neutron’s Floating IP port forwarding
rules API JSON. This new field will be a nullable String
containing the description/reason why this new port forwarding
rule is being created.
Change-Id: If98a70011b187d2143a660f1f281ab197d21eb4d
Implements: blueprint portforwarding-description
Closes-Bug: #1850818
Neutron-interconnection project has no activity since very long time.
There is no any implementation done in the repo so far.
So during the Shanghai PTG, we agreed that we will drop
neutron-inteconnection project from stadium projects list and
remove its api-ref from neutron-lib.
This partially reverts commit 888a28d598.
It don't rever original release note and adds new release note about
removal of interconnection API from neutron-lib.
Change-Id: I186a8f42e1d387bfb31025b0c5c224a86d00cd6e
There are still fwaas_v1 exceptions and definitions in
neutron-lib, it is necessary to remove them because the
fwaas_v1 code has been removed in the Stein cycle[1] and
the related extensions will be removed.
[1] https://review.opendev.org/#/c/616410/
Depends-On: https://review.opendev.org/#/c/692094/
Change-Id: Ibfc6dab327c9df59222cda3e6a1f5dc566aa1bde
Closes-bug: #1850602
Due to missing empty lines in LBaaS v2 section on main
page of Neutron's api-ref it was rendered incorrectly and
sections which are after LBaaS section on this page were not
rendered properly too.
This patch fixes this issue.
TrivialFix
Change-Id: I429a00fc4f0f6614f0addc576262622aa2c415f5
Closes-Bug: #1848023
Neutron-LBaaS has now been retired and there will be no Train
release[1]. This patch removes the neutron-lbaas API reference and
various other references to Neutron-LBaaS from neutron-lib.
[1] https://review.opendev.org/658494
Depends-On: https://review.opendev.org/665838
Related-Bug: #1833125
Change-Id: I0200abba2bca07a610839ba4fa8e2d9f2fa82218
The api documentation is now published on docs.openstack.org instead
of developer.openstack.org. Update all links that are changed to the
new location.
Note that redirects will be set up as well but let's point now to the
new location.
For details, see:
http://lists.openstack.org/pipermail/openstack-discuss/2019-July/007828.html
Change-Id: Ia756506e25d7b74030f55d1032b5cb71f5e1925b
The api-ref now lives on docs.openstack.org, update links to it.
Also, remove version number from published document.
Change-Id: I173973d8c62d2d0169697aa3329c36de3b2d5a41
Add a new attribute ``dns_publish_fixed_ip`` into ``subnet``
resource. This attribute will be used to indicate whether to publish DNS
records for fixed IPs from this subnet.
Neutron patch: https://review.opendev.org/662409
Thanks go to [0] which I took as a reference to create this patch.
[0] I1371fc0b47c0015423e4346ffd43d39c8264b1a3
Change-Id: I08ef19fcc06559c92ae3f8e6e66c5fd896815232
Partial-Bug: 1784879
Parameter "internal_ip_address" used in floating IP port forwarding
was wrongly marked as optional as in api definition it is required.
This patch updates api-ref description to be matched with current
definition in the code.
Change-Id: Ib42bed3c5b293c207a8a81f24bd5016f168706fe
Closes-Bug: #1830554
Attribute 'tags' is not allowed in POST. This patch fixes the issue in
Create port POST api-ref where "tags" is listed. No other resource
api-ref is impacted.
Closes-bug: #1815600
Change-Id: I77232b9eadf628805e162c66f270548a38725078
Introduces a new API extension exposing conntrack_helpers
field in Router response. The extension requires the
``router`` and ``conntrack_helper`` service plugin.
Related-Bug: #1823633
Change-Id: I55d659c47f3e9a65af78509fbd63416373a501f3
Adds standard attributes with tagging support to the API definition and
samples of network-segment-range extension.
Co-authored-by: Allain Legacy <Allain.legacy@windriver.com>
Partially-implements: blueprint network-segment-range-management
Change-Id: I18679b4f7d2c65abd5106f256eff4a1b481d239d
After the neutron server removes this option [1], it will be removed
from the response of agent endpoint.
[1] https://review.openstack.org/#/c/567369/
Depends-On: I07474713206c218710544ad98c08caaa37dbf53a
Change-Id: I2ca0ef560484dff384b3a3b477456c9fe4352b8b
This introduces a new extension that provides API's that enable
operations against the prefix list of a subnet pool to be more
explicit. In its current form, the subnetpool extension does not
clearly define how operations on the prefix list of a subnet pool
are to be performed and leaves unnecessary ambiguity to be handled
by implementers of the extension. This extension makes prefix
management for subnet pools explicit operations, while making support
for this discoverable for clients.
Change-Id: Ia84d767f582f28a2fc77799a58f6729a7fd42f34
Related-Bug: #1792901
Adds definition for 'interconnection' API extension for
neutron-interconnection project.
This patch partially implements the following spec:
https://specs.openstack.org/openstack/neutron-specs/specs/rocky/neutron-inter.html
Signed-off-by: Thomas Morin <thomas.morin@orange.com>
Submitted on behalf of a third-party: Orange
Change-Id: I7c16ffb21f88de88ab80a19d91b898be53419514
The neutron-lib part of this change: https://review.openstack.org/624751
This change introduces a new shim extension
(floatingip-autodelete-internal) to signal a change in API behavior
introduced by the fix of a bug referred below. That is now we autodelete
unused floating IPs when changing a network to router:external=False.
It also documents the API change.
Change-Id: I247106e95abb5d6822aa35ae793531a1d79edbd4
Needed-By: https://review.openstack.org/624751
Partial-Bug: #1806032
Agents supporting the guaranteed minimum bandwidth feature need to share
their resource view with neutron-server and in turn with Placement too.
The resource information is synchronized to neutron-server via the
periodic agent heartbeat therefore transient synchronization errors are
fixed by the next heartbeat. But synchronization to Placement is not
done periodically, but on a (mostly) on demand basis. Therefore to fix
transient errors of the synchronization to Placement we must remember
the success/failure of the last synchronization attempt.
This change introduces a new boolean agent attribute: resources_synced
This attribute is:
* admin-only (just like the whole agent extension)
* read-only (it is only updated by the internal synchronization process)
If this attribute is not set then no synchronization to Placement ever
happened (which is the natural state of agents not tracking their
resources via Placement).
If it is False, then another successful synchronization is needed before
the contents of Placement can be considered up to date.
If it is True, then this agent's resources are up to date in Placement.
Change-Id: Ia3dea82fabe5e068192fbe931db8d341d3d37149
Needed-By: https://review.openstack.org/630999
Partial-Bug: #1578989
See-Also: https://review.openstack.org/502306 (nova spec)
See-Also: https://review.openstack.org/508149 (neutron spec)
Neutron OVS ML2 mechanism driver will allow binding the `smart-nic`
vnic_type. The rationale for creating new vnic_type and not using the
barmetal one is that there is a wide range of mechanism drivers that
use heirachical port binding for configuring TOR switches and we want
to allow this to work with smart NICs.
Story: #2003346
Change-Id: I91f63810626ce4e054e358f5de5e46434c4da131
Change [1] wrongly attempted to re-define bandwidth_limit_rules,
dscp_marking_rules and minimum_bandwidth_rules as first level API
resources, leading to conflicts in the QoS API. We now define
alias_bandwidth_limit_rules, alias_dscp_marking_rules and
alias_minimum_bandwidth_rules that will enable users to perform GET,
PUT and DELETE operations on the corresponding QoS rules without having
to specify the associated policy ID.
[1] I5366dfee9b760ff5c884981582cdd17245b4d16f
Change-Id: I978668ee073c26d6e05ea5e5a0a4e16a7e513fa1
Partial-Bug: #1777627
Before the final merge of the minimum bandwidth resource classes
they got renamed in Nova and Placement. So we have to adapt.
The previous names were never released or used in any other way
outside of WIP patches, so there's no upgrade impact.
Change-Id: Ib81d3a6b312ab7d63df9b5dc97c20d32c3fb214c
Partial-Bug: #1578989
See-Also: I996bf705b14b564106426a2e57299638fb178750
See-Also: https://review.openstack.org/502306 (nova spec)
See-Also: https://review.openstack.org/508149 (neutron spec)
Change [1] introduced support for advsvc role. This added
possibility for user with role advsvc to make CRUD operations
on ports, subnets and networks in foreign tenants.
Due the check in _validate_privileges() it was not working.
This patch fixes that.
Closes-Bug: #1796854
[1] https://review.openstack.org/#/c/101281
Change-Id: I6a3f91337bf8dd32012a75916e3409e30f46b50d