IGALC migration to ROC_LA, 23/08/2012 Present: R. Diacovo/IGALC T. Ferrari/EGI.eu R. Santana/ROC_La R. Trompert/COD T. Szymocha/COD SUMMARY OF ACTIONS ACTION 1 (RD, RS): to agree on the list of sites to be migrate and to communicate the list to Tiziana so that she can contact the GOCDB team. ACTION 2 (RD): to provide a list of these services (action already closed, see list at the end) ACTION 3 (RS): to update EGI when the list of ROC_LA+IGALC core services will be finalized so that the monitoring system for top-BDII availability statistics can be updated (the lsit of top-BDIIs is currently hardcoded). ACTION 4 (RS): to discuss internally an MoU with EGI ====================================== R. Diacovo A number of core services is currently operated by IGALC, including a VO SAM instance of the EELA VO and a DIRAC instance that will be supported by IN2P3 in the future. All these services will be migrated to site ICN-UNAM (Mexico, ROC_LA). ACTION 1 (RD, RS): to agree on the list of sites to be migrate and to communicate the list to Tiziana so that she can contact the GOCDB team. ACTION 2 (RD): to provide a list of these services (action already closed, see list at the end) T. Ferrari In addition to the migration, these core services will have to be harmonized with existing ROC_LA ones. An example is top-BDII which in the past months was underperforming at ROC_LA. ROC services (including operational tools like SAM) should be part of a single entity in GOCDB, so that ROC monthly availability statistics can be generated. Two technical options are possible: - 1 GOCDB grouping like NGI_UA_SERVICES (https://goc.egi.eu/portal/index.php?Page_Type=View_Object&object_id=113183&grid_id=0), which can cluster logically end-points that belong to different GOCDB sites. The naming convention for ROC_LA would be ROC_LA_SERVICES. This is suitable in case multiple end-points are hosted by different countries. - 1 new GOCDB site hosting all these end-points R. Santana Very likely several services (top-BDII, SAM) will be migrated to a new site (CBPF). This will happen however after the migration. ACTION 3 (RS): to update EGI when the list of ROC_LA+IGALC core services will be finalized so that the monitoring system for top-BDII availability statistics can be updated (the lsit of top-BDIIs is currently hardcoded). T. Ferrari: the existing IGALC Resource Provide MoU needs to come to an end. Is a new MoU possible including all new sites of the ROC? ACTION 4 (RS): to discuss internally an MoU with EGI The ROC_LA operations contacts remain as they are today, with Renato being the operations manager. The ROD team won't change. LIST OF IGALC SERVICES prod.vo.eu-eela.eu VO ------------------------------ VOMS MyProxy WMS - may be shared with the ROC WMS if the hardware can handle the load LB - same as the WMS LFC AMGA UI Nagios - I don't think it can be the same box as the ROC Nagios, SAM is tricky =/ top-BDII - Having a top-BDII containing only sites that support the VO is good because the operations may instantly remove faulty sites from it, improving user experience. Also, not having to pull ~80MB over the Atlantic every 15 minutes means better performance and availability. DIRAC - This is managed by Vanessa Hamar from CC-IN2P3 (also in cc). It is my understanding that she will still manage this service, regardless of the location. Not obvious VO manpower: VO shifters - monitor the VO, submit and follow up tickets. It is worth noting that the list of sites supporting this VO is a superset of IGALC sites. Please check bdii.eela.ufrj.br (the aforementioned top-level BDII) for the complete list. VO user support VO software installation - eventually, a new application needs to be installed on the VO area. Honestly, I cannot predict the volume of new applications without a project (such as GISELA) to advertise grid to new potential users, but it is safe to assume that this is not going to be a heavy load, unless more dissemination mechanisms are put in place. ROC services ------------------------------ Nagios WMS and LB BDII