<div dir="ltr"><div><div><div>Hi everyone!<br><br></div>When I started contribution to OpenStack long time ago, I asked about the reason of having two entities - service type and name; at that time I got an answer that service name is a name of the project that implements particular service type, so it is possible to have several projects which implement one service type. That answer satisfied me. <br><br></div><span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-">The reality of</span> OpenStack is <span class="gmail-">that there is no and there will not be several implementations of one "service type". Even when we had nova-net and neutron, only the neutron registered his service in the catalog. <br><br>An example of Octavia shows that everybody was ok about having service name equal with type before inconsistency was found. That is why I want to ask again: Do we need two separate entities and if yes - why? Maybe service name and description fields should be enough?<br></span></span></div><span id="gmail-result_box" class="gmail-short_text" lang="en"><span class="gmail-"></span></span><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 15, 2017 at 3:08 AM, Qiming Teng <span dir="ltr"><<a href="mailto:tengqim@linux.vnet.ibm.com" target="_blank">tengqim@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">When reviewing a recent patch that adds openstacksdk support to octavia,<br>
I found that octavia is using 'octavia' as its service name instead of<br>
'loadbalancing' or 'loadbalancingv2' or something similar.<br>
<br>
The overall suggestion is to use a word/phrase that indicates what a<br>
service do instead of the name of the project providing that service.<br>
<br>
Below is the list of the service types currently supported by<br>
openstacksdk:<br>
<br>
'alarming', # aodh<br>
'baremetal', # ironic<br>
'clustering', # senlin<br>
'compute', # nova<br>
'database', # trove<br>
'identity', # keystone<br>
'image', # glance<br>
'key-manager', # barbican<br>
'messaging', # zaqar<br>
'metering', # ceilometer<br>
'network', # neutron<br>
'object-store', # swift<br>
'octavia', # <--- this is an exception<br>
'orchestration', # heat<br>
'volume', # cinder<br>
'workflowv2', # mistral<br>
<br>
While I believe this has been discussed about a year ago, I'm not sure<br>
if there are things we missed so I'm brining this issue to a broader<br>
audience for discussion.<br>
<br>
Reference:<br>
<br>
[1] Patch to python-openstacksdk:<br>
<a href="https://review.openstack.org/#/c/428414" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/428414</a><br>
[2] Octavia service naming:<br>
<a href="http://git.openstack.org/cgit/openstack/octavia/tree/devstack/plugin.sh#n52" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack/octavia/tree/<wbr>devstack/plugin.sh#n52</a><br>
<br>
Regards,<br>
Qiming<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<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.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr">Best regards,<br>Andrey Kurilin.<br></div></div>
</div></div></div></div></div></div>