...
| Excerpt |
|---|
Planned:
|
The call recording is available here:
...
20200915 Indy Contributors Call
Remember the Hyperledger Code of Conduct
...
- Catch up on Indy Interop-athon - Presentation
- Getting started on a new release of indy-node
- Schedule a meeting - to review the contents - Richard/Stephen to coordinaterelease contents.
- This Thursday at 6AM Pacific, 3PM CET to discuss. We'll use this Zoom room, Richard to invite interested parties.
- Getting started on a CI/CD migration
- Getting started on the did:indy Method
- Discussion
- Why did the Sovrin node hard requirements get bumped to where they are today?
- Factors:
- Primarily based on load testing, including load testing the Sovrin token and in particular, a token launch event.
- This would trigger a spike in usage plus an ongoing higher load, plus a gradual load increase as payment events rise.
- Also based on the load expected from revocation (gradual climb).
- Primarily based on load testing, including load testing the Sovrin token and in particular, a token launch event.
- Any Indy Network must set the node hardware spec.
- indy-node-monitor validator info includes usage information (CPU, disk space) and should be used for trending to predict when to increase resources
- Clarity required on what the resources measure – e.g. overall load/disk usage on the server vs. indy-node load/disk usage.
- Factors:
- Why did the Sovrin node hard requirements get bumped to where they are today?
Future Calls
Next call:
Future:
...