WIL Conf call 10 March 2008

From GEANT2-JRA1 Wiki

Contents

[edit]

Meeting details

Date and Time: Monday, the 10th of March, 10:30 - 12:00 CET, 09:30-11:00 BST.

Skype

[edit]

Actions

  1. NS to create a dedicated page with the actions
  2. All to update the actions
  3. LK to have a look at SK proposal for bugzilla
  4. LK to create a new instance of bugzilla (+ transfer bugs)
  5. ST to ensure that there is a change log available for pS base, to tell developers to update their change log with the pSbase version number and to organise regual call to coordinate the developments. - DONE. It's enough to update it during rel mgmt calls
  6. NS to create a fridge section for the agenda
  7. AH to coordinate the visualisation tests (pSUI for end of March, mid Apil the other tools)
  8. NS proposal on what should be asked to the NOC during the visit should be made.(services, long term objectives, how far can pS help them when investigating issues)
  9. ST to investigate with JM if he can present the results on monitoring with Nagios at the plenary. - DONE. He will present it during JRA1 meeting
[edit]

Minutes

  1. Last Meeting Actions
  2. Change process
    • Bugzilla new structure from SK
      • SK suggested to stay with the ML for discussion to avoid having too many places where the discussion happens.
      • Classification on bugzilla done by LK and LM
      • LK mentioned about new bugzilla instance (available around mid April)
      • There is no process to follow-up consistently on RFE. The change process should remedy to it.
    • What info leve in bugzilla?
    • Where to hold discussions?
  3. pS base: release and what version is used
    • See actions
  4. MDM feedback
    • Lack in tests and in utilisation scenario examples for training
  5. Visualisation tool test
    • Test to verify that the functionalities work, that they work consistently, fill bugzilla bugs and suggest enhancements or suggestions. (in case of minor issues -e.g. types, re-wording-, use a single bug to list them all. The tests needs to be done from the point of view of the users.
    • Potential dedicated session in Zagreb.
    • Testers: AH, Ns, PM, DS
  6. Data consistency
  7. *Thomas worked on event categorisation for Hades. The goal is to eliminate the false alerts. BWCTL is more difficult as it depends on hundreds of things.
  8. Transformation Service
  9. Next JRA1 and pS meeting
    • Keep only the WIL status update for the January-June meetings.
    • MM & MY to attend over VC.
    • Present the results on Nagios during the plenary.
  10. Other
    • Visiting the NOCs: seen as a potential good idea. A proposal on what to ask them is required.


[edit]

Agenda

WIL Last Meeting Actions

  1. Last Meeting Actions
  2. Change process
    • Bugzilla new structure from SK
      • how to clarify the structure?
    • What info leve in bugzilla?
    • Where to hold discussions?
  3. pS base: release and what version is used
  4. MDM feedback
  5. Visualisation tool test
  6. Data consistency
  7. Transformation Service
  8. Next JRA1 and pS meeting
    • Do we wish to have WIL updates or do we prefer adding an additional parallel session?
  9. Priority Action Plan - identify our priorities for the next 6 months
  10. Test infrastructure
  11. Development lead
    • User steering committee - first thoughts
    • Technical development lead - getting started
    • NOC and PERT requirements
  12. Documents needed for perfSONAR
    • protocol
  13. Product contact information - Primary dev, Backup dev and QA/team leader
  14. Security
  15. License
[edit]

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. - step by step ongoing
  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 - ongoing as pSbase changes almost every day.
  4. AH: Exchange utilisation range (color) Evaluate: how the visualisation could cope with that change (+ ressource estimate) - sent document on Transformation Service to mailing list
  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 -modules ok, kernel modification only with RH
  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? data available via www.win-labor.dfn.de/ippm
  14. NS to try the BWCTL plug-in. - Done - working fine
  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. LK to check that pSbase has all the feature required.
  18. LK to coordinate the deployment of the GEANT RRD MA (restricted to MDM participants)
  19. NS to investigate how to organise the work on security
  20. NS: Leaving process: Improve proposal for the documentation that a tester needs to provide. - Done
  21. NS to send the pointer to the welcome pack. - Done
  22. NS: Is the introduction done by the WIL, or the AL gives general introduction then pass the token to the WIL?
  23. Technical lead: how to tackle it? What are the actions?
  24. NS to verify if CR can attend the JRA1 meeting on Thursday and Friday. - Request sent, awaiting answer
  25. NS to update the change process
  26. LK, LM, NS to finalise the date for 4.0 release.
  27. Get back to the developer functionalities at the next WIL
  28. Define project steering body
  29. Investigate with project from how much ressources the approval from the project is required.
  30. Investigate if bugzilla can be used for new features
  31. ST Test infrastructure - announce the LS is up and running to the mailing list. -Anounced to testers. But we're having problems with registration and investigating it now
  32. NS announce the LS is up and running to the cNIS group.
  33. All review DJ1.3.4 - AH: done
  34. All: next JRA1 meeting: list topics for plenary or parallel session for Wednesday 05/03 - AH:done
  35. NS ask ML to complement the agenda for 15/03
  36. NS to upload final agenda on 16/03
  37. ST to investigate who should take part to which pS dev session and who is actually taking part to it. - Done
  38. ST to kick the pS dev meeting prioritisation task (with WILs)
  39. NS to coordinate the protocol work for JRA1, follow-up JB emails on doc structure. Help from VV (?) on the technical side of it.
  40. NS and SK to investigate RFE in bugzilla
  41. NS to go over bugzilla product and change Q&A name by WIL name
  42. NS and SK: investigate how to get Q&A stats - what RFE I need to track.
  43. ST to look over the list of pS4.0 features and make a distinction between bug and enhancement
  44. 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)
  45. NS to provide two examples along with the template to be filled by the developers for the pS4.0 features definition
  46. NS to plan time for the pS4.0 feature definition and pS4.0 specification document
  47. NS look at the comments made on the change process
  48. NS Go over bugzilla and change the Q&A person as the WIL
  49. NS Protocol document coordinatio
Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/WIL_Conf_call_10_March_2008"
Personal tools