This repository was archived by the owner on Feb 11, 2022. It is now read-only.
Limits the number of concurrent vm creations to make sure vms are create... #146
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ated successfully
|
I'm having the same issue - I'm testing madjurranjan's fix and I'll report back on how it performs. We're currently trying to spin up between 10 and 80 nodes on AWS using vagrant and currently have to do it serially which is very painful. |
|
I understand why you want this change in but I'm not sure if this is the right way to accomplish it. I am not sure but I believe the |
|
Didn't quite find any options hence went with this option . Tried looking at it again but didn't find. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are using Vagrant-aws to create anywhere between 8-60 machines in parallel. A large number of instances begin to fail when there are more than 10-11 simultaneous calls. In order to allow this to happen, introduced class variable that keeps track of instances and allow only 10 creations at a time. We also saw instance timeout failures so increased the wait_for timeout. This setup is currently working for upto 60 parallel VMs. Let me know your thoughts.