WIL Conf call 4th of June 2008

Meeting details

Date and Time: Thursday, the 4th of June, 11:00 - 12:30 CET, 10:00-11:30 BST.

Berlin
- pS dev - organised by Szymon
- JRA1 - organised by Nicolas
- Edugain developer tutorial: NS to investigate who should attend?
- cNIS: NS or ST to attend the session (Wednesday afternoon)
- Circuit auto-monitoring: NS Tuesday afternoon
- Attributes repository : (DICE - Brugge follow-up): NS Wednesday last slot
Release 3.0 - Infrastructure not available
- This means that there aren't any working service to test the AA and that the Hades server doesn't work. The latest case implies that the service is not working.
- SK to follow-up on the Hades MA, ST on the two RRD MA, SM will provide a release of the looking glass next week

Berlin - http://intranet.geant2.net/server/show/nav.1438
- pS developer organisation - who organise?
- JRA1 organisation - who organise?
- Plenary - who present?
- Other sessions (APM?, PERT?, GIdP, DICE monitoring, Attributes, eduGAIN tutorial) - who represent JRA1?
Release 3.0 - Infrastructure not available : Hades MA, RRD MA with authentication, RRD MA MDM
APAN meeting: travel budget
FAQs for Service Desk and users
- pSUI-RRD MA (with/without AA); pSUI-BWCTL MP(with/without AA); pSUI-Hades MA(with/without AA); pSUI-LS(with/without AA)
- CNM-RRD MA; CNM-maps (including cNIS); CNM-Hades
- Methodology:
  1. list a serie of questions either you are wondering about, that you think an user would wonder about or that you think are not obvious. Use the tool at the same time, it will help greatly. Draft an answer based on your understanding at the same time. (1h-2h). Indicate the tool versions.
  2. Indicate who is best suited to review the answers (one name per person), forward them the questions and collect the answers.
  3. Once done, we need to identify what can go wrong in the communication between the services and within the services. wIt is about identifying what can go wrong in the communication and in the tools. This would be done by talking with the developers, identifying the flow of request/data retrieval within the services and indicate what can go wrong and draft how it can be identified and if possible solved. Submit it to the developer for completeness.