On 25 September 2014 16:13, Clint Byrum <[email protected]> wrote: > Excerpts from Mike Spreitzer's message of 2014-09-24 20:49:20 -0700:
>> As far as I can tell, the quantitative handling of capacities and >> demands in Kubernetes is much inferior to what Nova does today. >> > > Yes, TripleO needs to manage baremetal and containers from a single > host. Nova and Neutron do not offer this as a feature unfortunately. Well, we made that work, but see my earlier reply about issues and needing direction from Nova/Neutron. >> > As far as use cases go, the main use case is to run a specific >> > Docker container on a specific Kubernetes "minion" bare metal host. >> >> If TripleO already knows it wants to run a specific Docker image >> on a specific host then TripleO does not need a scheduler. >> > > TripleO does not ever specify destination host, because Nova does not > allow that, nor should it. It does want to isolate failure domains so > that all three Galera nodes aren't on the same PDU, but we've not really > gotten to the point where we can do that yet. Nit: Nova allows it, and Heat can pass it through. It just shouldn't be used ;). -Rob -- Robert Collins <[email protected]> Distinguished Technologist HP Converged Cloud _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
