Subramaniam Krishnan updated YARN-1708:

    Attachment: YARN-1708.patch

Thanks [~vinodkv] for taking the time to review and for the follow up 
discussions. I am uploading a new API patch based on the consensus we reached.

The summary of the changes are:

 - Make all proto fields as optional, with default and add server side code to 
check for required fields.
 - Rename ReservationCreateRequestProto -> ReservationSubmissionRequestProto
 - Rename ReservationDescriptionProto -> ReservationRequestsProto
 - Rename ReservationResourceRequestProto -> ReservationRequestsProto
 - Added a new ReservationRequestProto which will be specifically to specify 
resources to reserve instead of reusing ResourceRequestProto as currently 
reservations does not use locality constraints. In future we see convergence of 
 - Rename ReservationDescriptionInterpreterProto -> 
ReservationRequestInterpreterProto. Added examples for each reservation type in 
 - ReservationHandle is not needed. 
 - Add ReservationIdProto: ClusterTimeStamp + long id : Similar to appIDs
 - Rename ReservationCreateResponseProto -> ReservationSubmissionResponseProto
 - ReservationUpdateRequestProto: No need to pass queue-name
  -- Instead should specify ReservationID and the effect will be to replace the 
existing reservation with new one.
 - ReservationUpdateResponseProto: Can just be empty
 - Add a ReservationDeleteRequestProto with ReservationId which will be deleted
 - ReservationDeleteResponseProto: again can just be empty

> Add a public API to reserve resources (part of YARN-1051)
> ---------------------------------------------------------
>                 Key: YARN-1708
>                 URL: https://issues.apache.org/jira/browse/YARN-1708
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Subramaniam Krishnan
>         Attachments: YARN-1708.patch, YARN-1708.patch
> This JIRA tracks the definition of a new public API for YARN, which allows 
> users to reserve resources (think of time-bounded queues). This is part of 
> the admission control enhancement proposed in YARN-1051.

This message was sent by Atlassian JIRA

Reply via email to