WIL Conf call 14 May 2007

From GEANT2-JRA1 Wiki

Date and Time: Monday, the 14th of May 2007, 11:00 - 12:30 CET, 10:00-11:30 BST.

Skype

Agenda

1. Go over last conf call actions (see below).
2. Next steps - NS
   • Y4 plans
     • 15th of May - send to task leader the request to write down plans
     • 23rd of May - collect task leaders plan for Y4+6M
     • 29th of May - send request for expected NREN involvement
     • 13th of June - collect the contributions
     • 18th of June - finalise the TA and the manpower for the EXEC meeting
   • SOA
   • Use cases
3. Brasil feedback - AH, LK, ST
4. Cambridge meeting
   • Topics (8-12 needed + facilitator)
   • Next JRA1 meeting
   • Organisation Wednesday
   • Thursday
   • Friday
5. Cross work-item issues. (cNIS, LS registration API)
6. Update about AA, mLS, visualisation.
7. Note about future: transition into service and decisions for support (success criteria).
8. MDM Pilot training update
9. Other

Attendance

Andreas, Loukik, Nicolas, Stephan, Szymon.

Last Meeting Actions

1. SK to make sure that BWCTL on-demand is integrated in pSUI for early April so that it can be showed during the training.
2. LK to make a proposal for the training schedule for the next WIL conf call (ideal one, but should be around 1.5 day to 2 days) and propose who should be present (minimum number of people).NA
3. NS to re-evaluate when the training can be based on the time to order the equipment and the time when the service desk will be ready.
4. NS to ask about SWITCH experience and about Ruth experience and report. Also ask about the preparatory work necessary by those leader.
5. NS, LK to read Andreas document on visualisation release. To go over it during a conf call on Wednesday 14:30 and add the TopS as topic. - Done.
6. During the pilot, each network will register all its services to its local LS.
7. In the installation, each service should have a default blanc address for the LS (to avoid having the problem of a NREN registering a service without noticing it), but provide several URLs of LS avaible for registration. GEANT will provide a LS for this and add the URL in the documentation. LK to act upon it.
8. NS to investigate with Candido about the need of having re-inforcement on the AA front.
9. SK to present a brief update about the status of their WI.
10. LK to make proposal on how to organise the testing. Long plan term for testing. ONGOING
11. LK Get feedback from the developers on the testing phase. Report on functional testing, experiences, provides suggestions on how to organise the work. Not Started
12. ST to lead the on estimating the ressource needed to extend and support pSbase (and list the functionalities).
13. LK: to have a list of priorities for SA3 WI-15. Done
14. AH: investigate the needs to enhancing the visualisation tools: usability and look and feel. Also identify the skills (advices or implementation as well).
15. NS and LK: If release ready, it would be nice to make an official annoucement and describe it. Make an official event. LK to present it, NS to update the agenda. Done
16. SK to create a WI5 sessions, and cover the Y4 point. NS to ensure it happens.
17. ST to create a session for WI3 (Y4 planning) - DONE
18. ST to extend description of the AA session - DONE
19. NS to check for phone access and ST if NJ and VJ can attend.
20. NS to add the following topics for the following conf call:
    • Number of JRA1 meeting.
    • Cross work-item issues. (cNIS, LS registration API)
    • Note about future: transition into service and decisions for support (success criteria).
    • Update about AA, mLS, visualisation.