2022-04-12 Indy Contributors Call

Summary

• Before this meeting: did:indy DID Method Meeting (starts one hour earlier)
• Status of indy-node CI/CD and the Ubuntu upgrade
• Mixed version Indy networks – how to debug/fix?
• Q&A

Recording of Call: 

Welcome and Introductions

Attendees

• Stephen Curran
• Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
• Char Howland
• Lynn Bendixsen
• Mirko Mollik
• Paul Bastian
• Sebastian Schmittner
• Richard Esplin
• Robin Klemens
• Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>

Related Calls and Announcements

• IIW – anyone going?  What are you planning to talk to about?

Release Status and Work Updates

• Indy Node
• Indy SDK
• Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
• Indy Node Container - https://github.com/hyperledger/indy-node-container
• Indy/Aries Shared Libraries - Hyperledger (indy-vdr, indy-shared-rs, aries-askar)
• Ursa
• Indy DID Method – https://hyperledger.github.io/indy-did-method/

Meeting Topics

• Before the meeting: "did:indy" DID Method
  
  •  Separate meeting held one hour prior to this one. 
• Update on CI/CD Update and Ubuntu Upgrade: Status Document
  • Indy-Plenum Status: 
    • Done, 16.04, 20.04, Jenkins and GHA
  • Indy-Node Status:
    • Done, 16.04, 20.04, Jenkins and GHA
    • One 20.04 running in the IDUnion network of 16.04 nodes
    • Preparing and executing the automated release process.
  • indy-test-automation Status:
    
    • Working systemd image for 20.04, but the tests are not working – client messages not getting to the server.
    • Seems like there is a solution in the indy-node-container work.  To be checked with Robin Klemens.
  • Developer tools
    • indy-node-container (moved to Hyperledger) and GitPod tools available (node and plenum)
    • NEED THIS FIXED – HELP NEEDED: On plenum – error with building the dev containers about Indy SDK version – need to get the metadata version correct (https://github.com/hyperledger/indy-sdk/issues/2473)
      • Philipp raised a question on this, but no one had the info for an answer yet.
  • Indy-SDK build progress
    • Unblocked – builds are going and PRs are being reviewed (and rebasing PRs).
• How are we going to work through this issue and upgrade the various networks?
  • Concern - 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
• Presentation on the indy-node-container repo / project by Sebastian Schmittner

Future Calls

• 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

• 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
• Hyperledger campaign to recruit additional developers.

Action items