While network and transport is done via WebSocket, traffic is sent using Python. ( 🤔 not sure if this is the smartest idea, as Golang isn't really that strong with JSON. 🫠 )

Agent => Manager:

register: register an agent with the manager
update: agents sends CPU and Mem metrics (does this every second)
solution: solution of a task given by the manager
deregister: deregister an agent from the manager

Manager => Agent:

task: A task for the agent to chew on

Commands

Register

Hostname
CPU cores
Memory

Update

cpu usage
memory usage
assigned task [none,taskID]

Solution

taskId
solution ([][9]string)

deregister

Hostname

task

taskId
split
part
puzzle ([][9]string)

Protocol

For ease of programming I would like start of easy and use ;-separated string to push values between manager and its agents. In this setup the format is predefined, and parsing will be based on the first field after the string is split on ;.

register;string;int;memory int
update;float;float;int
solution;string;string;string;string;string;string;string;string;string;string
deregister;string
task;int;int;int;string;string;string;string;string;string;string;string;string

I still have the impression that Go and JSON is hard to do as the rigidness of Go does not go well with the free spirited nature of JSON. I might revise this in the future.

Imports

I intend use golang/sudoku-funpark for the code to determine workload and calculate the puzzles that need to be solved. And while this is all modular, it unfortunately isn't flexible enough to actually use it in the tool (or I am not trying hard enough).

Other notes

Load ordering

Outputter Controller Export Flags Solver

	controller := controller.Controller{}
	outp := outputter.Outputter{}
	export := export.Export{Controller: &controller}
	flags := flags.Flags{Controller: &controller}
	solver := solver.Solver{Controller: &controller, Outp: &outp}

README.md

sfcs

Notes

Network Protocol