<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
As we did not hear back further on the requirement of this
blueprint, I propose to keep the existing behavior without any
modification.<br>
<br>
We would like to explore the decision on this blueprint on our next
weekly IRC meeting[1].<br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<pre class="moz-signature" cols="72">Regards,
SURO
irc//freenode: suro-patz
[1] - <a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Meetings/Containers">https://wiki.openstack.org/wiki/Meetings/Containers</a><meta http-equiv="content-type" content="text/html; charset=utf-8"></pre><table class="wikitable"><tbody><tr><td>2015-07-28 </td>
<td> UTC 2200 Tuesday </td></tr></tbody></table><pre class="moz-signature" cols="72"> </pre><div class="moz-cite-prefix">On 7/21/15 4:54 PM, SURO wrote:
</div><blockquote cite="mid:55AEDBCC.7030708@gmail.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
Hi all,
[special attention: Jay Lau]
The bp[1] registered, asks for the following implementation -
<ul>
<li>'magnum service-list' should be similar to 'nova service-list'</li>
<li>'magnum service-list' should be moved to be '
<meta http-equiv="content-type" content="text/html; charset=utf-8">
magnum k8s-service-list'. Also similar holds true for
'pod-list'/'rc-list'</li>
</ul>
As I dug some details, I find -
<ul>
<li>'magnum service-list' fetches data from OpenStack DB[2],
instead of the COE endpoint. So technically it is not
k8s-specific. magnum is serving data for objects modeled as
'service', just the way we are catering for 'magnum
container-list' in case of swarm bay.</li>
<li>If magnum provides a way to get the COE endpoint details,
users can use native tools to fetch the status of the
COE-specific objects, viz. 'kubectl get services' here.</li>
<li>nova has lot more backend services, e.g. cert, scheduler,
consoleauth, compute etc. in comparison to magnum's conductor
only. Also, not all the api's have this 'service-list'
available.
</li>
</ul>
With these arguments in view, can we have some more
explanation/clarification in favor of the ask in the blueprint?
[1] -
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://blueprints.launchpad.net/magnum/+spec/magnum-service-list">https://blueprints.launchpad.net/magnum/+spec/magnum-service-list</a>
[2] -
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/openstack/magnum/blob/master/magnum/objects/service.py#L114">https://github.com/openstack/magnum/blob/master/magnum/objects/service.py#L114</a>
<pre class="moz-signature" cols="72">--
Regards,
SURO
irc//freenode: suro-patz
</pre>
</blockquote>
</body></html>