[openstack-dev] [openstackclient] Image create-or-update

Steve Martinelli stevemar at ca.ibm.com
Tue Jun 2 21:34:34 UTC 2015

I'm thinking that the current approach is probably how we want to keep 
things. I can't imagine many other projects being okay with multiple 
create calls with the same name.
Though if you're really adamant about including that support, we could 
include a new flag (--or-update) that performs the update if it's found, 
otherwise it continues with a new create. 

Does that make sense?


Steve Martinelli
OpenStack Keystone Core

Marek Aufart <maufart at redhat.com> wrote on 06/02/2015 10:55:20 AM:

> From: Marek Aufart <maufart at redhat.com>
> To: openstack-dev at lists.openstack.org
> Date: 06/02/2015 10:55 AM
> Subject: [openstack-dev] [openstackclient] Image create-or-update
> Hi,
> I have a question related to openstack image create command v1 from 
> python-openstackclient.
> It behaves like create-or-update (if image with *name* specified for 
> create already existed, it is updated). Actually it looks, that it is in 

> collision with glance, which allows create multiple images with same 
> names instead of update one.
> Is the create-or-update approach still wanted?
> Related code:
> https://github.com/openstack/python-openstackclient/blob/master/
> openstackclient/image/v1/image.py#L247-L269
> Thanks.
> -- 
> Marek Aufart
> Email: maufart at redhat.com
> IRC: maufart / aufi on freenode
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150602/82a22027/attachment.html>

More information about the OpenStack-dev mailing list