Skip to content

Conversation

@mnietoji
Copy link
Contributor

@mnietoji mnietoji commented Nov 20, 2025

[NFV] OVS DPDK SRIOV IPV6 with 1 or 2 nodesets scenarios
Created 2 new scenarios adding ipv6 to 2 already existing scenarios:

  • VA OVS DPDK SRIOV
  • DT OVS DPDK SRIOV with 2 nodesets

@mnietoji mnietoji marked this pull request as draft November 20, 2025 16:34
@mnietoji mnietoji changed the title ipv6 2 nodesets nfv [NFV] OVS DPDK SRIOV IPV6 with 1 or 2 nodesets scenarios Nov 21, 2025
@mnietoji mnietoji force-pushed the nfv_ipv6 branch 4 times, most recently from dcd3c5e to 8cd7e21 Compare November 26, 2025 18:48
@mnietoji mnietoji force-pushed the nfv_ipv6 branch 4 times, most recently from b07ffb5 to f97984c Compare December 5, 2025 09:52
@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2f91bf54d0db4b6cbfca37fbbc74c932

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 3m 47s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 4m 36s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 4m 17s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 07s

@mnietoji mnietoji added ready-review Request is ready to be reviewed and removed do-not-merge/work-in-progress labels Dec 5, 2025
@mnietoji mnietoji marked this pull request as ready for review December 5, 2025 10:00
@openshift-ci openshift-ci bot requested a review from abays December 5, 2025 10:00
@mnietoji
Copy link
Contributor Author

mnietoji commented Dec 5, 2025

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/160c2efa99e5423597fe38340a7365ae

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 4m 52s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 3m 49s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 5m 49s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 32s

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/db9dc39a0fe24eb1ab2730dda6867641

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 3m 46s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 3m 46s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 4m 37s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 31s

@mnietoji
Copy link
Contributor Author

mnietoji commented Dec 5, 2025

rdoproject.org/github-check is failing because there is a dependency with this PR in ci-framework. I need to merge in first place ci-framework PR and then this architecture PR
openstack-k8s-operators/ci-framework#3476

@fultonj
Copy link
Contributor

fultonj commented Dec 8, 2025

waiting on openstack-k8s-operators/ci-framework#3476
remove DNM when it's ready

@mnietoji
Copy link
Contributor Author

recheck

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/b0b6ef44390345e0b5beb4a24e7df0a8

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 4m 01s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 6m 11s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 5m 22s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 5m 15s

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/8a64eca3dd664cab9c02755796875f0f

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 3m 52s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 4m 35s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 4m 34s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 24s

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/a1c7151e396c48489df3840582505931

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 3m 40s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 3m 36s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 4m 07s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 03s

@mnietoji mnietoji added do-not-merge Changes are not ready to be merged and removed ready-review Request is ready to be reviewed labels Dec 22, 2025
@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/93c9d62fd0ee45639b259b5de374c397

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 4m 35s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 4m 54s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 4m 00s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 10s

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/18532a3574464381b18ef43e321259bc

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 5m 04s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 4m 59s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 4m 15s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 4m 33s

@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2dc465459d2c4b8488d95434d57f5e1e

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 3m 34s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 4m 37s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 3m 58s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets SUCCESS in 4m 51s

@fultonj
Copy link
Contributor

fultonj commented Jan 5, 2026

@mnietoji I see you made some changes. Feel free to remove the "do not merge" label and add the "ready for review" label when you need me to review it again.

@mnietoji mnietoji force-pushed the nfv_ipv6 branch 2 times, most recently from 891c045 to 0478dd1 Compare January 9, 2026 16:26
@softwarefactory-project-zuul
Copy link
Contributor

Build failed (check pipeline). Post recheck (without leading slash)
to rerun all jobs. Make sure the failure cause has been resolved before
you rerun jobs.

https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/fd3f3beea66147ae9c223c06227e8de6

✔️ noop SUCCESS in 0s
✔️ rhoso-architecture-validate-ovs-dpdk SUCCESS in 3m 26s
✔️ rhoso-architecture-validate-ovs-dpdk-sriov SUCCESS in 3m 51s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6 FAILURE in 3m 12s
rhoso-architecture-validate-ovs-dpdk-sriov-ipv6-2nodesets FAILURE in 3m 23s

@mnietoji mnietoji added ready-review Request is ready to be reviewed and removed do-not-merge Changes are not ready to be merged labels Jan 12, 2026
```
Change to the nfv/ovs-dpdk-sriov/edpm directory
```
cd architecture/examples/va/nfv/ovs-dpdk-sriov/edpm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cd architecture/examples/va/nfv/ovs-dpdk-sriov/edpm
cd examples/va/nfv/ovs-dpdk-sriov/edpm

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be the v6 path?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am checking documentation in other examples and paths start with the architecture repo that contains the repo, I would not modify it to have same format than the other ones
It is not v6 path because edpm it is being reused

```
Change to the nfv/ovs-dpdk-sriov directory
```
cd architecture/examples/va/nfv/ovs-dpdk-sriov
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
cd architecture/examples/va/nfv/ovs-dpdk-sriov
cd examples/va/nfv/ovs-dpdk-sriov

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example is in examples/va/nfv/ovs-dpdk-sriov-ipv6/

Shouldn't they be doing the following instead?

cd examples/va/nfv/ovs-dpdk-sriov-ipv6

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, updated

Copy link
Contributor

@fultonj fultonj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a big improvement over the original PR as it has about half as much code (~900 lines, not 1800 lines).

  • The steps in the control-plane.md files make sense to me for the v6 scenarios if you update the paths to use the v6 scenarios (I could follow the md file to create the CRs)
  • The steps in the data-plane.md files do not make sense to me since the v6 scenarios do not contain an edpm directory. (I could not follow the md file to create the CRs)

I have more detailed questions below.

```
Change to the nfv/ovs-dpdk-sriov directory
```
cd architecture/examples/va/nfv/ovs-dpdk-sriov
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This example is in examples/va/nfv/ovs-dpdk-sriov-ipv6/

Shouldn't they be doing the following instead?

cd examples/va/nfv/ovs-dpdk-sriov-ipv6

```
Change to the nfv/nfv-ovs-dpdk-sriov-2nodesets directory
```
cd examples/dt/nfv/nfv-ovs-dpdk-sriov-2nodesets
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be the v6 path?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, control-plane routes are wrong, updated

```
Change to the nfv/nfv-ovs-dpdk-sriov-2nodesets/edpm directory
```
cd examples/dt/nfv/nfv-ovs-dpdk-sriov-2nodesets/edpm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be the v6 path?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR adds the nfv-ovs-dpdk-sriov-ipv6-2nodesets directory. The readme files do not say to use this directory though. I originally thought this was a lack of editing after doing a copy/paste, but I also see that the edpm directory does not exist for the added nfv-ovs-dpdk-sriov-ipv6-2nodesets directory.

Are you sure this readme file is correct? In the 2-nodeset v6 sceario do they still use the v4 edpm directory? If so how and when do they use the nfv-ovs-dpdk-sriov-ipv6-2nodesets directory?

This should be clear from reading the .md files but it's not clear to me right now since I have the above questions.

[fultonj@stybba nfv{nfv_ipv6}]$ ll
total 4.0K
drwxr-xr-x. 4 fultonj fultonj  162 Jan  6 10:27 nfv-ovs-dpdk-sriov-networker
drwxr-xr-x. 5 fultonj fultonj 4.0K Jan  6 10:27 nfv-ovs-dpdk-sriov-hci
drwxr-xr-x. 4 fultonj fultonj  162 Jan  6 10:27 nfv-ovs-dpdk-sriov-2nodesets
drwxr-xr-x. 3 fultonj fultonj  150 Jan 12 15:18 nfv-ovs-dpdk-sriov-ipv6-2nodesets
[fultonj@stybba nfv{nfv_ipv6}]$ find . -name edpm
./nfv-ovs-dpdk-sriov-2nodesets/edpm
./nfv-ovs-dpdk-sriov-networker/edpm
[fultonj@stybba nfv{nfv_ipv6}]$ 

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated readme

```
Change to the nfv/ovs-dpdk-sriov/edpm directory
```
cd architecture/examples/va/nfv/ovs-dpdk-sriov/edpm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be the v6 path?

Created 2 new scenarios adding ipv6 to 2 already existing scenarios:
* VA OVS DPDK SRIOV
* DT OVS DPDK SRIOV with 2 nodesets

Signed-off-by: Miguel Angel Nieto Jimenez <[email protected]>
@openshift-ci
Copy link

openshift-ci bot commented Jan 13, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mnietoji
Once this PR has been reviewed and has the lgtm label, please ask for approval from fultonj. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mnietoji
Copy link
Contributor Author

There were some issues in the documentation, updated:

  • control plane files: update path the the ipv6 folder
  • dataplane files: Added a comment to clarify that ipv4 are reused because there is no difference

Copy link
Contributor

@fultonj fultonj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm label Jan 13, 2026
@fultonj fultonj dismissed their stale review January 13, 2026 21:44

Issue has since been addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm ready-review Request is ready to be reviewed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants