You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gearpump.apache.org by "Manu Zhang (JIRA)" <ji...@apache.org> on 2016/04/22 06:18:12 UTC

[jira] [Commented] (GEARPUMP-98) Define and isolate Admin UI

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

Manu Zhang commented on GEARPUMP-98:
------------------------------------

Comments from [~clockfly],

{quote}
Current, in backend, there are three layer of users which require authentication.
1. guest
2. normal user
3. admin user.

We can only show authorized content when user is logged in as admin.
{quote}

> Define and isolate Admin UI
> ---------------------------
>
>                 Key: GEARPUMP-98
>                 URL: https://issues.apache.org/jira/browse/GEARPUMP-98
>             Project: Apache Gearpump
>          Issue Type: New Feature
>          Components: Dashboard
>            Reporter: Manu Zhang
>
> imported from [https://github.com/gearpump/gearpump/issues/1947] on behalf of [~kkasravi], 
> admin operations like /terminate and worker, master, cgroup operations should be isolated and shown in separate UI panels. Angular components and JSON structures should be defined such that they can easily be isolated and possibly hosted in some like TAP



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