Sprint After sprint Planning zigo set up CI in casulana We could not use it - ownership problems? Who is building thing. Nt everything is pluggedin Infomaniak has external API - should we use it We should have fuller CI ASAP Monitoring of processes, fixing it fter notiing that something is broken Still much to do Bastian knows most of it, is most active We need to spread this knowledge We suck at communicating progress and who is working on it How we publish images to OpenStack Do we push it (and thus need to store credentials - safelu!) or use RSS feed from image finder, possibly even signed RSS, so they can pull And this way we don't even need to store credentials Hosting on Image Finder Initially some VM, on *.debian.net Then after it works, we might talk to DSA to host on D infrastructure, and on *.debian.org New feature in Image Finder - webhook telling OpenStack providers to get image Or push those images, just like we do for Big3 zigo is still single point of contact to Open Stack world Account status Image building People are asking for Buster images I guess the most problems are with AWS - no official account yet Some scripts are still missing to have automatic (or less manual) publishing images If it takes more time, we'll publish Buster images through old account (jeb's one) casulana - big machine used to build images patterson - publishing box. Huge bandwidth, we host all big things there Other (Azure, GCE) have good accounts (we hope) Sprint planning Till now in Seattle Now plan 14-16 Oct, Boston, MIT Meeting rooms are already booked :-) We want to have Digital Ocean involved. Other Open Stack providers also OpenStack - build images using FAI Bastian has FAI code to build no-cloud images (just basic disk image) need for testing zigo wants to test full chain from patterson no building from local machine or laptop Great question: we're building images, but where? Where they finish? SoC Main program (code) is finished We need to have some users/auth/API keys to avoid spamming and DoSby eager uses of sevice Hosting: zigo on infomaniak Documentation is in wiki Workflow, communication, team interactions Single people doing much of work serpent will try to organize monthly meetings IRC Steve resigns as delegate, other responsibilities Docker images Vagrant images For now Docker image is built by Paul Tag Debian image on DockerHub is not official (not according to our definition) We don't have official policies for Vagrant and Docker Who control Vagrant and Docker repositories? We (as a team) should take care What is special about Vagrant image? How it differs from just dd if=/dev/sda after installing Debian? Can Vagrant use our no-cloud image Current Vagrant image is at least 6 months old (no updates for many months) It also has hard-coded SSH keys https://github.com/hashicorp/vagrant/tree/master/keys(Insecure Keypair) Vagrant is a bit like VM to be run on own machine, not in public cloud vagrant has post-provision phase It uses this hard-coded key to install new software (a bit like Ansible with SSH scripts?) It's supposed to delete this initial hard-coded key and then generate new key during first startup Other images, like rapsbian? We need more automation and process FAI idea is that everyone can add to configuration space, and build own images vagrant mostly use virtualbox image, or lxc image, not qemu image Vagrant images are hosted on hashicorp cloud, but they can also hosted on external site, take centos for example, http://cloud.centos.org/centos/7/vagrant/x86_64/images/ We should host vagrant images on cdimage.d.o Can we have more arch, for nocloud images(qemu images)? (FYI zigo: you can download the images generated by the GitLab CI jobs directly from Salsa, no need to authenticate or to first download and extract the zip file; perhaps that can help you start testing on OpenStack without images having to be pushed to casulana/patterson?) - Head to https://salsa.debian.org/cloud-team/debian-cloud-images/pipelines, locate the one you want - Expand the jobs list in the first stage of the build - Choose the relevant job, e.g. "generic buster amd64 build official" - Under "Job Artifacts" on the right, click browse - You then have links to directly download the assets (you may need to click through first) - e.g. https://salsa.debian.org/cloud-team/debian-cloud-images/-/jobs/231053/artifacts/raw/debian-buster-generic-amd64-official-20190722-422.tar.xz