Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Tuesday, April 5, 2016, Duncan Thomas wrote: > What about commands the become ambiguous in the future? I doubt there are > many operations or objects that are unique to Cinder - backup, snapshot, > transfer, group, type - these are all very much generic, and even if

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

Duncan, Agreed, but the OSC team is concerned about unnecessarily adding API names into commands as much as the Cinder team wishes to make it clearer which commands belong to our component. This is where we need to keep this discussion open with the OSC team to find a good common ground. I am

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

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

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

What about commands the become ambiguous in the future? I doubt there are many operations or objects that are unique to Cinder - backup, snapshot, transfer, group, type - these are all very much generic, and even if they aren't ambiguous now, they might well become so in future... On 5 April 2016

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Sun, Mar 27, 2016 at 9:44 AM, Duncan Thomas wrote: > I think it is worth fixing the client to actually match the API, yes. The > client seems to be determined not to actually match the API in lots of > ways, e.g.

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Mon, Mar 28, 2016 at 4:29 AM, Duncan Thomas wrote: > Because it leads to false assumptions, and code that breaks when something > breaks those assumptions (e.g. somebody creates a volume with no name on > horizon and breaks all the users of openstackclient that

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

On Sun, Mar 27, 2016 at 6:11 PM, Mike Perez 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

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

Because it leads to false assumptions, and code that breaks when something breaks those assumptions (e.g. somebody creates a volume with no name on horizon and breaks all the users of openstackclient that expects one because their client suggested it was mandatory On 28 March 2016 at 01:40,

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

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

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

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

Re: [openstack-dev] [cinder][openstackclient] Required name option for volumes, snapshots and backups

I think it is worth fixing the client to actually match the API, yes. The client seems to be determined not to actually match the API in lots of ways, e.g. https://bugs.launchpad.net/python-openstackclient/+bug/1561666 On 24 March 2016 at 19:08, Ivan Kolodyazhny wrote: > Hi