At Fusion 2018 we ran a two camera setup for recording only. With the flight cases for room 1 and room 2 came two tallycoms whose config differed from their label and whose config was inconsistent.
device | ipv4 | /etc/issue | config |
---|---|---|---|
tallycom2-1 | 10.73.2.15/16 | Raspbian GNU/Linux 9 | partially ansibilised, please redo completely for next event |
tallycom3-2 | 10.73.2.17/16 (should be 10.73.3.16/16) | Raspbian GNU/Linux 8 | partially ansibilised, please redo completely for next event |
Getting voctolight on both tallycoms to (manually) work took unnecessarily much time. It boils down to being new to the matter, wrong labels, wrong config and different behaviour after correcting the config, due to different base OS versions (https://www.raspberrypi.org/forums/viewtopic.php?t=187225).
This section describes how to (re-)setup a tallycom from scratch, that should enable a VOC rookie with a linux laptop to go right ahead. WARNING: Due to time constraints no tallycom was actually re-flashed and the steps below are incomplete. If anything, they should be seen as a rough guide. Feel free to extend.
IP: 10.73.100.X SNM: 255.255.0.0 GW: 10.73.0.254 DNS: 10.73.0.254
user@laptop$ sudo {dnf,yum,apt-get} install ansible git
user@laptop$ cd ~/Downloads user@laptop$ wget http://director.downloads.raspberrypi.org/raspbian_lite/images/raspbian_lite-2018-04-19/2018-04-18-raspbian-stretch-lite.zip
user@laptop$ cd ~/Downloads user@laptop$ unzip -p 2018-04-18-raspbian-stretch-lite.zip | sudo dd of=/dev/sdX bs=4M conv=fsync
user@laptop$ sudo {dnf,yum,apt-get} install ansible git
user@laptop$ mkdir -p ~/Documents/voc/ user@laptop$ cd ~/Documents/voc/ user@laptop$ git clone https://github.com/voc/cm.git OR user@laptop$ git clone git@mng.ber.c3voc.de:cm
user@laptop$ cd ~/Documents/voc/cm/ user@laptop$ git checkout feature/tally-pis
user@laptop$ egrep '(tally|cam)' ~/Documents/voc/cm/ansible/event [tally-pis] 10.73.1.15 cam=cam2 encoder=encoder1.lan.c3voc.de 10.73.1.16 cam=cam3 encoder=encoder1.lan.c3voc.de 10.73.2.15 cam=cam2 encoder=encoder2.lan.c3voc.de 10.73.2.16 cam=cam3 encoder=encoder2.lan.c3voc.de 10.73.3.16 cam=cam3 encoder=encoder3.lan.c3voc.de 10.73.4.15 cam=cam2 encoder=encoder4.lan.c3voc.de 10.73.4.16 cam=cam3 encoder=encoder4.lan.c3voc.de #10.73.3.15 cam=cam1 encoder=encoder3.lan.c3voc.de
user@laptop$ cat ~/Documents/voc/cm/ansible/tally-pis.yml --- - hosts: tally-pis roles: - { role: common, tags: ['common'] } - { role: tally, tags: ['tally'] }
user@laptop$ cd ~/Documents/voc/cm/ user@laptop$ ./ansible-playbook-keepass -u voc –ask-pass –become –become-method=sudo –ask-become-pass \ --inventory-file event \ --tree tally \ -l 10.73.1.15,10.73.1.16,10.73.2.15,10.73.2.16,10.73.3.16,10.73.4.15,10.73.4.16 \ -t tally \ tally-pis.yml
The tallycoms were in an undefined state. They should either be checked prior to sending them out to the next event or a solution should be provided to quickly reset them at the event. One solution could be to have (pre-baked) working images per device (on e.g. the local encoder), which just need to be flashed to a microSD card, stuck back into the tallycom and $profit. If pre-baked images seem overkill, the process of flashing them with a base OS and running ansible against them should be made more straight forward/documented better.