Implement Oracle Cloud Infrastructure support

[alaviss]

Implementing a new supported platform

Platform request: #414

During Development

Create PRs addressing the following:

• Ignition (PR)
  • Add userdata fetch
  • If the platform supports it (unlikely), add userdata deletion Not supported by platform.
• Afterburn (PR)
  • (Cloud Only) Add relevant attributes
  • (Cloud Only) Add SSH key support if available
  • (Cloud Only) Add hostname support if available
  • (Cloud Only) Add check-in if needed (unlikely) Not required/supported.
• stream-metadata-go (PR)
  • Add platform to the Media struct in release/release.go
  • Add supporting code for new platform to toStreamArch func in release/translate.go
  • (Cloud Only) Cloud Images need to have an Images field
• (Cloud Only) stream-metadata-rust (example PR)
• fedora-coreos-tracker - metadata: add examples for oraclecloud #1985
  • Update the metadata for the new platform
• coreos-assembler (PR)
  • Updated cmd-generate-release-meta
  • cosa osbuild <platform> works
• fedora-coreos-config (PR)
  • Add a stanza to platforms.yaml if the system should use a serial console, or both serial and graphical consoles
• fedora-websites-3.0 (MR)
  • Add friendly name for platform to components/utilities/FpDownloadItem.vue
  • Add artifact to pages/coreos/download.vue
• fedoraproject.org CMS (MR)
  • Possibly add logo to content/editions/coreos/home.yml
• fedora-coreos-browser (PR)
  • Add a list element for new platform in browser/index.html
• build pipeline (PR)
  • Add platform to the list found in config.yaml for building the new artifact
• fedora-coreos-docs (PR)
  • Add a provisioning-<platform>.adoc that walks through how to setup the new platform
  • Add an entry in the modules/ROOT/nav.adoc that points to new documentation

At Release

1. Merge upstream changes and put out a release:
   • Ignition (2.22.0)
   • Afterburn (5.9.0)
2. Merge metadata changes:
   • stream-metadata-go
   • stream-metadata-rust
   • fedora-coreos-tracker
   • fedora website
   • fedoraproject.org CMS
   • fedora-coreos-browser
3. Release updated components
   • Create and follow release checklist for stream-metadata-go
   • Ensure that Dependabot has PRed stream-metadata-go into fedora-coreos-stream-generator and coreos-assembler. Merge the update PRs.
     • This can be triggered manually by navigating to fedora-coreos-stream-generator's Dependabot and coreos-assembler's Dependabot respectively, then clicking "Check for updates".
       • This might need to be done a few times, as Dependabot might not pick up tag changes for a few attempts after initial tagging.
   • Create and follow release checklist for fedora-coreos-stream-generator
4. Merge the following changes:
   • coreos-assembler
5. Wait for updates made to coreos-assembler to be propagated to latest container
   • Download latest version of coreos-assembler container. Verify platform support functionality.
6. Merge changes for:
   • Build pipeline
7. Wait for new images to reach stable then merge documentation.
   • fedora-coreos-docs merged

[alaviss]

I'm interested in working on Ignition and Afterburn on this. What should be the shortname for this platform? I noticed that oraclecloud was presented as an option in prior discussions, but cloud-init uses the name oracle.

[jlebon]

Thanks! I think oraclecloud would be better.

fedora-coreos-docs (coreos/fedora-coreos-docs#652)

Not sure that PR qualifies. It's currently using the OpenStack platform instead, and requires mutating the QEMU image. With proper support, it would instead be a dedicated image with the right platform ID.

[alaviss]

I would like to discuss this in the next meeting, can this issue be tagged meeting?

[jlebon]

I would like to discuss this in the next meeting, can this issue be tagged meeting?

Sure thing, added. And thanks for your contributions!

[tlbueno]

Regarding the ignition/afterburn release, I will check with maintainers if there is a scheduled one and explain the needs for it.

[alaviss]

As discussed in today FCOS community meeting, I've converted this issue into a top-level platform implementation checklist.

[tlbueno]

Regarding the ignition/afterburn release, I will check with maintainers if there is a scheduled one and explain the needs for it.

@alaviss I talked with the ignition and afterburn mainteners and we are going to create a release for both. I will be the one responsible for it and I just need to get some permissions to be able to do it. I am expecting work on that next week. I will keep you posted.

[dustymabe]

@alaviss can we add a OCI logo to the website too?

Something like this.

/me notes we should update this template to do ^^