Alert.png 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
  • ...information about the scope of this infrastructure VO, the AUP and related procedures. | [[OPS vo|OPS VO]]
    2 KB (231 words) - 15:20, 12 September 2013
  • === Operation Procedures === NGI-DE is part of EGI. The following EGI procedures approved by the OMB are part of the GOP.
    4 KB (526 words) - 19:16, 28 November 2012
  • | '''[[Operations Procedures|Procedures and Policies]]''' ...re partners. The purpose of a procedure is to define the related workflow. Procedures are approved by the OMB and are periodically reviewed. The intructions prov
    3 KB (311 words) - 14:56, 22 September 2021
  • ...M: EMI-NAGIOS metapackage support ended. This metapackage contains all the procedures to install and configure the EMI probes. We should assess the impact. * SAM EGI Ops phoneconf
    2 KB (227 words) - 11:30, 6 January 2015
  • ...VOMS service and VO membership management for infrastructural VOs (DTEAM, OPS), the provisioning of middleware services needed by the monitoring infrastr == OPS VO Membership management ==
    4 KB (581 words) - 15:45, 6 June 2016
  • This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process. This ticket was created according to procedures: https://wiki.egi.eu/wiki/PROC02 in order to track process.
    13 KB (2,152 words) - 09:44, 8 June 2016
  • ...M: EMI-NAGIOS metapackage support ended. This metapackage contains all the procedures to install and configure the EMI probes. We should assess the impact. ==== 3.2.4 Ops Portal ====
    2 KB (291 words) - 11:31, 6 January 2015
  • ...VMI endorsement procedure is approved by OMB, and it is implemented in the ops tools where necessary * Develop new operational security procedures for the EGI Federated Cloud Service for incident response and vulnerability
    3 KB (432 words) - 11:34, 24 June 2015
  • **[[Operations Procedures|Procedures and Policies]] **[[Other Operations Documentation|DTEAM and OPS VOs]]
    4 KB (538 words) - 14:57, 22 September 2021
  • === Definition of procedures relevant for operational tools === Two procedures relevant for operational tools were approved at the Operations Management B
    9 KB (1,339 words) - 20:31, 24 December 2014
  • Two procedures relevant for operational tools were approved at the Operations Management B * Management of the EGI OPS Availability and Reliability Profile ([[PROC08]])
    5 KB (802 words) - 18:59, 6 January 2015
  • * Staged rollout wiki and procedures updated: ** [[Staged-rollout-procedures]]
    3 KB (480 words) - 18:10, 29 November 2012
  • ...ility. Two monitoring boxes are kept within NGI_PL - one for monitoring of OPS VO services and the other one for monitoring vo.plgrid.pl services which is ...l and global systems as well the regional tool works without any problems. Procedures and teams for handling tickets proved to be well crafted as no tickets stay
    7 KB (1,087 words) - 18:55, 19 December 2012
  • ...ed rollout. Problematic ggus tickets. ARC probes in Nagios. New CA probes. Ops tools info. ...nfo. All components should go into staged rollout in order to be released. Ops tools info. COD issues.
    7 KB (1,011 words) - 18:50, 6 January 2015
  • ...ace OMB in Amsterdam it was decided that all services will be monitored by OPS VO (see details in the following [https://www.egi.eu/indico/contributionDis Work on three procedures relevant for operational tools started:
    9 KB (1,457 words) - 18:59, 6 January 2015
  • =SAM-related Procedures= * Validate ROC or NGI Nagios Procedures: [[PROC05]]
    7 KB (1,025 words) - 12:15, 13 July 2016
  • ...and is now deployed. The algorithm of this probe is incorporated into the ops portal and it will now generated alarms when a site's availability and reli ...participants. Further we gave two presentations from COd in the Future of Ops session at EGI TF12.
    9 KB (1,321 words) - 19:11, 6 January 2015
  • ** [https://www.egi.eu/indico/conferenceDisplay.py?confId=820 Ops-Workshop im April 2012] ([https://www.egi.eu/indico/conferenceTimeTable.py? ...s in the NGI-DE helpdesk) really softly. We have to think about escalation procedures/escalation table with expiration dates dependent on the priority of ticket.
    3 KB (474 words) - 10:13, 23 April 2012
  • ...missioning of unsupported software, followup of missing/incomplete probes, procedures for ticketing of sites and related escalation * ops VO membership management
    6 KB (831 words) - 17:47, 6 January 2015
  • ...been updated, and Staged-rollout-procedures contains information about the procedures/steps that EAs have to follow. * Major changes in procedures, tools, repositories, affecting sites should be announced well in advance (
    7 KB (1,169 words) - 18:38, 4 December 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)