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
- ...or notification purposes in case of unscheduled downtime of EGI.eu central services, and discussion of GGUS minimum service level targets, revision of status o ...of status and progress of sites that promised to decommission unsupported services by the end of November, assessment of migration of unsupported VOMS instanc6 KB (871 words) - 18:19, 6 January 2015
- * Developing guide for migration of SAM central services * Discussing cloud monitoring probe solution2 KB (213 words) - 11:44, 6 January 2015
- ...updates to existing pages, discussion of new content about the operations services as part of the EGI portfolio ...ng about the implementation plan of changes to the EGI core infrastructure services to make them comply to service management best practices: assessment and ne4 KB (545 words) - 18:24, 6 January 2015
- =SA1.4 Central tools= * Monitoring tickets.4 KB (595 words) - 18:20, 6 January 2015
- * EGI-CSIRT meeting on operational implications of having central banning (according to the proposed change in the policy for service operati * planning of activities for testbed on central allocation of resources7 KB (1,005 words) - 18:19, 6 January 2015
- * Reschedule glue-validation campaign with gradual migration to active monitoring =SA1.4 Central tools=3 KB (442 words) - 18:30, 6 January 2015
- ** Help in the campaign to decommission UMD-1 in favor of UMD-3 services (whenever possible) ** MSG: Enhance monitoring tools for PROD MSG network3 KB (374 words) - 19:54, 24 December 2014
- ...ronment. Traceability continues to be of utmost importance and logging and monitoring will also be essential. We agreed that we need to start by considering some ...work has also been done on the possible methods for achieving the security monitoring of all worker nodes in a site.9 KB (1,376 words) - 18:43, 6 January 2015
- ...ll, and preparation of service management improvement plan for EGI.eu core services =SA1.4 Central tools=3 KB (412 words) - 18:30, 6 January 2015
- ....ac.uk/~dbauer/grid/staged_rollout_emi2.html) tracking the roll out of EMI services in the UK. ...ages and opens tickets for the monitoring pages not working as part of her Monitoring Core Tasks.7 KB (1,021 words) - 13:14, 9 January 2015
- ...ftware support extensions (dCache), start of DPM EMI 1 and EMI 2 v < 1.8.6 monitoring campaign =SA1.4 Central tools=4 KB (629 words) - 18:16, 6 January 2015
- =SA1.4 Central tools= * discussion about new GOCDB services (ARC-CE, MPI)5 KB (796 words) - 18:17, 6 January 2015
- * preparation of SHA-2 monitoring plan ...ar, planning of future release, change of decommissioning plan and related monitoring infrastructure4 KB (571 words) - 18:25, 6 January 2015
- ...ll, and preparation of service management improvement plan for EGI.eu core services =SA1.4 Central tools=3 KB (448 words) - 18:29, 6 January 2015
- *Operation of e-infrastructure services *Cloud services for science and education9 KB (1,334 words) - 14:38, 2 June 2014
- * FedSM meeting and implementation plan for improvement of EGI.eu core services * discussion of SHA-2 support next steps (monitoring infrastructure, upgrade to SHA-2 compliant middleware)4 KB (641 words) - 18:24, 6 January 2015
- * Presentation and discussion of central user suspensions issues at OMB (26 Mar) =SA1.4 Central tools=6 KB (815 words) - 18:16, 6 January 2015
- * monitoring of progress of mw upgrade campaign, coordination of development of new prob * planning for operational implications of supporting central banning5 KB (819 words) - 18:19, 6 January 2015
- =SA1.4 Central tools= * Ticket monitoring4 KB (518 words) - 18:24, 6 January 2015
- According to our monitoring, your site is running EMI 2 software, 2. UPGRADE of EMI 2 SERVICES22 KB (3,376 words) - 14:48, 23 October 2014