Its probably worth linking this document here, which was started by some
guys at Nvidia and updated by ct.cl...@gmail.com
https://docs.google.com/document/d/1VR5hwcqkkFYM7I6qgZlA9y1qWJkkLLmL5plleiZa_ig/edit?disco=A5synUc
Kevin
On Tue, Feb 7, 2017 at 2:09 PM Benjamin Mahler
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
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 <
vincent.gromakow...@gmail.com> wrote:
> It's OK for host selection but I am looking for a way to tag disks within
> agents. One agent could have
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" a écrit :
> search a more useful docs to you: https://github.com/
>
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
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 :
> Hi,
> Regarding the documentation, I can't find any way to tag some disks
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
7 matches
Mail list logo