API interface, multi-tier heartbeating, architecture changes

using Flask RESTful API
separated into two resources: logging and commands
Multi-tier heartbeating
tree hierarchy of client nodes
allows intermediate relays and leaves
heartbeats aggregate service status updates for dependents
nodes ignorant of topology beyond one layer
Logging
web interface contains endpoint for getting logs from a service
routing through relay nodes for multi-layer topology
Architecture changes
API interface as module on canopy server
each client runs a TCP server to receive commands and socket to send heartbeats
servers and relays run TCP server to receive heartbeats
servers and relays maintain list of services at leaves, automatically remove and broadcast when connection to leaves is lost
clients send command TCP server address upwards to listen for commands

acm-uiuc / canopy