[atlas-sw-probes] Feedback from today/yesterday

Hi!

> Am 24.10.2019 um 09:21 schrieb Robert Kisteleki <robert at ripe.net>:
> 
> I believe there will be demand for a docker version, so I'm happy that
> it's emerging! The way I see it there are some issues to resolve:
> * permanent storage of key material, so outside the container?
> * how to handle upgrading if there's a new (upstream) available

The question I have is a more sustainable versioning overall. On GitHub is just the source code available but not the rpm.

Key is stored outside with the docker overlay2 driver or directly on the disk. I would prompt the users to make a backup from it. 
Upgrading can handle another container, it just watches for a new version, pulls it, deletes the old container and is starting the new one. With CentOS at this time it is a good idea to keep the software inside docker up to date :)

> Can you explain what problem you want to solve? If you want to "move"
> your probe from one server to another as a one-off action, you can
> always just install the new one, submit its key to us as a replacement
> [almost implemented :-)] and stop the old instance.

Sure, but both solutions are producing the same end result. The same probe ID is reporting.

> Happy to see progress on software probes :). I will try to deploy it on our raspberries on the weekend.
> 
> My thoughts on the docker stuff, we should aim to make it run with alpine linux before we release an official container, because a CentOS container seems to be too bloated. 
> 
> Storage outside of the container should be no problem, I suggest we make a docker-compose file to setup all the storage stuff etc.. If there is an upgrade script between versions we should run the upgrade script at every container start.

Hi Anika,

Any success with RPI?

The problem at this time is that we need tini for handling multiple running processes inside one container like cron, SSH, telnet, the pings and pongs, so implementing that into Alpine would also be an overhead :)

###
   CGroup: /docker/XYZ/system.slice/atlas.service
           ├─   28 /bin/sh /usr/local/atlas/bin/ATLAS
           ├─   73 /usr/local/atlas/bb-13.3/usr/sbin/telnetd -b 127.0.0.1 -p 2023 -P /var/atlas-probe/run/telnetd-port2023-pid.vol
           ├─   95 /usr/local/atlas/bb-13.3/bin/perd -c /var/atlas-probe/crons/main -A 9801 -P /var/atlas-probe/run/perd-main.pid.vol
           ├─   97 /usr/local/atlas/bb-13.3/bin/eperd -c /var/atlas-probe/crons/7 -A 9807 -P /var/atlas-probe/run/perd-7.pid.vol -O /home/atlas/data/new/7 -i 7
           ├─   98 /bin/sh /usr/local/atlas/bin/ATLAS
           ├─  100 /usr/local/atlas/bb-13.3/bin/eooqd /var/atlas-probe/crons/oneoff -A 9809 -P /var/atlas-probe/run/eooqd.pid.vol -i 9
           ├─  124 /usr/bin/ssh -o ServerAliveInterval 60 -o StrictHostKeyChecking yes -o UserKnownHostsFile /var/atlas-probe/.ssh/known_hosts -R 54453:127.0.0.1:2023 -L 8080:127.0.0.1:8080 -i /var/a...
           └─11726 sleep 180
###

Afaik there is no upgrade needed? The only dependency we have inside Docker is the magic ssh key :)


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ripe.net/ripe/mail/archives/atlas-sw-probes/attachments/20191028/903c2d48/attachment.html>