WIL Conf call 11 February 2008

From GEANT2-JRA1 Wiki

Contents 1 Meeting details 2 Actions 3 Minutes 4 Last Meeting Actions 5 Agenda

Meeting details

Date and Time: Friday, the 11th of February, 14:30 - 16:00 CET, 13:30-15:00 BST.

Skype

Actions

1. NS: Newcomer introduction: Improve proposal for the documentation that a tester needs to provide.
2. NS to send the pointer to the welcome pack.
3. NS: Is the introduction done by the WIL, or the AL gives general introduction then pass the token to the WIL?
4. Technical lead: how to tackle it? What are the actions?
5. NS to verify if CR can attend the JRA1 meeting on Thursday and Friday.
6. LK, LM, NS to finalise the date for 4.0 release.
7. Get back to the developer functionalities at the enxt WIL
8. Define project steering body
9. Investigate with project from how much ressources the approval from the project is required.
10. Investigate if bugzilla can be used for new features

Minutes

Attendance: AH, SK, ST, NS. Apologised: LK

• Newcomer introduction
  • There are several aspectes: administrative information (AL or WIL), the work itself (WIL)
  • Is the introduction done by the WIL, or the AL gives general introduction then pass the token to the WIL?
  • Decision: the technical lead for the project lies within the WIL
• Next Meeting
  • Autz very important. DS can cover for PM.
  • Things to do during the JRA1 meeting: finalise pS4.0, plan for 3.x, launch work for 4.0
• Next steps
  • proposal: identify who made the proposals and add more text to them. Provide a template for providing the information
    • Tools targeted, Description of the feature, Effort estimated, impact on other tools, Urgency (why), priority (set by Change group)
    • Features to tackle: AH: AuhZ, performances, PERT; SK: AutZ, Explain the benefits for PERT (alert, etc)
  • Decision: the user functionalities must be the base for the developers to add their functionalities. The developer shoulnd't push for a feature without a clear benefit for the users or moving on with the developments.

Last Meeting Actions

1. SK to investigate why the BWCTL MP tests don't work with the MDM Pilot. To check with perfSONARUI plug-in
2. NS to check the timeline or LIPCU (for ordering the kits and scheduling the workload)
3. ST to add in the document the details as which ps-base to go for or which schema version.
4. AH: Exchange utilisation range (color) Evaluate: how the visualisation could cope with that change (+ ressource estimate)
5. NS find out who has constrains on providing utilisation data.
6. NS to plan the end of the Pilot
7. NS to draft a prototype plan
8. NS to start setting up the quotes for Prototype and LHC-OPN
9. LK to follow-up on the starting date for the LHC-OPN activity.
10. SK to investigate if we can get RH support after having modified the kernel
11. LK to indicate when the release 3.0 will be available. NS to contact PW about training schedule.
12. LK to send a summary about issues relater to 3.0 and on-time parts.
13. SK to send an email about the traceroute : where are they visualised. Which ones are available?
14. NS to try the BWCTL plug-in.
15. NS to ask JM and LHC to specify who are the users of those data so that we can tailor the visualisation.
16. release management to coordinate the development side for ps3.0
17. ST to add in the document the details as which ps-base to go for or which schema version.
18. LK to check that pSbase has all the feature required.
19. LK to coordinate the deployment of the GEANT RRD MA (restricted to MDM participants)
20. NS to investigate how to organise the work on security

Agenda

1. Last Meeting Actions
2. Newcomer introduction
   • The Leaving_process describes what needs to be done when someone leaves the project. There is a question about who is in contact with the developer. Some arguments on who get in touch with a new developer.
   • Utilisation categories - AH
3. Next JRA1 and pS meeting
   • 1st week of April: NOK for GARR, UGENT, (Friday PM and AH) - JM
   • 2nd week of April: NOK for CR (Mon-Wed), PM
4. Priority Action Plan - identify our priorities for the next 6 months
   • Next steps?
   • Suggestions: pS4.0 suggested improvements
   • Rome's feedback - distribute the actions, which ones to start first
5. Development lead
   • Technical development lead - first thoughts
   • User steering committee - first thoughts
   • NOC and PERT requirements
6. Change process
7. Documents needed for perfSONAR
   • protocol
8. Product contact information - Primary dev, Backup dev and QA/team leader
9. Current Issues (all to prepare a list)
   • Deployment issues
10. Security