> On May 21, 2015, 11:08 p.m., Niklas Nielsen wrote:
> > A higher level question is whether we should have touples of actions.
> >
> > For example:
> >
> > message KillAction {
> > optional ExecutorID executor_id = X;
> > }
> >
> > message ResizeAction {
> > optional TaskID task_id = X;
> > optional Resources resources = Y;
> > }
> >
> > ...
Yes, the resizing action of custom isolators could be tricky to formalize.
We have two choices:
1) Make an union of possible actions with bodies
2) Use labels to carry metadata
I would go for the first choice. If someone would like to resize his custom
iso, one should need to extend the ResiseAction message.
- Szymon
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34571/#review84814
-----------------------------------------------------------
On May 21, 2015, 11:02 p.m., Bartek Plotka wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/34571/
> -----------------------------------------------------------
>
> (Updated May 21, 2015, 11:02 p.m.)
>
>
> Review request for mesos, Jie Yu, Niklas Nielsen, and Vinod Kone.
>
>
> Bugs: MESOS-2760
> https://issues.apache.org/jira/browse/MESOS-2760
>
>
> Repository: mesos
>
>
> Description
> -------
>
> This part of proto describes a QoS corrections message which includes
> corrections for particular executors or tasks.
> It is a generic message between QoS Controller and slave.
>
>
> Diffs
> -----
>
> include/mesos/mesos.proto a66888916dc90e476c8bb20e67e3f6b08c47fb99
>
> Diff: https://reviews.apache.org/r/34571/diff/
>
>
> Testing
> -------
>
> make check
>
>
> Thanks,
>
> Bartek Plotka
>
>
