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

Provisioning: Add Oracle Cloud Infrastructure #652

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

travier
Copy link
Member

@travier travier commented Jul 10, 2024

Initial documentation to setup FCOS on Oracle Cloud Infrastructure.

See:coreos/fedora-coreos-tracker#414

@travier
Copy link
Member Author

travier commented Jul 10, 2024

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

----
source_image"fedora-coreos-qemu-image-name.qcow2"
image_name="fcos-oraclecloud.qcow2"
./covert-image.sh "${source_image}" "${image_name} oraclecloud
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I used openstack as a workaround until we get support in order in Ignition.
This uses the legacy IMDS endpoint (v1) so it must not be disabled when creating the image.

@jlebon
Copy link
Member

jlebon commented Jul 10, 2024

I'm sure you've seen this, though note that bare metal and VM shapes have different requirements: coreos/fedora-coreos-tracker#414 (comment). 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
Copy link
Member Author

travier commented Jul 11, 2024

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.

@travier travier force-pushed the main-prov-oraclecloud branch 2 times, most recently from 00e785b to e2daba8 Compare July 11, 2024 16:17
@jlebon
Copy link
Member

jlebon commented Jul 11, 2024

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 travier force-pushed the main-prov-oraclecloud branch 3 times, most recently from f6c9b86 to 7eef04d Compare July 16, 2024 10:11
@travier
Copy link
Member Author

travier commented Jul 16, 2024

Based on top of #654 for convenience as its likely to be merged earlier.

Copy link
Member

@jlebon jlebon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for writing this up!

.QEMU to Oracle Cloud Infrastructure image conversion script
[source, bash]
----
#!/bin/bash
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Definitely would be nice to just stick this in a container image, but there's overhead there too in maintenance.

AsciiDoc supports including files in multiple documents. That would allow us to define this script just once to make it easier to maintain here. (And I guess make the plaform ID be another parameter.)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agree that it would be nice to find a good place for this script.

@travier travier force-pushed the main-prov-oraclecloud branch 3 times, most recently from 3fa6537 to 91d55f5 Compare July 17, 2024 16:22
@michael-grundmann
Copy link

michael-grundmann commented Jul 19, 2024

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
Copy link
Member Author

travier commented Jul 19, 2024

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: coreos/fedora-coreos-tracker#414 (comment)

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.

Initial documentation to setup FCOS on Oracle Cloud Infrastructure.

See:coreos/fedora-coreos-tracker#414
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants