Stable instance of traction for prod showcase app
Opened this issue · 4 comments
- The showcase use cases uses CANDY DEV ledger
There are a couple of activities that need to be completed in order for a production tenant to be available for the Showcase app:
- we need to complete the chart clean-up and redeploy of Traction.
- we need to sort-out multi-ledger compatibility: Traction currently only works on a single ledger, multi-ledger in read mode is being investigated and there are additional complications at the ACA-Py level to have more than one ledger in write mode.
Some extra nuances are around the availability of endorsers on the ledgers to be targeted and having the Traction plugin manage those.
The plan is to have point 1 completed within the next 3 weeks or so (1.5 sprints) if everything goes well. For the multi-ledger support I don;t think I can (yet) commit to timelines since we are at the investigation/spike stage for multi-ledger read currently, and we will need to push some work AND do the same for the write part.
You could stand-up a single-tenant instance of ACA-Py if the timelines the BC Wallet team is looking at are tighter, and we could coordinate a migration to a tenant once we have it ready - integration-wise it should be a minor API integration pattern change. We don't want to be deploying multiple Traction instances targeting multiple ledgers as it would cause a significant amount of tech debt to reconcile them later on.
@esune, since the showcase is for ephemeral data (nothing needs to be stored, and there is no issue with resetting), can we start using the traction dev instance? Your team just need to be aware of it, and be a bit more careful when making changes. Once a new instance is available we should easily re-point to the new one. thoughts?
@cvarjao it should not be an issue in principle, however it would be best if you could wait a week or so longer.
We are finishing the new deployment charts that will give us a better hand at managing instances, and will be decommissioning and redeploying in a more production-like state our dev/test/prod instances. A lot of the issues we have been experiencing are caused by the current instance being a sandbox that was deployed with the intent of poking at things (not really hosting tenants) and ramping-up with Traction and the improvements we are pushing.
Per feedback from @WadeBarnes and @esune in separate RC chat , ....
"Enterprise apps team is working to get a stable instance that we can maintain properly, the current deployment is a sandbox that will be reset pretty soon. BC wallet team can either accept tech debt having to switch from single instance to a traction tenant, or having to restart with a different tenant once ready - the latter seems like a better option, as stated by Wade.
Additional feedback by @WadeBarnes dev and test are wired to traction agents. If BC wallet need to update prod with new content @WadeBarnes recommend hooking up to an existing traction instance for the time being, until the more permanent traction instances are available.