You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2017/06/30 18:45:00 UTC

[jira] [Commented] (MESOS-7647) Add a common ResourceProviderManager.

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

Jie Yu commented on MESOS-7647:
-------------------------------

commit 17c563e455b13bfd9dd371f4f4643677163559a9
Author: Jie Yu <yu...@gmail.com>
Date:   Thu Jun 8 12:09:01 2017 -0700

    Added stubs for the ResourceProviderManager.

    ResourceProviderManager will be used to manage resource providers,
    both local and external. It'll be used by the agent to manage local
    resource providers and used by the master to manage external resource
    providers. It'll expose an API endpoint allowing resource providers to
    subscribe to the manager.

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

> Add a common ResourceProviderManager.
> -------------------------------------
>
>                 Key: MESOS-7647
>                 URL: https://issues.apache.org/jira/browse/MESOS-7647
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Jie Yu
>
> ResourceProviderManager will be used to manage the lifecycle of resource providers, including both local resource providers and external resource providers.
> It resides in both the agent and the master (future). The agent's resource provider manager will be used to manage local resource providers. It processes resource_provider::Call from the local resource providers and sends resource_provider::Event to the local resource providers.
> The agent will also polling the manager for updates like resource changes so that it can inform the master about that.



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