events:fusion18:tally

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
events:fusion18:tally [2018/06/27 17:06] – frau_lutznevents:fusion18:tally [2026/07/26 22:17] (current) – external edit 127.0.0.1
Line 1: Line 1:
-==== Fusion 2018 - tallycoms ====+#### Fusion 2018 - tallycoms
 At [[events:fusion18]] 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. At [[events:fusion18]] 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.
  
-=== Status ===+### Status
 ^ device       ^ ipv4                                                         ^ /etc/issue                ^ config                                                            ^ ^ device       ^ ipv4                                                         ^ /etc/issue                ^ config                                                            ^
 | tallycom2-1  | 10.73.2.15/16                                                | ''Raspbian GNU/Linux 9''  | partially ansibilised, **please redo completely for next event**  | | 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 [[intern:netzplan|10.73.3.16/16]])  | ''Raspbian GNU/Linux 8''  | partially ansibilised, **please redo completely for next event**  |+| tallycom3-2  | 10.73.2.17/16 (should be [[intern:archive:netzplan|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 behavior after correcting the config, due to different base OS versions ([[https://www.raspberrypi.org/forums/viewtopic.php?t=187225]]).+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]]).
  
-=== Step for step rebuild === +### 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. This section can be moved to a separate page in true wiki fashion.+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 ==+## 1. Prerequisites
   - Ensure that you have access to this wiki. If you haven't, you can't read this. :brain_explosion:   - Ensure that you have access to this wiki. If you haven't, you can't read this. :brain_explosion:
-  - If DHCP doesn't work, have someone from the VOC team reserve and hand you a [[intern:netzplan|10.73.100.{1..254}/16]] address. Configure it manually. <code>+  - If DHCP doesn't work, have someone from the VOC team reserve and hand you a [[intern:archive:netzplan|10.73.100.{1..254}/16]] address. Configure it manually. <code>
 IP: 10.73.100.X IP: 10.73.100.X
 SNM: 255.255.0.0 SNM: 255.255.0.0
Line 24: Line 24:
 </code> </code>
  
-== 2. Flash latest Raspberry lite ==+## 2. Flash latest Raspberry lite
   - Download + unzip the latest Raspbian lite - [[https://downloads.raspberrypi.org/raspbian_latest]] (at the time of writing April 2018)\\ **WARNING: 350 MB** - A lot in case of shitty/shared uplink... <code>   - Download + unzip the latest Raspbian lite - [[https://downloads.raspberrypi.org/raspbian_latest]] (at the time of writing April 2018)\\ **WARNING: 350 MB** - A lot in case of shitty/shared uplink... <code>
 user@laptop$ cd ~/Downloads user@laptop$ cd ~/Downloads
Line 34: Line 34:
 </code> </code>
  
-== 3. Setup ansible + VOC cm repo ==+## 3. Setup ansible + VOC cm repo
   - Install ansible and git <code>   - Install ansible and git <code>
 user@laptop$ sudo {dnf,yum,apt-get} install ansible git user@laptop$ sudo {dnf,yum,apt-get} install ansible git
Line 46: Line 46:
 </code> </code>
  
-== 4. Run ansible ==+## 4. Run ansible
   - Get acquainted with the VOC [[:ansible]] repo structure   - Get acquainted with the VOC [[:ansible]] repo structure
   - Checkout the feature/tally-pis branch (**for now**) <code>   - Checkout the feature/tally-pis branch (**for now**) <code>
Line 52: Line 52:
 user@laptop$ git checkout feature/tally-pis user@laptop$ git checkout feature/tally-pis
 </code> </code>
-  - Check if the event inventory contains correct IP/hostname mappings <code>+  - Check if the event inventory file contains correct mapping of tallycom IP to the variables that end up in the voctolight config <code>
 user@laptop$ egrep '(tally|cam)' ~/Documents/voc/cm/ansible/event  user@laptop$ egrep '(tally|cam)' ~/Documents/voc/cm/ansible/event 
 [tally-pis] [tally-pis]
Line 64: Line 64:
 #10.73.3.15 cam=cam1 encoder=encoder3.lan.c3voc.de #10.73.3.15 cam=cam1 encoder=encoder3.lan.c3voc.de
 </code> </code>
-  - Check/extend  <code>+  - Check/extend the roles to be applied to the tallycoms <code>
 user@laptop$ cat ~/Documents/voc/cm/ansible/tally-pis.yml  user@laptop$ cat ~/Documents/voc/cm/ansible/tally-pis.yml 
 --- ---
Line 82: Line 82:
 </code> </code>
  
-=== Sources/Hints ===+### 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/documented better. 
 + 
 +### Sources/Hints
   * [[projects:tallycom]] - Base info about the raspberry pi 3 based tallycoms.   * [[projects:tallycom]] - Base info about the raspberry pi 3 based tallycoms.
   * [[:ansible]] - Base explanation of the VOC ansible repo.   * [[:ansible]] - Base explanation of the VOC ansible repo.
   * [[events:34c3:tally]] - Use the **tally-pis** branch from [[https://github.com/voc/cm]], might need some work and should probably be merged into the master branch eventually.   * [[events:34c3:tally]] - Use the **tally-pis** branch from [[https://github.com/voc/cm]], might need some work and should probably be merged into the master branch eventually.
   * [[https://www.raspberrypi.org/documentation/installation/installing-images/linux.md]]   * [[https://www.raspberrypi.org/documentation/installation/installing-images/linux.md]]
  • events/fusion18/tally.1530119218.txt.gz
  • Last modified: 2018/06/27 17:06
  • by frau_lutzn