You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Madhawa Vidanapathirana (JIRA)" <ji...@apache.org> on 2017/03/12 08:47:04 UTC

[jira] [Commented] (REEF-751) Add a standard way to provide cluster-local configuration

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

Madhawa Vidanapathirana commented on REEF-751:
----------------------------------------------

Hi, 
I am a 4th year student of Department of Computer Science and Engineering, University of Moratuwa. Additionally, I am familiar with both JAVA and C Sharp programming languages. 
I would like to contribute to this project on GSOC 2017.

Can I know more details about progress made so far on above discussed ideas?
How can I get started with work?




> Add a standard way to provide cluster-local configuration
> ---------------------------------------------------------
>
>                 Key: REEF-751
>                 URL: https://issues.apache.org/jira/browse/REEF-751
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF Client, REEF.NET Client
>            Reporter: Markus Weimer
>              Labels: C#, GSoC, gsoc2016, gsoc2017, java
>
> When running a REEF application on a specific cluster, we sometimes have to make cluster-specific configuration choices beyond what's available via e.g. the YARN Configuration. One example are clusters which only allow us to open TCP ports in a specific range.
> Right now, we require the application to add such configuration to the Driver, e.g. via the {{DriverConfigurationProviders}} mechanism. This is awkward, because it limits the portability of applications: In order for an app to run such a cluster, one would have to change the app's code. This is undesirable.
> Instead, we should have a standard mechanism by which one can provide additional runtime-level configuration to be picked up by the REEF client. Let's use this JIRA to discuss potential solutions to this issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)