You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2016/08/02 17:10:20 UTC

[jira] [Commented] (MESOS-4791) Operator API v1

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

Vinod Kone commented on MESOS-4791:
-----------------------------------

I think the MVP for operator API is done now. I'll move the unresolved tickets to a new epic "Operator API v1 Improvements" like we did with scheduler and executor epics.

> Operator API v1
> ---------------
>
>                 Key: MESOS-4791
>                 URL: https://issues.apache.org/jira/browse/MESOS-4791
>             Project: Mesos
>          Issue Type: Epic
>            Reporter: Vinod Kone
>
> This epic captures the work needed to update the current master HTTP endpoints for operators (e.g., /state, /metrics/snapshot).
> Some problems with the current operator endpoints
> --> No versioning
> --> Access patterns are not consistent (DELETE on /quota vs /destroy-volume)
> --> No published/standard schemas for requests or responses
> Note that we are doing similar work for Framework API.



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