[
https://issues.apache.org/jira/browse/MESOS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14165168#comment-14165168
]
Niklas Quarfot Nielsen commented on MESOS-101:
----------------------------------------------
[~ChrisHeller] Yes and no. Marathon can do this already, but that is not its
main purpose :-)
The issue is that framework writers need to run their framework processes
_somewhere_, keep them alive (in case those processes go down) and maintain HA.
A 'metaframework' or the ability to host framework processes in Mesos itself,
would ease that.
> Create meta-framework (i.e. a framework for launching and managing other
> frameworks)
> ------------------------------------------------------------------------------------
>
> Key: MESOS-101
> URL: https://issues.apache.org/jira/browse/MESOS-101
> Project: Mesos
> Issue Type: Story
> Components: framework
> Reporter: Andy Konwinski
>
> Framework developers should be able to submit their framework to, and have it
> run by, a metaframework (i.e. the metaframework would launch a mesos task
> which would run the new frameworks scheduler passing it the masters address).
> The meta framework could provide a way to kill or update currently running
> frameworks, it might also have its own webui.
> This framework could be written in any language.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
