[
https://issues.apache.org/jira/browse/MESOS-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359526#comment-14359526
]
Michael Park edited comment on MESOS-2205 at 3/12/15 10:16 PM:
---------------------------------------------------------------
Thanks [~nekto0n] so much for reading the doc and providing feedback!
{quote}Can you clarify which HTTP status(es) will be used?{quote}
For authorization issues we'll return {{401 Unauthorized}} as we do everywhere
else, in the case where the request cannot be satisfied by Mesos due to the
current state of the cluster, I think we can return maybe {{403 Forbidden}} as
we do in [r31228|https://reviews.apache.org/r/31228/] for example, or maybe a
{{409 Conflict}}. Do you have a recommendation in mind?
{quote}What happens if framework attempt to reserve/unreserve fails (if it
can)?{quote}
If the framework requests to (un)reserve resources that does not exist in the
offered resources, that's a validation error and the operation will be dropped.
This is symmetric to how launch task operations with invalid {{TaskInfo}} are
dropped. That will be all that happens for (un)reserve failures in v1. Once we
validate the (un)reserve operation on the master, we know that the (un)reserve
operation will succeed since the resources are currently offered to the
framework and therefore are available to them. Having said that, in the future
we'll likely want to add {{StatusUpdate}}-like messages for reservations in
order to report successful checkpoint completion on the slave.
was (Author: mcypark):
Thanks [~nekto0n] so much for reading the doc and providing feedback!
{quote}Can you clarify which HTTP status(es) will be used?{quote}
For authorization issues we'll return {{401 Unauthorized}} as we do everywhere
else, in the case where the request cannot be satisfied by Mesos due to the
current state of the cluster, I think we can return maybe {{403 Forbidden}} as
we do in [r31228](https://reviews.apache.org/r/31228/) for example, or maybe a
{{409 Conflict}}. Do you have a recommendation in mind?
{quote}What happens if framework attempt to reserve/unreserve fails (if it
can)?{quote}
If the framework requests to (un)reserve resources that does not exist in the
offered resources, that's a validation error and the operation will be dropped.
This is symmetric to how launch task operations with invalid {{TaskInfo}} are
dropped. That will be all that happens for (un)reserve failures in v1. Once we
validate the (un)reserve operation on the master, we know that the (un)reserve
operation will succeed since the resources are currently offered to the
framework and therefore are available to them. Having said that, in the future
we'll likely want to add {{StatusUpdate}}-like messages for reservations in
order to report successful checkpoint completion on the slave.
> Add user documentation for reservations
> ---------------------------------------
>
> Key: MESOS-2205
> URL: https://issues.apache.org/jira/browse/MESOS-2205
> Project: Mesos
> Issue Type: Documentation
> Components: documentation, framework
> Reporter: Michael Park
> Assignee: Michael Park
> Labels: mesosphere
>
> Add a user guide for reservations which describes basic usage of them, how
> ACLs are used to specify who can unreserve whose resources, and few advanced
> usage cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
