Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Dynamic network segments for each VLAN Group #771

Open
wants to merge 43 commits into
base: main
Choose a base branch
from

Conversation

stevekeay
Copy link
Contributor

This was opened to address PUC-787

@stevekeay stevekeay changed the title feat: Dynamic network segments feat: Dynamic network segments for each VLAN Group Mar 17, 2025
@stevekeay stevekeay force-pushed the dynamic-network-segments branch 6 times, most recently from 9a809bc to db6c164 Compare March 17, 2025 15:58
"-3f": "storage-appliance",
"-4f": "storage-appliance",
"-1d": "bmc",
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Reading through now, we won't need this code because we just need to create the correct network segment ranges for the "network" vlan groups which will match up with Nautobot.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It seems like we would need to find the baremetal port, perhaps by MAC address, and then look up its physical_network. This complicates things, so leaving it as a task to clean up later once we get this all working.

@stevekeay stevekeay force-pushed the dynamic-network-segments branch 7 times, most recently from d15a22a to 2118f7c Compare March 26, 2025 11:40
@stevekeay stevekeay force-pushed the dynamic-network-segments branch 3 times, most recently from f37859a to 8894c60 Compare March 26, 2025 14:59
Steve Keay added 9 commits March 27, 2025 14:39
The context only has the information we need in the later phases of the
process.  We will be called early in the process with incomplete
information, this is normal and we should not raise an error in these
conditions.
Neutron is now the authority for assigning those numbers
Our provisioning network uses this.
@stevekeay stevekeay force-pushed the dynamic-network-segments branch 2 times, most recently from 907bf94 to 91af998 Compare March 27, 2025 18:01
Steve Keay added 2 commits March 27, 2025 18:25
We don't want to "bind" the VXLAN segments that are passed to
bind_port().  We want to make a dynamic VLAN-type segment and bind that
instead.

We are no longer using any VLAN-type networks, so remove the code that
deals with those (it was handling the provisioning network which was
still confiured as VLAN type for legacy reasons, but that is now moving
to VXLAN-type network, same as all the others.)
@stevekeay stevekeay force-pushed the dynamic-network-segments branch from 71a7222 to 6f7aecb Compare March 27, 2025 18:25
@cardoe
Copy link
Contributor

cardoe commented Mar 28, 2025

Will you include a detailed description in the PR?

@stevekeay stevekeay force-pushed the dynamic-network-segments branch from 766acad to 89fcaf0 Compare April 2, 2025 18:56
This will record which sub-ports belong to which network segments.
@stevekeay stevekeay force-pushed the dynamic-network-segments branch from 89fcaf0 to f42e5c5 Compare April 3, 2025 10:36
@stevekeay stevekeay force-pushed the dynamic-network-segments branch from 3a39404 to d292b12 Compare April 4, 2025 14:28
@stevekeay stevekeay requested a review from Copilot April 7, 2025 17:54
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Comments suppressed due to low confidence (1)

python/neutron-understack/neutron_understack/tests/test_trunk.py:1

  • [nitpick] The removal of the entire trunk tests may lead to a gap in test coverage for trunk-related functionality. Please ensure that either this functionality is no longer needed or that its behavior is covered by alternative tests.
Entire file removed

stevekeay and others added 5 commits April 7, 2025 19:40
Committing co-pilot suggestion

Co-authored-by: Copilot <[email protected]>
This was removed but potentially still useful so I am putting it back.
This suppports the OVN router and it may be re-instated in future but
for now it is broken by our change to openstack vlan allocation so
removing it for now.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants