blob: 6c55eb39f3fd3a91e87d701b84a90d17825b260a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
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.
|
