WIL Conf call 25 February 2008
From GEANT2-JRA1 Wiki
Contents |
[edit]
Meeting details
Date and Time: Wednesday, the 11th of February, 15:30 - 16:45 CET, 14:30-15:45 BST.
Skype
[edit]
Agenda
- Last Meeting Actions
- Test infrastructure
- DJ1.3.4 review
- Next JRA1 and pS meeting
- Target and Objectives
ST suggestions: pS - general topics related to cooperation between I2 and JRA1, protocol, schema as listed here: PS_meeting_topics_proposals JRA1 - topics related to Java services, installation, release docs and process, etc, continuation of disucssion from pSdev meeting which applies to JRA1 services
- Priority Action Plan - identify our priorities for the next 6 months
- Next steps?
- Suggestions: pS4.0 suggested improvements
- Development lead
- User steering committee - first thoughts
- Technical development lead - getting started
- NOC and PERT requirements
- [Change process
- Documents needed for perfSONAR
- protocol
- Product contact information - Primary dev, Backup dev and QA/team leader
- Security
- License
[edit]
Notes
Attendance: AH, SK, ST, NS. Apologised: LK
- Last Meeting Actions
- Decision: all to update the actions status. We go over only the actions that need discussion: to be flagged-up.
- Test Infrastructure
- LS working well
- DJ1.3.4 review
- All to review
- Next JRA1 and pS meeting
- pS meeting - NS had a discussion with JB. We talked about having JZ or MS there to explain the structure of the protocol doc and the information contained. JB also to explain his proposal on protocol documentation. Then spend few hours on a subset of protocol to progress. Finally during the JRA1 meeting, explain how to do it for all the JRA1 developers.
- Next steps
- All change over bugzilla, see SK suggestion.
- bugzilla to track things. Keep information to a minimum: description and milestones (no document and discussion over it). URL to discussion pages.
- Q&A as WIL
- Review template
- Target: Zagreb meeting to take decisions
- Change process
- What happens with points discussed during meetings and agreed upon?
- What if the change is small?
- What if it is a bug?
- Change filtering into Description validation
- Add SD in steering
- What happens if the change is raported by an observer? Who does the filtering?
[edit]
Last Meeting Actions
- SK to investigate why the BWCTL MP tests don't work with the MDM Pilot. To check with perfSONARUI plug-in. - step by step ongoing
- NS to check the timeline or LIPCU (for ordering the kits and scheduling the workload)
- ST to add in the document the details as which ps-base to go for or which schema version - ongoing as pSbase changes almost every day.
- AH: Exchange utilisation range (color) Evaluate: how the visualisation could cope with that change (+ ressource estimate)
- NS find out who has constrains on providing utilisation data.
- NS to plan the end of the Pilot
- NS to draft a prototype plan
- NS to start setting up the quotes for Prototype and LHC-OPN
- LK to follow-up on the starting date for the LHC-OPN activity.
- SK to investigate if we can get RH support after having modified the kernel -modules ok, kernel modification only with RH
- LK to indicate when the release 3.0 will be available. NS to contact PW about training schedule.
- LK to send a summary about issues relater to 3.0 and on-time parts.
- SK to send an email about the traceroute : where are they visualised. Which ones are available? data available via www.win-labor.dfn.de/ippm
- NS to try the BWCTL plug-in. - Done - working fine
- NS to ask JM and LHC to specify who are the users of those data so that we can tailor the visualisation.
- release management to coordinate the development side for ps3.0
- LK to check that pSbase has all the feature required.
- LK to coordinate the deployment of the GEANT RRD MA (restricted to MDM participants)
- NS to investigate how to organise the work on security
- NS: Leaving process: Improve proposal for the documentation that a tester needs to provide. - Done
- NS to send the pointer to the welcome pack. - Done
- NS: Is the introduction done by the WIL, or the AL gives general introduction then pass the token to the WIL?
- Technical lead: how to tackle it? What are the actions?
- NS to verify if CR can attend the JRA1 meeting on Thursday and Friday. - Request sent, awaiting answer
- NS to update the change process
- LK, LM, NS to finalise the date for 4.0 release.
- Get back to the developer functionalities at the next WIL
- Define project steering body
- Investigate with project from how much ressources the approval from the project is required.
- Investigate if bugzilla can be used for new features
- ST Test infrastructure - announce the LS is up and running to the mailing list.
- NS announce the LS is up and running to the cNIS group.
- All review DJ1.3.4
- All: next JRA1 meeting: list topics for plenary or parallel session for Wednesday 05/03
- NS ask ML to complement the agenda for 15/03
- NS to upload final agenda on 16/03
- ST to investigate who should take part to which pS dev session and who is actually taking part to it. - Done
- ST to kick the pS dev meeting prioritisation task (with WILs)
- NS to coordinate the protocol work for JRA1, follow-up JB emails on doc structure. Help from VV (?) on the technical side of it.
- NS and SK to investigate RFE in bugzilla
- NS to go over bugzilla product and change Q&A name by WIL name
- NS and SK: investigate how to get Q&A stats - what RFE I need to track.
- ST to look over the list of pS4.0 features and make a distinction between bug and enhancement
- NS to review question template and get feedback on Szymon in respect with the information that might be required for the specification document (though it is understood that additional iteration would be needed to get some text for the specification document)
- NS to provide two examples along with the template to be filled by the developers for the pS4.0 features definition
- NS to plan time for the pS4.0 feature definition and pS4.0 specification document
- NS look at the comments made on the change process
