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/07/02 23:37] – added incomplete warning and summary frau_lutznevents:fusion18:tally [2024/03/31 13:09] (current) – ↷ Links adapted because of a move operation kunsi
Line 5: Line 5:
 ^ 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 behaviour 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]]).
Line 14: Line 14:
 == 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 82: Line 82:
 </code> </code>
  
-=== Summary ===+=== 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. 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.
  
  • events/fusion18/tally.txt
  • Last modified: 2024/03/31 13:09
  • by kunsi