Skip to content
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

Open
Tracked by #95
mike-nguyen opened this issue Jan 8, 2019 · 12 comments
Open
Tracked by #95

Add udev rules and scripts to support specific clouds #104

mike-nguyen opened this issue Jan 8, 2019 · 12 comments
Assignees
Labels
cloud* related to public/private clouds jira for syncing to jira

Comments

@mike-nguyen
Copy link
Member

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

@dustymabe
Copy link
Member

this looks like something we should do for all of fedora (i.e. add udev rules for various clouds). It looks like the cloud-init package has some for azure:

[vagrant@vanilla-f29 ~]$ rpm -ql cloud-init | grep rules.d
/lib/udev/rules.d/66-azure-ephemeral.rules

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 dustymabe added the cloud* related to public/private clouds label Jan 9, 2019
@sgallagher
Copy link

@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.

@bgilbert bgilbert changed the title aws: add nvme ebs udev rules and script Add udev rules and scripts to support specific clouds Jan 16, 2019
@bgilbert
Copy link
Contributor

Retitled bug to generalize to other clouds.

@dustymabe
Copy link
Member

proposed text for devel list email:

Subject: where to put udev rules for to support cloud providers

context: https://github.com/coreos/fedora-coreos-tracker/issues/104

There are some udev rules that support various hardware on different cloud providers
that we'd like to provide as part of Fedora CoreOS so it can operate on those platforms
as expected. In the past these udev rules could be provided by the cloud-init package
or by the cloud specific agent for a particular cloud provider. In Fedora CoreOS we are
attempting to not ship cloud agents but we'd like to ship various bits like these udev
rules. The question is: where (what package) should provide these rules?

One thing to think about is that we think this work would benefit the Fedora Cloud Base
image as well, so we are trying not to make it specific to Fedora CoreOS.

- Should they go into a `fedora-release-coreos` and `fedora-release-cloud` package?
    - Both of these share the same srpm
- Should they go into a `cloud-platforms` package where we could possibly put other
  cloud supporting bits as well?

Thanks
Fedora CoreOS Team

will send it tomorrow unless anyone objects

@bgilbert
Copy link
Contributor

In Fedora CoreOS we are attempting to not ship cloud agents

Maybe clarify that we're not shipping cloud-init either? LGTM otherwise.

@dustymabe
Copy link
Member

In Fedora CoreOS we are attempting to not ship cloud agents

Maybe clarify that we're not shipping cloud-init either? LGTM otherwise.

Done.. Started the devel list discussion here.

@dustymabe
Copy link
Member

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?

@dustymabe
Copy link
Member

opened: systemd/systemd#11532 to discuss with systemd team

@dustymabe dustymabe self-assigned this Feb 1, 2020
@dustymabe dustymabe added the jira for syncing to jira label Feb 1, 2020
@dustymabe dustymabe assigned darkmuggle and unassigned dustymabe Jun 4, 2020
@darkmuggle darkmuggle assigned bh7cw and unassigned darkmuggle Jun 4, 2020
@darkmuggle
Copy link
Contributor

@bh7cw can you pick this up?

bh7cw added a commit to bh7cw/fedora-coreos-config that referenced this issue Jun 17, 2020
The script is from Container Linux: coreos/fedora-coreos-tracker#104 (comment), I changed it and tested to make sure it works on fcos.
@davdunc
Copy link
Contributor

davdunc commented Jul 27, 2020

a peripheral dependency was discussed today related to private bug for BZ#1817209

@ravanelli
Copy link
Member

ravanelli commented Apr 13, 2023

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 google-compute-engine-guest-configs SRPM, which is an intermediate solution.

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

@jlebon
Copy link
Member

jlebon commented Feb 15, 2024

This seems like a duplicate of e.g. #601, #1165, #1122. Do we want to close this out or repurpose it to track the "let's put all those rules into a shared space"?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud* related to public/private clouds jira for syncing to jira
Projects
None yet
Development

No branches or pull requests

9 participants