737 Commits

Author SHA1 Message Date
Bence Romsics
111a8f4828 port-hints: Retrofit spec to details changed during implementation
Change-Id: Ibef6bab8aee22a4bcf107db006f6dd59f3e6a009
Related-Bug: #1990842
2023-04-03 17:12:55 +02:00
Rodolfo Alonso Hernandez
a0f4aa8ec9 Spec folder for 2023.2 cycle
According to the TC resolution [1] and the release identification
document [2], the release number will be used as primary identifier in
the development cycle. Release name will be used in marketing.

[1]https://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html
[2]https://governance.openstack.org/tc/reference/release-naming.html

Change-Id: I392f639720b8f525934d3c753aed68c04a5cb96d
2023-03-01 19:40:37 +01:00
Zuul
74e66150c6 Merge "Add spec for the OVN IPv6 DVR RFE" 2023-01-17 17:02:32 +00:00
ROBERTO BARTZEN ACOSTA
3811187f55 Add spec for the OVN IPv6 DVR RFE
Related-bug: #1998609
Change-Id: Id6243fee623c9d5c150d32169f15580219cc14a2
2023-01-17 16:28:18 +00:00
Rodolfo Alonso Hernandez
f116fcd004 OVN Neutron Agent and hardware offloaded QoS extension.
Change-Id: I3d1c17303c6aa4491fa156ebed76babe23593663
Related-Bug: #1998608
2023-01-17 16:27:39 +00:00
Zuul
780a7ced21 Merge "Add spec for the Default SG rules API" 2022-11-17 15:30:03 +00:00
Zuul
7d07728b4d Merge "Strict minimum bandwidth support for tunnelled networks" 2022-11-17 12:32:11 +00:00
Rodolfo Alonso Hernandez
5c12c2b8b8 Strict minimum bandwidth support for tunnelled networks
The aim of the RFE is to improve the previous implemented RFE
Strict minimum bandwidth support [1].

[1]https://bugs.launchpad.net/neutron/+bug/1578989

Related-Bug: #1991965
Change-Id: I21a1d9bee1d195f704a518ea3dbd3f2b1e35a357
2022-11-12 10:38:44 +01:00
Slawek Kaplonski
d55ea74e59 Add spec for the Default SG rules API
Related-Bug: #1983053
Change-Id: Ie93c87608191366928b9e37182bc6220cbbd9d7c
2022-11-10 20:39:10 +01:00
Bence Romsics
b7e53f1075 Spec: Add port hints and hint ovs-tx-steering
Change-Id: Ia2bd912e65d5091ca17f26b6cc4b4be3fc981324
Related-Bug: #1990842
2022-11-10 10:21:07 +01:00
Guillaume Espanel
9462d10a7b Add spec for metadata-rate-limit
Related-Bug: #1989199
Change-Id: I31fe80a2fa4c495acfab5886a304866c7da0d04b
2022-09-15 10:58:00 +02:00
ghanshyam mann
cc10828176 Spec folder for 2023.1 cycle
Using release number here. In Zed cycle, TC passed
a resolution[1] and updated the release Identification
document[2] to use the release number as primary
identifier in the development cycle. Release name will
be used in marketting and release team tooling (until they
are migrated to work with release number) only.

Let's use release number consistently across OpenStack
projects.

[1] https://governance.openstack.org/tc/resolutions/20220524-release-identification-process.html
[2] https://governance.openstack.org/tc/reference/release-naming.html

Change-Id: Ibd680413ef3e61da620004c0ce1f0bac7a9f8e8c
2022-09-01 00:31:22 +05:30
Zuul
8445977291 Merge "FWaaS Group Ordering Spec" 2022-08-29 12:26:48 +00:00
Anthony Timmins
5ed9f7a835 FWaaS Group Ordering Spec
Change-Id: I9a2a6d59d6c446f42189f90bb8c79223d8874670
2022-08-23 20:17:11 -05:00
Zuul
098f2706a4 Merge "Spec for Router Advertisement on Openvswitch Agent" 2022-08-22 15:00:38 +00:00
LIU Yulong
49b415960c Spec for Router Advertisement on Openvswitch Agent
Related-Bug: #1961011
Change-Id: I9255ed2df6003768878d275c706330be916f7bd9
2022-08-10 08:54:46 +08:00
Zuul
79dfad748b Merge "Add spec for Network cascade deletion" 2022-07-29 21:41:19 +00:00
Zuul
b68af46e6d Merge "[ovn]Floating IP adds distributed attributes" 2022-07-27 17:49:40 +00:00
Slawek Kaplonski
a0d3454d8f Add spec for Network cascade deletion
Co-authored-by: Sharon Koech <skoech@protonmail.ch>

Related-Bug: #1870319
Change-Id: Ic9d08e76e3bdaaa306017f796136d07d966c0cc3
2022-07-27 15:39:56 +02:00
zhouhenglc
94146b6b3c [ovn]Floating IP adds distributed attributes
Neutron adds distributed attributes to each Floating IP.
Users can set this attribute according to their actual
environment and use requirements.

see more [1]

[1] https://bugs.launchpad.net/neutron/+bug/1978039

Related-Bug: #1978039

Change-Id: Ibdaa0ae502b5fd413cb08e68356e0c18463c4974
2022-07-25 09:14:33 +08:00
Sahid Orentino Ferdjaoui
e562468c62 OVS: multiple routed provider segments per host
The proposed spec is to extend the current feature routed provider
networks to allow provisioning more than one segment per physical
network.

The support is for OVS only.

Related-Bug: #1764738
Related-Bug: #1956435

Change-Id: I00e32b5b4fc6e4127ac3a56c7d34a1b828e6cb02
Signed-off-by: Sahid Orentino Ferdjaoui <sahid.ferdjaoui@industrialdiscipline.com>
2022-07-04 17:02:18 +02:00
elajkat
97ee8a2810 Spec folder for Zed
As we run into a nasty setuptools issue/feature which broke even
tox -edocs, add py_modules=[] to setup.py's setup call, see [1].

[1]: https://review.opendev.org/q/topic:setuptools-issue-3197

Change-Id: I24adbcb9076f02c2eeefef98c21a4ccf247b0c5b
2022-04-13 17:28:52 +02:00
Frode Nordahl
be44496b70
smartnic-dpu: Update implementation details
During the review of the Nova and Neutron implementations the
wording used changed from "board serial number" to "card serial
number".

Partial-Bug: #1932154
Change-Id: Ib342351cad3ff1cd46016c1fcfe05e05bf92bf2b
2022-02-17 14:30:00 +01:00
Zuul
2ff4731ac1 Merge "Spec for distributed datapath for metadata" 2022-02-10 17:39:49 +00:00
LIU Yulong
ebaa989250 Spec for distributed datapath for metadata
Related-Bug: #1933222
Change-Id: Ice457e4ead492d3d128017a1bb551d482658ade5
2022-02-08 16:55:29 +08:00
Dmitrii Shcherbakov
7795bbd62a
Use VNIC_REMOTE_MANAGED instead of VNIC_SMARTNIC
After a round of reviews of Nova patches that utilized VNIC_SMARTNIC for
the off-path backend spec

https://review.opendev.org/q/topic:2021-09-10-off-path-net-backends-dep

it was determined that the Ironic's usage of VNIC_SMARTNIC would be
affected by how the decision is made whether a port is remote-managed or
not during the resource request creation.

https://review.opendev.org/c/openstack/nova/+/824835/13/nova/network/neutron.py#2325

See the following log for the relevant discussion:

https://meetings.opendev.org/irclogs/%23openstack-nova/%23openstack-nova.2022-02-07.log.html#t2022-02-07T15:49:56

Therefore, this change introduces a spec update to use a new VNIC
type.

Nova spec: https://review.opendev.org/c/openstack/nova-specs/+/787458
Nova BP: https://blueprints.launchpad.net/nova/+spec/integration-with-off-path-network-backends

Partial-Bug: #1932154
Change-Id: I63f156c5bfb5a41e5ebf94dc8f069828569e270a
2022-02-08 09:07:04 +01:00
Ihar Hrachyshka
077328f988 Allowed Address Pair: support matching ANY MAC address
Related-Bug: #1946251
Change-Id: I553ac57fc1e0325236282a6d218b0726a6693633
2021-11-29 13:26:48 -05:00
Zuul
89c638cd71 Merge "Move and extend qos-minimum-guaranteed-packet-rate spec" 2021-11-22 20:09:19 +00:00
Dmitrii Shcherbakov
8ff7a77df9 Off-path SmartNIC Port Binding with OVN
https://blueprints.launchpad.net/neutron/+spec/off-path-smartnic-dpu-port-binding-with-ovn

Off-path SmartNIC DPUs introduce an architecture change where network
agents responsible for NIC switch configuration and representor
interface plugging run on a separate SoC with its own CPU, memory and
that runs a separate OS kernel. The side-effect of that is that
hypervisor hostnames no longer match SmartNIC DPU hostnames which are
seen by ovs-vswitchd and OVN agents while the existing port binding
code relies on that. The goal of this specification is to introduce
changes necessary to extend the existing hardware offload code to cope
with the hostname mismatch and related design challenges while reusing
the rest of the code. To do that, PCI(e) add-in card tracking is
introduced for boards with unique serial numbers so that it can be used
to determine the correct hostname of a SmartNIC DPU which is responsible
for a particular VF. Additionally, more information is suggested to be
passed in the "binding:profile" during a port update to facilitate
representor port plugging.

WIP code: https://review.opendev.org/c/openstack/neutron/+/808961
Nova spec: https://review.opendev.org/c/openstack/nova-specs/+/787458
Nova BP: https://blueprints.launchpad.net/nova/+spec/integration-with-off-path-network-backends

Needed-By: I07ef52769da72cde8867f996111b7df4a80e4d79
Change-Id: Ic8db22d1b6570f68bd6400ecc653dc893a4b6184
Closes-Bug: #1932154
2021-11-03 15:06:23 +03:00
Balazs Gibizer
8f136023f5 Move and extend qos-minimum-guaranteed-packet-rate spec
The implementation of the qos-minimum-guaranteed-packet-rate spec did
not land in Xena so this patch moves it to the Yoga folder. Also it
extends the space based on findings during the implementation work.

Related-Bug: 1922237
Change-Id: I5ed384be490ad3962e274ad94ce28060bd6fe96b
2021-10-19 14:28:50 +02:00
Slawek Kaplonski
40f6c1663d Neutron VLAN networks with QinQ enabled
Related-Bug: #1915151
Change-Id: I4ebac838df82a64a5a6f2c773d69050ade5668ce
2021-10-07 09:42:37 +00:00
Balazs Gibizer
21b6188e86 Spec folder for Yoga
Change-Id: I46b7f1238b19cbbcca40abde6629d20bbe05542c
2021-09-15 16:43:33 +02:00
elajkat
1cffec094a FUP for BFD to allow optional src_ip on API
We got feedback from backend developers to enable src_ip as optional
parameter on the API, see [0].

[0]: https://review.opendev.org/c/openstack/neutron-specs/+/767337/20/specs/xena/bfd_support.rst#171

Change-Id: I1bcdfba3e0bc4933f954732f42da0e8bddf8c6e8
2021-09-09 11:05:58 +02:00
Zuul
cd23b983dc Merge "Create intermediate OVS bridge to improve live-migration in OVN" 2021-09-02 15:03:30 +00:00
Rodolfo Alonso Hernandez
81f4ecb9d4 Create intermediate OVS bridge to improve live-migration in OVN
This spec proposes to add an intermediate bridge between the VM patch
port and the integration bridge. That will allow the backend (OVN)
to properly configure the needed OpenFlow rules before the VM
is unpaused in the destination host. That will reduce the
networking disruption during the live migration process.

Change-Id: I558523a8922567efb0739173c7c2fda72504a8fe
Related-Bug: #1933517
2021-08-30 14:43:38 +00:00
Ilya Chukhnakov
31e452c6ea Add Node-Local Virtual IP Spec
Adding the spec to support Node-Local Virtual IP for the RFE
https://bugs.launchpad.net/neutron/+bug/1930200

Partial-Bug: #1930200
Co-Authored-By: obondarev <oleg.bondarev@huawei.com>
Change-Id: If9f137a839b37f8262f4842b34401a13967ed43e
2021-08-17 13:51:48 +03:00
Zuul
e3c7a586d4 Merge "BGPaaS enhancements" 2021-07-06 00:59:37 +00:00
Zuul
e727ef95ef Merge "Allow multiple external gateways" 2021-07-05 12:34:42 +00:00
Zuul
2333754314 Merge "BFD support for Neutron" 2021-06-27 23:16:09 +00:00
Bence Romsics
dceafdb988 Allow multiple external gateways
Change-Id: I4c66627e6c27be5d9e7e54862788e09403befdbc
Related-Bug: #1905295
2021-06-25 15:53:37 +02:00
Balazs Gibizer
6fbc6bd8a4 Fix up the pps spec config name
There was a comment from Rodolfo to add the resource_provider_ prefix
for the new packet processing config options but I forgot to add it to
the packet_processing_inventory_defaults config name. Fixed it now so
all the three new config option names have the same prefix.

Related-Bug: 1922237
Change-Id: I3018715e1265aff70002711a06b2bf5ee9ba53a5
2021-06-24 13:13:33 +02:00
Manu B
3bba00dea2 BGPaaS enhancements
Related-Bug: #1921461

Signed-off-by: Manu B <manubk2020@gmail.com>

Change-Id: I0d69aff98ee00d01fe2e4142b87ae39beae01adf
2021-06-24 06:33:33 +00:00
Zuul
c5ccab88d1 Merge "L3 router support ndp proxy" 2021-06-23 22:01:03 +00:00
elajkat
e35a6606f0 BFD support for Neutron
Change-Id: I2fa8d9b4f19080c7ab8ed954aff7525bb1dbc35a
Related-Bug: #1907089
2021-06-23 17:39:42 +02:00
Zuul
6a51ad233e Merge "Remove Xena placeholder spec" 2021-06-16 08:52:10 +00:00
Yang JianFeng
6e6ad985f1 L3 router support ndp proxy
Change-Id: I1b57cbd45513295f80df96efca917476c4fa5033
Related-Bug: #1877301
2021-06-08 11:30:18 +00:00
Zuul
8e42448055 Merge "QoS minimum guaranteed packet rate" 2021-06-04 07:55:32 +00:00
Bence Romsics
f9fd6ea7e5 Remove Xena placeholder spec
Can be removed as soon as we have merged the first Xena spec.

Change-Id: Id4de3ec57989190421658fc80416ea9ddc01a178
2021-06-01 15:22:24 +02:00
Balazs Gibizer
ceb39afd7d QoS minimum guaranteed packet rate
Similarly to how bandwidth can be a limiting factor of a network
interface, packet processing capacity tend to be a limiting factor
of the soft switching solutions like OVS. In the same time certain
applications are dependent on not just guaranteed bandwidth but also
on guaranteed packet rate to function properly. OpenStack already
supports bandwidth guarantees via the minimum bandwidth QoS policy
rules. This specification is aiming for adding support for a similar
minimum packet rate QoS policy rule.

Related-Bug: 1922237
Change-Id: Id17ee01dc288517a05f746a479500a6218ad55f4
2021-05-31 17:01:03 +02:00
Bodo Petermann
aa641b223f Add spec for VPNaaS for OVN
Adding the spec to support VPNaaS for OVN for the RFE
https://bugs.launchpad.net/neutron/+bug/1905391

Related-Bug: #1905391
Change-Id: If14135d42459296158a09641c880768994a1c9ac
2021-05-31 10:22:51 +02:00