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

Update README.md #252

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update README.md #252

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,3 +64,9 @@ compute_nodes_large:
flavor: c.c24m120
tag: compute-large
```

### Why is this not simply using Terraform?
> Because terraform couldn't downsize a cluster by chosing specific VMs, it had to be via count, which meant removing VMs from the "end".
thus I wrote ensure-enough [now synchronize.py] so we could remove unused VMs that weren't at the end of the count variable, and shrink the cluster more easily. hence non-linear numbering, it's part of the expectation that they'll get added or removed randomly, based on usage. (But then I spent most of the time with a fixed sized cluster because the Cloud isn't actually dynamic, at least in Freiburg. But that was before we were committed to taking up a large number of nodes) -- <cite>[@hexylena][1]</cite>

[1]: https://github.com/hexylena
Loading