Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-3914

Make request format consistent across endpoints

    XMLWordPrintableJSON

Details

    • Epic
    • Status: Accepted
    • Major
    • Resolution: Unresolved
    • None
    • None
    • master
    • Endpoint Cleanup

    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.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              alexr Alex R
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: