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 SAM central services]]
    67 bytes (8 words) - 15:46, 6 June 2016
  • ...with the funding support of the EGI Participants and the EC, EGI delivers services and activities to enable such international federation. *[[2016-bidding/CheckIn|Services for AAI (CheckIn)]]
    7 KB (868 words) - 09:54, 24 June 2021
  • ...CERN did not submit a bid so services hosted at CERN (ActiveMQ broker and SAM) will require migration to new partners. In order to achieve smooth transit ...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 | Discussions about the status of SAM and message broker migration.
    4 KB (676 words) - 18:58, 6 January 2015
  • ...dpoints per service (RT3347): this requirement needs not negligible GOCDB, SAM and Ops Portal effort to be fully satisfied. JRA1 management sent a summary * Migration of SAM central services:
    2 KB (294 words) - 11:45, 6 January 2015
  • * Operations portal: Improvement of sam-MSG-ops portal synchronization ** The different dashboards are not connect to SAM by using virtual queues and no more topics.
    5 KB (707 words) - 19:58, 24 December 2014
  • * Meeting for the migration of SAM central services ==== 3.2.1 SAM ====
    2 KB (256 words) - 11:43, 6 January 2015
  • ==== 3.2.1 SAM ==== * Migration of central services - Installation and migration guide for SAM central service
    2 KB (203 words) - 11:45, 6 January 2015
  • * Migration of SAM central services ==== 3.2.1 SAM ====
    2 KB (190 words) - 11:43, 6 January 2015
  • * preparations TF Madrid, central syslog workshop =SA1.4 Central tools=
    2 KB (232 words) - 18:15, 6 January 2015
  • ...and preparation of agenda. Main theme: collection of requirements for new services * Planning meeting for transition of SAM services and status of A/R mini project, advancement of VO availability/reliability
    3 KB (437 words) - 18:17, 6 January 2015
  • ...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
  • * Migration of SAM central services: planning of the next steps ==== 3.2.1 SAM ====
    3 KB (447 words) - 11:44, 6 January 2015
  • =SA1.4 Central tools= * New SAM instance for NGI_ZA (https://nagios.c4.csir.co.za/nagios/)
    2 KB (284 words) - 18:18, 6 January 2015
  • * Migration of SAM Central services ==== 3.2.1 SAM ====
    1 KB (167 words) - 11:43, 6 January 2015
  • Central Suspension - Argus performance/scalability discussion with Argus-Support, s =SA1.4 Central tools=
    3 KB (407 words) - 18:14, 6 January 2015
  • * SAM migration call =SA1.4 Central tools=
    3 KB (360 words) - 18:38, 6 January 2015
  • ...zation of EGI CSIRT Operational Procedure for Compromised Certificates and Central Security Emergency suspension * Addressed additional comments on the Compromised cert/central security emergency suspension procedure, document now ready to go to the OM
    5 KB (637 words) - 18:25, 6 January 2015
  • * Cloud resources monitoring: the current SAM central instance cannot monitor Fed Cloud resources for the following reasons: ** Now SAM uses a legacy proxy to monitor the other type of EGI resources. We don't kn
    3 KB (420 words) - 11:43, 6 January 2015
  • ==== 3.2.1 SAM ==== * Developing guide for migration of SAM central services
    1 KB (175 words) - 11:44, 6 January 2015

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