[
https://issues.apache.org/jira/browse/MESOS-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936291#comment-14936291
]
Qian Zhang commented on MESOS-3547:
-----------------------------------
Not sure if I understand the use case correctly. Does it mean that we can
support kind of "nested Mesos clusters"? I mean, there is a host Mesos cluster
which is started as usual, and on top of it, there can be a couple of guest
Mesos clusters which are started as the tasks of the host Mesos cluster?
> Investigate self-hosting Mesos processes
> ----------------------------------------
>
> Key: MESOS-3547
> URL: https://issues.apache.org/jira/browse/MESOS-3547
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Neil Conway
>
> Right now, Mesos master and slave nodes are managed differently: they use
> different binaries and startup scripts and require different ops procedures.
> Some of this asymmetric is essential, but perhaps not all of it is. If Mesos
> supported a concept of "persistent tasks" (see [MESOS-3545]), it might be
> possible to implement the Mesos master as such a task -- this might help
> unify the ops procedures between a master and a slave.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
