fix: ordered the notes and removed the datasets dir

1 files changed, 63 insertions, 0 deletions

diff --git a/notes/11_05_2026.txt b/notes/11_05_2026.txt
new file mode 100644
index 0000000..6a74ff9
--- /dev/null
+++ b/notes/11_05_2026.txt
@@ -0,0 +1,63 @@
+==AutoScaling== 
+To get it to run --? look at how failures are implemented. 
+The moment your pool of usable hosts becomes too tight then you activate new ones. 
+1) I want to implement which allows me to put hosts inactive and activate it again. 
+2) During the workload the operator should be able to close and open the workloads.
+i) then you build a policy as to when you activate new hosts and when you want to stop hosts. 
+ii) have many policies to do this 
+iii) add booting time --> cold start. A host becomes available but it takes still more time to make it workable because you need to boot everything. 
+iv) cold starts use zero power or very minimal --> idle power of a node that is turned off. Inactive have minimal power draw, but the downsides is that nodes may not be available immediately.
+Inactive takes more time to boot e.g., 5 minutes.
+The more you can predict how many nodes you will need to more you can save power without impacting the performance. 
+
+The bachelor focus -- the primary focus should be on the design of the digital twin.
+Be careful that you do not make implementing the main topic of the bachelor thesis. 
+The main topic should still be digital twinning. 
+
+The digital twin is activated in 2 ways: either the operators prompt the digital twin when they run a workload or the digital twin sends a notification to the datacenter. 
+
+IBM Dublin := you have metrics being managed and policies can decide to do actions. 
+And these actions can be many different things. 
+Currently does not matter what it would -- this could be auto-scaling, scheduling, routing.
+What is the difference between routing and scheduling? 
+
+Great success == we do not include AI inference in the bachelor thesis! 
+Policy decisions can be made using different heuristics --> AI inference. 
+Do not work too much on the policies. 
+
+The focus of the thesis is the digital twinning part. 
+
+Autoscaling vs. failures vs. scheduling. 
+MVP soon.
+
+Why can't we port a digital twin from other domains?
+Show that a digital twin can react. 
+
+Show the readers what would the perfect experiment look like in the perfect. 
+
+What a digital twin is --> give the answer in the background somehow. 
+What do you think a digital twin is? Make it clear.
+Why is a specific datacenter digital twin different from what there already is. 
+
+Versen Thesis Awards they are promoted at ICTO today and tomorrow. 
+
+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.
+