[ 
https://issues.apache.org/jira/browse/MESOS-3914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexander Rukletsov updated MESOS-3914:
---------------------------------------
    Description: 
We are inconsistent with the format of requests we expect for operator 
endpoints. For example, dynamic reservations take a string 
"slaveId={{<slaveID>}}&resources={{<JSON-for-resources>}}", while maintenance 
expects a {{JSON}} object representing {{maintenance::Schedule}} protobuf 
directly.

We agreed to accept single {{JSON}} objects and provide a corresponding 
{{*Request}} protobuf to document the schema, leverage HTTP verbs where 
appropriate. Next steps are:
* document how Mesos HTTP operator endpoints should be implemented;
* convert all nonconformant endpoints via a deprecation cycle.

  was:
We are inconsistent with the format of requests we expect for operator 
endpoints. For example, dynamic reservations take a string 
"slaveId={{<slaveID>}}&resources={{<JSON-for-resources>}}", while maintenance 
expects a {{JSON}} object representing {{maintenance::Schedule}} protobuf 
directly.

We should agree on the input: either we expect a string with key-value pairs, 
where values can be {{JSON}} objects, or we request {{JSON}} directly.

Once we agree on the approach, we should document the outcome and convert all 
nonconformant endpoints via a deprecation cycle.


> Make request format consistent across endpoints
> -----------------------------------------------
>
>                 Key: MESOS-3914
>                 URL: https://issues.apache.org/jira/browse/MESOS-3914
>             Project: Mesos
>          Issue Type: Epic
>          Components: master
>            Reporter: Alexander Rukletsov
>              Labels: http, mesosphere, tech-debt
>
> We are inconsistent with the format of requests we expect for operator 
> endpoints. For example, dynamic reservations take a string 
> "slaveId={{<slaveID>}}&resources={{<JSON-for-resources>}}", while maintenance 
> expects a {{JSON}} object representing {{maintenance::Schedule}} protobuf 
> directly.
> We agreed to accept single {{JSON}} objects and provide a corresponding 
> {{*Request}} protobuf to document the schema, leverage HTTP verbs where 
> appropriate. Next steps are:
> * document how Mesos HTTP operator endpoints should be implemented;
> * convert all nonconformant endpoints via a deprecation cycle.



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

Reply via email to