Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revisionBoth sides next revision | ||
| events:fusion18:tally [2018/07/02 23:37] – added incomplete warning and summary frau_lutzn | events:fusion18:tally [2018/07/02 23:41] – [Summary] frau_lutzn | ||
|---|---|---|---|
| Line 82: | Line 82: | ||
| </ | </ | ||
| - | === 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/ | 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/ | ||