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
New network script generator (60-network-devices.sh) #1574
Conversation
@rmetrich According to @gdha @gozora |
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 change is code is quite huge, and therefore, not easy to decide if everything is ok or not.
I suppose the first tests will tell us very quickly. On first sight the code looks clean and well written with good documentation. A job well done (I should do that more often:)
The only thing that bothers me are the Unit Tests - nice to have but do they belong in the code? There are pros and contras for it. We can leave it here for the moment |
@gdha |
@jsmeix I would prefer that we release 2.3 first and then do the merge as then we will have plenty of time to test the code base. |
@gdha I put the unit tests here just for reference. |
I also prefer to release ReaR 2.3 first to stay on the safe side. |
@rmetrich I can't tell nothing less then IMPRESSIVE! ;-) As i'm not much of a "code reader", I'd need to test this directly by clone and run ... V. |
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.
I've run several tests, and for me this PR works sufficiently well.
V.
"Sufficiently", did you find issues?
Renaud.
Sent from my phone.
Le 18 nov. 2017 2:05 PM, "Vladimir Gozora" <notifications@github.com> a
écrit :
… ***@***.**** approved this pull request.
I've run several tests, and for me this PR works sufficiently well.
V.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1574 (review)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABHBc3Ksen6YqZN29dNnc1D_DZ9K87tCks5s3tX8gaJpZM4QdcWP>
.
|
:-), no but I never actually used all those fancy ReaRs networking options and if my network is not up properly, I just configure it manually ;-).
I'm pretty sure that this is not related to your work though. I've tested your PR in vlan over bonded device and it worked well, and as I did not had time to test it much further I've choose word "Sufficiently" hope you don't mind ;-) V. |
@rmetrich At a RHEL6.5 server with several bridges and bonding interfaces here the ip link command mentions an
The version in use is "ip utility, iproute2-ss091226". |
@hpannenb Thanks for reporting. I'll test on RHEL6 and adjust. |
979ba3e
to
a7919c2
Compare
@hpannenb Please try the latest code. |
@hpannenb Thanks for feedback. I initially didn't test on RHEL6 because we (Red Hat) do not ship ReaR 2.x on RHEL6 ... |
@rmetrich Could you fix the conflicts then we are able to merge it without issues? |
…eam' and 'physdev' - Removed current teaming code - Have routes use interface mapping - Added explanations
- Adapt search for lower interfaces when no 'lower_*' symlink exists (RHEL6) - Always set device for bonding using 'echo "+dev" > .../bond/bonding/slaves' - Detect support for 'master' in 'ip link' (no support in RHEL6) - Replace 'readlink -f' by 'readlink -e' - Use 'brctl' when 'ip link' doesn't support 'bridge' type (RHEL6) - Use function 'resolve' to wrap 'readlink' when it doesn't support more than 1 filename (RHEL6)
dc31316
to
1c42620
Compare
@gdha Done! |
@jsmeix can we merge it? |
@gdha |
@rmetrich |
This work is a solution for Issue #1561.
It consists in a full rewrite of the 310_network_devices.sh script generating network interfaces for use during the ReaR recovery early boot.
It also handles corner cases/odd setups that can be found from time to time, typically when the administrator uses bonding + bridges + vlans as well as teaming.
With that new code, adding new configurations will be very easy in the future.
I also added interface mapping code to the corresponding 350_routing.sh script generating routes.
In the tests/ directory, you will 2 setups that I used to verify the network generation code. It covers quite a lot of setups found.