Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Power Saving in the Data Center: Auto-Scaling Available Machine Pool Size #340

Open
Gerrit91 opened this issue Oct 24, 2022 · 1 comment · May be fixed by #356
Open

Power Saving in the Data Center: Auto-Scaling Available Machine Pool Size #340

Gerrit91 opened this issue Oct 24, 2022 · 1 comment · May be fixed by #356
Assignees
@iljarotar

Comments

@Gerrit91
Copy link
Contributor

In order to save energy in the data center, we should implement an algorithm that can reduce the amount of waiting machines in the available machine pool. The algorithm has to act on every partition individually.

On trigger events like machine allocation / deletion / time interval, the algorithm needs to decide whether to reduce or increase the amount of waiting machines as defined by rules provided by the operator. Machines can be reduced or increased by starting and stopping them through machine IPMI.
@Gerrit91
Copy link
Contributor Author

Gerrit91 commented Oct 25, 2022 •
edited
Loading

Initial idea:

  • Add field for partition (waitingPoolSize of type string, can be a number or percentage), unset means disabled
  • In FSM
    • On enter waiting state: check whether machines that are waiting and exceed the pool threshold can be shutdown
    • On leave waiting state: check whether machines that are sleeping and undershoot the pool can be started up

Probably following questions still arise:

  • When considering race conditions, can it happen that a partition is drowning? (machines are asleep and no machines waiting anymore)
  • Maybe it has to be remembered which machines are shutdown by this algorithm (possible conflict with machine resurrection / machine liveliness --> can this be moved into the FSM, too?)

@iljarotar iljarotar linked a pull request Nov 8, 2022 that will close this issue
auto-scaling available machine pool size #356
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iljarotar iljarotar

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

auto-scaling available machine pool size metal-stack/metal-api
2 participants
@Gerrit91 @iljarotar