<html><body><p>I think extending the container object to Mesos via command like container-create is a fine idea. Going into details, however, we run into some complication.<br>1. The user would still have to choose a DSL to express the container. This would have to be a kube and/or swarm DSL since we don't want to invent a new one.<br>2. For Mesos bay in particular, kube or swarm may be running on top of Mesos along side with Marathon, so somewhere along the line, Magnum has to be able to make the distinction and handle things appropriately.<br><br>We should think through the scenarios carefully to come to agreement on how this would work.<br><br>Ton Ngo,<br><br><br><img width="16" height="16" src="cid:1__=07BBF58BDF9658238f9e8a93df938690918c07B@" border="0" alt="Inactive hide details for Hongbin Lu ---12/09/2015 03:09:23 PM---As Bharath mentioned, I am +1 to extend the "container" object"><font color="#424282">Hongbin Lu ---12/09/2015 03:09:23 PM---As Bharath mentioned, I am +1 to extend the "container" object to Mesos bay. In addition, I propose</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">Hongbin Lu <hongbin.lu@huawei.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">12/09/2015 03:09 PM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] Mesos Conductor using container-create operations</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><font color="#1F497D" face="Calibri">As Bharath mentioned, I am +1 to extend the “container” object to Mesos bay. In addition, I propose to extend “container” to k8s as well (the details are described in this BP [1]). The goal is to promote this API resource to be technology-agnostic and make it portable across all COEs. I am going to justify this proposal by a use case.</font><br><font size="4" color="#222222" face="Arial"> </font><br><font color="#1F497D" face="Calibri">Use case:</font><br><font color="#1F497D" face="Calibri">I have an app. I used to deploy my app to a VM in OpenStack. Right now, I want to deploy my app to a container. I have basic knowledge of container but not familiar with specific container tech. I want a simple and intuitive API to operate a container (i.e. CRUD), like how I operated a VM before. I find it hard to learn the DSL introduced by a specific COE (k8s/marathon). Most importantly, I want my deployment to be portable regardless of the choice of cluster management system and/or container runtime. I want OpenStack to be the only integration point, because I don’t want to be locked-in to specific container tech. I want to avoid the risk that a specific container tech being replaced by another in the future. Optimally, I want Keystone to be the only authentication system that I need to deal with. I don't want the extra complexity to deal with additional authentication system introduced by specific COE.</font><br><font size="4" color="#222222" face="Arial"> </font><br><font color="#1F497D" face="Calibri">Solution:</font><br><font color="#1F497D" face="Calibri">Implement "container" object for k8s and mesos bay (and all the COEs introduced in the future).</font><br><font size="4" color="#222222" face="Arial"> </font><br><font color="#1F497D" face="Calibri">That's it. I would appreciate if you can share your thoughts on this proposal.</font><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">[1] </font><a href="https://blueprints.launchpad.net/magnum/+spec/unified-containers"><u><font color="#0000FF" face="Calibri">https://blueprints.launchpad.net/magnum/+spec/unified-containers</font></u></a><br><font color="#1F497D" face="Calibri"> </font><br><font color="#1F497D" face="Calibri">Best regards,</font><br><font color="#1F497D" face="Calibri">Hongbin</font><br><font color="#1F497D" face="Calibri"> </font><br><b><font face="Tahoma">From:</font></b><font face="Tahoma"> bharath thiruveedula [</font><font face="Tahoma"><a href="mailto:bharath_ves@hotmail.com">mailto:bharath_ves@hotmail.com</a></font><font face="Tahoma">] </font><b><font face="Tahoma"><br>Sent:</font></b><font face="Tahoma"> December-08-15 11:40 PM</font><b><font face="Tahoma"><br>To:</font></b><font face="Tahoma"> openstack-dev@lists.openstack.org</font><b><font face="Tahoma"><br>Subject:</font></b><font face="Tahoma"> [openstack-dev] Mesos Conductor using container-create operations</font><br><font size="4" face="Times New Roman"> </font><br><font size="4" face="Calibri">Hi,</font><br><font size="4" face="Calibri"> </font><br><font size="4" face="Calibri">As we have discussed in last meeting, we cannot continue with changes in container-create[1] as long as we have suitable use case. But I honestly feel to have some kind of support for mesos + marathon apps, because magnum supports COE related functionalities for docker swarm (container-create) and k8s (pod-create, rc-create..) but not for mesos bays.</font><br><font size="4" face="Calibri"> </font><br><font size="4" face="Calibri">As hongbin suggested, we use the existing functionality of container-create and support in mesos-conductor. Currently we have container-create only for docker swarm bay. Let's have support for the same command for mesos bay with out any changes in client side.</font><br><font size="4" face="Calibri"> </font><br><font size="4" face="Calibri">Let me know your suggestions.</font><br><font size="4" face="Calibri"> </font><br><font size="4" face="Calibri">Regards</font><br><font size="4" face="Calibri">Bharath T</font><tt>__________________________________________________________________________<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>