Fang, One possibility we have been thinking about is using our Docker-Swarm bay type to leverage Swarm’s Mesos integration feature as that takes form. https://github.com/docker/swarm/blob/191b2b5fd4cef01eef0ae2a7e86f600d91b55ec1/ROADMAP.md https://github.com/vieux/swarm/blob/98a21bd373c4c26a41942b03f167f64ccd29e079/scheduler/mesos/mesos.go It’s probably best not to duplicate efforts here unless contemplated Magnum bay types turn out to be insufficient for real world use cases. I’d like to hear concrete guidance from users about the specific limitations of the naive scheduler implementation prior to giving a wide variety of choices here. This is also an area where we can collaborate with the Kubenetes development team to aim for an integration point where both Kubernetes and Docker-Swarm bay types can leverage a common plug-in interface for external resource placement in their respective schedulers. The key here is how can we get maximum leverage of prevailing tools without building custom bay types for every single one. We plan to pick the leaders, and have good integrations with those. Thanks, Adrian On Apr 15, 2015, at 7:29 AM, FangFenghua <fang_fenghua at hotmail.com<mailto:fang_fenghua at hotmail.com>> wrote: Apache Mesos maybe is a choice as a Magnum's Container backend. Now it native support Docker contanier . I thinks magnum have a Mesos bay is very Cool. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: OpenStack-dev-request at lists.openstack.org<mailto:OpenStack-dev-request at lists.openstack.org>?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150416/5a0bccaa/attachment.html>