[
https://issues.apache.org/jira/browse/MESOS-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3302:
-----------------------------------
Epic Name: HTTP API v1 (was: HTTP API)
> HTTP API v1
> -----------
>
> Key: MESOS-3302
> URL: https://issues.apache.org/jira/browse/MESOS-3302
> Project: Mesos
> Issue Type: Epic
> Reporter: Vinod Kone
> Assignee: Marco Massenzio
> Labels: mesosphere, twitter
>
> Currently Mesos frameworks (schedulers and executors) interact with Mesos
> (masters and slaves) via drivers provided by Mesos. While the driver helped
> in providing some common functionality for all frameworks (master detection,
> authentication, validation etc), it has several drawbacks.
> --> Frameworks need to depend on a native library which makes their
> build/deploy process cumbersome.
> --> Pure language frameworks cannot use off the shelf libraries to interact
> with the undocumented API used by the driver.
> --> Makes it hard for developers to implement new APIs (lot of boiler plate
> code to write).
> This proposal is for Mesos to provide a well documented public HTTP API that
> frameworks (and maybe operators) can use to interact with Mesos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
