The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Search results
Jump to navigation
Jump to search
- Central Suspension - Argus performance/scalability discussion with Argus-Support, s =SA1.4 Central tools=3 KB (407 words) - 18:14, 6 January 2015
- ...ampaign, definition of next steps, preparation of probes for EMI 1 version monitoring * Produced EGI core services availability table4 KB (526 words) - 18:19, 6 January 2015
- * Migration of SAM central services * Preparing for the migration of SAM central services2 KB (190 words) - 11:43, 6 January 2015
- * Migration of SAM central services: planning of the next steps * SAM/Nagios instance monitoring EUDAT infrastructure setup at surfSARA3 KB (447 words) - 11:44, 6 January 2015
- *handling of operations tickets and VO services tickets *status assessment of SHA-2 migration campaign of EMI-2 services that still do not support this capability4 KB (563 words) - 18:15, 6 January 2015
- * Work on details of Central-Banning Miniproject ...ng [https://indico.egi.eu/indico/conferenceDisplay.py?confId=1326 Pilot 4. Monitoring and Resource discovery] - EGI/EUDAT/PRACE collaboration activity5 KB (714 words) - 18:20, 6 January 2015
- ...OMB is analyzing the results of the survey on federation of NGI operations services * discussion of DPM tests business logics for the assessment of status of DPM monitoring for decommissioning of vulnerable and unsupported DPM instances, preparatio6 KB (841 words) - 18:16, 6 January 2015
- * Migration of SAM Central services * Monitoring and sys-admin v5 given network and SAN issues at RAL.1 KB (167 words) - 11:43, 6 January 2015
- =SA1.4 Central tools= * Monitoring tickets.3 KB (474 words) - 18:20, 6 January 2015
- ...e due to a number of issues with version publishing in BDII. The number of services currently monitored is still incomplete. * discussion of next steps for MPI monitoring in nagios5 KB (747 words) - 18:17, 6 January 2015
- ...l, and preparation of service managenment improvement plan for EGI.eu core services * planning of development of new dCache test for SHA-2 monitoring and decommissioning of non compliant software versions4 KB (521 words) - 18:15, 6 January 2015
- * Cloud resources monitoring: the current SAM central instance cannot monitor Fed Cloud resources for the following reasons: * FedCloud monitoring3 KB (420 words) - 11:43, 6 January 2015
- * Developing guide for migration of SAM central services * Discussing cloud monitoring probe solution1 KB (175 words) - 11:44, 6 January 2015
- ...ll, and preparation of service management improvement plan for EGI.eu core services =SA1.4 Central tools=4 KB (536 words) - 18:17, 6 January 2015
- * Discussion with SA1.2 about activities related to central banning * start of configuration campaign in GOCDB of NGI core services in preparation to the NGI availability/reliability monthly statistics6 KB (884 words) - 18:20, 6 January 2015
- *'''31-08-2015''': dCache 2.6.X 2 version monitoring probes start returning CRITICAL, alarms are displayed in the Operations Das ...ache 2.6.X decommissioning deadline - after this date all the dCache 2.6.X services must be decommissioned, upgraded to a supported version or in downtime.15 KB (2,164 words) - 19:57, 7 May 2015
- =SA1.4 Central tools= * coordinating migration of the central SAM and message broker network3 KB (360 words) - 18:38, 6 January 2015
- * Produced NGI core services A/R tables * Opened a GGUS ticket for misconfigured services in GOCDB (ARMGRID)5 KB (660 words) - 18:25, 6 January 2015
- ...ons sustainability: Various NGIs expressed interest in sharing operational services (as providers and/or consumers). A new survey with a detailed service portf * definition of SHA-2 monitoring work plan5 KB (705 words) - 18:25, 6 January 2015
- | "Monitoring & follow up of sites running unsupported software" - joint with EGI Operati ...before the deadline and the remaining small number voluntarily removed the services from production. There was no requirement to suspend a site. The final comp8 KB (1,247 words) - 18:43, 6 January 2015