<html><body><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 width="16" height="16" src="cid:1__=07BBF45CDF8E46918f9e8a93df938690918c07B@" border="0" 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"><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 size="2" color="#5F5F5F">From: </font><font size="2">Egor Guz <EGuz@walmartlabs.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"openstack-dev@lists.openstack.org" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">09/28/2015 10:20 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [magnum]swarm + compose = k8s?</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><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">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 <adrian.otto@rackspace.com<</tt><tt><a href="mailto:adrian.otto@rackspace.com">mailto:adrian.otto@rackspace.com</a></tt><tt>>><br>Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org<</tt><tt><a href="mailto:openstack-dev@lists.openstack.org">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)" <openstack-dev@lists.openstack.org<</tt><tt><a href="mailto:openstack-dev@lists.openstack.org">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, Íõ»ª <wanghua.humble@gmail.com<</tt><tt><a href="mailto:wanghua.humble@gmail.com">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: OpenStack-dev-request@lists.openstack.org<</tt><tt><a href="mailto:OpenStack-dev-request@lists.openstack.org">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">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: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br></tt><br><BR>
</body></html>