[ 
https://issues.apache.org/jira/browse/MESOS-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103438#comment-15103438
 ] 

Jie Yu commented on MESOS-4382:
-------------------------------

commit 1b56d99bfa8f64b81413908987f11539d4978a61
Author: Greg Mann <g...@mesosphere.io>
Date:   Sat Jan 16 12:45:59 2016 -0800

    Documented endpoint failure when HTTP authentication disabled.
    
    The `/reserve` and `/unreserve` endpoints currently do not work when
    HTTP authentication is disabled. To enable correct behavior, the
    `principal` field of `ReservationInfo` is being migrated from `required`
    to `optional`. This patch documents this behavior of these endpoints.
    
    Review: https://reviews.apache.org/r/42336/

commit 1dd713516d4f5e175ce45086263d71717bd9591e
Author: Greg Mann <g...@mesosphere.io>
Date:   Sat Jan 16 12:40:02 2016 -0800

    Changed 'ReservationInfo.principal' from required to optional.
    
    In order to allow dynamic reservation without a principal, this field is
    being changed to optional. However, the current patch alters the master
    to invalidate any reserve operations that do not set this field. After a
    deprecation cycle, the master will allow the field to be unset.
    
    Review: https://reviews.apache.org/r/42334/

> Change the `principal` in `ReservationInfo` to optional
> -------------------------------------------------------
>
>                 Key: MESOS-4382
>                 URL: https://issues.apache.org/jira/browse/MESOS-4382
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Greg Mann
>            Assignee: Greg Mann
>              Labels: mesosphere, reservations
>
> With the addition of HTTP endpoints for {{/reserve}} and {{/unreserve}}, it 
> is now desirable to allow dynamic reservations without a principal, in the 
> case where HTTP authentication is disabled. To allow for this, we will change 
> the {{principal}} field in {{ReservationInfo}} from required to optional. For 
> backwards-compatibility, however, the master should currently invalidate any 
> {{ReservationInfo}} messages that do not have this field set.



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

Reply via email to