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
  • [[Category:Catch All Grid Core Services]] ...the Service Availability Monitoring framework ([[SAM]]). Usage of the OPS VO is subject to the EGI [[SPG:Documents| Security Policies]].
    998 bytes (148 words) - 15:56, 28 June 2017
  • ...tise, CPU, storage space) regardless of geographical location. They join a VO in order to access resources to meet these needs, after agreeing to a set o = VO Procedures and Policies =
    4 KB (627 words) - 22:12, 4 May 2017
  • * Service name: Operations support services * Service category: Operations
    4 KB (581 words) - 15:45, 6 June 2016
  • == Availability reporting == Within quarter 16 availability reporting was performed as usual on a monthly basis. Publication of results
    3 KB (499 words) - 19:16, 6 January 2015
  • The [[SAM | Service Availability Monitoring (SAM) ]] system is used to monitor the resources within the production infrastructure. SAM monitoring data is used for calculation of availability and reliability of
    3 KB (488 words) - 12:34, 13 August 2021
  • * Service name: Operations portal ...l provides tools supporting security operations, VO management, broadcast, availability reporting.
    4 KB (557 words) - 15:21, 6 June 2016
  • ...yed for service level monitoring and reporting, the existing processes for service level management and the work plan for PY4. == Availability reporting ==
    4 KB (533 words) - 19:16, 6 January 2015
  • | Service Monitoring for Availability and Reliability == ARGO monitoring engine ==
    4 KB (629 words) - 11:11, 30 April 2020
  • *Service name: Operations portal ...l provides tools supporting security operations, VO management, broadcast, availability reporting.
    4 KB (591 words) - 17:36, 20 October 2016
  • = Availability reporting = ==== Operations tools and availability computations ====
    5 KB (688 words) - 19:59, 24 December 2014
  • = Availability reporting = ==== Operations tools and availability computations ====
    6 KB (846 words) - 19:59, 24 December 2014
  • ...production infrastructure. SAM monitoring data is used for calculation of availability and reliability of grid sites. '''Test''' is a procedure which checks specific functionality of a given service, i.e. single measurement (e.g. org.bdii.Freshness, hr.srce.RGMA-CertLifetim
    7 KB (1,025 words) - 12:15, 13 July 2016
  • == Availability reporting == Within quarter 15 availability reporting was performed as usual on a monthly basis. Publication of results
    4 KB (647 words) - 19:16, 6 January 2015
  • * Service name: * Service category: Operations
    5 KB (668 words) - 15:47, 6 June 2016
  • ...ices. The portal provides following tools: VO registration, VO management, VO dashboard, COD dashboard, Operation dashboard, Security dashboard, broadcas | '''Service Availability Monitoring'''
    5 KB (768 words) - 17:19, 17 February 2021
  • =Use case 1: NGI availability reports= ...ed by the NGI, this including the regional tools and other middleware core services operated, for example:
    5 KB (821 words) - 16:11, 6 January 2015
  • ...yed for service level monitoring and reporting, the existing processes for service level management and the work plan for PY4. == Availability reporting ==
    5 KB (698 words) - 19:16, 6 January 2015
  • ...: Infrastructure oversight, security operations, VO management, broadcast, availability reporting. ...//www.egi.eu/services/catalogue/fed-ops.html EGI&nbsp;Federated Operations service].<br>
    4 KB (542 words) - 17:36, 30 December 2015
  • ...t the needs of the NGIs and EGI Operations to introduce the new middleware services and regional calculations. ...on of A/R metrics and will also add VO-wise metric results (in addition to service-wise, site-wise and NGI-wise provisioning of results). Moreover the profile
    3 KB (470 words) - 11:49, 16 September 2013
  • * Service name: Marketplace and Resource allocation ...s/). This will comprise handling of service requests including pay-for-use services, authentication and authorization processes of long-tail of science, users
    3 KB (454 words) - 09:49, 25 October 2016
  • ...<b>existing</b> service endpoints together e.g. into an NGI grouping. The service endpoints themselves will still belong to their parent (non-virtual/physica * Child service endpoints
    7 KB (1,149 words) - 13:31, 18 December 2012
  • == Availability reporting == Within quarter 14 availability reporting was performed as usual on a monthly basis. Publication of results
    5 KB (732 words) - 19:16, 6 January 2015
  • = VO Job oriented tools = * The VO may want to offer a central installation to be used by all users
    12 KB (1,703 words) - 11:33, 23 November 2012
  • | O_title=Publishing middleware service versions | O_desc=All the services should publish in the information system the service version, and the middleware release. Other additional request, automaticall
    5 KB (799 words) - 16:43, 16 October 2012
  • ...istics]] (procedure) and [[Availability and reliability monthly statistics|Availability and reliability monthly statistics]] (reports). New procedure has been crea ...rt in creation of [https://documents.egi.eu/document/1093 EGI OLA] and EGI service proftolio documents. EGI OLA has been approved by OMB in December.<br><br><
    7 KB (1,032 words) - 19:15, 6 January 2015
  • The broad concept of defining/declaring resources availability for EGI Resource Allocation. ...Resource Provider (RP) offers [[Glossary#IT_Service|IT Services]] through service abstractions (e.g., computing power, storage, etc.). NGIs and or individual
    8 KB (1,347 words) - 17:33, 23 October 2014
  • ===Human Services=== ...ding management and developing policies and procedures for the operational services that are integrated into the production infrastructure through a set of dis
    9 KB (1,304 words) - 16:20, 6 January 2015
  • = Introduction to VO SAM = ...each NGI must deploy and operate their own [[SAM |'''Service Availability Monitoring (SAM)''']] system to monitor the fraction of EGI production infrastructure
    14 KB (2,184 words) - 07:47, 13 July 2016
  • ==Human Services== ...ding management and developing policies and procedures for the operational services that are integrated into the production infrastructure through a set of dis
    9 KB (1,292 words) - 16:17, 6 January 2015
  • * meeting with Availability/Reliability Mini Project, discussion of wider adoption of the software prod * Produced NGI core services A/R tables
    5 KB (660 words) - 18:25, 6 January 2015
  • ** based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with underperforming sites ** EGI Operations will check the status of the production cloud services in order to understand which issues (if any) the site has and provide help
    8 KB (1,224 words) - 13:44, 9 May 2016
  • ** based on the availability reliability of monitored services in cloudmon, EGI Operations will start follow up with underperforming sites ** EGI Operations will check the status of the production cloud services in order to understand which issues (if any) the site has and provide help
    8 KB (1,237 words) - 10:58, 18 April 2016
  • ** proposal for site-wide security monitoring ** nagios: CRL checking on services that have gridftp (CEs/SEs) and checking for known vulnerable file permissi
    5 KB (644 words) - 19:57, 24 December 2014
  • * JRA1 phone conference, A/R VO view availability calculation in progress ...O views in the accounting portal where URs are wrongly grouped by role and VO group. Issues identified in wrong Role parsing by DGAS publisher (fixed in
    4 KB (595 words) - 18:20, 6 January 2015
  • ...he related affecting operations assets . The min risks identified are: the availability of specialized support, the commitment to a timely delivering of fixes in c * D4.7 Operations Sustainability. Operations service portfolio completed according to fedSM guidelines. Other sections are being
    5 KB (763 words) - 17:46, 6 January 2015
  • * Services: https://poem.egi.eu/poem/admin/poem/public_service/ This table lists tests used for monitoring operational tools. Tests are executed on the central ARGO instances. Alarms
    6 KB (904 words) - 17:02, 10 October 2019
  • ...ll, and preparation of service management improvement plan for EGI.eu core services * VO validation/decommissioning activities
    3 KB (448 words) - 18:29, 6 January 2015
  • ...egi.eu/providers/operations-manuals/man02_service_intervention_management/ Service Intervention Management] ...volve or lead to the possibility of a loss, or noticeable degradation of a service.
    13 KB (1,653 words) - 17:34, 23 September 2021
  • ...agers to make sure that all the hostnames and aliases used to connect to a service are included in its host certificate Subject Alternative Name field''', at * sites that could be affected by this future change are the ones running services whose clients may use globus-gssapi-gsi for authentication (CE, FTS, SRM, G
    7 KB (1,108 words) - 16:42, 14 March 2016
  • A second, more detailed review to promote service exchange across NGIs is being prepared: *'Updating VO ID cards' campaign and decommission of obsoleted VOs
    3 KB (490 words) - 18:25, 6 January 2015
  • * VO validation/decommissioning activities * Produced core services AR tables
    2 KB (299 words) - 18:31, 6 January 2015
  • | Operations Tools and Availability Calculation (EGI TF) | Dedicated EGI TF session on operational tools monitoring and availability calculation.
    7 KB (1,076 words) - 19:09, 6 January 2015
  • ...nal services (as providers and/or consumers). A new survey with a detailed service portfolio will be produced to help NGIs in sharing operational effort in pr * definition of SHA-2 monitoring work plan
    5 KB (705 words) - 18:25, 6 January 2015
  • ...on the latest versions of Grid middleware as well as with the EGI-InSPIRE monitoring and operations procedures. * VO ID card for vo.aginfra.eu was updated.
    6 KB (871 words) - 14:03, 9 January 2015
  • ...f suspension policy related to the deployment of unsupported glite 3.1/3.2 services ** COD/CSIRT meeting to evaluate the status of unsupported middleware monitoring process
    6 KB (831 words) - 17:47, 6 January 2015
  • * meeting on cloud monitoring * 'Updating VO ID cards' campaign and decommission of obsoleted VOs
    5 KB (637 words) - 18:25, 6 January 2015
  • * handling of GGUS tickets and ongoing VO ID card update campaign * preparation of wiki pages on EGI.eu service management plan
    4 KB (638 words) - 18:15, 6 January 2015
  • * Updated document describing the VO availability requirement * monitoring of progress of mw upgrade campaign, coordination of development of new prob
    5 KB (819 words) - 18:19, 6 January 2015
  • *handling of operations tickets and VO services tickets *status assessment of EMI-1 decommissioning campaign: only 2 service end points are left for being upgraded
    4 KB (563 words) - 18:15, 6 January 2015
  • ...ll, and preparation of service management improvement plan for EGI.eu core services * VO validation/decommissioning activities
    4 KB (615 words) - 18:16, 6 January 2015
  • *'Updating VO ID cards' campaign and decommission of obsoleted VOs * SHA-2 monitoring
    4 KB (620 words) - 18:13, 6 January 2015
  • ....e. the resource BDII needs to be added to the site BDII, as for any other service in the site)'''. ...correctly published in the information system, so NGIs with VOMS gLite 3.2 service instances should check this.
    4 KB (626 words) - 12:24, 15 October 2012
  • == EGI central monitoring instance (ARGO) == Since July 1st, the EGI infrastructure is being monitored by two monitoring instances that can be found on these addresses:
    13 KB (1,956 words) - 16:16, 26 September 2016
  • ...ll, and preparation of service management improvement plan for EGI.eu core services * VO validation/decommissioning activities
    4 KB (536 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 versions
    4 KB (521 words) - 18:15, 6 January 2015
  • = Service/Activities = ...l core infrastructure platform service component whose continuity and high availability configuration must be ensured.
    10 KB (1,384 words) - 09:54, 24 June 2021
  • ...eduled downtime of EGI.eu central services, and discussion of GGUS minimum service level targets, revision of status of the report generator ...nsupported VOMS instances: opening of NGI tickets to request that affected service end-points are put in downtime (first escalation step)
    6 KB (871 words) - 18:19, 6 January 2015
  • * Operations Portal: discussion of VO availability/reliability computation algorithm for implementation of the first prototype * fixing many issues with incomplete/incorrect information in VO ID cards
    6 KB (884 words) - 18:24, 6 January 2015
  • ...updates to existing pages, discussion of new content about the operations services as part of the EGI portfolio ...of changes to the EGI core infrastructure services to make them comply to service management best practices: assessment and next steps
    4 KB (545 words) - 18:24, 6 January 2015
  • ...ll, and preparation of service management improvement plan for EGI.eu core services * VO validation/decommissioning activities
    3 KB (412 words) - 18:30, 6 January 2015
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    7 KB (1,130 words) - 12:04, 14 January 2022
  • * preparation of survey on service configuration tools in preparation to the end of support of Yaim core ...iguration campaign in GOCDB of NGI core services in preparation to the NGI availability/reliability monthly statistics
    6 KB (884 words) - 18:20, 6 January 2015
  • * GOCDB meeting to assess implications of service renaming and implementation plans ...ftware support extensions (dCache), start of DPM EMI 1 and EMI 2 v < 1.8.6 monitoring campaign
    4 KB (629 words) - 18:16, 6 January 2015
  • * discussion about the addition/renaming of GOCDB service types (SQUID and MPI) ...topology information in GOCDB (almost completed) for the generation of NGI availability statistics
    5 KB (714 words) - 18:20, 6 January 2015
  • ** Georgia (NGI_GE): monitoring was taken over by Serbian NGI (NGI_AEGIS) on December 13th 2010 ...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/contributionDispla
    9 KB (1,457 words) - 18:59, 6 January 2015
  • ** LCMAPS-plugins-vo-ca-ap 0.0.1-1 ** LCMAPS-plugins-vo-ca-ap 0.0.1-1
    11 KB (1,581 words) - 11:06, 14 June 2016
  • * Migration of SAM central services: planning of the next steps * SAM/Nagios instance monitoring EUDAT infrastructure setup at surfSARA
    3 KB (447 words) - 11:44, 6 January 2015
  • = Service/Activities = The Accounting Portal receives and stores the site, user, and VO level summaries generated by the Accounting Repository and provides views v
    13 KB (1,910 words) - 09:55, 24 June 2021
  • ...GOCDB), the accounting repository and portal, and the Service Availability Monitoring framework. The VO registration tool, the broadcast and downtime system, the periodic, operati
    9 KB (1,275 words) - 20:58, 24 December 2014
  • *VO validation/decommissioning activities ...about new service types in GOCDB &amp; support for multiple endpoints per service
    3 KB (398 words) - 18:30, 6 January 2015
  • * FedSM meeting and implementation plan for improvement of EGI.eu core services * assessment of VO availability prototype
    4 KB (641 words) - 18:24, 6 January 2015
  • ...Marian Babik @David: can you confirm that this applies in general for any services ? Since https://rt.egi.eu/rt/Ticket/Display.html?id=3347 suggests this is o ...meredith hi Marian, yes, multiple endpoints per service would apply to all service types – of course we need to have a new list of InterfaceName values used
    20 KB (2,745 words) - 12:44, 1 December 2014
  • ...tifact templates needed to improve service level management of EGI.eu core services * preparation of SHA-2 monitoring infrastructure, status assessment of services not SHA-2 compliant
    5 KB (768 words) - 18:23, 6 January 2015
  • ...ll, and preparation of service management improvement plan for EGI.eu core services * VO validation/decommissioning activities
    4 KB (553 words) - 18:16, 6 January 2015
  • ...agios system for monitoring of sites hosting unsupported gLite 3.1 and 3.2 services ...involving EGI, PRACE and relevant user communities, pilot of GlobusOnline service for transfer across peer infrastructures
    5 KB (764 words) - 17:45, 6 January 2015
  • ...m VO (for testing purposes) as described at: https://lcg-voms.cern.ch:8443/vo/dteam/vomrs for the group /dteam/NGI_DE/..your_resource_center.. * enable monitoring of the site
    7 KB (1,180 words) - 10:36, 8 July 2011
  • | talk on development and utilization of the Pakiti service in EGI, http://event.twgrid.org/isgc2011/slides/SecurityandNetworking/1/pre monitoring.https://egi-csirt.scc.kit.edu/
    5 KB (667 words) - 15:10, 7 January 2015
  • ** Added lcmaps-plugins-vo-ca-ap for SL6, needed for supporting the IGTF IOTA profile of CAs ...l ATP and POEM. These services became obsolete when we switched to central monitoring instances in July.
    8 KB (1,160 words) - 15:37, 5 December 2016
  • * Meeting on VO availability and reliability statistics + NGI statistics: discussion on how to consume t * Review of status of NGI service topology information in GOCDB: France and Germany missing.
    5 KB (796 words) - 18:17, 6 January 2015
  • ...uctures and RIs. The current set of services will be expanded to include a Service Registry and Marketplace. The main targets of this task are:<br> ...services through technological innovation and new services in the area of Service Registry and Marketplace and resource allocation.
    18 KB (2,697 words) - 16:54, 13 January 2016
  • == Monthly Availability/Reliability == ***INDIACMS-TIFR: SRM service not published in the BDII, DPM 1.9.0 version, asked to upgrade...
    16 KB (2,342 words) - 14:38, 13 January 2020
  • *Notifications flag at the service endpoint level ...his way ARGO will retrieve from GOC-DB the information about the sites and services whom sending the email notification and the related recipients.
    12 KB (1,798 words) - 17:08, 9 July 2019
  • ! style="border-bottom:1px solid black;" | Monitoring ! style="border-bottom:1px solid black;" | Monitoring
    23 KB (3,100 words) - 11:29, 10 December 2013
  • ...always a set of variable that *must* be edited in any installation of the service. While there are variables that can stay as they are, if particular customi ...pts should check that *all* the variables so identified were edited by the service administrator.
    26 KB (4,028 words) - 14:29, 10 December 2014
  • ...022 GGUS 142022]: Decision on preferred storage access protocols, required monitoring probes (assigned to Operations, on hold) **AppDB entry of VM image used by monitoring probe has expired and manual refresh was necessary, the probe does not chec
    12 KB (1,655 words) - 14:00, 9 September 2019
  • ...d by </span>'''<span style="color:red">[[EGI-InSPIRE-Tasks|'''this updated service decomposition''']]</span>'''<span style="color:red">.</span>''' ...action of the user, operations and technology communities; ‘Infrastructure Services’ for securely accessing resource hosted by different organisations.
    23 KB (3,395 words) - 18:36, 19 December 2012
  • Back to main page: [[Services Availability Continuity Plans]] ...ailability and continuity of the service. The process is concluded with an availability and continuity test.
    9 KB (1,427 words) - 12:18, 7 December 2021
  • * JRA1 meeting and requirement for change of availability computation ...having central banning (according to the proposed change in the policy for service operations)
    7 KB (1,005 words) - 18:19, 6 January 2015
  • ngi-de-monitoring@lists.kit.edu -> NGI-DE Nagios Team * Availability/reliability statistics
    4 KB (561 words) - 17:29, 17 May 2013
  • == Monthly Availability/Reliability == *** '''USC-LCG2''': SRM failures, services restarted
    12 KB (1,785 words) - 14:01, 13 September 2021
  • <b>Applications on Demand (AoD) Service Information pages</b> ...s://www.egi.eu/services/applications-on-demand/ EGI Applications on Demand service] (AoD) is the EGI’s response to the requirements of researchers who are i
    25 KB (3,775 words) - 12:04, 23 December 2020
  • #'''[https://voms.hellasgrid.gr:8443/voms/dteam Register] to Dteam VO''' - Dteam membership will give you possibility to test sites and debug pro ...eam is responsible for detecting problems, coordinating the diagnosis, and monitoring the problems through to a resolution. It monitors sites in their region, an
    8 KB (1,314 words) - 14:50, 23 October 2014
  • ...the possibility to also use an instance of the data integration Lavoisier service at IN2P3 Computing Center, in addition to the one at I3S. This would help g ...the possibility to also use an instance of the data integration Lavoisier service at IN2P3 Computing Center, in addition to the one at I3S. This would help g
    30 KB (4,630 words) - 12:01, 28 April 2014
  • ...tifact templates needed to improve service level management of EGI.eu core services * handling of GGUS tickets and ongoing VO ID card update campaign
    4 KB (538 words) - 18:14, 6 January 2015
  • === What does 'VO Support' consist in? === ...ous extend depending on VOs. Hereafter we provide a non exhaustive list of VO Support tasks:
    26 KB (4,265 words) - 15:46, 17 September 2013
  • *Notifications flag at the service endpoint level ...his way ARGO will retrieve from GOC-DB the information about the sites and services whom sending the email notification and the related recipients.
    12 KB (1,785 words) - 13:17, 17 June 2019
  • ...ly see monthly "metrics report for GGUS" see "Amount of tickets per SU and VO" --> <!-- tickets solved: I can't find a way to extract the number of solve | M.SA1.Operation.1, NGI monthly availability and reliability - P
    16 KB (2,273 words) - 16:16, 6 January 2015
  • * APEL accounting service was successfully deployed on CESNET cluster, complete migration to APEL wil ...uthority CESNET CA3 has started, most of services are already running with service certificate signed by new CA.
    5 KB (742 words) - 15:10, 7 January 2015
  • ...vices with other partner NGIs. EGI.eu will support NGIs interested in this service provisioning model with its coordination function during PY4 ...ion of service management processes and requirements to various operations services. Status of these will be assessed at the beginning of March to understand t
    7 KB (1,057 words) - 18:18, 6 January 2015
  • ...ssment of status and progress of COD tickets for unsupported gLite 3.1/3.2 services * collection of information of service deployment by VO and discipline
    6 KB (862 words) - 17:45, 6 January 2015

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