[
https://issues.apache.org/jira/browse/MESOS-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155985#comment-14155985
]
Timothy St. Clair commented on MESOS-876:
-----------------------------------------
[~jogo] re: containerizing Open Stack, from what I've heard re: Wilkes, even
VM's are spun from containers at google. If we follow that path, then tracking
and management would be the difficult part, given the libvirt spins under it's
daemon and not in user space.
> 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)