summaryrefslogtreecommitdiff
path: root/notes/dante.txt
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-06-27 16:37:00 +0200
committermjkwiatkowski <mati.rewa@gmail.com>2026-06-27 16:37:00 +0200
commit9bcc74a73393db0740c034191ed5125c0195f96e (patch)
tree797720bde28efca7cbb5278b760fb491a1c7a02d /notes/dante.txt
parent9b4a014a948eb0dbe0a2c1c78fbd5ffe2b915f3d (diff)
fix: ordered the notes and removed the datasets dir
Diffstat (limited to 'notes/dante.txt')
-rw-r--r--notes/dante.txt20
1 files changed, 0 insertions, 20 deletions
diff --git a/notes/dante.txt b/notes/dante.txt
deleted file mode 100644
index 6c55eb3..0000000
--- a/notes/dante.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-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.
-