> From: 王华 <wanghua.hum...@gmail.com> > To: "OpenStack Development Mailing List (not for usage questions)" > <openstack-dev@lists.openstack.org> > Date: 09/28/2015 11:34 PM > Subject: [openstack-dev] [magnum]swarm + compose = k8s? > > Hi folks, > > 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. >
Why should the users be deprived of direct access to the Swarm API when it is there? Note also that Compose addresses more general, and differently focused, orchestration than Kubernetes; the latter only offers homogenous scaling groups --- which a docker-compose.yaml file can not even describe. Regards, Mike
__________________________________________________________________________ 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
