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

Allow initial deploy to "update" all VMs across all AZs in parallel #1943

Closed
drnic opened this issue Apr 26, 2018 · 2 comments
Closed

Allow initial deploy to "update" all VMs across all AZs in parallel #1943

drnic opened this issue Apr 26, 2018 · 2 comments

Comments

@drnic
Copy link
Contributor

drnic commented Apr 26, 2018

Currently a deployment will create VMs in parallel, but the "update" step is done 1 AZ at a time (and subsequently restricted by canary/max_in_flight).

For an initial deployment, it can be desirable to allow VMs across AZs to start up (initial "update") in batches that span AZs. E.g. a 5-node zookeeper cluster would start up all 5 nodes across 3 azs.

@cppforlife
Copy link
Contributor

@mfine30
Copy link
Contributor

mfine30 commented Oct 2, 2018

Closing in favor of the linked bosh-note above

@mfine30 mfine30 closed this as completed Oct 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants