Feature Request: Support constraints on persistent volume id/path

[dylanwilder]

This will greatly help with multi tenant cluster reservations. We run many different disk configurations in combinations of RAID/JBOD, SDD/HDD, NFS. Currently, mesos supports no means of differentiating them. A useful workaround would be to filter either the path or the volume id to some regex.

[verma7]

One way to support different disk configurations is to set an agent attribute for the different configurations and then use Marathon-style placement constraints recently introduced in #333.

@gabrielhartmann Please comment if there is a better alternative.

[dylanwilder]

This works well if configuration is uniform per node. However, the per resource determination is more flexible and could conceivably be used for more open ended cases.

[keithchambers]

Hi Dylan, we are looking to introduce support for resource labels/attributes in Apache Mesos such that volumes can be tagged as SSD, HDD, etc. Once support lands in Apache Mesos, we'll work to plumb it in to dcos-commons, and finally the Cassandra Integration.

[superivaj]

Hi, has there been any progress in this area? Deploying services such as cassandra and HDFS is not really reliable unless they can each be assigned the right disks. For example HDFS might require larger disks than cassandra while they are both running on a large node. Currently the first disk (mount) that fits will be assigned even if its size is way larger than needed.