[jira] [Commented] (MESOS-3038) Resource offers do not contain Unavailability, given a maintenance schedule

["Joseph Wu (JIRA)" <ji...@apache.org>]

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

Joseph Wu commented on MESOS-3038:
----------------------------------

https://reviews.apache.org/r/37170/
https://reviews.apache.org/r/37172/
https://reviews.apache.org/r/37173/

> Resource offers do not contain Unavailability, given a maintenance schedule
> ---------------------------------------------------------------------------
>
>                 Key: MESOS-3038
>                 URL: https://issues.apache.org/jira/browse/MESOS-3038
>             Project: Mesos
>          Issue Type: Task
>          Components: allocation, master
>            Reporter: Joseph Wu
>            Assignee: Joris Van Remoortere
>              Labels: mesosphere
>
> Given a schedule, defined elsewhere, any resource offers to affected slaves must include an Unavailability field.
> The maintenance schedule for a single slave should be held in [persistent storage|MESOS-2075] and locally by the master.  i.e. In src/master/master.hpp:
> {code}
> struct Slave {
>   ... // Existing fields.
>   // New field that the master/allocator can access
>   Maintenances pendingDowntime;
> }
> {code}
> The new field should be populated via an API call (see [MESOS-2067]).
> The Unavailability field can be added to Master::offer (src/master/master.cpp).
> {code}
> offer->mutable_unavailability()->MergeFrom(slave->pendingDowntime);
> {code}
> Possible test(s):
> * PendingUnavailibilityTest
> ** Start master, slave.
> ** Check unavailability of offer == none.
> ** Set unavailability to the future.
> ** Check offer has unavailability.



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