Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
events:fusion18:tally [2018/06/27 11:34] – url typo frau_lutzn | events:fusion18:tally [2024/03/31 13:09] (current) – ↷ Links adapted because of a move operation kunsi | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== Tallycom' | + | ==== Fusion 2018 - tallycoms |
- | === Intro === | + | At [[events: |
- | At [[events: | + | |
=== Status === | === Status === | ||
- | ^ device | + | ^ device |
- | | tallycom2-1 | + | | tallycom2-1 |
- | | tallycom3-2 | + | | tallycom3-2 |
+ | |||
+ | 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:// | ||
+ | |||
+ | === Step for step rebuild === | ||
+ | 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.** | ||
+ | |||
+ | == 1. Prerequisites == | ||
+ | - Ensure that you have access to this wiki. If you haven' | ||
+ | - If DHCP doesn' | ||
+ | IP: 10.73.100.X | ||
+ | SNM: 255.255.0.0 | ||
+ | GW: 10.73.0.254 | ||
+ | DNS: 10.73.0.254 | ||
+ | </ | ||
+ | - Install ansible and git < | ||
+ | user@laptop$ sudo {dnf, | ||
+ | </ | ||
+ | |||
+ | == 2. Flash latest Raspberry lite == | ||
+ | - Download + unzip the latest Raspbian lite - [[https:// | ||
+ | user@laptop$ cd ~/ | ||
+ | user@laptop$ wget http:// | ||
+ | </ | ||
+ | - Unpack and write the Raspbian image to a microSD card (**replace** / | ||
+ | user@laptop$ cd ~/ | ||
+ | user@laptop$ unzip -p 2018-04-18-raspbian-stretch-lite.zip | sudo dd of=/dev/sdX bs=4M conv=fsync | ||
+ | </ | ||
+ | |||
+ | == 3. Setup ansible + VOC cm repo == | ||
+ | - Install ansible and git < | ||
+ | user@laptop$ sudo {dnf, | ||
+ | </ | ||
+ | - Clone the VOC cm repo < | ||
+ | user@laptop$ mkdir -p ~/ | ||
+ | user@laptop$ cd ~/ | ||
+ | user@laptop$ git clone https:// | ||
+ | OR | ||
+ | user@laptop$ git clone git@mng.ber.c3voc.de: | ||
+ | </ | ||
+ | |||
+ | == 4. Run ansible == | ||
+ | - Get acquainted with the VOC [[: | ||
+ | - Checkout the feature/ | ||
+ | user@laptop$ cd ~/ | ||
+ | user@laptop$ git checkout feature/ | ||
+ | </ | ||
+ | - Check if the event inventory file contains correct mapping of tallycom IP to the variables that end up in the voctolight config < | ||
+ | user@laptop$ egrep ' | ||
+ | [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 | ||
+ | </ | ||
+ | - Check/ | ||
+ | user@laptop$ cat ~/ | ||
+ | --- | ||
+ | - hosts: tally-pis | ||
+ | roles: | ||
+ | - { role: common, tags: [' | ||
+ | - { role: tally, tags: [' | ||
+ | </ | ||
+ | - Run on multiple tallycoms - **WARNING: placeholder only** < | ||
+ | user@laptop$ cd ~/ | ||
+ | user@laptop$ ./ | ||
+ | --inventory-file event \ | ||
+ | --tree tally \ | ||
+ | -l 10.73.1.15, | ||
+ | -t tally \ | ||
+ | tally-pis.yml | ||
+ | </ | ||
+ | |||
+ | === Conclusion === | ||
+ | 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/ | ||
=== Sources/ | === Sources/ | ||
- | [[events: | + | * [[projects: |
+ | * [[: | ||
+ | * [[events: | ||
+ | * [[https:// |