On 28/07/2022 17:25, Vladimir Benes wrote:
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
Hi Vladimir,
As NetworkManager was marked as "opted-in", your existing API key was imported by Pedro in new Duffy DB.
Yes you'll need to adapt to new api *but* you have time, as there is a compatibility layer so our dns change next monday should be transparent for you : you'll just use new duffy endpoint but as it was before (so no new features), so that means that you'll still get the same seamicro bare-metal nodes as before.
As announced, we'll stop the compatibility api endpoint in december (phase 3) , while it will be adapted in October to only give you EC2 instances instead of existing seamicro bare-metal nodes.
So good news : you don't have to adapt your workflow for next week .. but don't forget to start looking at it ASAP though, and not wait for end of the year ;-)
Hope that it answers your question