...

...

...

...

...

...

...

...

• Indy Node Controller Image
• DevOps Scripts
• Christian's Load Tester

Attendance

• Sebastian Schmittner (EECC)
• Christian Bormann (Robert Bosch GmbH)
• Marquart Franz (Siemens)
• Philipp Schlarb (esatus AG)  <p.schlarb@esatus.com>

In Progress

Indy Node Controller

• We do currently not support upgrade scripts
  • https://github.com/hyperledger/indy-node/tree/main/data/migrations
• https://github.com/hyperledger/indy-node-container/pull/97
  • PLEASE add review :+1: asap → fix pool restart via controller

IP Tables script:

• https://github.com/hyperledger/indy-node-container/blob/main/run/set_iptables.sh
• Add to README: flush Chain (default docker) before running the script
• Check that DROP rule is automatically moved to correct position

Network connectivity test script

Idea: Script to test that IP Tables rules are as they should be

• At least check that node can connect (TCP lvl) to all other nodes
• Bonus: Check that connection from outside is not possible

Load Test Script by Christian Bormann

• Rust Programm 
• Containerized :check:
• Add to container shipping repo
  • Consensus Vote...: YES! For Now.
• Philipp: Test Automation Repo
  • TBD: Conrtib Christians Code into our or the test repo?

Test Setup

• 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! 

Stale

Alerting

• 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

Using Container in Production Network

...

•  TODO: Set up a new node (step by step) from our repo+readme
  • check if it works and everything is explained well enough

...

• Upgrade Process 
  • Latest images

  • Upgrades via node controller

    •  We have a setting. Good enough?

Logging

• Stale PR https://github.com/hyperledger/indy-node-container/pull/83

  • Sebastian Schmittner → Nicklas (solidnerd): who is to finish this?

Stale

TRA / OSS Clearing / ...

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

Metrics

• Carlos: https://github.com/IDunion/indy-node-monitor
• https://github.com/WadeBarnes/indy-node-monitor/tree/monitoring-stack
• Existing Prometheus + Grafana setup by IFIS

Security

The node keys handling is currently sub optimal (env variable). Should be improved to e.g. file based setup: https://github.com/IDunion/indy-node-container/issues/52

• Cristian already has a nice setup elsewhere and offers to port it
  • https://github.com/internet-sicherheit/sovrin-container
  • Merge of IFIS repo?

Indy-Test-Automation

• Issue#102: Indy Node system tests depend on the Sovrin package
  • Improve our own testing!

Support for non-docker setup

• Helm Charts
  • Might geht interesting at some point in the future 
    • Potential Clients Spherity/MGM
• Podman
  • https://github.com/IDunion/indy-node-container/issues/48

Next Meeting

• Change to Bi-Weekly: THU Next meeting: 2022-08-18 17:00-18:00 (UTC+2)Next Meeting: 2022-06-23