[MESOS-3920] Consider changing /reserve, /unreserve endpoint syntax.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Labels: http mesosphere reservations
• Epic Link: Operator API v1
• Assignee: Unassigned
• Reporter: Neil Conway
• Created: 13/Nov/15 19:09
• Updated: 26/Nov/18 12:32
• Resolved: 26/Nov/18 12:32

Description

Right now, the "reserve" and "unreserve" endpoints work as follows:

1. slaveID and resources are sent as two separate key-value pairs in the body of the request, which is URL-encoded (application/x-www-form-urlencoded media type).
2. resources is itself a JSON document.

This is a bit weird: it would more idiomatic to send a single JSON document (using content-type application/json) with the required information. [ Updated: the initial bug description claimed that slaveID and resources were sent as query parameters, but that is incorrect. ]

Obviously, there are some backward compatibility concerns if we want to change this.

Issue Links

• is superceded by: MESOS-5499 Implement RESERVE_RESOURCES Call in v1 master API.
• is superceded by: MESOS-5500 Implement UNRESERVE_RESOURCES Call in v1 master API.