server create problems in boot-from-volume

[Dean Troyer]

A boot-from-volume via 'server create' has a couple of problems: --image is required; and the volume mapping must be an id not a name.

[Dean Troyer (dtroyer)]

I think the UI here needs to be rethought, it was copied from the nova command. --image is used to specify a Glance image, --volume should be used to specify a Cinder volume. The mapping is still required, maybe it can be inferred for the boot volume?

[Dean Troyer (dtroyer)]

https://review.openstack.org/#/c/129672/ is under review

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/129672
Committed: https://git.openstack.org/cgit/openstack/python-openstackclient/commit/?id=2c9d263611190996d64e35bc74a8575aeb25ed3e
Submitter: Jenkins
Branch: master

commit 2c9d263611190996d64e35bc74a8575aeb25ed3e
Author: Dean Troyer <email address hidden>
Date: Mon Oct 20 11:43:29 2014 -0500

    Fix server create for boot-from-volume

    * server create required --image even when booting the server from a
      volume. Change options to require either --image or --volume to
      specify the server boot disk. Using --volume currently uses device
      'vda' for the block mapping and ignores any other block mappings
      given in --block-device-mapping.
    * server create and server show are both affected by bug 1378842 where
      an excepion was thrown when no image ID was present in the returned
      server object, which is the case for a server booted from a volume.
    * Fix the remaining assertEqual() order problems in test_server.py

    Closes-Bug: 1378842
    Closes-Bug: 1383338
    Change-Id: I5daebf4e50a765d4920088dfead95b6295af6a4d