2021-04-13 Indy Contributors Call
Summary
Planned:
Status of indy-node CI/CD
Status of Ubuntu upgrade
Recording from the call: dummyfile.txt
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
Stephen Curran (Cloud Compass Computing Inc.) <swcurran@cloudcompass.ca>
Lynn Bendixsen (Indicio, PBC) <lynn@indicio.tech>
Related Calls and Announcements
Release Status and Work Updates
Indy Node
GitHub actions led by @Wade Barnes
Ubuntu 20.04 upgrade led by @Robin Klemens and@Ryan Marsh
Sovrin Updates @Wade Barnes
New branching model led by @Wade Barnes
Indy SDK
GitHub actions led by @Patrik Stas
Indy Node release needs a build of Indy SDK with freeze ledgers to do system tests. Currently blocked with publishing to pypi.
Indy Monitoring - https://github.com/hyperledger/indy-node-monitor
Indy/Aries Shared Libraries - donated to Hyperledger (indy-vdr, indy-shared-rs, aries-askar)
Ursa
Hyperledger Contribution Campaign (@Richard Esplin @Stephen Curran )
Meeting Topics
Update: GitHub actions led by @Kevin Griffin @Wade Barnes
CD: Hyperledger Debian repo is available and being used
Package artifacts
Secrets managed
Indy-Plenum
CI for Indy Plenum - merged
Being redone because of missing tests
CD for Indy Plenum - ready but not merged
CD is in master, needs to be merged into ubuntu2004 branch
GHA details in PR: https://github.com/hyperledger/indy-plenum/pull/1522#issuecomment-810531932
In PR is ability to run the GHAs off different branches.
Stable to Master merge - Merged
Ubuntu 20.04 tests
Now mostly running – had been missing the upgrades necessary to run the tests
1 test is failing, 1 split test is cancelling – details to go to Renata (Wade to provide)
Skipped tests – should verify why and make sure that is OK – Wade to review.
Task: Eliminate the pinned dependencies as possible – Renata's team to look at that
Requires code changes and additional tests
Indy-Node
Rinse and repeat the Plenum work
Stable to Master merge – still being reviewed (Wade); waiting on a response to a question (Renata)
Indy-SDK
CI/CD for Indy-SDK looks good – ready, Wade to review - waiting for Jenkins to sign off on the build (happening as we speak)
Jenkins failure is preventing merging – all tests must pass
Can someone look at that? Wade reviewed and not seeing the issue. ABSA has looked at it, but don't know the issue.
?? To be looked at...
Jenkins/GHAs to run in parallel for a bit, while the GHA are finalized.
CI – deprecating that sooner than later
CD – need the right triggers to fire (e.g. if PR merges to master and updates the tag, publishes artifacts)
Sovrin Release - @Wade Barnes
Working on CI/CD
Dev environment is working and new docs
Working on the Plenum side because it was blocking him
Discovered problems with plenum upgrade – many failing tests – mostly fixed
Jenkins
Ubuntu 20.04
Upgrade from indy-crypto to ursa-crypto - done
Upgrade Python - done
Rinse and repeat from Plenum for dependencies
indy-test-automation – had been working, but it is dependent on the Sovrin packages that are not made yet.
Need to research the publishing of the artifacts from GHA to the Sovrin repos
Before – indy and sovrin artifacts were in Sovrin repos
To Be Done – indy artifacts will be hosted on Hyperledger Artifactory; Sovrin on Sovrin repositories
Indy Contribution Campaign
Timing – HGF coming up – timing perhaps best is after HGF
Video – 3 month lead time on that – Digital Identity
Look at second half of the year – but we need to get started
Status of indy-sdk CI/CD
Sovrin Network Upgrade process:
Inputs: New CI/CD, OS Upgrade, Post Feb. 2020 functionality (e.g. Rich Schema), indy-crypto vs. ursa-crypto
Today: 16.04 with no post Feb 2020, Functionality, mix of indy-crypto/ursa-crypto
Release 1: Another 16.04 using the new CI/CD code but no code changes plus the Post-Feb. 2020 changes
Concern: Have the new GHAs been made ONLY for 20.04? Not supposed to be, but TBD.
Release 1: Ubuntu 20.04 that runs with today's nodes.
Proposal: Call the new version 1.13.0 that is tested ONLY on Ubuntu 20.04, MUST be compatible with 1.12.4
One Steward at a time – 1) remove their 16.04 1.12.4 node, 2) create new 20.04 device, 3) install 20.04 node, 4) add their 1.13.0 node
Cannot affect consensus – we'll verify that as we go.
Short term request of Stewards – get ESM from Canonical
Release 3: Post Feb. 2020 changes
Future Calls
Next call:
Future:
Changed to indy-node as needed for did:indy
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.