Design proposition

This is a draft for the design of the polyprog livesystem infrastructure

components

• live system(s): one per participant
• backup server: non-live system for backups of every live system
• management server : non-live system for managing every other system
• monitoring server : non-live system for monitoring every computer

discovery

Every system should be able to speak to each other.

Avahi mdns seems a good way of being able to connect to each other without needing to know the ip address of each others

management

Using saltstack for managing the state of the architecture seems the easiest as saltstack supports a cloud setting, which accepts automatically new clients

monitoring and backup

Icinga2 seems to stay the best for doing those, managed through saltstack to discover clients