On May 2, 2013, at 4:34 PM, Viknes Balasubramanee <[email protected]> wrote:
> Thanks Marlon and Chris for your suggestions. > > Suresh, > I will keep this in mind when I submit the proposal. > Speaking of UI, It looks like the sandbox code uses JSP pages to display the > workflow information. I was thinking of displaying these information using > just HTML5 and JS pages. So for the front end I will be using Twitter > Bootstrap and AngularJS. Both these frameworks are lightweight and would > help speed up the development. They also ensure browser interoperability > across platforms and devices. > > Also the sandbox code connects to a DB to get the workflow information. My > guess is that the Airavata Registry would contain all the required > information and the APIs would provide a way to access these information. So > I am assuming I would not have to interact with any DB directly or maintain > one for the webapp. Please correct me if I am wrong. This is all correct. Sandbox project and legacy UI is only to give you an idea. OODT OPSUI might be a different story, you probably can borrow some code, and make it more prettier and responsive using HTML5/JS using the libraries you mention and contribute back. Important thing to note for these UI's is to have have them light weight and framework independent (self-contained) so they can be easily embedded into any existing interfaces. Something along the lines of Google custom search - https://developers.google.com/custom-search/docs/element#html5 Suresh > > Thanks > Viknes > > -----Original Message----- > From: Suresh Marru [mailto:[email protected]] > Sent: Thursday, May 02, 2013 4:23 PM > To: [email protected] > Cc: [email protected] > Subject: Re: Workflow monitoring webapp > > This is very nice, lots of things Airavata could derive from. Thanks Chris. > > Viknes, it will be nice if you can do a cross project and include in your > milestone to review the OODT code as well. If you design it right and keep > it backend independent, may be you can contribute some interfaces to OODT as > well. The UI needs seems to be identical. > > When you submit your proposals, list OODT & Airavata as the projects. > > Suresh > > On May 2, 2013, at 4:12 PM, "Mattmann, Chris A (398J)" > <[email protected]> wrote: > >> Check out: >> >> https://cwiki.apache.org/confluence/display/OODT/Quick+Start+for+PCS+O >> PSUI >> >> >> For some ideasŠ >> >> Cheers, >> Chris >> >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: [email protected] >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department University of >> Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> >> >> >> >> >> >> -----Original Message----- >> From: Viknes Balasubramanee <[email protected]> >> Reply-To: <[email protected]>, <[email protected]> >> Date: Thursday, May 2, 2013 1:00 PM >> To: <[email protected]> >> Subject: RE: Workflow monitoring webapp >> >>> Hi Marlon, >>> Can you please let me know if you have any specific use cases in mind >>> and point me to it so that I could have a look at. >>> >>> Thanks >>> Viknes >>> >>> -----Original Message----- >>> From: Marlon Pierce [mailto:[email protected]] >>> Sent: Thursday, May 02, 2013 3:40 PM >>> To: [email protected] >>> Subject: Re: Workflow monitoring webapp >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> +1 would be good to consider some specific use cases from gateways >>> integrated with Airavata in addition to a "generic" use case: what >>> information is needed to debug and how to display. >>> >>> >>> Marlon >>> >>> >>> On 5/2/13 3:36 PM, Suresh Marru wrote: >>>> + 1. >>>> >>>> This is a good addition. The legacy version of such interface is at >>>> - http://community.ucs.indiana.edu:19440/XWorkflows/ (you will need >>>> to pick the dates back to 2009 to see sample data and reports). The >>>> code for this is at - >>>> https://svn.apache.org/repos/asf/airavata/sandbox/workflow-monitorin >>>> g- >>>> util/ >>>> >>>> Since you expressed in GSoC you can work on this as your project. >>>> Note that this is different then the master project which focuses on >>>> user level monitoring and this is more of a admin level system >>>> monitoring. This monitoring tools does not need any pub-sub system >>>> and should be more of a report generation based on data in registry. >>>> The user level monitoring us for real-time monitoring. >>>> >>>> Suresh >>>> >>>> On May 2, 2013, at 2:42 PM, Viknes B <[email protected]> wrote: >>>> >>>>> Hi Everyone, >>>>> >>>>> I have been playing around with Airavata lately and I feel adding a >>>>> couple more features would prove to be really helpful. Although you >>>>> can run a workflow easily from the XBaya GUI, and see the output, >>>>> it does not provide all the details a user/admin might want to see. >>>>> It lets you run/monitor only one workflow at a time, we don't have >>>>> a way to access the status of the workflow or the jobs in the >>>>> queue, which machine it runs on, the reason for the failure of a >>>>> workflow. For an admin who deploys Airavata, a collective graphical >>>>> display of the experiments and workflows running, the dates related >>>>> to it, notifications about it would be very helpful. I feel it >>>>> would be nice to have a simple webapp to display all these >>>>> information. The webapp will be lightweight and made using HTML5 >>>>> and JS and would provide all the monitoring capabilities for a user. >>>>> >>>>> Please let me know your thoughts/suggestions. >>>>> >>>>> Thanks Viknes >>>>> >>>>> >>>> >>>> >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG/MacGPG2 v2.0.18 (Darwin) >>> Comment: GPGTools - http://gpgtools.org >>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ >>> >>> iQEcBAEBAgAGBQJRgsETAAoJEOEgD2XReDo5XdIH/0ViEh+a2DNxXFSXIQQVIvbG >>> Qo2jdXP40Ls2jIOetqWg4zhM8a+k9KGH1grpukifNsdG46tyTGoUgS+807+l/CMP >>> tX2J6FuAiDfHyuZ7cpafBoXFJ9srQNCRQB/R+kS4HZGWjbxD3h54/MsTiF3gCmoS >>> O52r1baSVgsKjS7mOqkBzHgxfQm0j24Clsgv2/FPvEeyT+h3n0H6ak/ee2K5G9HQ >>> 1jh3tndziy4OiigTsgAx9xFwjiuqezSc4n+2OPYhPGMId8rCHauwJXwCamNw3LKB >>> HAXjU3kegi0s9XiNFGqvGvaHgfASH7PWhoxug2J+3bsu5j8l0ysCZWUScMHm6KY= >>> =Fti6 >>> -----END PGP SIGNATURE----- >> >
