Hi all,
Last year, due to DC move, and so machines needed to be
reshuffled/reinstalled/moved/recycled/etc, we had to remove the ppc64le
architectures from the duffy pools.
While it wasn't a problem for most of you CI tenants (using almost
exclusively x86_64 - or eventually aarch64), some, like Kmods SIG, were
keen on having the ppc64le support added back in, as they also build
kernel and kernel modules for ppc64le.
It took some time (due to other higher priorities on the list) but we
have now the pool ready to be used ! :
```
for i in 9 10 ; do duffy client show-pool
virt-kvm-medium-centos-${i}s-ppc64le ; done
{
"action": "get",
"pool": {
"name": "virt-kvm-medium-centos-9s-ppc64le",
"fill-level": 2,
"levels": {
"provisioning": 0,
"ready": 3,
"contextualizing": 0,
"deployed": 0,
"deprovisioning": 0
}
}
}
{
"action": "get",
"pool": {
"name": "virt-kvm-medium-centos-10s-ppc64le",
"fill-level": 2,
"levels": {
"provisioning": 0,
"ready": 2,
"contextualizing": 0,
"deployed": 0,
"deprovisioning": 0
}
}
}
```
One thing to keep in mind (but it was already the case when we were
offering that from previous on-prem DC) : they don't have public ip
addresses at all, but once requested from openshift cico workspace, you
can still reach these directly.
If you want to consume from other environment, (like gitlab runner or
else), just use a small duffy x86_64 or aarch64 ec2 instance, as these
ones have the needed VPC info and tunnel to get to the provisioned
ppc64le instances
Let us know if something doesn't work for you but I just tested and it
was working fine
PS: the ppc64le have smaller specs :
- kvm guest
- Architecture: ppc64le , CPU(s): 4 , Model name: POWER9
(architected), altivec
- Mem : 16G
- block device: Virtio 10GB device
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
