[ 
https://issues.apache.org/jira/browse/FALCON-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Srikanth Sundarrajan updated FALCON-790:
----------------------------------------
    Attachment: FALCON-790-additional.patch

Attaching patch for further changes to avoid writing generated source under 
webapp/src/main/webapp/public.

Would like 

{noformat}
falcon-ui/dist
falcon-ui/node
falcon-ui/node_modules
{noformat}

to be actually generated under target. For now have added them to .gitignore.

Please review the additional patch. Will commit once you ack. If it is possible 
to move out the above listed directories out of falcon-ui into 
falcon-ui/target, then it would be cleaner

> 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
>              Labels: falcon-syncup
>             Fix For: 0.7
>
>         Attachments: 4.4.zip, FALCON-790-V4.patch, 
> FALCON-790-additional.patch, README.md, create feed_1.png, falcon.log, 
> landing.png, new cluster.png, new feed_2.png, new feed_3.png, new feed_4.png, 
> patch.tar.gz, patch_1.0.1.patch, rat.txt.gz
>
>
> 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