SAM WBS Tasklist (updated 2001/01/30)

Detailed Tasklists

• 1.2.1 Major revision for focus on Users - instead of development project
• 1.5.1 Coding standard document
• 1.5.2 How to use SoftReltools, make file standards, CTBUILD?
• 1.5.3 Note on cutting a version, tagging in cvs and putting into KITS
• 1.5.4 Note on how to upd distribute from ups repository other than KITS
• 1.7.1 Prepare for SC98 Poster
• 1.7.2 Prepare and give SC98 Demo
• 1.7.3 Von Ruden Review - prepare D0 Data Handling overview document
• 1.7.4 Von Ruden Review - Joint Projects talk and demo
• 1.7.5 Database server code generation talk for Support Databases meeting
• 1.7.6 Batch working group status at Run II meeting
• 1.7.7 Von Ruden Review - June 99
• 1.7.8 Mini-review/status report to Run II Steering - October 26, 1999
• 1.7.9 Status report to Run II Steering - June, 2000
• 1.7.10 Preparations for SC2000
• 1.8.1 Database Server Generator and Server codeOctober/November5 FTEdays
• 1.8.2 Project Master design and code reviewDecember5 FTEdays
• 1.8.3 Station Master and File Storage server code reviewDecember10 FTEdays
• 1.8.4 InfoServer code reviewdone by Sinisa informally in moving code90%
• 3.3.1 SAM commands in different sections of a farm jobMaciej/Sinisa working on
• 3.3.2 Synchronization of farm job sections while SAM station servers are running
• 6.2.1a Make Volume/File changes to ER diagram - update devel dbJT100%
• 6.2.1b Update Forms for supporting data - add new form
• 6.2.1 Prepare DDL for production instance within sam_db product.This includes checking Tablespaces, Storage parameters, Sequences, Naming conventions, and version cutting mechanisms
• 6.2.2 Migrate DDL to d0ora2 and run to produce production SAM tables
• 6.2.3 Assure backup procedures in place
• 6.2.4 Test scripts against production database
• 6.3.1 db_server_gen completion, upcase issue,few additions, exception handling4FTEdays90%
• 6.3.2 Directory restructuring.100%
• 6.3.3 Include exceptions in templates.100%
• 6.3.4 Change debugLog parameters.100%
• 6.3.5 Create listener process.100%
• 6.3.6 Write middle layer of SAMDbServer, using generated objects.add transaction100%
• 6.3.7 Split business layer, making separate Servers for ProjectDbServer, StationDbServer, ConsumerDbServer, FileDbServer and the original SAMDbServer.100%
• 6.3.8 Include business rule based exceptions in new servers.100%
• 6.3.9 Produce makefiles that work with SoftRelTools.defer to V1
• 6.3.10 Document setup procedures for generating and running DbServer.100%
• 6.3.11 Use Factory model to generate multiple forks (vs. threads) on the SAMDbServerdefer multiple threads to V1.
• 6.3.12 Incorporate "Smart Pointers" into server.this is not SAM work
• 6.3.13 Dictionary changes and server changes for new ER model100%
• 6.3.14 Add/modify interfaces to server - commit,insert into volume table100%
• 6.3.15 Interface to delete project definitions and snapshotsneeds checks?
• 6.3.16 Data precision problem in dcoracleSW,MV
• 6.6.1 Implement minimum command line syntax100%
• 6.6.2 Add necessary additional interfaces to dbServer100%
• 6.6.3 Refurbish Java-based tool to implement minimal command line functionalityRW100%
• 6.7.1 New MC specific page VW
• 6.7.2 Allow to point to either production db or devel db VW+JT,SW
• 6.8.1 Test with new version of Orbacus --> 12.x need more consumers in tests
• 6.9.1 Build Enstore file writing routine, which communicates back to meta-data with volume information, a.k.a. on what tapes did it put the files.
• 6.9.2 Build post-import QA script to verify that the meta-data was created correctly in SAM.
• 6.9.3 Implement logging means for import meta-data, keeping files in case review of what was loaded is needed. Archiving may also be required.
• 6.9.4 Decide design details of import, verify and enstore interactions from the users perspective.
• 6.9.5 Pick a user interface metaphor, www or command line or both.
• 6.9.6 Design flow of data files, notification, naming conventions, disk areas, logging
• 6.14.1 Recreate to new table specs and place in sam_db_admin product.
• 6.14.2 List allowable values for Data tier, type, and other support tables
• 6.14.3 Populate support tables using forms.
• 8.2.1 Project Master recovers context on restart/reboot to file level of granularity100%
• 8.2.2 Re-run project again and provide consumers with missing and failed files100%
• 8.2.3 Run project - with constraintse.g. omit particular file100%
• 8.4.1 FSS failure/restart define model of operation 100%
• 8.4.2 sam - copy/transfer/xxxx/store-again command and FSS support for it3PD
• 8.4.3 sam store destination mapping initially simple map in FSS. Think about database design and mapping algorithsm 5FTEdays
• 8.6.1 physical management of processes - project masters, fss, stagers
• 8.6.2 disk cache algorithms
• 8.6.3 configuration parameters - database storage, setting, viewing
• 8.6.4 station master interfaceshow user interacts with a station
• 8.6.5 refurbishing a lot of scripts
• 8.7.1 Framework metadata for output files from reconstruction program initially
• 8.7.2 Framework metadata for D0gstarextra params in RCP file and command line
• 8.8.1 Update database schema for card files decide which entity they hang on3FTEdays
• 8.8.2 Add card file upload and save to db to dbserver
• 8.8.3 Add to file store meta-data and sam store user command
• 9.1.1 Move naming service and log service 100%
• 9.1.2 Move and fix infoserver and admin also unit tests using html/python - see 9.860%
• 9.1.3 sam lock 'dataset' command4 FTEdays0%
• 9.1.4 RedHat 6.1 version100%
• 9.1.5 make corba utils package for framework standalone and in D0 tree100%
• 9.1.6 delete file scripts3 FTEdays
• 9.1.7 array inserts in DB100%
• 9.1.8 support for vlpc raw datafiles100%
• 9.7.1 Improve and package scripts
• 9.7.2 Scripts for use with Requests fetch files for export
• 9.10.1 Unit test pages for infoserver decide metrics2 FTEdays
• 9.10.2 Log File raw viewer/searcher tool7 FTEdays
• 9.10.3 Start layout of improved status pages ? FTEdays
• 9.10.4 Add more tailored browsing & summary pages redo browsing pages layout? FTEdays
• 9A.1.3 sam lock 'dataset' command4 FTEdays
• 9A.1.6 delete file scripts3 FTEdays
• 9A.7.1 Improve and package scripts
• 9a.7.2 Scripts for use with Requests fetch files for export
• 9A.9.1 Unit test pages for infoserver decide metrics2 FTEdays
• 9A.9.2 Log File raw viewer/searcher tool7 FTEdays
• 9A.9.3 Start layout of improved status pages ? FTEdays
• 9A.9.4 Add more tailored browsing & summary pages redo browsing pages layout? FTEdays
• 21.1.1 SAM Tutorial October 28,1999 - training room
• 22.16.1 Define and implement components of user-loads
• 22.16.2 Create and configure general test harnessconfigurable loads
• 22.16.3 Define regression tests
• 22.16.4 Display of test run information90%
• 22.16.5 Save all test results, expected test results initially in files, later use database4 FTEdays
• 22.17.1 Use of OEM - get reports on web
• 22.17.2 Populate database - test performance

################################################################################
# Project               : SAM
# Package               : sam_doc
#
# Most Recent Update by : lauri
#
# This work is part of a development project, called SAM, which consists of a
# number of coordinated packages each named sam_xxxx .
#
# Notice of authorship, copyright status,  and terms and conditions, should
# the software eventually become available for use outside Fermilab, can be
# found in the README and LICENCE files in the top level directory of the main
# sam package.
################################################################################