[
https://issues.apache.org/jira/browse/MESOS-7705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Park updated MESOS-7705:
--------------------------------
Description:
We output the "endpoint" format through the endpoints
for backward compatibility of external tooling. A framework should be
able to use the result of an endpoint and pass it back to Mesos,
since the result was produced by Mesos. This is especially applicable
to the V1 API. We also allow the "pre-reservation-refinement" format
because existing "resources files" are written in that format, and
they should still be usable without modification.
This is probably too flexible however, since a framework without
a RESERVATION_REFINEMENT capability could make refined reservations
using the "post-reservation-refinement" format, although they wouldn't be
offered such resources. It still seems undesirable if anyone were to
run into it, and we should consider adding sensible restrictions.
was:
We output the "endpoint" format through the endpoints
for backward compatibility of external tooling. A framework should be
able to use the result of an endpoint and pass it back to Mesos,
since the result was produced by Mesos. This is especially applicable
to the V1 API. We also allow the "pre-reservation-refinement" format
because existing "resources files" are written in that format, and
they should still be usable without modification.
This is probably too flexible however, since a framework without
a RESERVATION_REFINEMENT capability could make refined reservations
using the "post-reservation-refinement" format, although they wouldn't be
offered such resources. It still seems undesirable if anyone were to
run into it, and we should consider adding back sensible restrictions.
> Reconsider restricting the resource format for frameworks.
> ----------------------------------------------------------
>
> Key: MESOS-7705
> URL: https://issues.apache.org/jira/browse/MESOS-7705
> Project: Mesos
> Issue Type: Bug
> Components: master
> Reporter: Michael Park
>
> We output the "endpoint" format through the endpoints
> for backward compatibility of external tooling. A framework should be
> able to use the result of an endpoint and pass it back to Mesos,
> since the result was produced by Mesos. This is especially applicable
> to the V1 API. We also allow the "pre-reservation-refinement" format
> because existing "resources files" are written in that format, and
> they should still be usable without modification.
> This is probably too flexible however, since a framework without
> a RESERVATION_REFINEMENT capability could make refined reservations
> using the "post-reservation-refinement" format, although they wouldn't be
> offered such resources. It still seems undesirable if anyone were to
> run into it, and we should consider adding sensible restrictions.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
