On Thu, 2022-07-28 at 15:03 +0200, Fabian Arrotin wrote:
On 27/07/2022 16:06, Fabian Arrotin wrote:
As previously announced in June (see https://lists.centos.org/pipermail/ci-users/2022-June/004547.html and also https://www.youtube.com/watch?v=aqgs-3NnRmA), we'll migrate existing Duffy API service to the new Duffy v3, starting with Phase 1 .
Probably a silly question, unsure if answered in the video above. Do we need to migrate our code from the old duffy to v3? Will the v2 version be doomed after 1st? I am just leaving for PTO and do not want to have the CI in silly state, so would be nice to tune it up over the weekend.
Thanks! Vladimir
Migration is scheduled for """"Monday August 1st 7:00 am UTC time"""". You can convert to local time with $(date -d '2022-08-01 07:00 UTC')
The expected API downtime will be under the 60 seconds (DNS TTL).
Worth knowing:
- new duffy api (in legacy mode) has currently less available
nodes, but that will be resolved during the day (see below)
- we'll have to wait ~6h (default maximum "lease" time for a test
node) to be able to let new duffy api reinstall older seamicro nodes and so be available in the new duffy v3 pool (transitioning from old to new duffy pool)
- currently running jobs will continue so to work, but when you'll
hit new duffy api endpoint (DNS switch) to "return nodes" it will just answer that session doesn't exist (new one) but it's safe to ignore
As soon as new duffy API is available you'll already be able to switch your workflow to new the Duffy API and so use the new features. Tenants/users documentation about how to interact with Duffy is available on https://sigs.centos.org/guide/ci/ (see the Duffy part of that documentation) That means that switching to EC2 nodes will be directly possible.
During the day we'll tune the duffy nodepool configuration based on usage metrics.
IMPORTANT remark : *only* projects/tenants that opted-in in the last 45 days are currently migrated (api and ssh keys), so if you haven't (yet), you can still opt-in, otherwise all your requests for duffy ephemeral nodes will be declined by new duffy api service next monday.
In case of troubles, both Pedro (nick phsmoura) and myself (nick arrfab) will be also present in the #centos-ci irc channel on irc.libera.chat the whole day.
Thanks for your understanding and patience.
on behalf of the Infra team,
One thing that we'll also do on that day is to ensure that cico-workspace image will be updated to have duffy client available . As we never received feedback for that image (see https://lists.centos.org/pipermail/ci-users/2022-June/004554.html) that means that ansible-core will be replacing ansible (no collection embedded in that image)
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab _______________________________________________ CI-users mailing list CI-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users