From 82f8418f49b0564c5093c28be1ca522a628d0b4f Mon Sep 17 00:00:00 2001 From: mjkwiatkowski Date: Thu, 26 Feb 2026 19:51:57 +0100 Subject: feat: added notes from last meeting with my supervisor --- dante.txt | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 dante.txt (limited to 'dante.txt') diff --git a/dante.txt b/dante.txt new file mode 100644 index 00000000..6c55eb39 --- /dev/null +++ b/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