<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/27/2014 05:02 PM, Ana Krivokapic
wrote:<br>
</div>
<blockquote cite="mid:530F6179.6060305@redhat.com" type="cite">
<br>
On 02/27/2014 04:41 PM, Tzu-Mainn Chen wrote:
<br>
<blockquote type="cite">
<blockquote type="cite">Hello,
<br>
<br>
I think if we will use Openstack CLI, it has to be something
like this
<br>
<a class="moz-txt-link-freetext" href="https://github.com/dtroyer/python-oscplugin">https://github.com/dtroyer/python-oscplugin</a>.
<br>
Otherwise we are not Openstack on Openstack.
<br>
<br>
Btw. abstracting it all to one big CLI will be just more
confusing when
<br>
people will debug issues. So it would
<br>
have to be done very good.
<br>
<br>
E.g calling 'openstack-client net-create' fails.
<br>
Where do you find error log?
<br>
Are you using nova-networking or Neutron?
<br>
..
<br>
<br>
Calli 'neutron net-create' and you just know.
<br>
<br>
Btw. who would actually hire a sysadmin that will start to use
CLI and
<br>
have no
<br>
idea what is he doing? They need to know what each service do,
how to
<br>
correctly
<br>
use them and how do debug it when something is wrong.
<br>
<br>
<br>
For flavors just use flavors, we call them flavors in code
too. It has
<br>
just nicer face in UI.
<br>
</blockquote>
Actually, don't we called them node_profiles in the UI code?
<br>
</blockquote>
<br>
We do:
<a class="moz-txt-link-freetext" href="https://github.com/openstack/tuskar-ui/tree/master/tuskar_ui/infrastructure/node_profiles">https://github.com/openstack/tuskar-ui/tree/master/tuskar_ui/infrastructure/node_profiles</a><br>
<blockquote type="cite"> Personally,
<br>
I'd much prefer that we call them flavors in the code.
<br>
</blockquote>
I agree, keeping the name "flavor" makes perfect sense here, IMO.
The only benefit of using "node profile" seems to be that it is
more descriptive. However, as already mentioned, admins are well
used to the name "flavor". It seems to me that this change
introduces more confusion than it serves to clear things up. In
other words, it brings more harm than good.
<br>
<br>
</blockquote>
<br>
I see, we have brought an API flavor wrapper
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://github.com/openstack/tuskar-ui/blob/master/tuskar_ui/api.py#L91">https://github.com/openstack/tuskar-ui/blob/master/tuskar_ui/api.py#L91</a><br>
<br>
Nevertheless keeping 'flavor' make sense.<br>
<br>
<blockquote cite="mid:530F6179.6060305@redhat.com" type="cite">
<blockquote type="cite">
<br>
Mainn
<br>
<br>
_______________________________________________
<br>
OpenStack-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>