Pipeline

Jira Front-End Jira Back-End

• 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

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Version 2.5 back-end release

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Data Portal

Jira

Data Catalog

Jira Front-End Jira Back-End

• 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

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Crawler 1.1 release

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Data Catalog web interface 1.4 release

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

(Simple) Skimmer

• Make 1.3 release

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Download Manager

• Add line mode version of download manager

WIRED Event Display

• Get working with real data/CEL files

Xrootd

• Get archiving to tape working

Infrastructure

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

Tomcat Server Monitoring

• 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

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

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

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

Data Monitoring

Ops Log

• 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

Data Quality Monitoring

• 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

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

• Back End

  type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Data Processing

• 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)

Portal

Jira:

• 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

Cross Trending

Jira

Report Generation

Shift Database/Web Display

Science Products Web Access

Source Monitoring

GCN/GRB Web front end

Jira

• Integrate with Source Monitoring application