2022-05-10 Indy Contributors Call

Owned by Stephen Curran
Last updated: May 10, 2022
4 min read

Summary

  • Progress on Indy / Aries Shared Components – Load Test Results
  • Call for Resources: Completing the Indy Ubuntu 20.04 Upgrade
  • Q&A

Recording of Call: dummyfile.txt

Sections:

  • IndySDK vs. Aries Askar performance - from 0:00 to 9:10
  • Ubuntu Upgrade discussion from 9:18 to the end of the recording.

Chat:


Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome and Introductions

Attendees

Related Calls and Announcements

Release Status and Work Updates

Meeting Topics 

  • An apples to apples test of the "Shared Components" vs. the Indy-SDK shows performance is remarkably improved with the Shared Components. We'll take a look at the reports, talk about what you get when you switch, the effort and next the steps in moving this forward.
  • A plan for getting the Ubuntu upgrade complete and a request for resources to help with the work.

Upgrade Notes

  • Upgrading Indy to Ubuntu 20.04 Presentation 
  • Update on CI/CD Update and Ubuntu Upgrade: Status Document
    • NEWIndy Shared GHA Repo
      • Updates being made across all repos to organize the GHAs into a single repository (indy-shared-gha), and dependent updates being made to all indy repos
    • Indy-Plenum Status: 
    • Indy-Node Status:
    • indy-test-automation Status:
      • Working on automated triggers across repositories but must be in the main branch – perhaps time to convert over main to 20.04, and to have a 16.04 branch.  To be discussed.
      • Working systemd image for 20.04, but the tests are not fully tested because of permissions handling decisions to be made after GHA work completed. 20.04 requires root where 16.04 doesn't and we want to confirm that to be the case.
      • There might be a solution in the indy-node-container work.  To be checked with Robin Klemens.
    • indy-node-container (moved to Hyperledger) and GitPod tools available (node and plenum)
    • Indy-SDK build progress
      • Unblocked – builds are going and PRs are being reviewed (and rebasing PRs).
    • Backlog Issue: Mixed OS versions of Indy Node have issues:
      • How are we going to work through this issue and upgrade the various networks?
      • 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)
      • Robin has the details of what tests have been run and what observations have been done. See Hack MD document with some details. 
      • Perhaps because of libsodium v18 and v23.
      • It might also be a ledger corruption issue, perhaps with the lead node having corruption issues and then propagating those issue.
      • Can we get the indy-node-container folks run tests with a mixed environment of nodes
      • Richard Esplin at Avast can get help answering questions about Plenum. Tag him on Discord with your question.
      • Blog post on troubleshooting an Indy network.

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?
  • Status of Indy-SDK
    • Statement on the future of the Indy SDK: PR 2329
    • Plans for future of Indy CLI (move to Indy VDR?)
    • Indy SDK in test for Indy Node (move to Indy VDR?)
    • Status of GitHub Actions for the Indy-SDK
  • Indy bugs
    • Using GitHub tags "Good First Issue" and "Help Wanted" 
    • Node 1490: problems with large catch-up
    • Plenum 1506: view change message consensus calculation error

Action items