[openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-11 Thread Hongbin Lu
Hi all, I was working on the OSC plugin of my project and trying to choose a CLI option to represent the availability zone of the container. When I came across the existing commands, I saw some inconsistencies on the naming. Some commands use the syntax '--zone ', while others use the syntax '--av

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread Graham Hayes
On 12/02/18 04:18, Hongbin Lu wrote: > Hi all, > > I was working on the OSC plugin of my project and trying to choose a CLI > option to represent the availability zone of the container. When I came > across the existing commands, I saw some inconsistencies on the naming. > Some commands use the

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread Dean Troyer
On Sun, Feb 11, 2018 at 10:18 PM, Hongbin Lu wrote: > I was working on the OSC plugin of my project and trying to choose a CLI > option to represent the availability zone of the container. When I came > across the existing commands, I saw some inconsistencies on the naming. Some > commands use the

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread Dean Troyer
On Mon, Feb 12, 2018 at 7:50 AM, Graham Hayes wrote: > Please please move to `availability-zone` - zone is a DNS zone (seen as > Keystone took Domain :) ) within OSC. As stated in another message, changing the Compute usage of --zone makes sense for OSC 4. Two additional things here: * Command

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread Graham Hayes
On 12/02/18 14:51, Dean Troyer wrote: > On Mon, Feb 12, 2018 at 7:50 AM, Graham Hayes wrote: >> Please please move to `availability-zone` - zone is a DNS zone (seen as >> Keystone took Domain :) ) within OSC. > > As stated in another message, changing the Compute usage of --zone > makes sense f

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread Dean Troyer
On Mon, Feb 12, 2018 at 9:13 AM, Graham Hayes wrote: > OSC only predates Designate by 5 months ... My bad, I didn't check dates. > "Zone" was what we were recommend to use by the OSC devs at the time we > wrote our OSC plugin, and at the time we were also *not* supposed to > name space commands

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread William M Edmonds
keystone may have taken "domain", but it didn't take "dns-domain" Dean Troyer wrote on 02/12/2018 10:24:05 AM: > > On Mon, Feb 12, 2018 at 9:13 AM, Graham Hayes wrote: > > OSC only predates Designate by 5 months ... > > My bad, I didn't check dates. > > > "Zone" was what we were recommend to us

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread Graham Hayes
On 12/02/18 16:04, William M Edmonds wrote: > keystone may have taken "domain", but it didn't take "dns-domain" No, but the advice at the time was to move to zone, and match DNS RFCs, and not namespace objects with the service type. We moved from "domain" -> "zone" and "records" -> "recordsets" i

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

2018-02-12 Thread William M Edmonds
Graham Hayes wrote on 02/12/2018 11:17:45 AM: > On 12/02/18 16:04, William M Edmonds wrote: > > keystone may have taken "domain", but it didn't take "dns-domain" > > No, but the advice at the time was to move to zone, and match DNS > RFCs, and not namespace objects with the service type. > I was