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
Chris
[1] https://www.archlinux.org/packages/community/any/cloud-init/
[2] https://git.launchpad.net/cloud-init/commit/?id=5d5a32e039782ce3e1c0843082f…
[3] https://github.com/archlinux/arch-boxes/commit/9d9f04f9618367e2af8d92bef2d5…
Hi All,
Today we have another DevOps meeting at 20:30 UTC or in your own
timezone visit:
https://time.is/compare/2030_27_Feb_2020_in_UTC
Since I didn't get any feedback on topics yet, I propose to hold a debug
session on the terraform situation and discuss mailman 3.
--
Jelle van der Waa
Hi All,
Tommorow we have another DevOps meeting at 20:30 UTC or in your own
timezone visit:
https://time.is/compare/2130_13_Feb_2020_in_UTC
The topics for the meeting are:
* AUR progress
* Keycloak progress
* Rsync.net offsite backups
* Ansible testing
--
Jelle van der Waa