Back to POOL Home page
Minutes of the POOL meeting, CERN, 11.03.03
Developers should use the Savannah task list to describe the main targets
of the incoming releases.
Reharsals for CHEP will be scheduled for next week.
|WP Coordinators reports|
-- Storage service:
It is unclear, whether objects, which are described through an
LCG dictionary only can be written using the keys. It is unclear,
if a rootcint generated dictionary is required or not.
This wissue will be investigated.
-- Savannah task list:
Two entries, solved, but not committed.
- review items on the Savahna task list:
-- complete catalog use-cases for LCG-1: 50% complete
-- composite catalog: logically mergible container is implemented in POOL0.4
-- implement file meta data attribute list: not started
-- define back-end independent catalog query API: not started
- Achieved / Improved:
- Released with minor delay (not entirely our responsibility)
- Integrated with the SEAL releases using SCRAM
- SPI compliance wherever possible (directories, include directives, etc)
- Examples and tests part of the release.
- Development against internal/public releases.
- Proper handling of the binary output (libraries, tests, examples).
- Proper handling of the compiler versions (to be tested for more than one platforms).
- Removing of the uneccessary dependencies (include dirs)
at compile time.
- Acceptable update of the design and user documents (at all levels).
- Meeting most requirements for the Storage Manager and the File Catalog components.
- Not achieved:
- Coherent unit/integration/system testing (still weak validation process)
- Meeting the functional requirements for the Collections.
- Enough tests for exercising the new functionality.
- Need to address (lessons learned):
- Further collaboration with SEAL for agreing to the mechanism of automatic dictionary generation.
- Building the release:
- Proper handling of the reference output of the executables, tests (for the validation process).
- Developing and preparing a new public release:
- Algorithm defining coherent sets of tags for testing.
- Validation criteria for any candidate release (tests, documents).
- Both need collaboration with SPI.
- Release Plan, Test Plan, AAD:
- Current scheleton of the Release Plan needs elaboration.
- Needs connection to the (non-existing) test plan and the (non-existing) high-level ADD.
- Design/Code reviews:
- Standard procedure after every major public release?
2) Schedule for next releases:
- Tue 18/3 0.5.0 : implementation the proposed changes from the code/design review.
- Fri 28/3 0.6.0 (or 0.5.1) : Bug fixes, first integration with the developments in Collections.
- Tue 29/4 1.0.0 : POOL functionally completed (for LCG-1).
|Related LCG projects reports|
- Exception class under revision
- PluginManager going from design phase to initial prototype
o CMS Iguana approach presented
o SEAL design incarnation of the CMS approach done
o Based on the above initial prototype is being prepared
- SEAL release plan by end of March 2003
- Time utility classes
- RLS & RMC server side now supports reg.
expressions in wildcard searches,
e.g. for GUIDs, PFNs, LFNs & their attributes
o One can use the following:
- reg. exp.: ? - 1 char
* - 0 or more
- SQL : _ - 1 char
% - 0 or more
o RLS & RMC Java based command-line tools will be released for end user and
- RMC C++ client library created and complete interface implementation
o RLS and RMC C++ clients support the reg. exp. as well
o TODO complete port of all RMC functional test from Java
- In order not to increase the POOL external package dependencies a wrapper
package will be created and will contain both C++ bindings for RLS and RMC
living in their own namespaces.