summaryrefslogtreecommitdiff
path: root/notes/dante.txt
diff options
context:
space:
mode:
authormjkwiatkowski <mati.rewa@gmail.com>2026-06-01 14:15:37 +0200
committermjkwiatkowski <mati.rewa@gmail.com>2026-06-01 14:15:37 +0200
commitf771af4e69db4b8937f64fbf4024eb518a7cc230 (patch)
tree320be41b46d66def4f27ad7611e1ebfd51aa3386 /notes/dante.txt
parent91ca6b9411a1675f5735a86ac658833dc78cc382 (diff)
feat: added some notes
Diffstat (limited to 'notes/dante.txt')
-rw-r--r--notes/dante.txt20
1 files changed, 20 insertions, 0 deletions
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.
+