...
| Excerpt |
|---|
|
Recording of Call:
...
20220621 Indy Contributors Call Recording.mp4
|
Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct. |
|---|
...
Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>
Lynn Bendixsen(Indicio PBC) <lynn@indicio.tech>
Char Howland(Indicio PBC) <char@indicio.tech>
Related Calls and Announcements
...
- Progress on completing the Ubuntu upgrade.
- Using Overlays Capture Architecture (OCA) with AnonCreds
Upgrade Notes
- Upgrading Indy to Ubuntu 20.04 Presentation
- Summary of the work done ^^
- Update on CI/CD Update and Ubuntu Upgrade
- Indy Shared GHA Repo
- Indy-Plenum StatusPlenum:
- Indy-Node StatusNode:
- indy-test-automation Status:
- indy-node-container:
- Call time changed – 17:00 CET / 8:00 Pacific on Thursdays.
- Indy-SDK build progress
- Issue: Mixed OS versions of Indy Node have issues:
- Issue: - running mixed nodes 16.04 and 20.04 a consensus problem occurs "in a while" (sometimes immediately, sometimes a few days has been seen)
- 2022.06.21
- Two efforts trying to replicate the problem Christian Bormann (rust script to generate load) and Gavin Bendixsen (PR to indy_node_container), working on adding a node
- At this point, the issue has not been replicated.
- There is an indy node load generator - https://github.com/hyperledger/indy-node/tree/master/scripts/performance
- Another plan of attack: Use old artifact to try to recreate, try again with RC and see if that replicates the issue.
- Note from Lynn: He has seen and documented consensus issues in the past – maybe this has nothing to do with 20.04.
- For example: 2 nodes went down seemingly together, restarted them and issue resolved.
- 2022.06.07
- Indicio team is working on a docker environment to replicate this, they are expecting to have something running in a few days.
- docker-compose, 4 nodes (3 16.04 and 1 20.04), running for a week, but not able to replicate the issue.
- Lynn to share how to do this publicly so that others could contribute.
- Put a folder into the indy-node-container repo about how to do it.
- Plan is to use indy-vdr to generate DIDs and publish them to the ledger.
- 2022.06.21
- Issue: - running mixed nodes 16.04 and 20.04 a consensus problem occurs "in a while" (sometimes immediately, sometimes a few days has been seen)
- Related work - Sovrin token-plugin repo being reworked to match indy-node/plenum.
- Mostly done the code.
- Working on the pipeline
- Linting issues documented and being cleaned
Future Calls
- GDPR and the right to be forgotten – mitigations and approaches.
- Dealing with Indy Node DoS attacks.
- Issues that could impact indy-node on 20.04
- indy-sdk: needs an upgrade to OpenSSL 1.1 to properly support Ubuntu 18.04/20.04. For indy-node, just using indy-sdk as is.
- Multiple libsodium versions could impact consensus – intermittent issue on a mixed network.
- Plans for a new Indy-SDK release?
- A few people from the community have asked.
- The most recent request has been for a release to include this feature; https://github.com/hyperledger/indy-sdk/pull/2400
...