You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Michael Park (JIRA)" <ji...@apache.org> on 2017/06/19 06:40:01 UTC

[jira] [Updated] (MESOS-7665) V0 Operator API update for reservation refinement.

     [ https://issues.apache.org/jira/browse/MESOS-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Park updated MESOS-7665:
--------------------------------
    Summary: V0 Operator API update for reservation refinement.  (was: v0 Operator API update for reservation refinement.)

> V0 Operator API update for reservation refinement.
> --------------------------------------------------
>
>                 Key: MESOS-7665
>                 URL: https://issues.apache.org/jira/browse/MESOS-7665
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Benjamin Mahler
>
> In order to preserve backwards compatibility, the v0 endpoints (e.g. /state) should expose the old format using `Resource.role` and `Resource.reservation` if the resources do not contain a refined reservation.
> If the resource contains a refined reservation, then we need to ensure the v0 endpoints reflect that in the JSON.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)