You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Yan Xu (JIRA)" <ji...@apache.org> on 2016/10/10 17:29:20 UTC

[jira] [Commented] (MESOS-6062) mesos-agent should autodetect mount-type volume sizes

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

Yan Xu commented on MESOS-6062:
-------------------------------

{noformat:title=}
commit d0c0430c4b506e56d1da71d631d70b5678e634be
Author: Anindya Sinha <an...@apple.com>
Date:   Thu Oct 6 11:27:37 2016 -0700

    Refactor parsing of resources.
    
    Refactored `Resources::parse()` into 2 separate static functions:
    1. Resources::fromJSON() to parse JSON representation of resources.
    2. Resources::fromSimpleString() to parse text representation of
       resources.
    
    Note that these 2 new functions return a `Try<vector<Resource>>`, the
    existing `Resources::parse()` calls them and converts the result to a
    `Resources` object after validating each item in the vector. This
    refactor is done to expose all successfully parsed resources for
    further processing before semantic validation.
    
    Review: https://reviews.apache.org/r/51999/
{noformat}

> mesos-agent should autodetect mount-type volume sizes
> -----------------------------------------------------
>
>                 Key: MESOS-6062
>                 URL: https://issues.apache.org/jira/browse/MESOS-6062
>             Project: Mesos
>          Issue Type: Improvement
>          Components: slave
>            Reporter: Yan Xu
>            Assignee: Anindya Sinha
>
> When dealing with a large fleet of machines it could be cumbersome to construct the resources JSON file that varies from host to host. Mesos already auto-detects resources such as cpus, mem and "root" disk, it should extend it to the MOUNT type disk as it's pretty clear that the value should be the size of entire volume.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)