Open jsjiang opened 7 months ago
Related tickets: Update EZID to use N2T alias #581 Stop proc-binder job #563
Load tests findings:
Request statistics (10 users, top: minter only, bottom: minter + resolver, RPS decreased from 8.6 to 6.5)
Response time (10 users, top: minter only, bottom: minter + resolver, 50%ile (ms) increased from 780 to 960)
@ashleygould Can you provide detailed information on DNS name change. Thank you!
Tickets for DNS cutover:
Verify N2T functionalities after go-live: ref ticket
Check logs in OpenSearch for
The production implementation of the EZID/N2T Resolver Refactoring is planned on Mar 12 and 13. The EZID ARKs will be resolved by EZID with this migration. So there is no need to send ARKs to N2T anymore. However we still need to keep the EZID updating N2T workflow to support rollback of N2T migration. Modify EZID to support N2T migration.
ok: cron hitrnt ids-n2t2-dev.n2t.net
email to the Slack n2t channelNAAN registry updated
email to the Slack n2t channelpfxsync_update
script on the legacy n2t-stage instance