All, Just to document the discussion we had during the OSC IRC meeting last week: I believe the consensus we reached was that it wasn't appropriate to pretend "volume" before all Cinder commands but that it would be appropriate to move in that direction to for any commands that may be ambiguous like "snapshot". The cinder core development team will start working with the OSC development teams to address such commands and move them to more user friendly commands and as we move forward we will work to avoid such confusion in the future.
Jay On Mon, Mar 28, 2016 at 1:15 PM Dean Troyer <dtro...@gmail.com> wrote: > On Sun, Mar 27, 2016 at 6:11 PM, Mike Perez <thin...@gmail.com> wrote: > >> On 00:40 Mar 28, Jordan Pittier wrote: >> > I am going to play the devil's advocate here but why can"t >> > python-openstackclient have its own opinion on the matter ? This CLI >> seems >> > to be for humans and humans love names/labels/tags and find UUIDS hard >> to >> > remember. Advanced users who want anonymous volumes can always hit the >> API >> > directly with curl or whatever SDK. >> >> I suppose it could, however, names are not unique. >> > > Names are not unique in much of OpenStack. When ambiguity exists, we exit > with an error. > > Also, this works to produce a volume with no name should you absolutely > require it: > > openstack volume create --size 10 "" > > > dt > -- > > Dean Troyer > dtro...@gmail.com > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
