Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Wed, 4 Nov 2015 05:34:27 +0000 (UTC)
From: "Neil Conway (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12910247.1446615144000.146888.1446615267679@Atlassian.JIRA>
In-Reply-To: <JIRA.12910247.1446615144000@Atlassian.JIRA>
References: <JIRA.12910247.1446615144000@Atlassian.JIRA>
 <JIRA.12910247.1446615144871@arcas>
Subject: [jira] [Updated] (MESOS-3826) Add an optional unique identifier for
 resource reservations
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Neil Conway updated MESOS-3826:
-------------------------------
    Labels: mesosphere  (was: )

> Add an optional unique identifier for resource reservations
> -----------------------------------------------------------
>
>                 Key: MESOS-3826
>                 URL: https://issues.apache.org/jira/browse/MESOS-3826
>             Project: Mesos
>          Issue Type: Improvement
>          Components: general
>            Reporter: Sargun Dhillon
>            Priority: Minor
>              Labels: mesosphere
>
> Thanks to the resource reservation primitives, frameworks can reserve resources. These reservations are per role, which means multiple frameworks can share reservations. This can get very hairy, as multiple reservations can occur on each agent. 
> It would be nice to be able to optionally, uniquely identify reservations by ID, much like persistent volumes are today. This could be done by adding a new protobuf field, such as Resource.ReservationInfo.id, that if set upon reservation time, would come back when the reservation is advertised.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)