[MESOS-2860] Create the basic infrastructure to handle /scheduler endpoint

• Type: Story
• Status: Resolved
• Priority: Major
• Resolution: Done
• Fix Version/s: 0.24.0
• Component/s: master
• Labels: mesosphere
• Target Version/s: 0.24.0
• Epic Link: Scheduler API v1
• Sprint: Mesosphere Sprint 15, Mesosphere Sprint 16
• Story Points: 3
• Assignee: Isabel Jimenez
• Reporter: Marco Massenzio
• Shepherd: Vinod Kone
• Created: 11/Jun/15 23:50
• Updated: 26/Nov/18 15:34
• Resolved: 26/Nov/18 15:34

Description

This is the first basic step in ensuring the basic /call functionality: processing a

POST /call

and returning:

• 202 if all goes well;
• 401 if not authorized; and
• 403 if the request is malformed.

We'll get more sophisticated as the work progressed (eg, supporting 415 if the content-type is not of the right kind).

Issue Links

• incorporates: MESOS-2497 Create synchronous validations for Calls
• is part of: MESOS-2293 Implement the scheduler endpoint on master