[arch-devops] cloud-images

Christian Rebischke Chris.Rebischke at archlinux.org
Sun Nov 3 17:42:07 UTC 2019

Dear devops team,

Recently I have pushed cloud-init back to [community][1], one Arch Linux
user did some improvements on the cloud-init codebase as well and they
are going to officially support arch linux with version 19.3[2].

Therefore I have added support for cloud-images to the arch-boxes
project[3]. These images are qcow2 images and are expected to be
installed in cloud-environments like Openstack.

The only thing what is missing is a way to distribute the images and
release them.

My current plan has been that I build and sign them locally and then
upload them to a web directory (This is the most secure way as
possible right now).

For this I need answers for a few questions:

1. Can I have a web-directory, where only I have access to?
2. Which key should I use to sign them? A new cloud-image signing key or
my personal key? (I think latter should be enough).
3. I expect to build them monthly like the ISOs, how many images do you
want to keep? My current assumption is that 1 year of image backup of
cloud-images (qcow2) only would cost us around 30-50GB.
4. Do we want to mirror the images?

Best greetings


[1] https://www.archlinux.org/packages/community/any/cloud-init/
[2] https://git.launchpad.net/cloud-init/commit/?id=5d5a32e039782ce3e1c0843082fe26260fa9273a
[3] https://github.com/archlinux/arch-boxes/commit/9d9f04f9618367e2af8d92bef2d5e5fc4da9843f
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://lists.archlinux.org/pipermail/arch-devops/attachments/20191103/8dbbae00/attachment.sig>

More information about the arch-devops mailing list