Add the API extension ``uplink-status-propagation-updatable`` to make
the port field ``propagate_uplink_status`` updatable. Now is possible
to send a port PUT request to update the value defined during the
creation.
This change will have an effect in the ML2/SR-IOV agent that will need
to update the VF status accordingly.
Related-Bug: #2078661
Change-Id: I96d8b1cfe2f0cce2198d74f48abfc90d952384bd
This new extension allows to set port to be trusted. That value will be
then passed to Nova in the port's binding:profile dict.
Related-Bug: #2060916
Change-Id: Ia809fb0a35cc764ad017d81b018efc81b6de8500
This is a shim extension that indicates if Neutron quota engine
checks the resource usage before updating any quota limit. That
makes the extension ``quota-check-limit`` to be the default Neutron
quota engine behaviour and aligns it with other projects.
To enforce a quota limit without checking the resource usage, now
it is needed to pass the CLI parameter "--force".
Related-Bug: #1953170
Related-Bug: #1936408
Change-Id: I778e6090fe4d01e2bf0b51933897e80624bab38a
The ``tag-creation`` shim extension API definition enables the creation
of multiple tags for a single resource using a ``POST`` request. The
value of the tags is passed as an argument of the call.
Related-Bug: #2073836
Change-Id: I8b7ac688f7aed64995b3c244b0a3662aa81313bc
Neutron can't really validate if string provided as 'target_tenant' in
the /v2.0/rbac-policies POST/PUT request is project ID or something
else, like e.g. project's name.
This patch adds small note about this to the Neutron api-ref document so
that users can be more aware of that.
Related-Bug: #2065743
Change-Id: Ie5bec404c372209ca15e4c8454957040032751cb
The spec networking_general_api_information.html was moved
to api-ref in [0] but some of the links pointing to it
were not updated. This change makes all the refs consistent
and adds links where missing.
Also moved sync/async and bulk create sections lower to
group all the filtering, pagination and sorting sections
together since they are inter-related.
[0] https://review.opendev.org/c/openstack/neutron-lib/+/362877
Change-Id: I895cc9aaee2546b95e93150c134f350a50346447
With new default API policies binding:profile attribute of the port can
be only set or updated by the SERVICE user. This patch adds small note
about this to the Neutron API-REF document.
Related-Bug: #2052937
Change-Id: I0b2f2225e29537c9fd2de53b0945a451b9bcdde3
This extension adds a new field to the "subnet" resource:
"router:external". This boolean field, that is False by default,
represents if the subnet belongs to an external network.
Related-Bug: #2051831
Change-Id: I75a9c30f1e8031d40a548df345b02fbe0bc47706
Neutron support bulk create of security group rules, but that's
undocumented in the api-ref. This commit fixes that by adding the docs
and examples of these calls.
Change-Id: I32ce8b3501a01552fed67ba24602e891c3c01cd4
The Neutron patch linked below changes behavior of API update requests
to vnic_type port binding attribute on bound ports. It's no longer
allowed to update the vnic_type if the port is already bound.
Depends-On: https://review.opendev.org/c/openstack/neutron/+/892815
Related-bug: #2033090
Change-Id: Ic5c6d54a1e5e57e977623ac6a4e2e6278f7237b7
Signed-off-by: Jakub Libosvar <libosvar@redhat.com>
SG rule template API accepts any string (any uuid) as remote group id or
remote address group id. It may be something what's not existing in the
time of the creation of template and that's fine. But if it will be not
existing when regular SG will be created for project it will fail making
SG for that project.
This patch adds small warning about this to the default SG rules
template api-ref.
Additionally this patch updated some small issues in the "create
default security group rule" section.
Related-Bug: #1983053
Change-Id: I9bad07d8ed11796047883f87b45a7da0799cdcb1
Added a new API extension
``security-groups-rules-belongs-to-default-sg`` that adds a new
read only field ``belongs_to_default_sg`` in the security group
rules. This flag determines if this security group rule belongs
to the project's default security group.
Related-Bug: #2019960
Change-Id: Ibd8f57d82b28f5cdb8874f1ae22cb35adcd8e880
This new network API field, that can be used during the network
creation, will trigger the creation of a ``ha_router_networks``
database register. This register binds the project with the
created network and defines it as the high availability network
of the project, that is unique per project.
The default value is "False".
Related-Bug: #2016198
Change-Id: Id6e434060a7559026f9083904a91213b39361336
API additions for [1].
* Added a new router attribute: external_gateways;
* Added new API definitions for:
PUT add_external_gateways
PUT update_external_gateways
PUT remove_external_gateways
* Added extensions for each of the new router-level attributes:
* enable_default_route_ecmp
* enable_default_route_bfd
* Combined the validation logic for the external_gateway_info type
across extensions (l3_ext_gw_mode, qos_gateway_ip and the new
extension called l3_ext_gw_multihoming).
[1] https://review.opendev.org/c/openstack/neutron-specs/+/870030/
Change-Id: I2618475636b2bb9bfd743a62f5d4859d4f68a547
Related-Bug: #2002687
This behavior matches what ML2/OVS implementation does and what we
intend to implement for ML2/OVN. More than that, a decision was made
during vPTG to make the behavior part of api-ref to facilitate
cross-backend consistency.
Related-Bug: #2006949
Related-Bug: #2009053
Change-Id: Ic633eedd9f0d320d9ad0c27a72f07b1b016d7ba3
