-
Notifications
You must be signed in to change notification settings - Fork 22
2022 02 18
Sebastian Schmittner edited this page Feb 18, 2022
·
1 revision
- Sebastian (EECC)
- Sebastian (Köln)
- Guido (MGM)
- Marquart (Siemens)
We have contributed our repo to Hyperledger: https://github.com/hyperledger/indy-node-container
HL Teams: https://github.com/orgs/hyperledger/teams/indy-node-container-maintainers
- Adapt Readme https://github.com/hyperledger/indy-node-container/pull/80
- run/READM -> links
- container refs (run) -> hyperledger
-
https://github.com/hyperledger/indy-node-container/blob/main/.github/workflows/trivy-all.yml
- tryvy ref -> HL (owner like in other action)
- Minutes
- Move to HL Confluence
- @Echsecutor -> ask ??? for Confluence Space
- https://github.com/hyperledger/indy-node-container/issues/46
- Add Slack bot
- https://action-slack.netlify.app/usage was added to ID Union Slack
- Sebastian Zickau continues in a personal fork
Suggestion by Marquart:
- limit docker logs
logging:
driver: "json-file"
options:
max-file: "5"
max-size: "100m"
-
default log level?
- https://github.com/hyperledger/indy-node-container/blob/main/run/etc_indy/indy_config.py
- set to 1
- += run/README.md
-
mounting log files (
/var/log/indy
)- https://github.com/hyperledger/indy-node-container/blob/main/run/docker-compose.yml
- rotation?
⚠️ - += run/README
-
Also limit container journal -> Docker build? or Startup script?
- Read man pages for journalctl ! 😉
- Default roataion?
# /var/log/journal
sudo journalctl --rotate
sudo journalctl --vacuum-size=100M
sudo journalctl --vacuum-files=5
- Ubuntu 20 / node 1.13.0~dev206 eventually runs into consensus problems
- do not use 1.13.0~dev206 for Debian images (for now)!
- Todo: rather produce Debioan images similar to https://github.com/IDunion/indy-node-container/blob/main/build/Dockerfile.ubuntu18
- @Echsecutor
- Concretely: Need Ubuntu 20.04 systemd container
- https://github.com/hyperledger/indy-test-automation/blob/main/system_node_only/docker/node/Dockerfile.ubuntu-2004
- Hyperledger Indy has a Test Automation Suite which starts the Indy software as a systemd service in a container to simulate operation in a VM. Mainly it is about Pool Restart, Upgrade, Start & Stop Node
- Could probably be based on https://github.com/solita/docker-systemd/tree/master (which is not maintained anymore)
- other examples
- requires sysbox-runc: https://github.com/nestybox/dockerfiles/blob/master/ubuntu-focal-systemd/Dockerfile
- requires privileged mode: https://github.com/fauust/docker-systemd
- requires privileged mode: https://github.com/robertdebock/docker-ubuntu-systemd
See https://github.com/hyperledger/indy-test-automation/blob/main/system_node_only/docker_setup.py#L78
Update from @Robin today: Looks promising!
- Carlos: https://github.com/IDunion/indy-node-monitor
- https://github.com/WadeBarnes/indy-node-monitor/tree/monitoring-stack
- Existing Prometheus + Grafana setup by IFIS
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?
-
Issue#102: Indy Node system tests depend on the Sovrin package
- Improve our own testing!
- Helm Charts
- Might geht interesting at some point in the future 😉
- Potential Clients Spherity/MGM
- Might geht interesting at some point in the future 😉
- Podman
- Weekly Fri 9:15-10:00 (UTC+1)