On Tue, Dec 20, 2016 at 2:11 PM, Dean Troyer wrote:
>
> This is exactly how it should work. I do want to make an additional
> important but subtle point: while it looks like those are namespaced
> commands, we used 'server' not 'compute' because it is not a
>
On 20/12/16 05:09 PM, Steve Martinelli wrote:
> This was my initial thought when discussing the problem with Hongbin
> last night.
>
> We have three main "swift" resources in OSC -- "object store account",
> "container" and "object". I think renaming "container" to "object store
> container" is
From: Steve Martinelli [mailto:s.martine...@gmail.com]
Sent: December-20-16 5:09 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [osc][openstackclient][zun] Collision on the
keyword 'container'
On Tue, Dec 20, 2016 at 4:39 PM, Clay Gerrard
On Tue, Dec 20, 2016 at 3:39 PM, Clay Gerrard wrote:
> http://docs.openstack.org/developer/python-openstackclient/command-list.html
> The collision of top-level resource names is not new. You see stuff like
> "volume create" & "server create" - but also "volume backup
On Tue, Dec 20, 2016 at 4:39 PM, Clay Gerrard
wrote:
>
> On Tue, Dec 20, 2016 at 1:00 PM, Hongbin Lu wrote:
>
>>
>>
>> $ openstack objectstore container
>>
>> $ openstack container container
>>
>> $ openstack secret container
>>
>>
>>
>>
On Tue, Dec 20, 2016 at 1:00 PM, Hongbin Lu wrote:
>
>
> $ openstack objectstore container
>
> $ openstack container container
>
> $ openstack secret container
>
>
>
> Thoughts?
>
This is the closest thing I can see that's somewhat reasonable - with the
obvious
On Tue, Dec 20, 2016 at 3:00 PM, Hongbin Lu wrote:
> In the long-term, I am going to propose to follow the style of AWS CLI, that
> is prefixing each command with a project name. For example:
We have been down this particular path multiple times, and this is not
how the
t;openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [osc][openstackclient][zun] Collision on the
keyword 'container'
> Hi OpenStackClients Team,
>
> I am from the Zun team, and my team encountered a name collision issue when
> implementing
> a OSC plugin [1]. We wanted to use the
Hi OpenStackClients Team,
I am from the Zun team, and my team encountered a name collision issue when
implementing a OSC plugin [1]. We wanted to use the keyword 'container' to
represent a linux container used to host a containerized application. In
particular, the commands our contributor