Some notes.

This commit is contained in:
Sacha Ligthert 2025-02-02 19:39:53 +01:00
parent 30593d1372
commit fd41e0c03e

View File

@ -1,3 +1,73 @@
# sfcs # sfcs
Sudoku-Funpark Cluster Software: same as [Sudoku-funpark](https://gitea.ligthert.net/golang/sudoku-funpark/), but networked. Sudoku-Funpark Cluster Software: same as [Sudoku-funpark](https://gitea.ligthert.net/golang/sudoku-funpark/), but networked.
## Notes
### Network Protocol
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
1. Hostname
2. CPU cores
3. Memory
#### Update
1. cpu usage
2. memory usage
3. assigned task [none,taskID]
#### Solution
1. taskId
2. solution ([][9]string)
#### deregister
1. Hostname
#### task
1. taskId
2. split
3. part
4. 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
```Go
controller := controller.Controller{}
outp := outputter.Outputter{}
export := export.Export{Controller: &controller}
flags := flags.Flags{Controller: &controller}
solver := solver.Solver{Controller: &controller, Outp: &outp}
```