-
Notifications
You must be signed in to change notification settings - Fork 400
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
Support for wicked network manager #900
Conversation
26d15f0
to
ee66a19
Compare
ee66a19
to
43b46cc
Compare
43b46cc
to
98289ae
Compare
Effective diff between the wicked (a) and the bluetooth dbus module (b):
|
About your first point:
Maybe we could just add them explicitely, since it's just two files? About the second point:Do you mean the systemd service files for the wickedd parts? it's less messy to start it like this vs explicit calls since there are dependencies between the multiple wicked components and also due to the dependency with dbus. We tried multiple combinations and we had trouble to get get wicked started only when dbus was ready to be used. This way it seemed it worked fine. |
Yes. If there is no deeper reason behind that, we should go for it. Also, we need to ensure the module either becomes host only safe.
I was referring to this:
|
@rtorrero ping? |
I'm currently recovering the setup I used to test this. I think I remember it had something to do with the resulting lease file in case of DHCP (that will be used after the initrd stage too). |
After doing some tests, I can confirm that
|
Hi, any progress on this? I'm reworking the NetworkManager dracut module to run as a systemd Maybe the dbus module could be a separate PR, so that it can be |
This commit changes how NM is started inside the initramfs. Instead of synchronously running NM from the initqueue hook in the special --configure-and-quit=initrd mode, start it from a systemd service. This has multiple advantages. First, we no longer need to run NM in a special mode that requires additional testing and maintenance. NetworkManager works exactly as in the real root. Also, now NM runs with D-Bus support and therefore its API can be used by other modules. This open the possibility, for example, to integrate nm-cloud-setup to automatically configure networking in the initramfs based on cloud metadata. This commit also enables the NetworkManager dispatcher service, that allows to run shell scripts when an interface state changes. In this way, we can call the various dracut hooks (online, netroot) as soon as one interface gets activated instead of waiting that all interfaces were configured (as the current implementation does). Requirements for this commit are: - the D-Bus dracut module submitted at: dracutdevs#544 dracutdevs#900 - the systemd-hostnamed dracut module submitted at dracutdevs#895 , which allows NM to change the hostname via D-Bus through hostnamed
c5d73f5
to
f3588a9
Compare
@bengal Sorry for the slow progress. I've done some testing, addressed (most of) your concerns and will be doing some more testing tomorrow, before merging this. |
a1b5fc5
to
864a525
Compare
864a525
to
9cbebc6
Compare
Follow-up to try to test this module - #2117 |
This introduces support for wicked as network management module.
Todo: