Uploading to cloud platforms: DigitalOcean

[dustymabe]

This is part of #146 and tracks the work/discussion around uploading to DigitalOcean.

[bgilbert]

I expect our approach will be similar to CL: we'll publish signed OS images for DO, and DO will automatically import them.

[bgilbert]

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.

[jlebon]

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 #395? Or is it a separate track for uploads initiated from DO itself?

[bgilbert]

There are two separate tracks:

• Interim: publish artifacts for users to upload on their own. As Image for DigitalOcean #395 (comment) points out, we'll want to compress the artifact with gzip or bzip2 for compatibility with the DO API.
• Long-term: publish artifacts for DO to consume automatically. I think this will likely be the same artifact as above (might as well continue using gzip/bzip2 rather than artificially breaking users' ability to create a custom image from it) but will need additional support for non-DHCP network configuration.

[bgilbert]

The next testing and stable releases should include a DigitalOcean artifact (qcow2.gz) that users can upload and use as a custom image.

[jlebon]

Re. the DHCP issue, see discussions in #71, esp. #71 (comment).