	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

Attendance

...

Change to a US friendly time slot
- Thursday 17:00 CEST (UTC+2)
- next call 2022-06-23
- stay bi-weekly

Discussion

https://github.com/hyperledger/indy-node-container/tree/main/test
Currently:
- Run 4 node setup with 3 x ubuntu16 + 1 x test candidate
- Local run possible
- Runs as github https://github.com/hyperledger/indy-node-container/blob/cb40bd1eba6d2024fc968d55e61491310c8f7be6/.github/workflows/build-all.yml#L106
Christian developed new test setup
- Writing many transactions via VDR ( https://st1.zoom.us/web_client/3jktxx3/html/externalLinkPage.html?ref=https://github.com/hyperledger/indy-vdr )
To reproduce consensus problems
- Sebastian Schmittner: try to find setup that consistently reproduces the write consensus problems!
  - Old debian images → pypi
New PR for (test?) network(s?)
- https://github.com/hyperledger/indy-node-container/pull/92
- This seems to be directed to either run or more likely test
- Talk to contributor and integrate into our work
- DRY! No copy-paste files in another directory!

Sebastian Z finished work on slack alerting action.
Send webhook to Sebastian Schmittner → Forward to Stephen Curranto add to github repo, then MR github action

...

Marquart triggering Siemens processes to check whether Indy nod (Container) can be run in productive setting for a Siemens scale company

...