Hi Martin,
Apologies for the delay in response but access to /dev/kvm is not something we want to support in the new setup. Sorry we can't provide this for you but if your workflow can change to fit in our infrastructure we would welcome you.
Thanks, Mark
On Mon, Jul 11, 2022 at 8:05 AM Martin Pitt mpitt@redhat.com wrote:
Hello Camila,
Camila Granella [2022-06-15 8:49 -0300]:
We will transition to AWS EC2 instances for the aarch64 and x86_64 architectures by default, with a (limited) option to request “metal” instances for projects requiring virtualization for their tests (like KVM/vagrant/etc)
Does that apply to OpenShift as well? I.e. can pods be placed onto a metal cluster (with /dev/kvm access) like they can on the current infra?
With that being said, tenants can start preparing for the changes to
happen
with the maximum deadline of the end of December 2022 wherein at this point, Duffy API legacy mode will be removed. You are required to opt-in
if
you and/or your team want to use Duffy CI. Projects will only be migrated if they reply to this email confirming that they wish to proceed.
Our team currently uses the "frontdoor" project on console-openshift-console.apps.ocp.ci.centos.org, where we run part of our CI. We strictly depend on /dev/kvm access in our pods [1], so if it's possible to keep that, I'd like to opt into the new infra. Otherwise, I'll look for another place (I'm currently experimenting with PSI, but this still has a lot of problems).
We don't use "duffy" at all, just plain k8s/OCP.
Thank you!
Martin
[1] the kubevirt operator does not suffice, and nested virt is usually too slow and brittle
CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users