diff options
| author | Matt Riedemann <mriedem.os@gmail.com> | 2019-07-29 12:59:52 -0400 |
|---|---|---|
| committer | Dean Troyer <dtroyer@gmail.com> | 2019-08-09 16:36:17 +0000 |
| commit | 6a199bd14152889f18ad95919a4bee9c0c083d5d (patch) | |
| tree | dc3e16951eaec250d7c151962365d94eecb50ebe /openstackclient/tests/functional/common | |
| parent | c4743199096e77bdc89423dc37f632ac24acdba1 (diff) | |
| download | python-openstackclient-6a199bd14152889f18ad95919a4bee9c0c083d5d.tar.gz | |
Support type=image with --block-device-mapping option
The --block-device-mapping option on the server create
command currently only supports booting from volume and
volume snapshot. A common boot-from-volume scenario is
providing an image and letting nova orchestrate the
creation of the image-backed volume and attaching it to
the server.
This adds support for type=image in the --block-device-mapping
option. The volume size is required in this case. Note that
the CLI currently says if type=snapshot that size is also required
but that's technically not true. When booting from a volume
snapshot, the compute API will use the size of the volume snapshot
to create the volume if an explicit size is not provided. For the
purposes of this patch, we need the size anyway for the image
being the block device mapping source type.
Change-Id: I57b3c261d8309f7b9f62a3e91612bce592a887a3
Story: 2006302
Task: 36016
Diffstat (limited to 'openstackclient/tests/functional/common')
0 files changed, 0 insertions, 0 deletions