[ 
https://issues.apache.org/jira/browse/MESOS-8060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202690#comment-16202690
 ] 

Jie Yu commented on MESOS-8060:
-------------------------------

commit d79dd983e484bfe5690d34b53716e2c97f1d288e
Author: Jie Yu [email protected]
Date:   Fri Oct 6 14:04:23 2017 -0700

Added first class profile for disk resources.

This is similar to storage classes. Instead of adding a bunch of
storage backend specific parameters (e.g., rotational, type, speed,
etc.) into the disk resources, and asking the frameworks to make
scheduling decisions based on those vendor specific parameters. We
propose to use a level of indirection here.

The operator will setup mappings between a profile name to a set of
vendor specific disk parameters. The framework will do disk selection
based on profile names.

The storage resource provider will provide a hook allowing operators
to customize the profile name assignment for disk resources.

Review: https://reviews.apache.org/r/62820

> Introduce first class 'profile' for disk resources.
> ---------------------------------------------------
>
>                 Key: MESOS-8060
>                 URL: https://issues.apache.org/jira/browse/MESOS-8060
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Jie Yu
>            Assignee: Jie Yu
>             Fix For: 1.5.0
>
>
> This is similar to storage classes. Instead of adding a bunch of storage 
> backend specific parameters (e.g., rotational, type, speed, etc.) into the 
> disk resources, and asking the frameworks to make scheduling decisions based 
> on those vendor specific parameters. We propose to use a level of indirection 
> here.
> The operator will setup mappings between a profile name to a set of vendor 
> specific disk parameters. The framework will do disk selection based on 
> profile names.
> The storage resource provider will provide a hook allowing operators to 
> customize the profile name assignment for disk resources.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to