clearlinux / micro-config-drive

An alternative and small cloud-init implementation in C
Other
46 stars 17 forks source link

Resolve config drive issue #43

Closed donnydavis closed 4 years ago

donnydavis commented 5 years ago

This PR is to create a udev rule that imports the FS_LABEL so udev can recognize config-2.

Resolves: https://github.com/clearlinux/micro-config-drive/issues/40

jascott1 commented 5 years ago

@ahkok Is this approach viable? Let me know if I can help.

donnydavis commented 5 years ago

@ahkok Do you think it would be best to have a rule that takes care of import and then seperate rules that handle the different cloud providers with proper options for each?

jascott1 commented 5 years ago

@ahkok Any updates?

ahkok commented 5 years ago

I've spent some significant time on this in the last 2-3 days. No resolution yet, unfortunately.

ahkok commented 4 years ago

Did we ever validate this properly? It looks like we need this in the end anyway for -native kernels and I might just include it in the bundle by default (the risk of double-parsing the config-2 file system is minimal).

We just need to know it actually functions.

ahkok commented 4 years ago

--user-data-once doesn't help if the SSH keys are in meta_data.json. We should figure out a way to solve that, too.

donnydavis commented 4 years ago

@ahkok If you need any help testing please lmk.

ahkok commented 4 years ago

This is now obsolete - we modprobe sr_mod to force any locally attached config-2 filesystem to appear explicitly in case it isn't found.