Summary

• Call for Resources: Completing the Indy Ubuntu 20.04 Upgrade
• Q&A

Recording of Call: <To Be Added>

Welcome and Introductions

Attendees

Related Calls and Announcements

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 

• Progress on completing the Ubuntu upgrade.

Upgrade Notes

• Upgrading Indy to Ubuntu 20.04 Presentation 
• Update on CI/CD Update and Ubuntu Upgrade
  • Indy 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: 
    • Done, 16.04, 20.04, Jenkins and GHA
      
    • New Release Workflow PR: https://github.com/hyperledger/indy-plenum/pull/1590
  • Indy-Node Status:
    • Done, 16.04, 20.04, Jenkins and GHA
    • One 20.04 running in the IDUnion network of 16.04 nodes
      
    • New Release Workflow PR: https://github.com/hyperledger/indy-node/pull/1749
  • indy-test-automation Status:
    •  
  • 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?
  • 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

Action items