Participants: ============= Malgorzata Krakowian, TIC Rafal Lichwala, SAMAP Hélène Cordier, OPM Cyril L'Orphelin, Best PrActices for Cods Alfredo Pagano, Failover, Philippa Strange, OPM Andy Newton, GOCDB Antonio Retico, PPS & CERN Ioannis Liabotis, OPM Due to bad sound quality the phone conf has been shortened. I deeply apologize for the inconvenience to participants. The next one could be held late August in order to prepare COD-14 which could be 1/2 day face-to-face meeting during EGEE07. Demo session on the daily operations of the grid is also scheduled during EGEE07. from GOCDB3 - Andy Newton, Philippa Strange : --------------------------------------------- Once the version is more stable,there will be a VRVRS meeting with all the people involved in the GOCDB-DISCUSS list next week. Cyril and Osman to represent France to that meeting. from Failover - Alfredo Pagano : --------------------------------- Tools for CODs synchronized with GOCDB3. Failover strategy and schedule for GOCDB3 to be established and tested during summer time. Oracle school and seminars to be held in July for oracle replication in Bologna. SAM backup instance to be checked with CE offer - see Marcin and Judit -as Piotr will still be out of office most of July: Topic followed by Alessandro who is coming back in the office tomorrow. from TIC group - Malgorzata Krakowian : --------------------------------------- * rb/wms/myproxy - Rb/Wms - first results you can find in Cyfronet SAM instance in RB sensor section (difference between our and Dave tests is that we check particular commends (job-listmatch job-submit job-status etc) do they work properly, not just time to match) - myproxy - Fread set deadline to 13.07 so I will haunt him this week * enoc test - this task is canceled, because enoc people decided to give their test result in a standard way (GridMonitoringDataExchangeStandard) so it would be usable by SAM. They don't want new test because it would double results or to publish their result directly into SAM because they test network every 2 min (it is too often for SAM), so there is no work for TIC * caver test - We are waiting for replay from Domenico who carry on this issue with SAM people (especialy with judit) * apel test - Dave Kant is waiting for instruction from SAM team how to publish results directly into SAM DB * CENTRAL SERVICES failures - Marcin's collecting those failures from ROC raports. Next step will be to provide wiki page with them and find volunteers - for example on rollout list * SAM fail over - unfortunately I don't know anything about updates in this topic (I have to ask Marcin - he will back this week from holidays). from SAMAP group - Rafal Lichwala : ----------------------------------- SAMAP update: - SAMAP has been fully integrated on GOCDB3 and full switch to this new release has been made - in the last few days together with Andy we made some SQL query optimizations that makes SAMAP response shorter SAMAP future action plan: - cron functionality implementation which is needed by ROC CERN admins - integration with a new (backup) WMS server setting up by ROC CERN (thanks! :) - implementation of Change Request procedures (a web page) for SAMAP as it was requested by Nick - SAMAP wiki page update from BEst PraCtices for CODs - Cyril L'Orphelin: ------------------------------------------------ - How to handle PPS sites : Since Nick's mails asking to reconsider that COS teams raise tickets against PPS sites again. The general position discussed in the mainling list is still diverse between the following two suggestions or a mix of the two - the last one could be quite heavy weight and confusing for people -: 1)No tickets raised for PPS sites . All admin of PPS Sites are notified by mail of generated alarms for their site . In this case COD people don't take into account PPS sites and maybe a PPS coordinator must follow the number of alarms for PPS sites. 2) Tickets are raised for PPS sites but the steps are the same than with production sites ( with more time between escalation step ) . In this case we can follow the procedure and raised the last escalation step with the discussion into the WLCG phone conference .