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/21 00:46:00 UTC
[jira] [Comment Edited] (MESOS-7665) V0 Operator API update for
reservation refinement.
[ https://issues.apache.org/jira/browse/MESOS-7665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16056734#comment-16056734 ]
Michael Park edited comment on MESOS-7665 at 6/21/17 12:45 AM:
---------------------------------------------------------------
{noformat}
commit fd3e9e9f16f6659d3eb88da02b7d02b2d49bd729
Author: Michael Park <mc...@gmail.com>
Date: Tue Jun 13 01:40:43 2017 -0700
Converted the resources to the "endpoint" format for V0 endpoints.
Review: https://reviews.apache.org/r/60041
{noformat}
was (Author: mcypark):
{noformat}
commit fd3e9e9f16f6659d3eb88da02b7d02b2d49bd729
Author: Michael Park mcypark@gmail.com
Date: Tue Jun 13 01:40:43 2017 -0700
Converted the resources to the "endpoint" format for V0 endpoints.
Review: https://reviews.apache.org/r/60041
{noformat}
> 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)