1. Report on execution of work in TSA 1.2.4 (20')
Missing data from: ICM, ELUB, SiGNET.
CZ (9)
- top BDII: in place
- services for new and existing (voce, auger) VOs (VOMS, LFC, WMS): are you ready to accept new VO if it comes?
HR (6)
* Top level BDII with dynamic failover based on dynamic DNS and distributed Nagios monitoring - in place
* Running regional Nagios instance - this instance will be aligned with SAM evolution, so in the future we expect it to be official regional monitoring system - in place
* Running central ce-egee.org services, some effort for web site, mail, blog services, dynamic DNS for top BDII and any other service we might need in future - in place
* MSG broker - we're planning to run brokers for messaging systems which will enable various monitoring instances (site, regional, central) to exchange information: what's the plans? Can others use it in case they want to play with the technology?
AT
- GUP (3) - PPS - release testing: status?
- UIBK (3) - top BDII and/or WMS/LFC/VOMS as these services are interesting on a national level: plans?
PL
- CYF(2)
* top BDII + DNS failover: in place
* services for existing VOs (Gaussian, vo.plgrid.pl, vo.ilmc.eimm.org,
* SAM monitoring services for hosted VOs + FCR (to be decided if feasible): plans?
* coordination of TSA 1.2.4, web pages, commitment monitoring, mailing lists, jabber server etc. - in place
- WCSS (2,65) - PPS - release testing: plans?
- ICM (5) - ? plans?
SK (4) - Services to support VOs from IISAS's NA4 involvement. WMS for VOCE (wms.ui.savba.sk): plans?
HU
- ELUB (6) - ? plans?
- KFKI (3) - Hungarian top-level BDII and RB services, MyProxy & LFC services for the national community in general, and the HunGrid VO in particular. VOMS service for the HunGrid VO, UI/AFS infrastructure for HunGrid: plans?
SI (6) - ? plans?
2. Communication - jabber server progress (LF)
3. Do we still need dynamic DNS in a situation we have multi-value LCG_GFAL_INFOSYS?
4. Reliability/Availability enforcement (5') (MR)
Idea of site admins being able to comment on the problem, as well as
setting "relevance" field accepted by OAT.
Actions
1. All people involved in operations in CE federation: register for “EGEE jabber account”.
2. MR & LF: Analyze requirements for SSL and DN-based authorization for Dynamic DNS.
3. MR: Send an e-mail to Jan & Emir with suggestion how 1st line support could use CE web log.
4. MR: Raise an issue on OAT regarding availability calculation.