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

[#175041036] Vertically scale non-dev BOSH directors #398

Merged
merged 2 commits into from
Oct 12, 2020
Merged

Conversation

tlwr
Copy link
Contributor

@tlwr tlwr commented Oct 9, 2020

Story

What

BOSH.io suggests that Directors should have at least 8gb of RAM, which I agree with, especially in London where it has to monitor lots of VMs and run more tasks

t3.medium -> m5.large increases the amount of network bandwith, memory, and CPU available to BOSH which should help high memory jobs like bosh clean-up and bosh cck

How to review

Code review

CI

Toby Lorne added 2 commits October 9, 2020 16:38
If we want to write a test for a change in a specific account, we would
like to generate a manifest for that particular account, rather than dev

Signed-off-by: Toby Lorne <toby.lornewelch-richards@digital.cabinet-office.gov.uk>
https://bosh.io/docs/quick-start/

suggests that Director should have at least 8gb of RAM, which I agree
with, especially in London where it has to monitor lots of VMs and run
more tasks

t3.medium -> m5.large increases the amount of network bandwith, memory,
and CPU available to BOSH which should help high memory jobs like
"bosh clean-up" and "bosh cck"

Signed-off-by: Toby Lorne <toby.lornewelch-richards@digital.cabinet-office.gov.uk>
@tlwr tlwr changed the title Vertically scale non-dev BOSH directors [#175041036] Vertically scale non-dev BOSH directors Oct 9, 2020
@tlwr tlwr merged commit 0baae1a into master Oct 12, 2020
@tlwr tlwr deleted the bish-bash-big-bosh branch October 12, 2020 07:38
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