InSPIRE-JRA1 phone conf

Thursday 17 Jun 2010, 10:00 → 12:10 Europe/Amsterdam

Periodic InSPIRE-JRA1 phone conf Title: EGI-JRA1 phoneconf Description: EGI-JRA1 phoneconf Community: Universe Meeting Access Information: - Meeting URL http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MaMDMt2D2uDIDn929sDI9a - Phone Bridge ID: 2021575 Central European Summer Time (+0200) Start 2010-06-17 09:30 End 2010-06-17 12:30

Minutes Minutes_JRA1_phone_17.docx

10:00 → 10:30 Review of Open Actions

https://rt.egi.eu/rt/Search/Results.html?Query=Queue%20%3D%20%27inspire-jra1%27%20AND%20%28Status%20%3D%20%27new%27%20OR%20Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27stalled%27%29

10:30 → 10:40 Milestones and Deliverables

PM1 Milestones: MS701: Define the roadmap for the CIC Operations Portal taking into account the CIC Operations regionalisation of the Portal work plan operational tools and new resource types being used on the infrastructure. (CNRS) MS702: A report describing the different operational tool product team’s development infrastructure and procedures including details of their development infrastructure. (INFN)

10:40 → 11:30 GOCDB4 Release Plan

Proposal from Gilles: The release can be done in 2 steps: 1./ swap all GOCDBPI URLs to point to GOCDB4 only 2./ release the frontend GOCDB4 input web portal 1./ at some time this month: the idea would be to swap GOCDBPI version 3 URL to point to the GOCDBPI_v4 for a day or so, and see what breaks, so that we have a clear list of what showstoppers we have. ------------ Need to identify showstoppers - in particular dependencies of the BDII config script Need to plan the testing that can be done (jra1 internal) before 1 Need to plan the announcements

document GOCDB4Rollout.pdf GOCDB_client_tools_gocdbpi_v4.pdf

11:30 → 11:50 NGIs NAGIOS Validation

Requests from NGIs - how to validate an NGI NAGIOS with some automatic procedure from the OAT wiki: (https://twiki.cern.ch/twiki/bin/view/EGEE/ValidateROCNagios) "for a ROC to validate an NGI Nagios instance, you can use the ops-monitor nagios, and select Service Groups --> Summary --> SERVICE_NagiosNGIDiff. There, select your NGI and then check the ngi.nagios.diff which describes the differences between the services and probes run by your ROC and your NGI. As a second and optional check, you can use the MyEGEE interfaces of your ROC and NGI to compare the status bar of all the services defined in the ROC_CRITICAL profile (CE, SRMv2 & sBDII) during the last 7 days. If you see the same services and their status have been similar in the last week, your instance can be considered validated." From James Casey: Even though NGIs might be starting their own operations, currently all NGIs except Greece are monitoring by their ROC - the ROC is still responsible for the monitoring and this is where both availability and alarms is taken from. This is according to version 0.10 of the NGI procedure and what was agreed at the OAT and published previously to this list. We are in the process of finalizing a v0.11 version which also covers the step of a ROC validating an NGI Nagios and moving control to that instance.

11:50 → 12:00 AOB