On 23/08/2022 16:52, Evgeni Golov wrote: > Camila, > > Do you know where (roughly) the limit for metal is? Right now (in this > thread), I see three projects wanting/needing virtualization > capabilities and thus metal (systemd, networkmanager, foreman). > That means that, even if projects adjust their tests to run multiple > things on one metal host, there might still be at least three parallel > machines needed (or the projects will block each other, which would be > very unfortunate). > > Evgeni > If you look at actual status, we already have 10 metal nodes in parallel (and we can't provision more due to AWS lack of nodes in these zones). So yes, if each tenant can just ask for *one* metal node and adapt workflow so that they can run their ci jobs on top of that single metal node, that would (in theory) work ... It just needs some orchestration at the tenant jobs side -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0xA25DBAFB17F3B7A1.asc Type: application/pgp-keys Size: 12767 bytes Desc: OpenPGP public key URL: <http://lists.centos.org/pipermail/ci-users/attachments/20220823/c5f5c30e/attachment-0001.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/ci-users/attachments/20220823/c5f5c30e/attachment-0001.sig>