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.
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
Support specification of multiple scaling strategies #566
Support specification of multiple scaling strategies #566
Changes from all commits
5852999
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure I understand this comment.
all_or_nothing_batch
is actually a boolean that is passed downstream toFleetManagerFactory
asall_or_nothing
..so maybe it would be better to rename this parameter accordingly since is not clear if/what the_batch
addsWhile, regards doing
scaling_strategy in [ScalingStrategy.ALL_OR_NOTHING]
instead of
scaling_strategy == ScalingStrategy.ALL_OR_NOTHING:
as done a few lines above, I assume that this is because we are planning to add another strategy that falls in the "all or nothing" category.
Is this the meaning of the comment above ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In
all_or_nothing_batch
the_batch
alludes to the way we chunk the launch attempts in "batches" of a certain size/count of instances. Soall_or_nothing_batch
implies that each batch will be done in an all-or-nothing fashion.Exactly, it was done with this in mind. That expression will be reused in the upcoming PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See comment above.