Fwd: [jira] [Updated] (MESOS-3826) Add an optional unique identifier for resource reservations

[Benjamin Mahler <be...@gmail.com>]

Are you actually going to shepherd this michael? We ended up not adding IDs
to these because we wanted dynamic reservations to be symmetric with static
reservations. Needs some thought.

---------- Forwarded message ----------
From: Guangya Liu (JIRA) <ji...@apache.org>
Date: Tue, Nov 3, 2015 at 10:39 PM
Subject: [jira] [Updated] (MESOS-3826) Add an optional unique identifier
for resource reservations
To: issues@mesos.apache.org



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

Guangya Liu updated MESOS-3826:
-------------------------------
    Shepherd: Michael Park

> 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
>            Assignee: Guangya Liu
>            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)