...

Recording of Call: 

...

20220510 Indy Contributors Call Recording.mp4

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:

• IndySDK / Aries Askar performance comparison with ACA-Py:
  • 08:13:03 From Stephen Curran : https://github.com/lissi-id/acapy-load-test-results/blob/main/AcaPy_0-7-4/Endurance_Test/02-0_7_4_askar_0_2_5-200rpm/report-test-results-0-6.pdf
• Ubuntu Upgrade:
  • 08:12:57 From Wade Barnes : FYI, links to the PRs for the new GHA based workflows and automated release processes for plenum and node: - https://github.com/hyperledger/indy-plenum/pull/1590 - https://github.com/hyperledger/indy-node/pull/1749
  • 08:13:56 From Stephen Curran : https://docs.google.com/presentation/d/1LPccSn6HaLRkKt6DSgcWicORpRknwUsH9knKr9LBCz4/edit#slide=id.p
  • 08:27:41 From Lynn Bendixsen : Has the error been seen with simply "adding" a 20.04 to an existing network with 16.04's in it? Or must one be "replaced"?
  • 08:28:35 From Christian Bormann : If i remember correctly so far, it was only seen by upgrading a node - not sure if adding a new node was tested
  • 08:28:48 From Wade Barnes : https://github.com/hyperledger/indy-node-container is the other option for the network for the tests.
  • 08:30:40 From Wade Barnes : Lynn, Yes adding a 20.04 node to and existing 16.04 network is known to trigger the issue.
  • 08:35:48 From Wade Barnes : About the mixed nodes issues https://hackmd.io/GSJnYPt0Q9yFKgoNGWtcMw
  • 08:44:03 From Philipp Schlarb : i can look into the von side if not planned in for the sovtoken gha/gitpod changes
  • 08:46:15 From Christian Bormann : Are people planning to switch to container-based deployments for the nodes when upgrading?
  • 08:46:49 From Philipp Schlarb : as far as i know in idunion is a node running containerized
  • 08:54:27 From Wade Barnes : The GitHub issue for the mixed node network issue; https://github.com/hyperledger/indy-node/issues/1750
  • 08:56:50 From Christian Bormann : do we also need indy-plenum packages Wade?
  • 08:57:07 From Christian Bormann : or is the current indy-node enough?

Welcome and Introductions

Attendees

• Stephen Curran
• Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>
• Wade Barnes (Neoteric Technologies Inc.) <wade@neoterictech.ca>
• Richard Esplin(Avast) <richard.esplin@avast.com>

Related Calls and Announcements

...

• 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.
  • Report: ACA-Py 0.7.4-RC with Indy-SDK
  • Report: ACA-Py 0.7.4-RC with Aries Askar (and other Shared Components) 
• 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

  • Status
    colour Green title New

    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:
    • 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.

...