[
https://issues.apache.org/jira/browse/MESOS-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Massenzio updated MESOS-3302:
-----------------------------------
Description:
This Epic covers all the refinements that we may want to build on top of the
{{HTTP API}} MVP epic (MESOS-2288) which was released initially with Mesos
{{0.24.0}}.
The tasks/stories here cover the necessary work to bring the API v1 to what we
would regard as "Production-ready" state in preparation for the {{1.0.0}}
release.
was:
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.
> 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
>
> This Epic covers all the refinements that we may want to build on top of the
> {{HTTP API}} MVP epic (MESOS-2288) which was released initially with Mesos
> {{0.24.0}}.
> The tasks/stories here cover the necessary work to bring the API v1 to what
> we would regard as "Production-ready" state in preparation for the {{1.0.0}}
> release.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
