From f771af4e69db4b8937f64fbf4024eb518a7cc230 Mon Sep 17 00:00:00 2001 From: mjkwiatkowski Date: Mon, 1 Jun 2026 14:15:37 +0200 Subject: feat: added some notes --- notes/dante.txt | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 notes/dante.txt (limited to 'notes/dante.txt') diff --git a/notes/dante.txt b/notes/dante.txt new file mode 100644 index 0000000..6c55eb3 --- /dev/null +++ b/notes/dante.txt @@ -0,0 +1,20 @@ +Create a model in draw.io +Look at OpenTelemetry (read up - is this a lot of work?) +https://github.com/atlarge-research/opendc/tree/radice-paper +Make sure you the fields you specify in the schema itself are automatically exported. +Measure Kafka latency of exporting. +Also ensure whether the user wants to export to database or not. +Add multiple export functions. +Make sure specify the config files in the command line. +The prediction should be about auto-scaling. +BUT -> there is no auto-scaling. +Do auto-scaling. +Idle power takes a lot of energy. +Predicting when to turn nodes on and off would be nice. +Datacenters are heavily underutilized. +Predict when to turn the hosts on and when to turn them off. +Look at the failure models and how they work in OpenDC - this is how I stop a host, and this is how I start back a host. +With auto-scaling you can do it a bit smarter or not. +Do auto-scaling in OpenDC. +Rescheduling. + -- cgit v1.2.3