<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">lb's use the term pools too. A little more specific might be good.<br>
<br>
Thanks,<br>
Kevin<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF977677"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Victoria Martínez de la Cruz [victoria@vmartinezdelacruz.com]<br>
<b>Sent:</b> Tuesday, October 13, 2015 5:28 AM<br>
<b>To:</b> Flavio Percoco; OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">Fair enough, +1 to Flavio's suggestion
<div><br>
</div>
<div>Thanks all,</div>
<div><br>
</div>
<div>Victoria</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-10-13 3:35 GMT-03:00 Flavio Percoco <span dir="ltr">
<<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<span class="">On 12/10/15 19:25 -0300, Victoria Martínez de la Cruz wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
HI all,<br>
<br>
Thanks for your feedback. We discussed this topic in this week weekly meeting<br>
and we came to the conclusion that it would be better to use "pool-flavor"<br>
instead of creating a namespace for Zaqar only (by prefixing everything with<br>
the "message" key).<br>
<br>
So, this commands would look like<br>
<br>
openstack pool-flavor create<br>
openstack pool-flavor get<br>
openstack pool-flavor delete<br>
openstack pool-flavor update<br>
openstack pool-flavor list<br>
</blockquote>
<br>
</span>First and foremost, I'm sorry for not attending the last meeting.<br>
<br>
I just read the logs from the meeting and I'd like to raise my<br>
concerns with the above. I think it's very confusing for users to have<br>
a non-namespaced command.<br>
<br>
For example, what's a pool-flavor? Is it related to Nova's flavors? Is<br>
it something related to some network pools? etc.<br>
<br>
I understand that one of the concerns is that things like `openstack<br>
message message post` wouldn't look good but I think that the project<br>
namespace could match the service catalog (will let folks for OSC<br>
confirm/deny this).<br>
<br>
Some examples:<br>
<br>
$ openstack messaging post<br>
$ openstack messaging flavor create<br>
$ openstack messaging pool add<br>
<br>
etc<br>
<br>
Does the above make sense?<br>
Flavio
<div class="HOEnZb">
<div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
<br>
Best,<br>
<br>
Victoria<br>
<br>
2015-10-10 10:10 GMT-03:00 Shifali Agrawal <<a href="mailto:shaifali.agrawal09@gmail.com" target="_blank">shaifali.agrawal09@gmail.com</a>>:<br>
<br>
All right, thanks for responses, will code accordingly :)<br>
<br>
On Wed, Oct 7, 2015 at 9:31 PM, Doug Hellmann <<a href="mailto:doug@doughellmann.com" target="_blank">doug@doughellmann.com</a>><br>
wrote:<br>
<br>
Excerpts from Steve Martinelli's message of 2015-10-06 16:09:32 -0400:<br>
><br>
> Using `message flavor` works for me, and having two words is just<br>
fine.<br>
<br>
It might even be good to change "flavor" to "server flavor" (keeping<br>
flavor as a backwards-compatible alias, of course).<br>
Doug<br>
><br>
> I'm in the process of collecting all of the existing "object" works<br>
are<br>
> putting them online, there's a lot of them. Hopefully this will<br>
reduce the<br>
> collisions in the future.<br>
><br>
> Thanks,<br>
><br>
> Steve Martinelli<br>
> OpenStack Keystone Core<br>
><br>
><br>
><br>
> From: Shifali Agrawal <<a href="mailto:shaifali.agrawal09@gmail.com" target="_blank">shaifali.agrawal09@gmail.com</a>><br>
> To: <a href="mailto:openstack-dev@lists.openstack.org" target="_blank">
openstack-dev@lists.openstack.org</a><br>
> Date: 2015/10/06 03:40 PM<br>
> Subject: [openstack-dev] [Zaqar][cli][openstack-client] conflict<br>
in nova<br>
> flavor and zaqar flavor<br>
><br>
><br>
><br>
> Greetings,<br>
><br>
> I am implementing cli commands for Zaqar flavors, the command should<br>
be<br>
> like:<br>
><br>
> "openstack flavor <create/update/delete>"<br>
><br>
> But there is already same command present for Nova flavors. After<br>
> discussing with Zaqar devs we thought to change all zaqar commands<br>
such<br>
> that they include `message` word after openstack, thus above Zaqar<br>
flavor<br>
> command will become:<br>
><br>
> "openstack message flavor <create/update/delete>"<br>
><br>
> Does openstack-client devs have something to say for this? Or they<br>
also<br>
> feel its good to move with adding `message` word to all Zaqar cli<br>
> commands?<br>
><br>
> Already existing Zaqar commands will work with get a deprecation<br>
> message/warning and also I will implement them all to work with<br>
`message`<br>
> word, and all new commands will be implement so that they work only<br>
with<br>
> `message` word.<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">
OpenStack-dev-request@lists.openstack.org</a>?<br>
subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
</blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex; border-left:1px #ccc solid; padding-left:1ex">
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
<br>
<br>
</div>
</div>
<span class="HOEnZb"><font color="#888888">-- <br>
@flaper87<br>
Flavio Percoco<br>
</font></span><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
</body>
</html>