You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
General
- Stop using SLACDEV database (in progress)
- Rationalize use of Dev/prod etc, decide if we need other configuration options
- For ISOC the databases are: Flight, Integration, Test, Nightly
- Look into tomcat clustering
- Integration between monitoring tools and Ops Log
- Ability to easily copy plots to ops log and comment on them
- Ability to find all recent comments on a plot
- Figure out why automatic generation of tomcat configuration on glast-win01,02 did not work
Infrastructure
- implement links between application (in progress)
Data Quality Monitoring Application
Data Processing
- Remove duplication between data processing page and other apps
- One possibility is to hide queries in functions
Cross Trending / Reports
A user would write reports in the form of jsp pages with some special tags to embed plots, text, links, etc.
These pages will be registered with the applications.
The application would provide a tabulated lists of all the available reports and a way to generate them on some time period.
- Write database tables to store report jsp pages
- Define tags API to embed plots in jsp apges
Data Catalog
- Improve data catalog interface especially for real data
- L1 data products arranged by groups rather than folders
- Look into WebDav/GUI for data catalog
Ops Log
- Make Ops Log use same login system as everything else
Data Server
- Get LAT Data Server tied into L1Proc
Data Portal
- Get portal working, at least for items like data processing page, grb summary etc
- Generate RSS feeds from LogWatcher, Ops Log, JIRA, Confluence etc to display on portal page
Web Apps / Servers Monitor
- Ability to monitor all tomcat servers/applications from one page (and maybe restart them)