Please be advised that the CentOS CI Production Openshift cluster is due
for scheduled maintenance from 07:00 to 08:00 UTC on 2025-01-20. During
this period necessary updates will be applied to the cluster.
The upgrade is not expected to be service affecting, however there might
be periods of slight performance degradation (pods restarting on other
workers) during this maintenance period. We apologize for any
inconvenience that this may cause.
PS : We have already tested on staging cluster and it applied successfully.
We'd like then to start evaluating migrating to OCP 4.16 branch
Kind regards,
CentOS CI Infrastructure.
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi all CI tenants,
We got today a request to provide more powerful aarch64 ec2 instances
for duffy (https://pagure.io/centos-infra/issue/1576)
While I don't see a problem doing that, there are two ways to implement
this :
- either just change the ec2 instance type from c6g.2xlarge to
c6g.4xlarge or c6g.8xlarge and then let the pool being drained and
reprovisioned automatically with newer instance type (no change in
current workflow)
- or have a new duffy pool with limited number of provisioned instances
and using these more powerful ec2 instances. (so tenants willing to use
these ones would need to query a different pool name)
From a usage perspective, and fact that machines are pre-provisioned,
I'd like to implement option 2, so that nothing would impact the actual
pool and then propose another pool name for these other aarch64 machines
(both for c9s and c10s).
While AWS is sponsoring that infra, I'd like to keep "costs" at
reasonable level, and so not deploying for all machines that would have
an impact on "virtual budget" while tenants wouldn't even use the added
vcpus/memory.
Ideas, opinions, thoughts ?
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]