falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadav (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-790) Falcon UI to enable entity/process/feed edits and management
Date Fri, 26 Dec 2014 17:51:13 GMT

    [ https://issues.apache.org/jira/browse/FALCON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259161#comment-14259161

Ajay Yadav commented on FALCON-790:

[~kho@hortonworks.com] Will the existing UI (html/css/js) co-exist with this one? Reason I
ask is because I didn't see any deletions in the patch. If that is the case then we should
probably think of making the front end stack consistent. Old one used dust.js for templating
and current one uses Angular js.

Another question that I have is will the authentication work only with Ambari or can it be
used even if someone doesn't use Ambari? If yes, then how different will the two processes

+1 to breaking it in manageable chunks and uploading to review board will help to review and
provide inline comments on the code.

> Falcon UI to enable entity/process/feed edits and management
> ------------------------------------------------------------
>                 Key: FALCON-790
>                 URL: https://issues.apache.org/jira/browse/FALCON-790
>             Project: Falcon
>          Issue Type: New Feature
>          Components: ui
>    Affects Versions: 0.6
>            Reporter: kenneth ho
>            Priority: Critical
>             Fix For: 0.7
>         Attachments: 4.4.zip, create feed_1.png, falcon-ui-integration (2).patch, landing.png,
new cluster.png, new feed_2.png, new feed_3.png, new feed_4.png
> Falcon UI is currently read-only. As a step towards enabling a full fledged cluster/feed/process
management and monitoring UI, the following features will be added to the existing UI:
> For the first phase - 
> Entity Creation:
> 1. allow to create a new cluster from the UI
> 2. allow to create a new feed from the UI
> 3. allow to create a new process from the UI
> 4. allow to browse and import an entity XML and then edit
> 5. Clone an existing entity and edit.
> Provisioning and managing:
> 1. Submit an entity
> 2. Schedule an entity
> 3. Suspend an entity
> 4. Delete an entity
> For the second Phase -
> 1. integrating with Ambari view for login.

This message was sent by Atlassian JIRA

View raw message