[ https://issues.apache.org/jira/browse/MESOS-9254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894129#comment-16894129 ]
Chun-Hung Hsiao commented on MESOS-9254: ---------------------------------------- Additional patch for fixing a typo: {noformat} commit c3482852abd26d1d35af3ecb0141784acfc0748f Author: Chun-Hung Hsiao <chhs...@umich.edu> Date: Fri Jul 26 08:38:16 2019 -0700 Fixed a typo in `src/Makefile.am`.{noformat} > Make SLRP be able to update its volumes and storage pools. > ---------------------------------------------------------- > > Key: MESOS-9254 > URL: https://issues.apache.org/jira/browse/MESOS-9254 > Project: Mesos > Issue Type: Improvement > Reporter: Chun-Hung Hsiao > Assignee: Benjamin Bannier > Priority: Critical > Labels: mesosphere, mesosphere-dss-post-ga, storage > > We should consider making SLRP update its resources periodically, or adding > an endpoint to trigger that, for the following reasons: > 1. Mesos currently assumes all profiles have disjoint storage pools. This is > because Mesos models each resource independently. However, in practice an > operator can set up, say two profiles, one for linear volumes and one for > raid volumes, and an "LVM" resource provider that can provision both linear > and raid volumes. The correlation between the storage pools of the linear and > raid profiles would reduce one's pool capacity when a volume of the other > type is provisioned. To reflect the actual sizes of correlated storage pools, > we need a way to make SLRP update its resources. > 2. The SLRP now only queries the CSI plugin to report a list of volumes > during startup, so if a new device is added, the operator will have to > restart the agent to trigger another SLRP startup, which is inconvenient. -- This message was sent by Atlassian JIRA (v7.6.14#76016)