Repository navigation
feat: Handle multiple network leaf pairs in vlan_group naming convention - #2187
Merged
Merged
Conversation
mfencik
reviewed
Aug 6, 2026
Contributor
|
Given the new request for -3 switches. We need to revisit this. |
Contributor
Author
|
2724f39 already adds support for those. What do we need to revisit? Note that this is an interim solution anyhow. |
Contributor
Milan messaged me about concerns here. Speak with him. |
stevekeay
force-pushed
the
vlan_group_names
branch
from
October 2, 2026 10:17
2724f39 to
27a5528
Compare
stevekeay
enabled auto-merge
October 5, 2026 08:52
stevekeay
force-pushed
the
vlan_group_names
branch
from
October 5, 2026 08:55
27a5528 to
f96c362
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release note:
This change will take effect on baremetal node inspection.
Any existing data should be updated before any nodes are inspected.
So for each of the devices in these cabs we should be updating the
physical_networkin the Ironic baremetal ports as well as the Neutron network segments.In addition we should ensure that nautobot picks up those changes, fixing up if necessary.
If an OVN/OVS network node is in these cabs then we might need further updates, investigation would be required there to make sure we don't break any ovn bridge mappings. Envs where the infra nodes are connected to a "-2" switch, note the first two are already done: