Image for DigitalOcean

[tyranron]

Similar to #355

I have recently played with Terraform, DigitalOcean and FCOS, without success, however. DigitalOcean doesn't provide prepared FCOS image at the moment, nor I could create custom DO image using any link from stable.json. The problem is quite nasty: whille DO accepts qcow2/raw formats, it doesn't accept them packed into .xz archive, only gzip/bzip2 😕

Also, I didn't found any capabilities to launch DO droplet in "rescue mode" to install FCOS via coreos-installer.

It would be very nice to have at least DO-compatible images at download page to use them as custom ones.

Thank you!

[lucab]

Cross-referencing: #151

[lucab]

Last status update was at https://github.com/coreos/fedora-coreos-tracker/blob/52cb105c15aadd9b1cf70fc8b55fe91f49f74431/Design.md#digitalocean. I am not aware of any changes since then.

[bgilbert]

Thanks for the report. I've added #151 (comment) suggesting that we provide custom images to use with DHCP while waiting for proper DigitalOcean networking support to land in FCOS. I suspect we'll continue shipping xz-compressed images though; the expectation is that users will uncompress them before uploading.

Closing this as a duplicate of #151.

[tyranron]

@bgilbert thanks for the clarification.

I suspect we'll continue shipping xz-compressed images though; the expectation is that users will uncompress them before uploading.

This, unfortunately, doesn't automate well. DO's POST /v2/images supports only specifying files via URL, it doesn't allow in-place multipart uploading or something like that. And while the downloading and re-compressing is not a big deal for automation tools like Terraform, the uploading to some place to have that link is, actually.

I'm not against xz-compressing, but is it possible to provide alternatives, or, at least one raw uncompressed image?

[bgilbert]

This, unfortunately, doesn't automate well. DO's POST /v2/images supports only specifying files via URL, it doesn't allow in-place multipart uploading or something like that.

Ah, thanks for the clarification. Yes, we could special-case compression for this artifact. Noted in #151 (comment).