Issue LIBCLOUD-402: Support OS-DCF:diskConfig #152
Closed
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.
Rackspace is implementing a change to server creation where disk partitioning will not automatically fill the entire disk, leaving the option to the user to expand the disk or not. When creating nodes, you have the ability to specify if you want a MANUAL disk config, or if you want an AUTO disk config. The former results in quicker server creation,
while the latter results in the entire disk being used.
This change is exposed via an extension to the OpenStack compute APIs, which Rackspace's Cloud Servers are built on top of. "
OS-DCF:diskConfig
" is an attribute to be set in message bodies POST'ed to /servers, and is exposed as the "ex_disk_config
" parameter toOpenStack_1_1_NodeDriver.create_node
.