• Indy Release 1.13

• Network Upgrades

• Future of this workgroup

Attendance

• @Philipp Schlarb (esatus AG) <p.schlarb@esatus.com>

• @Christian Bormann (Robert Bosch GmbH) <christiancarl.bormann@de.bosch.com>

• @Sebastian Schmittner (EECC)

• @Guido Wischrop (mgm)

In Progress

Indy Release 1.13

• Things are happening

• Soon ready (still)

• New 1.13 Networks are working

• Upgrade Tests 1.12 → 1.13 of existing Networks are the biggest outstanding issue

Upgrade Test (DEV Netz)

Altes Netz 2022:

• Siemens

  • Marquart

• Esatus

  • Lead: Christopher

• MGM

  • Guido

• Bosch 

  • Christian

• T-Labs

  • Dirk

2023:

• Bosch

  • If possible: only provide tools, do not run own node

• T-Labs

  • Not eager

• MGM

  • Still running a node

  • Firewall needs to be changed

• EECC

  • Prune and use old prod node

• Esatus

  • Node

• Köln

  • Node?

Next Steps

• It makes more sense to fokus our ressources on the Indy Release 1.13 upgrade testing than to work on containers for 1.12.

• We will fokus on upgrade tests from now on to make enable the 1.13 upgrade ASAP

Stale

Issues

• https://github.com/hyperledger/indy-node-container/issues/126
  Explicit Dependency Removal

  • @Sebastian Schmittner 

Controller with and without podman

• Todo: Create an imageflavour with and one without podman

  • https://github.com/hyperledger/indy-node-container/issues/112

Indy Node Controller

• https://github.com/hyperledger/indy-node-container/pull/123

  • IP Adress conflict on github runner → Remove network bridging

    • Done

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)

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?

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 regular meeting: 2023-05-26 10:00-10:25 (Berlin time)