compute, block storage: Rework scheduler hints #3022
Merged
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.
As noted in #2945 and #2938, scheduler hints in the Compute and Block Storage service are slightly weird in that they are passed as separate top-level keys in the request body, rather than nested in the
server
orvolume
bodies, respectively.Reflect this API nuance in our own API by exposing these hints as a top-level argument to the
Create
functions for servers and volumes. This should ease the path to auto-generation down the line and keeps us a little "truer" to the APIs themselves.