You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Amila Wijayarathna (JIRA)" <ji...@apache.org> on 2016/02/29 11:34:18 UTC

[jira] [Issue Comment Deleted] (REEF-1159) A Web UI for the Driver

     [ https://issues.apache.org/jira/browse/REEF-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amila Wijayarathna updated REEF-1159:
-------------------------------------
    Comment: was deleted

(was: Hello all,
I am a Information Technology student at University of Moratuwa, Sri Lanka and I'm currently studying as a second year student. Up to now I worked with C, Java, css, HTML, JavaScript, php, mySQL.. and I am willing to contribute to this project . Can I have some more information about what are the parts of this project that are still open and what things expected to done during GSoC period?

Thank You!
Amila Wijayarathna)

> A Web UI for the Driver
> -----------------------
>
>                 Key: REEF-1159
>                 URL: https://issues.apache.org/jira/browse/REEF-1159
>             Project: REEF
>          Issue Type: New Feature
>            Reporter: Markus Weimer
>              Labels: GSOC, gsoc2016, web
>
> We run a web server in nearly every REEF Driver. However, that web server is used almost exclusively for REST API endpoints. It would be amazing to also host a Web UI there, that allows the user access to REEF-level information, including:
>   * The log files of the Driver
>   * The number of events received of the various types.
>   * Uptime, time to allocation, ... whatever statistics we keep.
> Further, just like the REST endpoint, the UI should be extensible such that services and user code in the Driver can register with it. For example, the name service could expose a page listing its current entries.



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