-
Notifications
You must be signed in to change notification settings - Fork 97
lag based on lag.members syntax #1350
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
Conversation
677c103 to
d38cc9c
Compare
|
You keep adding stuff, so I put the PR back into draft. Please let me know when you're done. |
|
@jbemmel Is this final and ready for review? Thank you! |
|
Found an interesting case that crashes netlab: define LAG link group without enabling the LAG module, and the link transformation crashes: I think this should be fixed. Alternatively, I could merge the PR and then rework it to use lag.members attribute which would force LAG module to be used. It would also get rid of the group link code. FWIW, if I use... ... then netlab complains about missing module before it complains about the lack of nodes on the link, so it looks like we could do the transformation in a module (i.e. it would not require a plugin) How would you like to proceed? |
Thanks for reviewing, I will rework it to use |
1fd9a90 to
a8701b3
Compare
|
Wow, this was super-fast. Will review it tomorrow, it's getting late over here. |
|
Great job, just a ton of minor suggestions ;) |
… instead of reverse engineering through _linkname
Cleanup _link_group attribute
…k groups Based on discussion, this syntax forces a check for the presence of the lag module
5566449 to
65ee6c2
Compare
* Check that link.members is a list * Change naming of links * Update test results
A variation on the earlier PR:
This forces a check for the
lagmodule when using this functionality, it is more conciseReplaces #1337