search

coreos / fedora-coreos-docs

Documentation for Fedora CoreOS
https://docs.fedoraproject.org/en-US/fedora-coreos/
Other
50 stars 121 forks source link

Provisioning: Add Oracle Cloud Infrastructure #652

Open travier opened 1 month ago

travier commented 1 month ago

Initial documentation to setup FCOS on Oracle Cloud Infrastructure.

See:https://github.com/coreos/fedora-coreos-tracker/issues/414

travier commented 1 month ago

Draft as it's not complete yet. I still need to figure out the networking section.

jlebon commented 1 month ago

I'm sure you've seen this, though note that bare metal and VM shapes have different requirements: https://github.com/coreos/fedora-coreos-tracker/issues/414#issuecomment-1795808614. Short-term, getting the VM shapes to work shouldn't be too much work. For the bare metal shapes, we could for now recommend using the bare metal installation flows, until we have "dual" support in the same image.

travier commented 1 month ago

Ah indeed, thanks for the pointer. So those docs would be only for VM shapes right now. I should update the list of shapes to select only those.

For Bare Metal shapes, maybe we should add the kargs directly to the image as part of the conversion step that we have right now as we don't produce oracle cloud specific images. Then we would have users upload this image and select the right shape for it.

jlebon commented 1 month ago

For Bare Metal shapes, maybe we should add the kargs directly to the image as part of the conversion step that we have right now as we don't produce oracle cloud specific images. Then we would have users upload this image and select the right shape for it.

I think that's fine for now, yeah.

travier commented 1 month ago

Based on top of https://github.com/coreos/fedora-coreos-docs/pull/654 for convenience as its likely to be merged earlier.

michael-grundmann commented 1 month ago

i tried your instructions, but it seems that the metadata endpoint used in afterburn is not available here:

Jul 19 12:42:30.959 WARN failed to locate config-drive, using the metadata service API instead Jul 19 12:42:30.966 INFO Fetching http://169.254.169.254/latest/meta-data/public-keys: Attempt #1 Jul 19 12:42:30.972 INFO Fetch failed with 404: resource not found

Instead i found it available here: http://169.254.169.254/openstack/latest/meta_data.json or here http://169.254.169.254/opc/v1/instance/metadata/ssh_authorized_keys

ist there a way to overide the metadata endpoint that is used by afterburn (i.e by kernel command line)?

travier commented 1 month ago

Thanks for giving it a try.

This is due to the fact that we re-use the openstack implementation as is for now which is not the long term plan: https://github.com/coreos/fedora-coreos-tracker/issues/414#issuecomment-596855759

This is why I've commented out all Afterburn mentions in the docs for now.

As far as I know, afterburn does not let you configure that on the kernel command line.