You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2015/11/13 17:03:10 UTC

[jira] [Created] (MESOS-3914) Make request format consistent across endpoints

Alexander Rukletsov created MESOS-3914:
------------------------------------------

             Summary: Make request format consistent across endpoints
                 Key: MESOS-3914
                 URL: https://issues.apache.org/jira/browse/MESOS-3914
             Project: Mesos
          Issue Type: Improvement
          Components: master
            Reporter: Alexander Rukletsov


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.



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