18102006-mLS-release
From GEANT2-JRA1 Wiki
The objective of this phone call is to discuss the next release of multidomain LS.
Contents |
Information
Time: 14:00 UTC, 15:00 CEST
Gatekeeper: pgk.vc.dfn.de (for non-GDS members)
- GDS number: 004910091212314***4522
ISDN 0049 30 254 10800
- Listen to the lady
- Type conf-id 004910091212314***4522#
Skypecast: skype:+99001110003386163
Agenda
- mLS status update (ST)
- Handover process for mLS
- proposal, what to include (LK)
- discussion (all)
- mLS in the next release - discussion (all)
- feasibility
- how to proceed
- timeline
Notes
Attendance
LK, MG, RL, LM, ST, NS
Update from Szymon about the status of the LS:
Jason: code should be merged into the SVN by the end of the week. He will provide some documentation and some basic testing. No information about those two available. Final version of the code.
MG: would prefer to have it in a separate branch. Maciej to Liaise with Jason about this
Handover process:
http://wiki.perfsonar.net/jra1-wiki/index.php/SA3-WI15-Release_Management-Task_Description
Check if the documents are there.
- functional specs – most important as needed for the testing process
- This may corresponds to MS syntax and semantics, so we may be able to re-use MS's work. to provide the template for the specification.
- interfaces specification – most important as needed for the testing process
- This may corresponds to MS syntax and semantics, so we may be able to re-use MS's work. MS to provide the template for the specification.
- specification of ANT targets – important for packaging
- RL to provide the template.
- sample configuration files (required entries, what the entry means).
- MG to provide a template for the semantics of the configuration.
- sample metadata configuration file.
- ST to provide a template for the metadata configuration file.
Three networks to install multi-LS:
- PSNC confirmed
- ACAD – to be investigated
- Third one?
Eric: perfSONAR r1.0 installtion scripts done entriely in perl.
MG: ANT is more for development process, not for installation. Understand that there is little manpower for the release so possibly we could keep ANT for the next release. But need to investigate another solution for the next one. RL: Observation, we don’t have enough developer’s resources. Simplest solution is to keep ANT for the next release.
Agreement reached that Ant will be used for the next release but we will investigate the other possibilities for the next release.
ST: each service has its own installation script. Will there be a master script to install the bundle?
Which services for the release? (JRA1)
- RRD MA – end of November.
- SQL MA – end of November.
- Single LS – end of November.
- Telnet/SSH MP – end of December.
- BWCTL MP – end of December, early January.
- Multi-LS – early January.
- L2 status MP – to de discussed with JRA4.
When the mLS code from Jason is received MG has to evaluate scope of change, study the code, install service (mLS will need to be installed in a few locations), evaluate functionality of changes, test if everything works fine, integrate with changes from single domain LS. Difficult to give timeline now. If the Multi-LS don’t make it on time (mid-December), then it won’t go in the release and we may be lead to make it a JRA1 bundle instead of a perfSONAR one. The L2 status MP is unsure.
LK: which one would we support? The JRA1 bundle or the perfSONAR bundle? It will increase complexity the auto-update process in the future. No conclusion drew from it.
Which services shall we support?
What’s needed for the release? The documentation, the deployment requirement and/functional tests,
Waiting for the last three points from LM, MG and LK.
LM:
- As discussed in Montpellier, we should have snapshots of each service and start testing something of that snapshot of the service, in order to have less possibility of bugs appearing when a Release Candidate is out;
- A Release Candidate will be formed of several snapshots of services, snapshots made on different dates;
- This raises a problem with generic classes that are used by all services, as development continues after a snapshot is created, and the generic classes may be changed afterwards, and a bundle can contain multiple version of the generic classes. What to do? (ACTION to follow)
Actions
- (MG): To ask Jason to create a separate branch in SVN for mLS.
- (ST): To ask Jason what kind of documentation and tests he is going to do.
- (MS): To provide the document template for functional and interface specification of service.
- (RL): To provide the document template for specifying Ant targets.
- (MG): To provide the document template for sample configuration files.
- (ST): To provide the template for sample metadata configuration files.
- (LK): To provide a meta template document.
- (LK): To provide the due data for templates.
- (ST): To chase Martin for templates and due date
- Ant used for the second release but investigate the other possibilities for the next releases.
- If the Multi-LS don’t make it on time (mid-December), then it won’t go in the release and we may be lead to make it a JRA1 bundle instead of a perfSONAR one.
Back to JRA1 events
