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

Venkatesh Seetharam commented on FALCON-790:
--------------------------------------------

Why is this hosted in nodejs? This is not what we have followed in Falcon. 

bq. NodeJs , npm, Grunt must be installed in the local pc.
This is not acceptable for users. Not sure why do you need NodeJS? If you still 
need, pull it using maven and we do not ask anything to be installed for 
building falcon apart from maven and jdk.

IMHO, we should be using Bootstrap and AngularJS or backend and connect with 
REST APIs in Falcon.

Can you please explain the architecture of this?

> 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, README.md, create feed_1.png, landing.png, new 
> cluster.png, new feed_2.png, new feed_3.png, new feed_4.png, patch01.patch, 
> patch02, patch03, patch04
>
>
> 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
(v6.3.4#6332)

Reply via email to