{toc}
h1. [Pipeline|http://glast-ground.slac.stanford.edu/Pipeline-II]
[Jira Front-End|https://jira.slac.stanford.edu/browse/PFE] [Jira Back-End|https://jira.slac.stanford.edu/browse/PII]
* Ongoing tuning of Oracle database usage
* Switch from exchange server to unix mail server
* Tuning of web interface for ongoing data processing (as opposed to MC Tasks)
* Version 1.0 front-end release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10360&fixfor=11212&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Version 2.5 back-end release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10150&fixfor=11174&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h1. Data Portal
[Jira|https://jira.slac.stanford.edu/browse/DATASERV]
h2. [Data Catalog|https://glast-ground.slac.stanford.edu/DataCatalog/]
[Jira Front-End|https://jira.slac.stanford.edu/browse/GDC] [Jira Back-End|https://jira.slac.stanford.edu/browse/GDCB]
* L1 data products arranged by groups rather than folders
* ASP output arranged by groups rather than folders
* Documentation
** Generate FAQs on data catalog usage
** Work with Chuck on workbook documentation
* Improve data catalog interface especially for real data
** Look into WebDav/GUI for data catalog
* Line-mode client 1.0 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10470&fixfor=11140&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Crawler 1.1 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10470&fixfor=11229&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Data Catalog web interface 1.4 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10442&fixfor=11228&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. Astro Server
* Get Astro Server loading tied into L1Proc
* Configure to use with RAID disk
* Test with full year data
* Accessing files in ROOT format
* Accessing extended event files
h2. (Simple) Skimmer
* Make 1.3 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10047&fixfor=11231&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. Download Manager
* Add line mode version of download manager
h2. WIRED Event Display
* Get working with real data/CEL files
h2. Xrootd
* Get archiving to tape working
h1. Infrastructure
h2. Tomcat Servers
* Finish migrating to using _common_ configuration (not all servers are using common/conf/server.xml)
* Migrate to using 64 bit OS and 64 bit java to push the memory limit to 4Gb
* Wrap the tomcat application with _java wrapper_ to be able to start/stop a server programmatically
* Figure out why sometimes jar files are lost from classpath (seems to be effecting apps on tomcat07)
* Look into tomcat clustering
h2. [Tomcat Server Monitoring|http://glast-ground.slac.stanford.edu/ServerMonitoring/]
* Enable start/stop/restart servers from this application
* create a java program to register a MBean listener to receive notifications from the memory MBean when the memory goes over a given threshold
* find a way to assess the status of a web application. So far we can tell if an application is running or not according to tomcat, but even if the application is running it might be producing errors
* run a java application inside or outside this web app to run a simple query against the JDBC data sources to make sure they are running
* Make 1.1 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10514&fixfor=11232&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. Ongoing
* Maintainance of confluence/JIRA
** Upgrade JIRA to latest version (we are far behind)
* Maintainance of Tomcat/CAS/etc
* Oracle performance/tuning
* Switch to new oracle server
h2. Misc
* 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
* Make sure all web projects are under cruisecontrol
* Switch to netbeans 6/maven2
h1. Data Monitoring
h2. [Ops Log|http://glast-ground.slac.stanford.edu/elog/Index.jsp]
* Make Ops Log use same login system as everything else
* Install latest version from Fermilab
* Enable programmatic entry creation
* 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
h2. [Data Quality Monitoring|http://glast-ground.slac.stanford.edu/DataQualityMonitoring]
* Stress test the trending database
* Alarm Handling
** Ingest detailed information from xml file, like which bins produced an alarm etc.
** Display alarm information on the plots, like warning/alarm limits or arrows on responsible bins
* Data Trending
** Given the volume of data a database table only approach might be insufficient. We might have to consider a hybrid solution that involves reading data straight from tuple files (less efficient that reading from a db)
* Front End
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10443&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Back End
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10527&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. [Data Processing|http://glast-ground.slac.stanford.edu/DataProcessing]
* Remove duplication between data processing page and other apps
** One possibility is to _hide_ queries in functions
* Add links to log messages (pending refactoring and improvement on logger)
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. [Portal|http://glast-ground.slac.stanford.edu/Portal]
[Jira|https://jira.slac.stanford.edu/browse/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
h2. [Cross Trending|http://glast-ground.slac.stanford.edu/CrossTrending]
[Jira|https://jira.slac.stanford.edu/browse/CROSS]
h2. Report Generation
h2. Shift Database/Web Display
h1. Science Products Web Access
h2. [Source Monitoring|http://glast-ground.slac.stanford.edu/SourceMonitoring]
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10414&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. [GCN/GRB Web front end|http://glast-ground.slac.stanford.edu/GRBMonitoring]
[Jira|https://jira.slac.stanford.edu/browse/GCN]
* Integrate with Source Monitoring application
h1. [Pipeline|http://glast-ground.slac.stanford.edu/Pipeline-II]
[Jira Front-End|https://jira.slac.stanford.edu/browse/PFE] [Jira Back-End|https://jira.slac.stanford.edu/browse/PII]
* Ongoing tuning of Oracle database usage
* Switch from exchange server to unix mail server
* Tuning of web interface for ongoing data processing (as opposed to MC Tasks)
* Version 1.0 front-end release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10360&fixfor=11212&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Version 2.5 back-end release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10150&fixfor=11174&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h1. Data Portal
[Jira|https://jira.slac.stanford.edu/browse/DATASERV]
h2. [Data Catalog|https://glast-ground.slac.stanford.edu/DataCatalog/]
[Jira Front-End|https://jira.slac.stanford.edu/browse/GDC] [Jira Back-End|https://jira.slac.stanford.edu/browse/GDCB]
* L1 data products arranged by groups rather than folders
* ASP output arranged by groups rather than folders
* Documentation
** Generate FAQs on data catalog usage
** Work with Chuck on workbook documentation
* Improve data catalog interface especially for real data
** Look into WebDav/GUI for data catalog
* Line-mode client 1.0 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10470&fixfor=11140&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Crawler 1.1 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10470&fixfor=11229&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Data Catalog web interface 1.4 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10442&fixfor=11228&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. Astro Server
* Get Astro Server loading tied into L1Proc
* Configure to use with RAID disk
* Test with full year data
* Accessing files in ROOT format
* Accessing extended event files
h2. (Simple) Skimmer
* Make 1.3 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10047&fixfor=11231&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. Download Manager
* Add line mode version of download manager
h2. WIRED Event Display
* Get working with real data/CEL files
h2. Xrootd
* Get archiving to tape working
h1. Infrastructure
h2. Tomcat Servers
* Finish migrating to using _common_ configuration (not all servers are using common/conf/server.xml)
* Migrate to using 64 bit OS and 64 bit java to push the memory limit to 4Gb
* Wrap the tomcat application with _java wrapper_ to be able to start/stop a server programmatically
* Figure out why sometimes jar files are lost from classpath (seems to be effecting apps on tomcat07)
* Look into tomcat clustering
h2. [Tomcat Server Monitoring|http://glast-ground.slac.stanford.edu/ServerMonitoring/]
* Enable start/stop/restart servers from this application
* create a java program to register a MBean listener to receive notifications from the memory MBean when the memory goes over a given threshold
* find a way to assess the status of a web application. So far we can tell if an application is running or not according to tomcat, but even if the application is running it might be producing errors
* run a java application inside or outside this web app to run a simple query against the JDBC data sources to make sure they are running
* Make 1.1 release
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10514&fixfor=11232&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. Ongoing
* Maintainance of confluence/JIRA
** Upgrade JIRA to latest version (we are far behind)
* Maintainance of Tomcat/CAS/etc
* Oracle performance/tuning
* Switch to new oracle server
h2. Misc
* 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
* Make sure all web projects are under cruisecontrol
* Switch to netbeans 6/maven2
h1. Data Monitoring
h2. [Ops Log|http://glast-ground.slac.stanford.edu/elog/Index.jsp]
* Make Ops Log use same login system as everything else
* Install latest version from Fermilab
* Enable programmatic entry creation
* 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
h2. [Data Quality Monitoring|http://glast-ground.slac.stanford.edu/DataQualityMonitoring]
* Stress test the trending database
* Alarm Handling
** Ingest detailed information from xml file, like which bins produced an alarm etc.
** Display alarm information on the plots, like warning/alarm limits or arrows on responsible bins
* Data Trending
** Given the volume of data a database table only approach might be insufficient. We might have to consider a hybrid solution that involves reading data straight from tuple files (less efficient that reading from a db)
* Front End
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10443&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
* Back End
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10527&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. [Data Processing|http://glast-ground.slac.stanford.edu/DataProcessing]
* Remove duplication between data processing page and other apps
** One possibility is to _hide_ queries in functions
* Add links to log messages (pending refactoring and improvement on logger)
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10500&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. [Portal|http://glast-ground.slac.stanford.edu/Portal]
[Jira|https://jira.slac.stanford.edu/browse/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
h2. [Cross Trending|http://glast-ground.slac.stanford.edu/CrossTrending]
[Jira|https://jira.slac.stanford.edu/browse/CROSS]
h2. Report Generation
h2. Shift Database/Web Display
h1. Science Products Web Access
h2. [Source Monitoring|http://glast-ground.slac.stanford.edu/SourceMonitoring]
{jiraissues:url=http://jira.slac.stanford.edu/secure/IssueNavigator.jspa?view=rss&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=10414&reset=true&decorator=none&os_username=glast-jira-issue-browser&os_password=glast}
h2. [GCN/GRB Web front end|http://glast-ground.slac.stanford.edu/GRBMonitoring]
[Jira|https://jira.slac.stanford.edu/browse/GCN]
* Integrate with Source Monitoring application