<a_entry> Fix nameservice
<a_short_description>add persistency to naming service so when it crashes
it will come back up with previous list.
<a_status>
<long_description_of_problem>
<a_owner>Sinisa
<package>sam_nameservice
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry> Compile station with Kai
<a_short_description> Compile with gcc - first making new gcc and then all products like orbacus built with this new compiler.
<a_status>done
<long_description_of_problem>
<a_owner>Sinisa
<package>sam_station
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>ACL callback
<a_short_description> Look into ACL problem on online -some udp callback to fss (optimizer we think?) causing problem for online subnet isolation.
<a_status>Done
<long_description_of_problem>
<a_owner>Sinisa, Carmenita
<package>sam_station
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>SC2001
<a_short_description> Mine the log files for SC2001 data
<a_status>done
<long_description_of_problem>
<a_owner>Sinisa
<package>sam_info_server
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>FBS/linux
<a_short_description> Help Chris with fbs/linux install and testing
<a_status>done
<long_description_of_problem>
<a_owner>Sinisa
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> Look for an unresolved project master bug
<a_status>
<long_description_of_problem>
<a_owner>Sinisa
<package>sam_station
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>sam_util Linux
<a_short_description> compile sam_util for linux
<a_status>
<long_description_of_problem>
<a_owner>Sinisa
<package>sam_util
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description>possible sam_manager work that may be needed.   Pingable
client. Check restart option works with --CPID on command line.Also desire to cleanup Gabriele's api for ROOT.
<a_status>defer
<long_description_of_problem>
<a_owner>Sinisa
<package>sam_manager
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> standardizing builds 
<a_status>defer
<long_description_of_problem>requires a lot of design which is the bulk of the job. May not have
completed by end of Oct. Benefit is anyone can build any piece of sam easily.
<a_owner>Lauri
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry> D0 handholding
<a_short_description>
<a_status>ongoing
<long_description_of_problem>
<a_owner>Lauri
<package>NA
<sam_vsn>NA
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry> sam_bbftp
<a_short_description>release new versions of bbftp, 512 char in/out file field change.
<a_status>done
<long_description_of_problem>
<a_owner>Lauri
<package>sam_bbftp
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>10/19
<zz_notes>

<a_entry>sam user
<a_short_description> start working on sam_user with Carmenita - taking over - cleanup, error messages, adding new commands
<a_status>
<long_description_of_problem>
<a_owner>Lauri
<package>sam_user
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>get run
<a_short_description> sam get run command -(needs further specification of course)
<a_status>
<long_description_of_problem>
<a_owner>Lauri
<package>sam_user,sam_db_server
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>diskcache
<a_short_description> samadmin remove diskcache command. Need uncache file, disk, group cache, station.
<a_status>in progress
<long_description_of_problem>Mark disk and files on it as not available. Need to go over use cases.
<a_owner>Lauri,Igor
<package>sam_admin
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> archiving of log files (waiting on sam on sun)
<a_status>
<long_description_of_problem>
<a_owner>Lauri
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>sun sam
<a_short_description>build sam on SUN, probably with gcc. gcc needs to be compiled with sqangle.
<a_status>
<long_description_of_problem>
<a_owner>Sinisa, Igor
<package>sam_station
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>Plots
<a_short_description> more work on plots, additional monitoring plots. Maybe move to new plot package.
<a_status>
<long_description_of_problem>
<a_owner>Lauri
<package>sam_admin
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>unit tests
<a_short_description> Produce unit tests for sam user interface
<a_status>
<long_description_of_problem>
<a_owner>Lauri,Chris,Carmenita
<package>sam_user
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry> V3.2 build test
<a_short_description>Test v3.2 for central analysis environment
<a_status>
<long_description_of_problem>
<a_owner>Chris + help
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry> V3.2 build test
<a_short_description>Test v3.2 for distributed Linux cluster environment, including FBS
<a_status>
<long_description_of_problem>
<a_owner>Chris + help
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>sam/farm
<a_short_description> get sam station on Farms
<a_status>
<long_description_of_problem>Need to get the v3_2 of sam installed on the farms. Start
in integration. needs new scripts to run with station features. Need
way to communicate environment between FBS and sam. Hiedi will 
be here T,Th, and Fr. on the 6th floor.
<a_owner>Igor,Sinisa,Chris,Heidi
<package>
<sam_vsn>v3.2.1
<package>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>quick station
<a_short_description> decrease station startup time  (Matt picking up the ball on that, but will require station changes) Matt's top priority.
<a_status>week of SC
<long_description_of_problem>
<a_owner>Matt,Igor
<package>
<sam_vsn>v3.2.2
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> fix change of params crashing station
<a_status>may be done
<long_description_of_problem>
<a_owner>Igor
<package>sam_station
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>sam_cp
<a_short_description>Needs to be able to recognize intra-node, intra-domain, and 
extra-domain transfers. Includes using rcp, kerborized rcp, bbrcp, and Gridftp.
<a_status>done, not tested
<long_description_of_problem>
<a_owner>Lauri
<package>sam_cp
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>10/19
<zz_notes>

<a_entry>
<a_short_description> batch queue management and restrictions to hold a single user to
limited no of files
<a_status>
<long_description_of_problem>
<a_owner>
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>Crummy
<a_short_description> Add crummy file status and needed support features. Could 
use more enduring name, like unofficial or suspect. Matt's second priority.
<a_status>
<long_description_of_problem> storing of 'crummy' half finished files - proposal on how to use status of file. Investigation of what code would need to change in sam store (or whether it is just a little samadmin command you are allowed to do right after the store has succeeeded). Investigate how to deal with --resubmit
 which wants to overwrite a crummy file - needs to call another samadmin
 command to first delete the file in pnfs space. Additional thought and 
discussion indicates that the way we use the current file status is 
incorrect, and some current statuses should be moved to file@location status.
Additional statuses discussed at d0 include :incomplete, obsolete, superseded,
user-added, unofficial. May be more or others 
<a_owner>Matt + others
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>MC metadata
<a_short_description> Add and test new MC metadata to import classes, and db server. 
<a_status>
<long_description_of_problem>Meta data is there, need response from Dave
concerning the MC_Runjob description files he has produced as examples.
Need way to add support entries (might get Julie to do this with forms).
Store works, but need  to be able to initilaize request and get a 
request ID back, then validate attributes when processed data metadata
returns from remote MC centers. Some of the server interfaces are there,
 need to build client part in sam user.
<a_owner>Carmenita
<package>sam_db_server,sam_user
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>MC Request
<a_short_description> Add interface to add  MC requests to MC request tables.
<a_status>
<long_description_of_problem>write client side routines to access these things. Julie and 
Carmenita have been working on the db sever side.
<a_owner>Carmenita
<package>sam_db_server,sam_user
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>Helpdesk Followup
<a_short_description> Need to follow up HD tickets assigned to sam and resolve and closeout
<a_status>
<long_description_of_problem>
<a_owner>Lauri,Carmenita
<package>
<sam_vsn>ongoing
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>Documentation
<a_short_description>Look through documentation and fix problems. Need sam quick reference page, to replace the quick start guide that is obsolete.
<a_status>after Thanksgiving
<long_description_of_problem>sam get metadata,list definition --keywords, sam create dataset --keyword???,  sam run project, sam submit may have problems, mc runjob new metadata, auto dest "sam store --descrip=...", add new phase needs to be documented. 
need to document metadata for luminosity and archive files, sam batch 
commands, psusp, files not delivered. python api, new dimensions and 
examples. Translation of status block . sam toonl should be documented. 
Sam station starting options through sam_bootstrap startup. new flags need to be documented. Questions about groups need to be answered in docmentation.
<a_owner>
<package>sam_doc
<sam_vsn>v3.2.3
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> dcoracle and fnorb are incompatible on solaris under py 2.1, need to understand, fix
<a_status>done
<long_description_of_problem>
<a_owner>steve
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>omniORB.py
<a_short_description>continue to understand issues of omniORB.py use with sam 
<a_status>
<long_description_of_problem>
<a_owner>steve
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>fnorb
<a_short_description>Jerry added code to get fresh pointer when dbserver 
or sewer drops off it will reconnect. This needs to be tested. 
Code is there, this python, need to set up tests. build on Fri 12,
Jerry run tests next week.  
<a_status>done on OSF1
<long_description_of_problem>
<a_owner>Carmenita
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>fnorb
<a_short_description>understanding the voodoo that has been added to make it work 
with 2.1. only needed for the db server. she would like to understand this 
<a_status>
<long_description_of_problem>
<a_owner>Carmenita
<package>
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>sam_common
<a_short_description> this is already rebuilt, need to make sure the idl does 
not break anything in the new version of sam_user, then the error messages
will be in sync. Should not be a big thing, run through tests 
with declare and sam stores.
<a_status>done
<long_description_of_problem>
<a_owner>Carmenita
<package>sam_common
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>autodest
<a_short_description> autodestination with processed files needs to be resolved
bug in the server in constructing the path, pulling info from the
parent that it should not. 
<a_status>next
<long_description_of_problem>
<a_owner>Carmenita
<package>sam_user,sam_db_server
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>get num copies
<a_short_description> get the number of copies for each file from the sam database
 need to decide where this is kept in sam.
<a_status>
<long_description_of_problem>
<a_owner>Carmenita
<package>sam_user
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>file_family
<a_short_description>Add  code to sam autodest so that the proposed path string
uses an optional entry for "file_family=..." to supersede the  stream field.
This has been requested by Gerry for the online direction of files to tape.
Still some debate, but will provide flexibility for streaming decisions
to be made later. 
<a_status>
<long_description_of_problem>
<a_owner>Carmenita
<package>sam_user
<sam_vsn>v3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry> user dbserver
<a_short_description>Make the seperate user db server function for central analysis
<a_status>done
<long_description_of_problem>
<a_owner>carmenita
<package>sam_config
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>FSS re-reg and tr-try intervals
<a_short_description> need to make the time interval for the FSS to re-register with the naming service, and to re-try a store, adjustable parameters.
<a_status>done
<long_description_of_problem>
<a_owner>
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>fix pin
<a_short_description> File pinning is broken and needs to be fixed. 
<a_status>done
<long_description_of_problem>
<a_owner>
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>samadmin
<a_short_description> mark entire station as down, also might want node down, station down, fss down.
<a_status>not critical
<long_description_of_problem>
<a_owner>Lauri
<package>sam_admin
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>SC2001
<a_short_description>Work with Gabrieli in preparation for SC2001  
<a_status>done
<long_description_of_problem>
<a_owner>
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>/sam/cache
<a_short_description> Re-organize /sam/cache disks.
<a_status>
<long_description_of_problem>Re-organize /sam/cache disks into following:
1. /sam/cache - used for sam station cache, 2. /sam/route - used for
remote station routing to enstore, 3. /sam/remote - used for remote
station access to fnal MSS, and 4. /sam/external - used as "external" 
locations (e.g. farm and online data). Would like to have following
arrangement: as many 273GB disks as needed for /sam/cache, and 
/sam/external. Allocate one 273GB disk for each /sam/route, and 
/sam/remote. Under the covers, disks will be called /sam/generic, 
and have sym links that assign to a particular usage, and group.
For example, /sam/route/uta -> /sam/generic05/A, /sam/cache28 -> 
/sam/generic06, /sam/remote/in2p3 -> /sam/generic07/A, /sam/cache25 ->
/sam/generic08.
<a_owner>Lee, Dave F.
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>new robots
<a_short_description>
Need to pass robot server as part of the location, and sam_cp needs to be able
to parse, set env variable ENSTORE_CONFIG_HOST to stkensrv2 for stk robot,
or d0ensrv2 for d0 aml/2 robot. Discussed format like 
FNAL:ENSTORE-stken:/pnfs/sam/dzero..., but maybe following would work?
stkensrv2.fnal.gov:/pnfs/sam/dzero and d0ensrv2.fnal.gov:/pnfs/sam/dzero
<a_status>done
<long_description_of_problem>
<a_owner>carmenita,steve,lauri
<package>sam_user,sam_dbserver,sam_cp
<sam_vsn>3.2.1
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> 
<a_status>
<long_description_of_problem> Known issues/operations/testing stuff a) clueD0 and other linux stations strange things with PM, b) restarts - are they working - tell the users how to do it., c) writing out root-tuples at end of input file - tell users how to do it - Jim K was going to write a mail about this - root-tuple writer package needs to catch framework 'event' that input file has been closed, just like sam_manager catches it., d) remote stations getting files through from tape via their own stager need to test, e) stken need to test, f) routing and use of Gb interfaces - needs more discussion and a written, understanding of what we are going to do, g) sam submit - not allowing users to run in Farm-like mode, h) testing from Nikhef - running analysis project on d0mino to use files from SARA robot.  Also the inverse - running project there and pulling files  from d0mino with bbftp.
<a_owner>Need to decide
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>lto stk locations
<a_short_description> still needs autodestination map entries, testing for online 
need to enable ability to store to new robot locations.
<a_status>done on online
<long_description_of_problem>
<a_owner>lee
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>

<a_entry>
<a_short_description> 
<a_status>
<long_description_of_problem>
<a_owner>
<package>
<sam_vsn>
<xest_pers_days>
<zdate_added>
<zdate_finished>
<zz_notes>