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.

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

configurable reserve of machines per size per partition #134

Closed
wants to merge 3 commits into from

Conversation

majst01
Copy link
Contributor

@majst01 majst01 commented Nov 6, 2020

Currently consumers, like cluster-api, of metal-api actually just check if enough workers for the current request are available. With this approach we will end up with a situation that all workers are allocation in a partition.
But this will prevent further actions like rolling updates of worker nodes or firewalls.
To prevent this a configurable amount of machines must stay as reserved to be able to perform these updates.
The reserved machines are now configurable per size and partition.
But this implementation only performs the configuration of these reservation and does not enforce them. This enforcement is still a responsibility of the caller side.

@majst01
Copy link
Contributor Author

majst01 commented Nov 6, 2020

we should add a fixed amount on top of this value during cluster creation.

@Gerrit91
Copy link
Contributor

Gerrit91 commented Nov 6, 2020

Somehow I don't understand what this is doing. Any explanation such that I can understand it?

@Gerrit91
Copy link
Contributor

We've decided to implement this directly in the cloud-api (probably in config file) because this approach has no direct advantage for adopters.

@Gerrit91 Gerrit91 closed this Dec 10, 2020
@majst01 majst01 deleted the partition-reserve branch February 4, 2021 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants