search

bcgov / DITP-DevOps

Digital Identity and Trust Program Team's DevOps Documentation Repository
Apache License 2.0
2 stars 5 forks source link

Deploy instances of the Aries Mediator Service with persistent queue support #113

Closed WadeBarnes closed 1 month ago

WadeBarnes commented 10 months ago

When testing, please use the following instances. The -pq instances are being scaled down and decommissioned as the following instances are migrated over to use the persistent queue.

-pq instances - Being scaled down and decommissioned as the above instances are migrated over to use the persistent queue.

Current State:

Next Steps:

jleach commented 10 months ago

A few of us have been testing this for weeks now with no issues. I think its safe to carry on promoting this to prod.

WadeBarnes commented 7 months ago

We're at a point were we want to migrate from the existing (non-persistent) mediator instances to the new instances backed by the persistent queue. I'd like to migrate the URLs to the new instances, but that will require some co-ordination; different instance equals different invite.

@cvarjao, @jleach, Looking for how you'd like to proceed.

cvarjao commented 7 months ago

is there a way to do it preserving existing invitation? I am not sure how we are going to coordinate releasing a new version of the wallet with the new invitation and the mediator server-side changes. We can change the invitation later, but I am not sure what would happen if people already using that invitation/mediation.

WadeBarnes commented 7 months ago

is there a way to do it preserving existing invitation? I am not sure how we are going to coordinate releasing a new version of the wallet with the new invitation and the mediator server-side changes. We can change the invitation later, but I am not sure what would happen if people already using that invitation/mediation.

I'll investigate.

WadeBarnes commented 7 months ago

I've migrated the existing dev mediator over to a persistent queue setup and smoke tested it using the load test tool and an old invite I had. Would someone from the wallet team be able to run some tests in dev and make sure any old invites you have still work, and that the mediator is working as expected. Then we can migrate test and confirm before moving on to schedule prod.

cc @cvarjao, @jleach

jleach commented 7 months ago

I think if we choose to change the prod mediator invitation we would need to run both in parallel while users update the app. We may also want to add some logic that deletes old mediator connections. It typically does not show up in the contact list unless developer options are enabled so not feasible for users to do.

WadeBarnes commented 7 months ago

I think if we choose to change the prod mediator invitation we would need to run both in parallel while users update the app. We may also want to add some logic that deletes old mediator connections. It typically does not show up in the contact list unless developer options are enabled so not feasible for users to do.

This is no longer an issue with the migration approach I'm taking now. I'm migrating the existing instances over to use the persistent queue, so all of the existing connections and invites will continue to work. The URLs will not change either.

WadeBarnes commented 7 months ago

We may also want to add some logic that deletes old mediator connections.

This brings up some thoughts about cleaning up connections on the mediator side.

WadeBarnes commented 7 months ago

I was able to perform enough testing in dev to have enough confidence to migrate the mediator instance in test. I've smoke tested test with a couple old invites to ensure they continued to work.

WadeBarnes commented 6 months ago

The test environment is getting tested along with the Firebase updates; https://github.com/bcgov/DITP-DevOps/issues/106

WadeBarnes commented 6 months ago

Blocked by progress on https://github.com/bcgov/DITP-DevOps/issues/106.

WadeBarnes commented 6 months ago

Please reassign to me when this is ready to move forward.

WadeBarnes commented 5 months ago

The prod mediator instance has been upgraded and migrated to use the persistent queue. Updates include the Firebase plugin; https://github.com/bcgov/DITP-DevOps/issues/106

cc @bryce-mcmath, @jamshale, @cvarjao, @jleach

WadeBarnes commented 5 months ago

Assigned to @bryce-mcmath for final testing, as this will be tested along with the Firebase plugin updates. Please close when testing is successfully completed.

WadeBarnes commented 4 months ago

@bryce-mcmath, How has the testing been going?

esune commented 4 months ago

@bryce-mcmath, How has the testing been going?

@bryce-mcmath any updates on this? Can we close the issue or are there still pending tasks?

bryce-mcmath commented 4 months ago

@esune ah sorry, I didn't realize there were two mediator deployment tickets. I commented here: https://github.com/bcgov/DITP-DevOps/issues/106#issuecomment-1959919742

All Testflight testing has gone well and we are about to do a release that includes GA push notifications