-
Notifications
You must be signed in to change notification settings - Fork 72
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
lag: Remove 'lag' link type, cleanup virtual links #1646
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "type" interface attribute should not be defined, otherwise it looks reasonable.
Also, what happened to "I will submit a PR when I'm done programming"? Got three notifications about this PR. |
4702a67
to
c812b6c
Compare
43d736c
to
3fd9f11
Compare
Please resolve the merge conflicts first. Thank you! |
ce43daf
to
c0adea1
Compare
Looks like you're still working on this one. Change it to "ready for review" when you're done. |
dc9eae3
to
0d182ec
Compare
What's going on with this one? Is it ready to merge (I won't even try to review it)? |
Waiting on the other lag PR to be merged, then I'll update this one |
* Modify lag member lag._parentindex to match lag.ifindex, not linkindex
…on intf.linkindex, not intf.lag.ifindex
…g interfaces get created * Fix the moment lag interfaces get created: After interface attribute validation, but before vlan pre link transformation callbacks Some issue remains with IP addresses being allocated to lag interfaces instead of vlan SVI
TODO: Validate all VLAN cases with/without lag
…er lag interfaces are created
* vlan-link-error: Now correctly identifying 'irb' as an invalid value, but hiding the mismatch in vlan.access name * vlan-trunk-attribute-error: Instead of identifying 'bgp' as being not enabled, 'bgp.as' is determined to be an invalid irb interface attribute
* Fix interface attribute inheritance
* Expand L3 test case to include gateway and custom IP settings
Update test results
In multi-provider scenario's, link.type is changed resulting in virtual lag links not being removed
128221d
to
13bf985
Compare
Conceptually a 'lag' link type does not make a whole lot of sense; the
lag
module temporarily uses a link object as a grouping construct until the node lag interfaces are created, but there is no reason to keep this around once that is doneThis PR cleans things up a little:
lag.ifindex
, notlinkindex
(which is now removed from the lag interface)Includes various bug fixes: