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

Page title matches

Page text matches

  • #REDIRECT [[EGI Core activities:2013-bidding Monitoring central services]]
    74 bytes (8 words) - 15:46, 6 June 2016
  • === Annex “NGI-DE infrastructure services” === * monitoring facilities
    811 bytes (98 words) - 17:59, 12 November 2012
  • ...with the funding support of the EGI Participants and the EC, EGI delivers services and activities to enable such international federation. *[[2016-bidding/monitoring|Monitoring]]
    7 KB (868 words) - 09:54, 24 June 2021
  • ...ttps://wiki.egi.eu/wiki/Core_EGI_Activities). CERN did not submit a bid so services hosted at CERN (ActiveMQ broker and SAM) will require migration to new part ...is critical because it has to be performed before the start of SAM central services migration.
    3 KB (506 words) - 18:53, 6 January 2015
  • | Migration of SAM Central Services | Migration of SAM Central Services
    4 KB (676 words) - 18:58, 6 January 2015
  • --- How to certify a resource centre with UNICORE services only: --- * run site-BDII and publish data to central BDII (UNICORE will allow for that with its next release in Feb/March 2013)
    1 KB (188 words) - 13:31, 29 November 2012
  • ...ribution of the monthly league tables regarding Resource Center and EGI.eu services and the maintenance of the relevant wiki space: = Catch all services and core grid services =
    6 KB (846 words) - 19:59, 24 December 2014
  • * preparations TF Madrid, central syslog workshop =SA1.4 Central tools=
    2 KB (232 words) - 18:15, 6 January 2015
  • * MSG: Enhance monitoring tools for PROD MSG network ** CERN team implemented detailed monitoring of queues used by known clients.
    5 KB (707 words) - 19:58, 24 December 2014
  • * meeting on cloud monitoring ...zation of EGI CSIRT Operational Procedure for Compromised Certificates and Central Security Emergency suspension
    5 KB (637 words) - 18:25, 6 January 2015
  • * Migration of SAM central services: * Migration of central services - Installation and migration guide for SAM central service
    2 KB (294 words) - 11:45, 6 January 2015
  • =SA1.4 Central tools= * Ticket monitoring
    2 KB (284 words) - 18:18, 6 January 2015
  • ...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
  • * Migration of central services - Installation and migration guide for SAM central service *Ticket monitoring
    2 KB (203 words) - 11:45, 6 January 2015
  • * Meeting for the migration of SAM central services * Support for the migration of SAM central services
    2 KB (256 words) - 11:43, 6 January 2015
  • =SA1.4 Central tools= * Issue with message broker monitoring: https://ggus.eu/ws/ticket_info.php?ticket=98637
    3 KB (428 words) - 18:30, 6 January 2015
  • Results of a survey on the federation of NGI services opened in June are being collected. * preparation of ARGUS deployment programme to enforce the policy on central user emergency suspension
    4 KB (544 words) - 18:21, 6 January 2015
  • A questionnaire about federating NGI services was circulated two weeks ago. * planning of SHA-2 readiness monitoring campaign
    3 KB (413 words) - 18:18, 6 January 2015
  • =SA1.4 Central tools= * FedCloud monitoring
    3 KB (490 words) - 18:25, 6 January 2015
  • ...about interest of the NGIs in sharing (offering and consuming) operational services was presented at the August OMB: https://indico.egi.eu/indico/getFile.py/ac ...rvices based on the availability of local expertise and effort. Sharing of services will structured by establishing MoUs between NGIs or by giving free access.
    4 KB (612 words) - 18:15, 6 January 2015

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