You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Adam B (JIRA)" <ji...@apache.org> on 2017/12/07 06:57:00 UTC
[jira] [Updated] (MESOS-8251) Introduce a way to resolve the
"profile" for disk resources
[ https://issues.apache.org/jira/browse/MESOS-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam B updated MESOS-8251:
--------------------------
Target Version/s: 1.5.0
> Introduce a way to resolve the "profile" for disk resources
> -----------------------------------------------------------
>
> Key: MESOS-8251
> URL: https://issues.apache.org/jira/browse/MESOS-8251
> Project: Mesos
> Issue Type: Task
> Reporter: Joseph Wu
> Assignee: Joseph Wu
> Labels: mesosphere, storage
>
> This builds off MESOS-8060 which introduced the {{profile}} field to disk resources.
> A volume profile will consist of a {{string}} which maps to a list of {{VolumeCapability}} and some free-form parameters (string key-value pairs). See the {{message CreateVolumeResponse}} under https://github.com/container-storage-interface/spec/blob/master/csi.proto for more information about the fields.
> We will introduce a module which will allow the operator to specify this mapping. Unfortunately, due to the nature of volume profiles, we cannot provide a reasonable "default" mapping of profiles (because we don't have any idea what volumes are available). Instead, there will be two implementations of the module:
> 1) The default will essentially turn volume profiles off. Any attempt to use volume profiles will simply fail.
> 2) An optional module will allow the operator to specify a URI (file or link) that contains a JSON representation of the mapping. The module will have some knobs to tune the frequency at which this URI is fetched from.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)