<div dir="ltr"><div>+1 to <span class="">Egor, I think that the final goal of Magnum is container as a service but not coe deployment as a service. ;-)<br><br>Especially we are also working on Magnum UI, the Magnum UI should export some interfaces to enable end user can create container applications but not only coe deployment.<br><br></span></div><div><span class="">I hope that the Magnum can be treated as another "Nova" which is focusing on container service.</span> I know it is difficult to unify all of the concepts in different coe (k8s has pod, service, rc, swarm only has container, nova only has VM, PM with different hypervisors), but this deserve some deep dive and thinking to see how can move forward..... <br></div><span class=""></span><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 1:11 AM, Egor Guz <span dir="ltr"><<a href="mailto:EGuz@walmartlabs.com" target="_blank">EGuz@walmartlabs.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">definitely ;), but the are some thoughts to Tom’s email.<br>
<br>
I agree that we shouldn't reinvent apis, but I don’t think Magnum should only focus at deployment (I feel we will become another Puppet/Chef/Ansible module if we do it ):)<br>
I belive our goal should be seamlessly integrate Kub/Mesos/Swarm to OpenStack ecosystem (Neutron/Cinder/Barbican/etc) even if we need to step in to Kub/Mesos/Swarm communities for that.<br>
<br>
—<br>
<span class="">Egor<br>
<br>
From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a><mailto:<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
</span>Date: Tuesday, September 29, 2015 at 08:44<br>
<span class="">To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
<br>
</span><span class="">This is definitely a topic we should cover in Tokyo.<br>
<br>
</span><span class="">On Sep 29, 2015, at 8:28 AM, Daneyon Hansen (danehans) <<a href="mailto:danehans@cisco.com">danehans@cisco.com</a><mailto:<a href="mailto:danehans@cisco.com">danehans@cisco.com</a>>> wrote:<br>
<br>
<br>
+1<br>
<br>
</span>From: Tom Cammann <<a href="mailto:tom.cammann@hpe.com">tom.cammann@hpe.com</a><mailto:<a href="mailto:tom.cammann@hpe.com">tom.cammann@hpe.com</a>>><br>
Reply-To: "<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">Date: Tuesday, September 29, 2015 at 2:22 AM<br>
</span>To: "<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
<br>
</span><span class="">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.<br>
<br>
On 29/09/15 06:30, Ton Ngo wrote:<br>
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>
<ATT00001.gif>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<br>
<br>
</span>From: Egor Guz <<a href="mailto:EGuz@walmartlabs.com">EGuz@walmartlabs.com</a>><mailto:<a href="mailto:EGuz@walmartlabs.com">EGuz@walmartlabs.com</a>><br>
To: "<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>"<mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>> <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span class="">Date: 09/28/2015 10:20 PM<br>
Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s?<br>
________________________________<br>
<br>
<br>
<br>
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 (<a href="https://github.com/mohitsoni/compose-executor" rel="noreferrer" target="_blank">https://github.com/mohitsoni/compose-executor</a>)<br>
which can give you pod like experience.<br>
<br>
—<br>
Egor<br>
<br>
</span>From: Adrian Otto <<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a><mailto:<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>><mailto:<a href="mailto:adrian.otto@rackspace.com">adrian.otto@rackspace.com</a>>><br>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">Date: Monday, September 28, 2015 at 22:03<br>
</span>To: "OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>>><br>
<span class="">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>
</span><span class="">On Sep 28, 2015, at 8:32 PM, 王华 <<a href="mailto:wanghua.humble@gmail.com">wanghua.humble@gmail.com</a><mailto:<a href="mailto:wanghua.humble@gmail.com">wanghua.humble@gmail.com</a>><mailto:<a href="mailto:wanghua.humble@gmail.com">wanghua.humble@gmail.com</a>>> 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>
</span>Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<br>
<span class=""><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>
OpenStack Development Mailing List (not for usage questions)<br>
</span>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><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe><br>
<span class=""><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>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
</span>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><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe><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>
<span class="im"><br>
<ATT00001.gif>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
</span><div class=""><div class="h5">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a><mailto:<a href="mailto:OpenStack-dev-request@lists.openstack.org">OpenStack-dev-request@lists.openstack.org</a>>?subject:unsubscribe<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>
__________________________________________________________________________<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>
</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></div></div></div>