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 ). 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.
Use case: 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. Solution: Implement "container" object for k8s and mesos bay (and all the COEs introduced in the future). That's it. I would appreciate if you can share your thoughts on this proposal.  https://blueprints.launchpad.net/magnum/+spec/unified-containers Best regards, Hongbin From: bharath thiruveedula [mailto:bharath_...@hotmail.com] Sent: December-08-15 11:40 PM To: email@example.com Subject: [openstack-dev] Mesos Conductor using container-create operations Hi, As we have discussed in last meeting, we cannot continue with changes in container-create 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. 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. Let me know your suggestions. Regards Bharath T
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev