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

2016-08-02 Thread Vinod Kone (JIRA)

[ 
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)


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

2016-06-15 Thread haosdent (JIRA)

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

haosdent commented on MESOS-4791:
-

[~vinodkone] Thank you for your remind. I found we miss this in those API 
submitted before. Let me create a ticket to track add them as well.

> 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)


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

2016-06-14 Thread Vinod Kone (JIRA)

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

Vinod Kone commented on MESOS-4791:
---

[~a10gupta], [~haosd...@gmail.com] and [~guoger] please make sure to transition 
the tickets to "Reviewable" if you have reviews out for them. Also, don't 
forget to add comments to the proto files describing the calls, parameters and 
responses.

> 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)