[
https://issues.apache.org/jira/browse/MESOS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636348#comment-14636348
]
Adam B commented on MESOS-2061:
-------------------------------
This protobuf message seems heavy with fields we won't use yet. Can we strip
this down to the minimum number of fields to support the basic feature?
Seems like Unavailability should be optional, and executor_ids should be
repeated. I don't think we should even include task_ids/executor_ids until we
have a real Preemption API/design.
> Add InverseOffer protobuf message.
> ----------------------------------
>
> Key: MESOS-2061
> URL: https://issues.apache.org/jira/browse/MESOS-2061
> Project: Mesos
> Issue Type: Task
> Reporter: Benjamin Mahler
> Assignee: Joseph Wu
> Labels: mesosphere
>
> InverseOffer was defined as part of the maintenance work in MESOS-1474,
> design doc here:
> https://docs.google.com/document/d/16k0lVwpSGVOyxPSyXKmGC-gbNmRlisNEe4p-fAUSojk/edit?usp=sharing
> {code}
> // A request to "deallocate" or "return" any resources already
> // being consumed by the framework.
> message InverseOffer {
> required OfferID id = 1;
> required FrameworkID framework_id = 2;
> repeated Resource resources = 3;
>
> // The slave ID if the resources need to be released on a particular slave.
> optional SlaveID slave_id = 4;
>
> // The executor and task IDs if the resources need to be released on
> specific
> // executors and/or tasks.
> optional ExecutorID executor_id = 6;
> repeated TaskID task_ids = 6;
>
> // The resources specified in this offer will become unavailable
> // at the specified start time and for the specified duration. Any
> // tasks running using these resources might get killed when
> // these resources become unavailable.
> required Unavailability unavailability = 7;
> }
> {code}
> This ticket is to capture the addition of the InverseOffer protobuf to
> mesos.proto, the necessary API changes for Event/Call and the language
> bindings will be tracked separately.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
