From 9bcc74a73393db0740c034191ed5125c0195f96e Mon Sep 17 00:00:00 2001 From: mjkwiatkowski Date: Sat, 27 Jun 2026 16:37:00 +0200 Subject: fix: ordered the notes and removed the datasets dir --- notes/dante.txt | 20 -------------------- 1 file changed, 20 deletions(-) delete mode 100644 notes/dante.txt (limited to 'notes/dante.txt') 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. - -- cgit v1.2.3