<div dir="ltr">I agree with Tom to see Magnum as COEDaaS. k8s, swarm, mesos are so different in their architectures that magnum can not provide unified API to user. So I think we should focus on deployment.<div><br></div><div>Regards,</div><div>Wanghua</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 29, 2015 at 5:22 PM, Tom Cammann <span dir="ltr"><<a href="mailto:tom.cammann@hpe.com" target="_blank">tom.cammann@hpe.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
This has been my thinking in the last couple of months to completely
deprecate the COE specific APIs such as pod/service/rc and
container.<br>
<br>
As we now support Mesos, Kubernetes and Docker Swarm its going to be
very difficult and probably a wasted effort trying to consolidate
their separate APIs under a single Magnum API. <br>
<br>
I'm starting to see Magnum as COEDaaS - Container Orchestration
Engine Deployment as a Service.<div><div class="h5"><br>
<br>
<div>On 29/09/15 06:30, Ton Ngo wrote:<br>
</div>
<blockquote type="cite">
<p>Would it make sense to ask the opposite of Wanghua's question:
should pod/service/rc be deprecated if the user can easily get
to the k8s api? <br>
Even if we want to orchestrate these in a Heat template, the
corresponding heat resources can just interface with k8s instead
of Magnum.<br>
Ton Ngo,<br>
<br>
<img src="cid:part1.07020809.04090006@hpe.com" alt="Inactive
hide details for Egor Guz ---09/28/2015 10:20:02 PM---Also I
belive docker compose is just command line tool which doe" border="0" height="16" width="16"><font color="#424282">Egor
Guz ---09/28/2015 10:20:02 PM---Also I belive docker compose
is just command line tool which doesn’t have any api or
scheduling feat</font><br>
<br>
<font color="#5F5F5F" size="2">From: </font><font size="2">Egor
Guz <a href="mailto:EGuz@walmartlabs.com" target="_blank"><EGuz@walmartlabs.com></a></font><br>
<font color="#5F5F5F" size="2">To: </font><font size="2"><a href="mailto:openstack-dev@lists.openstack.org" target="_blank">"openstack-dev@lists.openstack.org"</a>
<a href="mailto:openstack-dev@lists.openstack.org" target="_blank"><openstack-dev@lists.openstack.org></a></font><br>
<font color="#5F5F5F" size="2">Date: </font><font size="2">09/28/2015
10:20 PM</font><br>
<font color="#5F5F5F" size="2">Subject: </font><font size="2">Re:
[openstack-dev] [magnum]swarm + compose = k8s?</font><br>
</p>
<hr style="color:#8091a5" align="left" noshade size="2" width="100%"><br>
<br>
<br>
<tt>Also I belive docker compose is just command line tool which
doesn’t have any api or scheduling features.<br>
But during last Docker Conf hackathon PayPal folks implemented
docker compose executor for Mesos (</tt><tt><a href="https://github.com/mohitsoni/compose-executor" target="_blank">https://github.com/mohitsoni/compose-executor</a></tt><tt>)<br>
which can give you pod like experience.<br>
<br>
—<br>
Egor<br>
<br>
From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com" target="_blank">adrian.otto@rackspace.com</a><</tt><tt><a href="mailto:adrian.otto@rackspace.com" target="_blank">mailto:adrian.otto@rackspace.com</a></tt><tt>>><br>
Reply-To: "OpenStack Development Mailing List (not for usage
questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><</tt><tt><a href="mailto:openstack-dev@lists.openstack.org" target="_blank">mailto:openstack-dev@lists.openstack.org</a></tt><tt>>><br>
Date: Monday, September 28, 2015 at 22:03<br>
To: "OpenStack Development Mailing List (not for usage
questions)" <<a href="mailto:openstack-dev@lists.openstack.org" target="_blank">openstack-dev@lists.openstack.org</a><</tt><tt><a href="mailto:openstack-dev@lists.openstack.org" target="_blank">mailto:openstack-dev@lists.openstack.org</a></tt><tt>>><br>
Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
<br>
Wanghua,<br>
<br>
I do follow your logic, but docker-compose only needs the docker
API to operate. We are intentionally avoiding re-inventing the
wheel. Our goal is not to replace docker swarm (or other
existing systems), but to compliment it/them. We want to offer
users of Docker the richness of native APIs and supporting
tools. This way they will not need to compromise features or
wait longer for us to implement each new feature as it is added.
Keep in mind that our pod, service, and replication controller
resources pre-date this philosophy. If we started out with the
current approach, those would not exist in Magnum.<br>
<br>
Thanks,<br>
<br>
Adrian<br>
<br>
On Sep 28, 2015, at 8:32 PM, 王华 <<a href="mailto:wanghua.humble@gmail.com" target="_blank">wanghua.humble@gmail.com</a><</tt><tt><a href="mailto:wanghua.humble@gmail.com" target="_blank">mailto:wanghua.humble@gmail.com</a></tt><tt>>>
wrote:<br>
<br>
Hi folks,<br>
<br>
Magnum now exposes service, pod, etc to users in kubernetes coe,
but exposes container in swarm coe. As I know, swarm is only a
scheduler of container, which is like nova in openstack. Docker
compose is a orchestration program which is like heat in
openstack. k8s is the combination of scheduler and
orchestration. So I think it is better to expose the apis in
compose to users which are at the same level as k8s.<br>
<br>
<br>
Regards<br>
Wanghua<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">OpenStack-dev-request@lists.openstack.org</a><</tt><tt><a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank">mailto:OpenStack-dev-request@lists.openstack.org</a></tt><tt>>?subject:unsubscribe<br>
</tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:
<a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
</tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br>
</tt><br>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>__________________________________________________________________________<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.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>