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 getting started on Vultr tutorial #71

Merged
merged 1 commit into from
Jul 14, 2020
Merged

provisioning: Add getting started on Vultr tutorial #71

merged 1 commit into from
Jul 14, 2020

Conversation

dghubble
Copy link
Member

@dghubble dghubble commented May 8, 2020

  • Add Provisioning Fedora CoreOS on Vultr docs that shows uploading a snapshot image and creating an instance using the vultr-cli
  • Ignition config must include SSH authorized key setup

Related: coreos/fedora-coreos-tracker#355

@dghubble
Copy link
Member Author

dghubble commented May 8, 2020

I don't typically create instances via CLI, but I did test it out for this using my Vultr image (hosted elsewhere, pending FCOS pipeline publishing) and a small Ignition config with just an SSH authorized key setup. It provisioned and I'm able to login (with cloud firewall rule added).

Copy link
Member

@dustymabe dustymabe left a comment

Choose a reason for hiding this comment

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

LGTM - a few questions for my education.

modules/ROOT/pages/provisioning-vultr.adoc Show resolved Hide resolved
modules/ROOT/pages/provisioning-vultr.adoc Show resolved Hide resolved
@jlebon
Copy link
Member

jlebon commented May 8, 2020

We should probably hold this until it's actually downloadable from the getfedora.org page. (I added a corresponding checkbox in coreos/fedora-coreos-tracker#355).

* Add Provisioning Fedora CoreOS on Vultr docs that
shows uploading a snapshot image and creating an
instance using the `vultr-cli`
* Ignition config must include SSH authorized key setup

Related: coreos/fedora-coreos-tracker#355
@dustymabe
Copy link
Member

We should probably hold this until it's actually downloadable from the getfedora.org page

agree.

Thanks @dghubble - we'll merge this when the next round of releases comes out.

@dustymabe
Copy link
Member

hmm was just about to re-look at merging this but I still don't see vultr on the download page.

@dghubble
Copy link
Member Author

dghubble commented Jun 9, 2020

Vultr images show up in meta.json, but it seems a few more pieces are missing coreos/fedora-coreos-tracker#355 (comment)

@lucab
Copy link
Contributor

lucab commented Jul 14, 2020

The website is now showing Vultr artifacts: https://getfedora.org/en/coreos/download?tab=cloud_operators&stream=stable.

@lucab lucab merged commit 2a94126 into coreos:master Jul 14, 2020
@summatix
Copy link

Following the instructions here: https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-vultr/

I'm seeing the error: "Expected a raw disk image, but found: xz compressed data"

So the instructions may need to be updated a little (unless I'm misreading the instructions).

@lucab
Copy link
Contributor

lucab commented Jul 14, 2020

Ah yes, there is a decompress step missing. We can probably switch to use coreos-installer too, which can internally do the verify and decompress steps too.

@summatix
Copy link

summatix commented Jul 14, 2020

I see in the Vultr panel there is a new "Fedora CoreOS" server type option that requests for ignition content. So it seems like the Vultr team have added native support for Fedora CoreOS already.

Update: I can confirm that Vultr's native Fedora CoreOS option is working as expected. I am able to provision FCOS 32 with custom ignition.

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.

5 participants