<html><body><p><font size="2">keystone may have taken "domain", but it didn't take "dns-domain"</font><br><font size="2"><br></font><br><tt><font size="2">Dean Troyer <dtroyer@gmail.com> wrote on 02/12/2018 10:24:05 AM:<br>> <br>> On Mon, Feb 12, 2018 at 9:13 AM, Graham Hayes <gr@ham.ie> wrote:<br>> > OSC only predates Designate by 5 months ...<br>> <br>> My bad, I didn't check dates.<br>> <br>> > "Zone" was what we were recommend to use by the OSC devs at the time we<br>> > wrote our OSC plugin, and at the time we were also *not* supposed to<br>> > name space commands inside service parent (e.g. openstack zone create vs<br>> > openstack dns zone create).<br>> <br>> Namespacing commands and naming options are totally separate things.<br>> It is likely I suggested --zone at the time, and in the context of DNS<br>> commands it is very clear. Also, in the context of Compute commands,<br>> --zone meaning availability zone is also clear.<br>> <br>> > For command flags --dns-zone seems like a good idea - but having a plain<br>> > --zone is confusing when we have a top level "zone" object in the CLI,<br>> > when the type of object that "--zone" refers to is different to<br>> > "openstack zone <action>"<br>> <br>> Again, if there is confusion, things should be more specifically named<br>> to remove the confusion. Maybe allowing "zone" to be assumed to be a<br>> DNS zone was a mistake, I've made plenty of those in OSC already, so<br>> there is precedent, but it seemed reasonable at the time and we (OSC<br>> team) do not control what external plugins do.<br>> <br>> For example, I really resist using abbreviations in OSC, but in some<br>> places to not do so is to buck trends that any semi-experienced user<br>> in the field would expect. The last discussion of this was last week<br>> regarding "MTU" in Network commands.<br>> <br>> These are not hard rules, but strong guidelines that can and should be<br>> interpreted in the context that they will be applied. And in the end,<br>> the result should be one that is understandable, clear and even<br>> expected by the users.<br>> <br>> dt<br>> <br>> -- <br>> <br>> Dean Troyer<br>> dtroyer@gmail.com<br>> <br>> __________________________________________________________________________<br>> OpenStack Development Mailing List (not for usage questions)<br>> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>> <a href="https://urldefense.proofpoint.com/v2/url?">https://urldefense.proofpoint.com/v2/url?</a><br>> u=http-3A__lists.openstack.org_cgi-2Dbin_mailman_listinfo_openstack-2Ddev&d=DwIGaQ&c=jf_iaSHvJObTbx-<br>> siA1ZOg&r=uPMq7DJxi29v-9CkM5RT0pxLlwteWvldJgmFhLURdvg&m=Fr9TF_mDZVJgACWKoyXcnphs-6rMDWufyRhpQEtUask&s=m5wXNx8okCgs7CbNoMhHEQev0xJCFIq61pcmnWBugSs&e=<br>> <br></font></tt><BR>
</body></html>