[
https://issues.apache.org/jira/browse/MESOS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161864#comment-14161864
]
Timothy St. Clair commented on MESOS-876:
-----------------------------------------
Game on folks:
http://lists.openstack.org/pipermail/openstack-dev/2014-September/046911.html
+ http://www.projectatomic.io/blog/2014/10/libvirtd_in_containers/
I'm guessing any Kube deployment will be less flexible then a straight up
framework.
> Investigate OpenStack Integration
> ---------------------------------
>
> Key: MESOS-876
> URL: https://issues.apache.org/jira/browse/MESOS-876
> Project: Mesos
> Issue Type: Improvement
> Components: general
> Affects Versions: 0.17.0
> Reporter: Timothy St. Clair
> Assignee: Timothy St. Clair
>
> OpenStack for some time had it's own scheduling mechanics which allowed you
> to "plug-in" different algorithms, but has never really separated out the
> scheduling to allow a different scheduler as the substrate (at least when I
> last investigated).
> However there have been new grumblings found here:
> https://blueprints.launchpad.net/nova/+spec/forklift-scheduler-breakout ,
> which may enable this ability.
> This ticket is meant to track that progress and determine whether it's
> possible for mesos<>openstack to play nicely together.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)