<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
[special attention: Jay Lau]<br>
<br>
The bp[1] registered, asks for the following implementation -<br>
<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 -<br>
<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.<br>
</li>
</ul>
With these arguments in view, can we have some more
explanation/clarification in favor of the ask in the blueprint? <br>
<br>
[1] -
<a 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><br>
[2] -
<a 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><br>
<pre class="moz-signature" cols="72">--
Regards,
SURO
irc//freenode: suro-patz
</pre>
</body>
</html>