On 22/06/2022 18:45, Miroslav Vadkerti wrote:
Hi,
On Wed, Jun 22, 2022 at 5:39 PM František Šumšal <frantisek@sumsal.cz mailto:frantisek@sumsal.cz> wrote:
Hello! After reading & discussing the recent news regarding the move to AWS, I wonder if it would be possible to provide Fedora Rawhide images along with the C8S and C9S ones (and maybe active stable Fedora releases as well).
Fedora Rawhide AWS images are available on Fedora's AWS account, that we also use to test CentOS Stream:
❯ aws ec2 describe-images --filter Name=name,Values="Fedora-Cloud-Base-Rawhide*" | jq -r '.Images | .[] | .Name' | sort | tail -4 Fedora-Cloud-Base-Rawhide-20220621.n.3.aarch64-hvm-us-east-2-gp2-0 Fedora-Cloud-Base-Rawhide-20220621.n.3.aarch64-hvm-us-east-2-standard-0 Fedora-Cloud-Base-Rawhide-20220621.n.3.x86_64-hvm-us-east-2-gp2-0 Fedora-Cloud-Base-Rawhide-20220621.n.3.x86_64-hvm-us-east-2-standard-0
This is what we use in Testing Farm https://docs.testing-farm.io/.
Great, so we now know that they exist and we can investigate options to start deploying these ....
A bit of background: In the systemd project we have several jobs with utilize Vagrant to run an Arch Linux VMs, in which we run tests alongside the C8S/C9S jobs, to cover issues with the latest-ish kernel and other software, and to also hunt down security issues with the latest versions of ASan and UBSan. However, all this is held together by a lot of duct tape and sheer will power, and in the end it requires an EC2 Metal instance to run, due to the additional level of virtualization. If we were able to provision Rawhide instances directly (which should help us achieve the same goal as the Arch Linux VMs we currently use), that could, in theory, allow us to drop the requirement for Metal instances completely.
Do you need some direct access to AWS? We provide testing on AWS instances as a service.
Well .. you know that it's exactly what Duffy and newer CI infra would be doing , so overlapping solutions .. What I find amusing is that we now seem to have two solutions providing same thing, using the *same* AWS sponsored account, and with common projects ...