Allow allocating to non-active hosts with dynamic provisioning #8743
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.
With dynamic provisioning, we can allocate a container to a host that already has node(s) by this tenant as long as that host is
active
. Because we prepare for eachClusterSpec
separately, we will end up provisioning new hosts just for thelogserver
container, since any host just provisioned for acontainer
/content
node is still inprovisioned
. This PR relaxes that requirement:For non-dynamic provisioning: No change (host must still be
active
)For dynamic provisioning: Host can be any of
provisioned
,ready
oractive
.Not sure if this is possible, but ideally we should make sure that
logserver
is prepared last since it is most likely to be able to fit on any previously provisioned host.