CI-users September 2022

ci-users@lists.centos.org

2 participants
6 discussions

Changes on CentOS CI and next steps
by Camila Granella 02 Dec '22

02 Dec '22

*TL;DR: CentOS CI is going hardwareless and if you wish your project remains using it, we need your opt-in by August 2022. There is a Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022> session happening on Thursday, June 17th, that will explain further technical details. * Hello everyone, As many of you know, since the beginning of this year we have been reevaluating the future of CentOS CI, as currently the hardware being used for it is out of warranty. This is due to the fact that CentOS CI came from community donations of hardware which were maintained in a best effort manner by our team. With no warranties, when the physical machine dies we have no means to replace it. Right now though, our hardware, due to a lack of warranty, will not be moved with the upcoming data center changes due to data center requirements to have in warranty hardware for supportability. We decided to take this opportunity to modernize our current infrastructure, pushing it to a hybrid cloud environment. Duffy CI will become the main tool from now on, so that we can support the CI workflow and best practices on cloud and for this reason, the current hardware infra will no longer be available soon. However, as an effort to continuously provide resources and support CI best practices for projects, our team is adapting Duffy CI so that we can maintain most of the characteristics of our current, physical-based offering. At the technical level, what does that mean for you, CI tenants? - A new Duffy API service will replace the existing one: while it will be running in compatibility/legacy mode with the previous version, you will need to adapt your workflow to the new API, but more details below - 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) - We will keep a (very small) Power9 infra “on-premise” (AWS does not support ppc64le) for the ppc64le tests (available through a dedicated VPN tunnel) - The existing OpenShift cluster will be also decommissioned and a new one (hosted in AWS, so without an option to run kubevirt operator nor VMs) will be then used (you will have to migrate from one to the other) 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. Worth knowing that not opting in means that your API key will not be migrated and so all your requests to get temporary/ephemeral nodes will be rejected by the new Duffy API. The maximum decommission deadline of the current hardware infrastructure is December 12th, 2022 and the new Duffy CI will go live in August 2022, so please, complete your migration process by the end of CY22. Reminders of deadlines and of the opt-in requirements will be sent monthly, but your confirmation of opt-in is required by August 2022. When approaching December, reminders about deadlines frequency will increase so that we can ensure effective communication throughout the process. Here are the steps in which we will migrate CI Infra: Phase 1 - Deploy Duffy V3 (August 2022) - Deploy in legacy/compatibility mode, so existing tenants (that opted in !) can still request duffy nodes the same way (like with 'python-cicoclient') : no change at tenants side, and exactly same hardware for tests (transparent migration) - New Duffy API endpoint becomes available, and tenants can start adapting their workflows to point to new API (new ‘duffy-cli’ tool coming, with documentation) - Bare metal and VMs options will be available already through the new API (x86_64, aarch64, ppc64le) Phase 2 - Hybrid Cloud (October 2022) - Legacy/compatibility API endpoint will handover EC2 instances instead of local seamicro nodes (VMs vs bare metal) - Bare metal options will be available through the new API only - Legacy seamicro and aarch64/ThunderX hardware are decommissioned - Only remaining "on-premise" option is ppc64le (local cloud) Phase 3 - Decommission (December 2022) - Legacy/compatibility API deprecated and requests (even for EC2 instances) will no longer be accepted - All tenants that opted in will be using only EC2 for aarch64/x86_64 and on-premise cloud for ppc64le OpenShift new deployment planning and timeline To be defined (deadline for planning and timeline: end of June 2022) Do not hesitate to reach out if you have any questions. It is worth knowing that there will be a dedicated session about the Future of CentOS CI infra at the next CentOS Dojo happening on June 17h (check Dojo Summer 2022 <https://wiki.centos.org/Events/Dojo/Summer2022>). That session will be recorded and then available on Youtube but if you have any questions. Feel free to join the CentOS Dojo and reach out to us! Best regards, -- Camila Granella Associate Manager, Software Engineering Red Hat <https://www.redhat.com/> @Red Hat <https://twitter.com/redhat> Red Hat <https://www.linkedin.com/company/red-hat> Red Hat <https://www.facebook.com/RedHatInc> <https://www.redhat.com/>

9 20

Disabling dnf execution in background on an EC2 bare metal node
by Anoop C S 28 Nov '22

28 Nov '22

Hi, Post migration to new Duffy API we started noticing the following RPM error intermittently on bare metal nodes reserved from EC2 pool: . . . Running transaction check Waiting for process with pid 2881 to finish. Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction RPM: error: db5 error(-30969) from dbenv->open: BDB0091 DB_VERSION_MISMATCH: Database environment version mismatch RPM: error: cannot open Packages index using db5 - (-30969) RPM: error: cannot open Packages database in /var/lib/rpm The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Could not run transaction. . . . Especially the "Waiting for process with pid 2881 to finish." indicates some DNF operation in background which may or may not conflict with current DNF execution. With the help of others I got to know about a cloud-init service performing `dnf update` to cope with the very old AMI image with which it is provisioned. Please note that nodes are already marked ready in the pool before `dnf update` kicks in. Therefore I put forward a suggestion to disable `dnf update` as part of cloud-init service such that it does not interfere with other DNF operations done after the node is reserved by a tenant. Please feel free to correct me in any of the details mentioned above and let me know your thoughts. Thanks, Anoop C S.

3 9

CentOS CI infra changes: retiring ci.centos.org legacy jenkins
by Fabian Arrotin 03 Oct '22

03 Oct '22

as a FYI message : the legacy Jenkins server (initially shared instance between CI tenants) and available behind https://ci.centos.org will be decommissioned and powered off next week. It's not used anymore and was just put online with a notification about shutting it down and pointing to relevant ticket template to ask to be migrated to openshift (2 years ago) As we're also decommissioning other part of the CI infra, we'll also just delete that one from and also remove A record from public DNS (actually pointing to haproxy in front) related ticket: https://pagure.io/centos-infra/issue/931 Kind Regards -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 1

CentOS CI infra changes: Phase 2 approaching
by Fabian Arrotin 20 Sep '22

20 Sep '22

Hi , Reminder (see https://lists.centos.org/pipermail/ci-users/2022-June/004547.html) that we're approaching October 2022 and so Phase 2 of our move for CentOS CI infra. That means that on Monday October 3rd, we'll remove the seamicro pools and tenants still using the legacy API endpoint (that will also disappear end of this year in Phase 3 !) will get now EC2 instances transparently, instead of Seamicro bare-metal nodes. Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

infra outage : openshift (aka ocp.ci cluster)
by Fabian Arrotin 15 Sep '22

15 Sep '22

We are aware of an issue with the openshift cluster running CI workload. David is investigating the root cause as it's actually stuck between update/upgrade steps. We'll keep you informed on this list for status update[s] -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 1

Scheduled service migration : artifacts.ci.centos.org
by Fabian Arrotin 05 Sep '22

05 Sep '22

As announced some months ago, we are moving all CI infra components to new infra (mostly AWS) WRT Duffy api service itself, phase 1 was completed earlier this month (August) and phase 2 will be announced for October. Another service we need to migrate is https://artifacts.ci.centos.org, which is the next service we'll migrate next week. Migration is scheduled for """"Monday September 5th, 6:00 am UTC time"""". You can convert to local time with $(date -d '2022-09-05 06:00 UTC') The expected "downtime" should be really small, as it's will be just pointing DNS CNAME record to new host, and eventually (see below) last rsync between hosts. Worth knowing that CI tenants using that service in the past were relying on direct rsync access (tcp/873 and available only internally in dedicated CI VLAN) with a rsync secret. Due to the service being now publicly available on AWS, we decided to just disable plain rsync but allow rsync over ssh (or sftp/scp if you want), reusing your existing project keypair. More details available at https://sigs.centos.org/guide/ci/#artifacts-storage Don't forget to update your script for next monday or you'll not be able to push to the new storage server ! PS: while we consider all data "ephemeral" (and so to be discarded as there is also no backup at all for that temporary hosting solution), we can though migrate your existing data from old to new server. For that, please "opt-in" in the existing ticket so that we can keep track of projects we need to migrate. See ticket https://pagure.io/centos-infra/issue/906 Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users September 2022