Commit Graph

824 Commits

Author SHA1 Message Date
Roberto Bartzen Acosta eed0019aa3 Spec folder for 2024.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: I99ddc618ff7003497dc50d1b38b490d82495db53
2024-03-24 13:47:03 +00:00
Frode Nordahl 5852b695ef
Move Active-active L3 Gateway with Multihoming to 2024.1
The feature was fully implemented in the 2024.1 cycle.

Related-Bug: #2002687
Change-Id: I4e69bdf2ac9da1154d3847f3191b110f09130e02
Signed-off-by: Frode Nordahl <frode.nordahl@canonical.com>
2024-03-06 07:46:53 +01:00
Zuul 949a0f5d0a Merge "Add spec for coexistence support for OVN externally managed resources RFE" 2024-02-13 08:52:05 +00:00
Roberto Bartzen Acosta 6e5c76fb1b Add spec for coexistence support for OVN externally managed resources RFE
Related-bug: #2027742
Change-Id: I4915d482358f01e81e4b48986f18f733b9d93642
2024-01-24 08:58:20 -03:00
Zuul 36c79f432e Merge "port-hints: Retrofit CLI syntax" 2023-10-25 07:08:18 +00:00
Bence Romsics 4bdb10c3ca port-hints: Retrofit CLI syntax
Fix the CLI syntax in the spec, so it shows the syntax that got merged.

Change-Id: I94cb497609afd2c33deeead73d96cd0b65c48be9
Related-Bug: #1990842
Related-Change: https://review.opendev.org/c/openstack/python-openstackclient/+/882274
2023-10-24 14:12:48 +02:00
Roberto Bartzen Acosta 297f23572a Spec folder for 2024.1 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: I9440d838ca9845ae3bdf90755e763575aff18061
2023-08-14 16:17:05 -03:00
Miguel Lavalle 8a0eaebf9a Multiple backend support for L3 routers in ML2/OVN
This spec proposes to support multiple back-ends for routers in the
ML2/OVN mechanism driver

Partial-Bug: #2020823

Change-Id: Ic7f84d8252ef5197b4d1851f7296e237bf581503
2023-06-26 20:09:29 -05:00
Rodolfo Alonso Hernandez ec0a0fb2a2 Port extension to create hardware offloaded ports
The aim of the RFE is to create a new port extension to allow to create
ports with hardware offloaded capabilities.

Related-Bug: #2013228
Change-Id: I0ee77fd4a0b1fe28b206db7dc13e105ffff122a6
2023-05-30 04:19:46 +02:00
Zuul bd0a9ba5d4 Merge "ERSPAN and GRE mirroring for tap-as-a-service" 2023-06-01 11:02:08 +00:00
elajkat de2ee265fa ERSPAN and GRE mirroring for tap-as-a-service
Change-Id: Idc52ffb78033c658558dba381dc742cc23c0f2b7
Related-Bug: #2015471
2023-05-30 15:43:26 +02:00
Slawek Kaplonski 03e11287c7 Default SG rules - update fields in the API examples
This patch updates "configurable default SG rules" spec by
adding "description" field and remove other standard attributes such
as "created_at", "updated_at" and "revision_number" from the exmaples of
the API requests and responses.

Related-Bug: #1983053
Change-Id: I3fd5f08e691db3ab025a1c64f5105749234ae0c2
2023-05-22 09:40:27 +00:00
Slawek Kaplonski 7600a542f7 Add "remote_address_group_id" attribute to the default SG rules API
This patch adds new parameter to the API of the default SG rules
templates API. New parameter is called
"remote_address_group_id" and can be used to define uuid of the remote
address group which will be referenced in default rule(s) created for
each new SG.

Additionally this patch updates type of the "remote_ip_prefix" field in
the database. It was set by mistake to "Integer" but should be "String".

Related-bug: #1983053
Change-Id: Ieccd6e70bce6be9a16d38b25efc2774ffefe1699
2023-05-19 09:43:43 +02:00
Slawek Kaplonski 73f68a1fda Add "used_in_non_default_sg" attribute to the default SG rules API
This patch adds new parameter to the API of the default SG rules
templates API. New parameter is called
"used_in_non_default_security_group" and will be used to mark if rule
should be used in SGs other than "default" one for the project.

Related-bug: #1983053
Change-Id: Ic2fd7b00d4a9de150252eddaffd0409da0925e99
2023-05-19 07:37:57 +00:00
Slawek Kaplonski 55b8b9e886 Move configurable default SG rules spec to 2023.2 cycle
This spec was approved originally in the 2023.1 cycle but I didn't had
time to implement it then.
So now lets move it to the 2023.2 cycle and implement it finally.

Related-bug: #1983053
Change-Id: Id64231e30678207ee36225c18ce72b9928303afb
2023-05-16 20:02:07 +02:00
niuke d1eca25a3f setup.cfg: Replace dashes with underscores
Setuptools v54.1.0 introduces a warning that the use of dash-separated options in 'setup.cfg' will not be supported in a future version [1].
Get ahead of the issue by replacing the dashes with underscores. Without this, we see 'UserWarning' messages like the following on new enough versions of setuptools:

  UserWarning: Usage of dash-separated 'description-file' will not be
  supported in future versions. Please use the underscore name
  'description_file' instead

[1] https://github.com/pypa/setuptools/commit/a2e9ae4cb

Change-Id: I1ec92d9cb6148e2cf0172075ec1eeeede13015fa
2023-04-28 08:20:56 +00:00
Zuul 4ba8d5bd2a Merge "port-hints: Retrofit spec to details changed during implementation" 2023-04-03 20:10:24 +00:00
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
Dmitrii Shcherbakov 9763752c73
Active-active L3 Gateway with Multihoming
The aim of the RFE is to add multihoming support to routers along with
automatic management of ECMP for default routes and BFD next-hop
reachability verification.

https://bugs.launchpad.net/neutron/+bug/2002687

Co-Authored-By: Frode Nordahl <frode.nordahl@canonical.com>
Related-Bug: #2002687
Change-Id: I95a0d5f1b7aef985df5625cd83222799db811f2b
2023-03-27 15:32:12 +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
Brian Haley e5e141f134 Update envlist for tox4
tox4 even when running specific env with -e option tries
to find python version for all envs defined in envlist[1]
when running with --skip-missing-interpreters=false and
fails if interpreter missing for any of the env.

With py38 in envlist it tries to find python3.8
which is not available in ubuntu-jammy by default
and fails, hence use generic version instead i.e py3
to handle it.

Even though [1] is fixed we are still seeing this failure.

[1] https://github.com/tox-dev/tox/issues/2811

Also had to add "ignore_basepython_conflict = True".

Change-Id: I351870695b1c6706888d8a51fa33ea0fcbc63cd7
2023-01-17 09:47:07 -05:00
Rodolfo Alonso Hernandez af0209a18f Fix tox.ini for tox4
This patch also replaces the outdated py36 job with the py38 one.

Change-Id: Id330d8cdbcf70b0403e8283228ce9dec10403012
2023-01-03 15:11:01 +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
niuke 3941525d35 remove unicode prefix from code
Change-Id: Ie49e7ba96105bb117b7de6e85d7c6df823818e14
2022-08-13 09:10:09 +08: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