Decommission existing Traction instances, set-up new production-ready instances

[esune]

Current Traction instances need to be decommissioned and a new DITP-maintained and production-ready set of DEV/TEST/PROD instances deployed.

Acceptance Criteria:

• [ ] Backup wallets and decommission old EMDT instances in namespace set bc0192-*
• [ ] Decommission Anoncreds Workshop instance (if still up) in namespace a99fd4-test
• [x] Deploy DEV instance in bc0192-dev. Instance should be automatically updated when PRs are merged into main
• [x] Deploy TEST instance in bc0192-test. Instances should be updated on-demand, targeting the latest available release/chart.
• [ ] Deploy PROD instance in bc0192-prod. Instances should be updated on-demand, targeting the latest available release/chart.
• [x] Decommission sandbox DITP instance in namespace e79518-dev

Use a separate repository to store the deployment-specific configurations. The main Traction repo should - as much as possible - be used only for product changes and settings that are not use-case specific. Remove existing references from main traction repo.

Note: the BC Wallet showcase is using the DTS sandbox instance - coordinate with the the decommissioning so that they can request new tenants in the new instances.

[esune]

@krobinsonca just confirming, one last time, that the Traction instances in the bc0192-* namespaces can be safely decommissioned. Is there anything we should keep (i.e.: wallet backups)?

[krobinsonca]

Correct, they can be decommissioned. No backups are needed.

[swcurran]

How soon is this happening? We said that the Workshop instance would stay around for at least a week or so.

[WadeBarnes]

I'll monitor the Workshop instance for use daily and report usage, then we can look at decommissioning when usage drops off. We'll be using the Workshop instance to do some other debugging as well so it's not going any soon.

Workshop Traction Instance Usage 2023.06.01 - 07:56:

• Total 51 registered tenants
• We had about 30ish register before/during the Workshop. The remainder are internal test accounts.
• 2 new tenants since the end of the workshop

2023.06.02 - 07:23:

• Total 52 registered tenants
• 1 new tenant since yesterday

2023.06.12 - 04:47:

• Total 55 registered tenants
• 3 new tenants in the last 10 days
  • Created on the 4th, 5th, and 8th.

2023.06.20 - 05:29

• Total 60 registered tenants
• 5 new tenants in the last 8 days
  • Created on the 12th, 14th, 15th, and 2 on the 20th.

[esune]

How soon is this happening? We said that the Workshop instance would stay around for at least a week or so.

This is not slated to happen for at least the next couple of weeks - looking to further improve the Helm charts and CI/CD before then.

[esune]

@cvarjao @wadeking98 the new instances of Traction are up and running. @i5okie will add details (URLs) to request new tenants to this ticket (dev/test/prod): once migrated to the new instances please give us a heads up so we can decommission the current DTS deployment.

@swcurran we are also finally going to remove the Anoncreds workshop instance: any objections?

[swcurran]

Yes. There is more interest in building documentation around this type of thing for the Delivery team, so for now, I’d like to just keep it around. No maintenance needed on this, and if we decide that this type of thing is needed, we do a proper deployment.

[i5okie]

The following instances have been deployed and are ready to be used:

dev: https://tenant-ui-dev.apps.silver.devops.gov.bc.ca/ https://traction-acapy-dev.apps.silver.devops.gov.bc.ca/ https://traction-acapy-admin-dev.apps.silver.devops.gov.bc.ca/api/doc

test: https://tenant-ui-test.apps.silver.devops.gov.bc.ca/ https://traction-acapy-test.apps.silver.devops.gov.bc.ca/ https://traction-acapy-admin-test.apps.silver.devops.gov.bc.ca/api/doc

prod: https://tenant-ui.apps.silver.devops.gov.bc.ca/ https://traction-acapy.apps.silver.devops.gov.bc.ca/ https://traction-acapy-admin.apps.silver.devops.gov.bc.ca/api/doc

[cvarjao]

@esune, which ledger each instance is pointing at? I am assuming multi r/w ledger is not yet supported, right?

[esune]

@esune, which ledger each instance is pointing at? I am assuming multi r/w ledger is not yet supported, right?

Correct, this is a work in progress. Currently they use BCovrin Test for both read and write. This will change in the future as we implement the multi-ledger features, as well as the changes to the endorser service that are required to auto-approve new authors from known multi-tenant deployments (such as out Traction instances).

[i5okie]

Production instance has been uninstalled for the time being.

[i5okie]

Traction DTS has been uninstalled.