• Improved CI + Tags PR
• Controller
• Container Tagging

Attendance

• Sebastian Schmittner (EECC)
• Christian Bormann (Robert Bosch GmbH)
• Philipp Schlarb (esatus AG)
• Cristian Kubis
• Sebastian Zickau
• Michael Schaefer

In Progress

Indy Node Controller

• See 2022-11-17 Indy Container Meeting #48
• Update from ID Union Network meeting: >0 companies are using a Kubernetes (open shift) setup currently
• Step1: fix https://github.com/hyperledger/indy-node-container/issues/108
  • Cristian is working on this :+1:
• Step 2: Test Setup for current node upgrade:
  • Spin up a Network network with indy 1.12.4 containers
  • Do an upgrade to 1.12.6
  • Using https://github.com/hyperledger/indy-node-container/tree/main/testsetup with old images
    • E.g. container release 1.1.2 is the last indy 1.12.4

Indy VDR Containers

• Christian discovered Indy VDR using home brewn indy node containers for testing.
• https://github.com/hyperledger/indy-vdr/blob/main/ci/indy-pool.dockerfile
• Christian: PR → our containers as base for their testing
• Merge after https://github.com/hyperledger/indy-node-container/pull/121

Improve CI + Tagging of Container releases

• fixed by Philipp in https://github.com/hyperledger/indy-node-container/pull/121 :tada:
  • Sebastian Schmittnerask Stephen Curran or Rye  to change branch protection
  • Then merge!

• We could Improve the CI pipelines to not run if not necessary (e.g. not run if only md files are changed)
• Already tried this once → need to put work into required merge job cheks
• Include indy node version
  • currently RELEASE-FLAVOUR
  • Decision today: update to: NODE_VERSION-FLAVOUR-RELEASE
    • e.g. FLAVOUR=ubuntu20
    • e.g. FLAVOUR=debian10
• Release less flavours
  • Remove when 1.13 is there
  • Comment into readme now: deprecated ubuntu16, debian10,...

City of Cologne indy node (ID Union Test net) containers

• Trouble with their node operations

Stale

Container

• Use smaller base images
• python-slim + pypi indy packages?
  • Phillipp: Caution: pypi packages are not identical to deb versions
  • differences regarding config files for indy-node (https://github.com/hyperledger/indy-node/blob/ubuntu-20.04-upgrade/build-scripts/ubuntu-2004/prepare-package.sh)

Issues

• https://github.com/hyperledger/indy-node-container/issues/96
  • probably resolved?
• Maintainers.md: https://github.com/hyperledger/indy-node-container/issues/98
  • https://github.com/hyperledger/indy-node-container/pull/109

Load Test Script by Christian Bormann

• on hold

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
• Replace scan → github security alerts or do both?
  • BOTH
  • Sebastian Schmittner

Logging

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

• Discussion today:
  • Rather document how to edit the https://github.com/hyperledger/indy-node-container/blob/main/run/etc_indy/indy_config.py then overwriting those variables at container start through init script
  • Network Name → same!?
  • Definietly keep READE + docker logging explanation
  • → sesinsible default for logging in docker compose
  • Sebastian Schmittner

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

• Next meeting: Controller Discussion: 2022-11-04 9:15-10:00 (Berlin time)
• Next regular meeting: 2022-11-11 9:15-10:00 (Berlin time)