Thanks so much for the clarification, Benjamin. Wenzhao
On Fri, Jul 21, 2017 at 11:22 AM, Benjamin Bannier < [email protected]> wrote: > Hi Wenzhao, > > > I agree your statement, Marathon is only a management layer over Mesos. > > I believe I did not write that. > > > But, we can run a framework on Mesos via invoking Marathon's REST API. > > How does this happen? I think Marathon internally calls Mesos's API to > start the framework. But I don't see Mesos REST API to create a > framework. I only know to run a framework via "mesos-execute" command. > > > > Or maybe Marathon implements its own scheduler, and execute a framework > by itself? > > You are still mixing a few things up: > > * Marathon is a Mesos framework. A framework primarily consists of a > scheduler. > * `mesos-execute` creates a one-off framework. That framework will submit > and manage the given task(s). The framework is stopped when the task(s) > finish. > * There are different APIs. One of them is the scheduler API which > frameworks use to talk to Mesos, another one the operator API which can be > use to administrate Mesos. One cannot start tasks with the operator API. > > The documentation contains a lot of this, including diagrams making things > clearer, > > https://mesos.apache.org/documentation/ > > I’d especially encourage you to read the architecture overview, > > https://mesos.apache.org/documentation/latest/architecture/ > > and the documentation of the operator HTTP API, > > https://mesos.apache.org/documentation/latest/operator-http-api/ > > > Cheers and HTH, > > Benjamin
