<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 14/10/15 10:15, Dean Troyer wrote:<br>
</div>
<blockquote
cite="mid:CAOJFoEuYF66q9A3HkQbz+qyWAw1irkAkhbXT4o7u-3qPe6+Orw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Oct 13, 2015 at 3:58 PM,
Shifali Agrawal <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:shaifali.agrawal09@gmail.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:shaifali.agrawal09@gmail.com">shaifali.agrawal09@gmail.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>All above make sense, just one thing, how about
using word "zaqar" instead of messaging? That is
what all other projects are doing, for example:</div>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>These are the old project-specific CLIs, note that the
'keystone' command only supports v2 auth today and will be
removed entirely in the keystoneclient 2.0 release. </div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>$ keystone user-create</div>
<div>$ heat event-list</div>
</div>
</div>
</div>
</blockquote>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>This will create a separate namespace for the
project and also will solve the issue of
`openstack messaging message post`.</div>
</div>
</div>
</div>
</blockquote>
</div>
<div><br>
</div>
<div>One of the things I have tried very hard to do is make it
so users do NOT need to know which API handles a given
command. For higher-layer projects that is less of a
concern I suppose, and that was done long before anyone
thought that 20+ APIs would be handled in a single command
set.</div>
<div><br>
</div>
<div>Namespacing has come up and is something we need to
discuss further, either within the 'openstack' command
itself or by using additional top-level command names. This
is one of the topics for discussion in Tokyo, but has
already started on the ML for those that will not be
present.</div>
<div><br>
</div>
<div>No matter how we end up handling the namespacing issue, I
will still strongly insist that project code names not be
used. I know some plugins already do this today and we
can't stop anyone else from doing it, but it leads to the
same sort of inconsistency for users that the original
project CLIs had. It reduces the value of a single (or small
set of) CLI for the user to deal with.</div>
<div><br>
</div>
<br>
</div>
</div>
</blockquote>
I would agree with Dean here. "messaging" is a service, not a thing
the service provides. I'd like to think that commands can be built
using a list of nouns, with the first noun making it sufficiently
obvious of the general family of things you're working on. "queue"
seems to fit as the first noun in this case, so how about:<br>
<br>
openstack queue post<br>
<span class="">openstack queue pool flavor create<br>
openstack </span><span class=""><span class="">queue pool flavor</span>
get<br>
openstack </span><span class=""><span class="">queue pool flavor</span>
delete<br>
openstack </span><span class=""><span class="">queue pool flavor</span>
update<br>
openstack </span><span class=""><span class="">queue pool flavor</span>
list</span><br>
openstack queue pool create<br>
</body>
</html>