[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user asfgit closed the pull request at: https://github.com/apache/flink/pull/677 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user mxm commented on the pull request: https://github.com/apache/flink/pull/677#issuecomment-121533840 +1 good to merge and this is a prerequisite for getting a first version of the new web UI in. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user StephanEwen commented on the pull request: https://github.com/apache/flink/pull/677#issuecomment-121291504 If no one objects, I would like to merge this, with a switch to choose between the old web frontend, and the new web frontend. This should get the development of this started better... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user chiwanpark commented on the pull request: https://github.com/apache/flink/pull/677#issuecomment-121441621 Looks good to merge. After merging this PR, we need to modify PR #885. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user StephanEwen commented on the pull request: https://github.com/apache/flink/pull/677#issuecomment-114176858 I think it will. I will try and add further code for the new webfrontend in the next days, and then open a new pull request that subsumes this one and #297 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user uce commented on the pull request: https://github.com/apache/flink/pull/677#issuecomment-114049969 Does this subsume #297? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
Github user StephanEwen commented on the pull request: https://github.com/apache/flink/pull/677#issuecomment-102184072 A simple way to try this out is to execute the class `TestRunner` in the `flink-runtime-web` project. It starts a mini cluster, starts the new web server and runs three jobs (to have some jobs in the history to serve). --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] flink pull request: [FLINK-297] [web frontend] First part of JobMa...
GitHub user StephanEwen opened a pull request: https://github.com/apache/flink/pull/677 [FLINK-297] [web frontend] First part of JobManager runtime monitor REST AP This pull requests is the first step towards the new JobManager monitoring web frontend. The code for the new web server that handles the requests is in `flink-runtime-web`. That way, we keep the core runtime project free of the fat dependencies that come with some web frameworks. The new webserver runs side by side the old one for now. You can activate the new web server by adding `jobmanager.new-web-frontend: true` to the config. By default, the server listens at `http://localhost:8082`. The implementation uses almost pure netty, which is fast and lightweight (dependency wise), and we are using netty anyways in the network stack for data exchange. The server currently answers the following requests: http://localhost:8082/overview http://localhost:8082/jobs http://localhost:8082/jobs/job-id http://localhost:8082/jobs/job-id/vertices http://localhost:8082/jobs/job-id/plan Here, job-id refers to a the ID of a current or archived job. All requests respond with JSON. I am working with someone that helps me draft a frontend (HTML5 + angular.js) that renders the information and issues the requests against the given URLs. I'll share more as soon as we have something that is worth sharing. You can merge this pull request into a Git repository by running: $ git pull https://github.com/StephanEwen/incubator-flink web_frontend_2 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/flink/pull/677.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #677 commit 482d12f155a66e22120f5e0a9993a5b3e56503a5 Author: Stephan Ewen se...@apache.org Date: 2015-04-06T16:27:26Z [FLINK-297] [web frontend] First part of JobManager runtime monitor REST API - Adds a separate Maven project for easier maintenance. Also allows users to refer to runtime without web libraries. - Simple HTTP server based on netty http (slim dependency, since we use netty anyways) - REST URL parsing via jauter netty router - Abstract stubs for handlers that deal with errors and request/response - First set of URL request handlers that produce JSON responses --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
