reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Won Wook SONG (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (REEF-1159) A Web UI for the Driver
Date Mon, 14 Mar 2016 06:04:33 GMT

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

Won Wook SONG edited comment on REEF-1159 at 3/14/16 6:04 AM:
--------------------------------------------------------------

Hi, I'm also quite interested in the project for GSoC2016!
I have experience with Ruby on Rails, Django, Flask as backend of web applications (thus familiar
with RESTful APIs, web application structures, and related fields), and AngularJS, ReactJS,
and their relevant programming languages (i.e. JS, HTML). I also have experiences with different
kinds of databases (MySQL, PostgreSQL, SQLite, Redis) as well as web servers (Passenger, Unicorn,
uWSGI / Nginx). This job will be quite easy due to these circumstances, and it will be quite
nice if I could also contribute a bit more on other issues on this project as well.
I will go into more detail on my application.
It will be my second year of GSoC and it will be a pleasure to work on this project :)


was (Author: wsong0512):
Hi, I'm also quite interested in the project for GSoC2016!
It will be my second year of GSoC and it will be a pleasure to work on this project :)

> 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)

Mime
View raw message