[
https://issues.apache.org/jira/browse/FALCON-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768568#comment-13768568
]
Srikanth Sundarrajan commented on FALCON-37:
--------------------------------------------
Extract from the document:
{quote}
There is a plan of change of the current access style of Falcon entity status
data. As of now, It is available only when all the feeds are downloaded to a
central DC. Which is not a sustainable architecture as requirements of real
time data for monitoring, acting upon is intended to meet SLAs. The falcon
dashboard will summarize the entire private cloud of Falcon and show to the
User. Falcon Dashboard is aimed to serve the purpose of a high level monitoring
system of falcon acquisitions & replications over a period of time. The clear
detail is documented in the accompanying UseCase Document.
{quote}
Can you please elaborate on this ?
Also ensure that choice of technology is licensed through one of
http://www.apache.org/legal/resolved.html#category-a.
It might help to also enumerate the list of REST api's that you intend to add
further to what is already available and implications on the backend systems if
any. Also it would be good if you can spell out any persistence needs that this
feature will require. Currently falcon entirely depends on the underlying
scheduler to provide state management and doesn't maintain any transactional
status of instances that are executed through falcon.
> Falcon - Dashboard Feature
> --------------------------
>
> Key: FALCON-37
> URL: https://issues.apache.org/jira/browse/FALCON-37
> Project: Falcon
> Issue Type: New Feature
> Components: general
> Affects Versions: 0.4
> Reporter: Srikanth Sundarrajan
> Assignee: Srikanth Vittal
> Attachments: Designproposal.docx, Falcon – Dashboard.pdf
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
