-
Notifications
You must be signed in to change notification settings - Fork 59
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
Add udev rules and scripts to support specific clouds #104
Comments
this looks like something we should do for all of fedora (i.e. add udev rules for various clouds). It looks like the
and Container Linux has various rules as well: https://github.com/coreos/init/tree/master/udev/rules.d @sgallagher do you know of the best place to put a bunch of rules like this? |
@dustymabe I don't know the answer to that, unfortunately. It would probably be best to mail devel@lists.fedoraproject.org and see what you get there. |
Retitled bug to generalize to other clouds. |
proposed text for devel list email:
will send it tomorrow unless anyone objects |
Maybe clarify that we're not shipping cloud-init either? LGTM otherwise. |
Done.. Started the devel list discussion here. |
seems like the one suggestion we got was to maybe try to get them into the udev rules systemd carries. Anyone opposed to trying that route? |
opened: systemd/systemd#11532 to discuss with systemd team |
@bh7cw can you pick this up? |
The script is from Container Linux: coreos/fedora-coreos-tracker#104 (comment), I changed it and tested to make sure it works on fcos.
a peripheral dependency was discussed today related to private bug for BZ#1817209 |
Check also this PR: coreos/fedora-coreos-config#2350 where we are adding GCP udev rules in our overlay. We also have a bug open to request those rules to be added as a subpackage to the Ultimately we'd like to get all these rules centralized in systemd and the various clouds working together there to maintain them. See systemd/systemd#11532 |
This is work coming out of #66. From various conversations, AWS does not require a cloud agent and the only thing that is needed is the following udev rules + script.
coreos/init#268
The text was updated successfully, but these errors were encountered: