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.

Difference between revisions of "EGI-InSPIRE:SA1.4-QR10"

From EGIWiki
Jump to navigation Jump to search
Line 62: Line 62:
! scope="col" | Mitigation Description
! scope="col" | Mitigation Description
|-
|-
|  
|High availability of central operational tools is needed. || '''GOCDB''': dynamic loadbalancing DNS setup is provided for the address goc.egi.eu. Secondary instance in Fraunhofer institute is deployed, but needs to be updated to the latest version.
|  
|-
|-
|  
|Monitoring of MW version
|  
|As part of middleware upgrade campaign monitoring of MW versions was implemented on security monitoring instance. In the future this monitoring should become part of NGI SAM instances.
|}
|}


= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) -->
= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) -->

Revision as of 10:58, 13 November 2012

1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
30/08/2012 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1150 Meeting regarding monitoring of brokers At the meeting it was defined which tests should be run against broker network.
17/10/2012 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1245 Message brokers status update
24/10/2012 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1245 Discussion on PROD Broker network

2. Main Achievements

GOCDB version 4.4 was released on September 10th. Detailed list of new features can be found in JRA1 section. GOCDB failover instance was deployed at the Fraunhofer institute in Germany, however the failover instance is still running the old version of GOCDB.

GOCDB read-write portal at https://gocdb4.esc.rl.ac.uk/portal was decommissioned on July 31st and replaced by a single read-write version at https://goc.egi.eu/portal. This consolidated all GOCDB components (including the PI) under the same URL.

GOCDB failover instance is still in progress of upgrade to the latest version.


Two new versions of Operations portal were deployed in this quarter: 2.9.4 on June 12th and 2.9.5 on July 3rd. The major change in new versions is module for availability and reliability of core NGI services. Detailed list of new features can be found in JRA1 section. At the end of the quarter there were four NGI instances: NGI_BY, NGI_CZ, NGI_GRNET and NGI_IBERGRID.

Transition from topic to virtual destination in order to improve synchronization between SAM instances and Operations portal is in progress.


SAM Update-17 staged rollout successfully finished on August 27th. By the end of the quarter 30 instances were upgraded to SAM Update-17. At the end of the quarter following SAM/Nagios instances were in production:

  • 28 NGI instances covering 39 EGI partners
  • 3 ROC instances covering 3 EGI partners
  • 3 external ROC instances covering the following regions: Canada, IGALC and LA.

Detailed list of SAM/Nagios instances can be found on the following page: SAM Instances.

The new SAM instance for monitoring operational tools was deployed in October: https://ops-monitor.cern.ch/nagios. Integration with the central ACE was still in the progress at the end of the quarter.

3. Issues and Mitigation

Issue Description Mitigation Description
High availability of central operational tools is needed. GOCDB: dynamic loadbalancing DNS setup is provided for the address goc.egi.eu. Secondary instance in Fraunhofer institute is deployed, but needs to be updated to the latest version.
Monitoring of MW version As part of middleware upgrade campaign monitoring of MW versions was implemented on security monitoring instance. In the future this monitoring should become part of NGI SAM instances.

4. Plans for the next period