| Target date |
Who |
Description |
| 2/4/04 |
German |
- Collect existing CDB requirements (EDG web pages
and mailing lists, workshops, etc)
- Coverage of requirements by PAN.
- Write down initial (specific!) use cases
|
| 9/4/04 |
Service managers |
- Identify requirements and use cases, specifying:
- which 'EDG era' requirements are missing from
table
- which 'CERN added' requirements are missing
- which requirements are obsoleted
- which use cases need to be added
- Review PAN requirements coverage.
- The difference of the coverage of identified
requirements (and use cases) will be a main criteria for deciding between
any choices.
|
| 30/4/04 |
Vero, (German) |
- Conclusions of discussions with Pan/CDB designer (Lionel).
Feedback from/to USENIX LSSCONF forum.
|
| ~20/4/04 |
CMS |
- Presentation from CMS people on their SQL CDB.
- If looking promising, for a comprehensive
understanding, an instance would need to be set up and evaluated by FIO
service managers against the established requirements.
A decision on what prototype to continue would be needed if the
evaluation is positive (to be discussed).
|
| X/4/04 |
Vero |
- Define and document a data model, which can be used
for validating the identified requirements and Use Cases in a case-by case
basis. This data model needs to be approved by DB experts (Nilo / Eric)
and presented to the service managers (eg. in an ELFms meeting, after
having circulated the data model).
|
| X/5/04 |
Vero |
- (To be discussed) A prototype should demonstrate a
subset of the functionality. The subset will be determined by the feedback
from service managers (example: time for re-generating all XML
profiles). (It would be convenient that somebody from outside
IT/FIO, eg. LCG/EGEE, also runs this evaluation).
- The configuration data and schema subset copied
from the production CDB for this evaluation needs to be discussed as well
|
| X/5/04 |
Service Mgr |
- The evaluation of the prototype will be done by
another member of the service manager team (to be identified).
|
| X/5/04 |
Vero |
- (To be discussed) The prototype should demonstrate
a larger subset of the functionality
- Use full configuration data and schema
|
| X/5/04 |
Service Mgr |
- The evaluation of the prototype will be done by
another member of the service manager team (to be identified).
|