Open dustymabe opened 5 years ago
I expect our approach will be similar to CL: we'll publish signed OS images for DO, and DO will automatically import them.
As an interim step, we could publish images for users to upload on their own. The DO custom image mechanism includes DHCP support, so we could sidestep the networking issue for the time being.
I expect our approach will be similar to CL: we'll publish signed OS images for DO, and DO will automatically import them.
Hmm, doesn't it follow from this comment that we do need to provide images in a format digestible by their API as requested in https://github.com/coreos/fedora-coreos-tracker/issues/395? Or is it a separate track for uploads initiated from DO itself?
There are two separate tracks:
The next testing
and stable
releases should include a DigitalOcean artifact (qcow2.gz
) that users can upload and use as a custom image.
Re. the DHCP issue, see discussions in https://github.com/coreos/fedora-coreos-tracker/issues/71, esp. https://github.com/coreos/fedora-coreos-tracker/issues/71#issuecomment-438748290.
This is part of https://github.com/coreos/fedora-coreos-tracker/issues/146 and tracks the work/discussion around uploading to DigitalOcean.