WIL Last Meeting Actions

From GEANT2-JRA1 Wiki

WIL Done Actions


Contents

[edit]

04/06/08

  1. pS dev - organised by Szymon
  2. JRA1 - organised by Nicolas
  3. Edugain developer tutorial: NS to investigate who should attend?
  4. cNIS: NS or ST to attend the session (Wednesday afternoon)
  5. Circuit auto-monitoring: NS to attend Tuesday afternoon
  6. Attributes repository : (DICE - Brugge follow-up): NS to attend Wednesday last slot
  7. SK to follow-up on the Hades MA not workign
  8. ST on the two RRD MA for Nina to test and for MDM to work
  9. SM will provide a release of the looking glass next week


[edit]

11/04/08

  1. NS to check with Roberto details on visualisation tools usage monitoring
  2. AH to update document on Transformation Service - Done
  3. AH to update document on "Finding the closest MP" - Done
[edit]

27/03/08

  1. NS to check Zagreb JRA1 agenda (e.g. missing session helpers) - Done
  2. NS to chase people for perfSONAR 4.0 improvement proposals according to template
[edit]

10/03/08

  1. NS to create a dedicated page with the actions - Done
  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
  6. NS to create a fridge section for the agenda - Done
  7. AH to coordinate the visualisation tests (pSUI for end of March, mid Apil the other tools) - Done for psUI
  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) - Done
  9. ST to investigate with JM if he can present the results on monitoring with Nagios at the plenary - Done. He can do this
[edit]

Before 10/03/08

  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) - Done
  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. NS to ask JM and LHC to specify who are the users of those data so that we can tailor the visualisation. - On-going - likely the Tier1 sites operators
  14. release management to coordinate the development side for ps3.0
  15. LK to check that pSbase has all the feature required.
  16. LK to coordinate the deployment of the GEANT RRD MA (restricted to MDM participants)
  17. NS to investigate how to organise the work on security
  18. NS: Is the introduction done by the WIL, or the AL gives general introduction then pass the token to the WIL? - Done: NS to give the first general introduction and welcome pack, the WIL then takes over for specifying the work in details
  19. Technical lead: how to tackle it? What are the actions?
  20. NS to verify if CR can attend the JRA1 meeting on Thursday and Friday. - Done
  21. NS to update the change process - On-going
  22. LK, LM, NS to finalise the date for 4.0 release.
  23. Get back to the developer functionalities at the next WIL - On-going
  24. Define project steering body - On-going
  25. Investigate with project from how much ressources the approval from the project is required.
  26. Investigate if bugzilla can be used for new features - On-going
  27. 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
  28. NS announce the LS is up and running to the cNIS group. - Done
  29. All review DJ1.3.4 - AH: done
  30. NS ask ML to complement the agenda for 15/03
  31. NS to upload final agenda on 16/03
  32. ST to kick the pS dev meeting prioritisation task (with WILs)
  33. NS to coordinate the protocol work for JRA1, follow-up JB emails on doc structure. Help from VV (?) on the technical side of it. - On-going
  34. NS and SK to investigate RFE in bugzilla - On-going
  35. NS to go over bugzilla product and change Q&A name by WIL name
  36. NS and SK: investigate how to get Q&A stats - what RFE I need to track.
  37. ST to look over the list of pS4.0 features and make a distinction between bug and enhancement
  38. 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) - On-going
  39. NS to provide two examples along with the template to be filled by the developers for the pS4.0 features definition - Done
  40. NS to plan time for the pS4.0 feature definition and pS4.0 specification document
  41. NS look at the comments made on the change process - On-going
  42. NS Go over bugzilla and change the Q&A person as the WIL
  43. NS Protocol document coordinatio - To be removed, already covered by action 33
Retrieved from "http://wiki.perfsonar.net/jra1-wiki/index.php/WIL_Last_Meeting_Actions"
Personal tools