Its probably worth linking this document here, which was started by some guys at Nvidia and updated by [email protected]
https://docs.google.com/document/d/1VR5hwcqkkFYM7I6qgZlA9y1qWJkkLLmL5plleiZa_ig/edit?disco=AAAAA5synUc Kevin On Tue, Feb 7, 2017 at 2:09 PM Benjamin Mahler <[email protected]> wrote: For GPUs there have been requests to expose the hardware and topology information in a first class way, so that schedulers can consume it consistently. Uses cases have been: handling heterogenous gpu hardware, topology aware scheduling (critical for GPUs given NVLink vs PCI vs QPI communication path between GPUs). CPUs and disk have had similar requests. I filed https://issues.apache.org/jira/browse/MESOS-7080 to express the need on the GPU side, feel free to file a ticket that captures the use cases you have for disks. On Wed, Feb 1, 2017 at 9:14 AM, Gabriel Hartmann <[email protected]> wrote: This request has been made many times. Attributes on disks (or any resource) doesn't yet exist. On Wed, Feb 1, 2017 at 12:00 AM vincent gromakowski < [email protected]> wrote: It's OK for host selection but I am looking for a way to tag disks within agents. One agent could have several class of disks... Le 1 févr. 2017 5:28 AM, "tommy xiao" <[email protected]> a écrit : search a more useful docs to you: https://github.com/cantbewong/mesos-proposal-externalstorage/blob/master/Mesos%20Management%20of%20Persistent%20External%20Storage.md#use-of-attributes-to-indicate-connectable-storage-tuples-should-work-nicely-with-marathon 2017-02-01 12:26 GMT+08:00 tommy xiao <[email protected]>: the dis resource is tightly to host, so i think use constraint to filter specified agent, then create your volume. does it match your meet? 2017-01-31 1:20 GMT+08:00 vincent gromakowski <[email protected] >: Hi, Regarding the documentation, I can't find any way to tag some disks resources but only to provide label to agents. My use case would be to distinctly offer SSD and HDD based disks resources in a similar way as the type of disk resource ("mount" or "path"). The classic approach would be to have a storage class attribute ? Tx -- Deshi Xiao Twitter: xds2000 E-mail: xiaods(AT)gmail.com -- Deshi Xiao Twitter: xds2000 E-mail: xiaods(AT)gmail.com
