<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Jay,<br>
<br>
'service'/'pod'/'rc' are conceptual abstraction at magnum level.
Yes, the abstraction was inspired from the same in kubernetes, but
the data stored in DB about a 'service' is properly abstracted and
not k8s-specific at the top level. <br>
<br>
If we plan to change this to 'k8s-service-list', the same applies
for even creation and other actions. This will give rise to
COE-specific command and concepts and which may proliferate further.
Instead, we can abstract swarm's service concept under the umbrella
of magnum's 'service' concept without creating k8s-service and
swarm-service.<br>
<br>
I suggest we should keep the concept/abstraction at Magnum level, as
it is. <br>
<pre class="moz-signature" cols="72">Regards,
SURO
irc//freenode: suro-patz
</pre>
<div class="moz-cite-prefix">On 7/28/15 7:59 PM, Jay Lau wrote:<br>
</div>
<blockquote
cite="mid:CAFyztAHgNGkgTemj0h=0R58Sm+QpZ_u_SVO4J24FrTqLZxNPxw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>
<div>Hi Suro,<br>
<br>
</div>
Sorry for late. IMHO, even the "magnum service-list" is
getting data from DB, but the DB is actually persisting some
data for Kubernetes service, so my thinking is it possible to
change "magnum service-list" to "magnum k8s-service-list",
same for pod and rc.<br>
<br>
</div>
<div>I know this might bring some trouble for backward
compatibility issue, not sure if it is good to do such
modification at this time. Comments?<br>
<br>
</div>
Thanks</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2015-07-27 20:12 GMT-04:00 SURO <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:suro.patz@gmail.com" target="_blank">suro.patz@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div 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>
<pre cols="72">Regards,
SURO
irc//freenode: suro-patz
[1] - <a moz-do-not-send="true" href="https://wiki.openstack.org/wiki/Meetings/Containers" target="_blank">https://wiki.openstack.org/wiki/Meetings/Containers</a></pre>
<table>
<tbody>
<tr>
<td>2015-07-28 </td>
<td> UTC 2200 Tuesday </td>
</tr>
</tbody>
</table>
<div>
<div class="h5">
<pre cols="72"> </pre>
<div>On 7/21/15 4:54 PM, SURO wrote:
</div>
<blockquote type="cite"> 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 '
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"
href="https://blueprints.launchpad.net/magnum/+spec/magnum-service-list"
target="_blank">https://blueprints.launchpad.net/magnum/+spec/magnum-service-list</a>
[2] -
<a moz-do-not-send="true"
href="https://github.com/openstack/magnum/blob/master/magnum/objects/service.py#L114"
target="_blank">https://github.com/openstack/magnum/blob/master/magnum/objects/service.py#L114</a>
<pre cols="72">--
Regards,
SURO
irc//freenode: suro-patz
</pre>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Thanks,<br>
<br>
</div>
Jay Lau (Guangya Liu)<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>