mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Mahler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6845) All /master endpoint documentation lack request details
Date Sat, 07 Jan 2017 00:53:58 GMT

    [ https://issues.apache.org/jira/browse/MESOS-6845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15806335#comment-15806335
] 

Benjamin Mahler commented on MESOS-6845:
----------------------------------------

I don't know if we're quite at the point yet where we've called the existing http endpoints
deprecated, there are some pieces we need still to make it usable. For example, you can't
use them from the browser: MESOS-6773.

> All /master endpoint documentation lack request details
> -------------------------------------------------------
>
>                 Key: MESOS-6845
>                 URL: https://issues.apache.org/jira/browse/MESOS-6845
>             Project: Mesos
>          Issue Type: Documentation
>          Components: documentation
>            Reporter: Tobias Mueller
>
> When I was trying to use the /master/teardown endpoint (http://mesos.apache.org/documentation/latest/endpoints/master/teardown/),
I was unsuccessful in tearing down my specific framework, because the docs say nothing about
request details, such as
> * HTTP method
> * Request body contents
> This makes the usage rather hard, if not impossible. 
> I'd suggest to add call examples like for the Scheduler HTTP API at http://mesos.apache.org/documentation/latest/scheduler-http-api/
> E.g.
> TEARDOWN Request (JSON):
> POST /master/teardown  HTTP/1.1
> Host: masterhost:5050
> Content-Type: application/json
> frameworkId=12220-3440-12532-2345
> TEARDOWN Response:
> HTTP/1.1 200 Ok



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message