Difference between revisions of "EGI-InSPIRE:SA1.4-QR13"
(2 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Template: | {{Template:EGI-Inspire menubar}} | ||
{{Template:Inspire_reports_menubar}} | |||
{{TOC_right}} | |||
= 1. Task Meetings = <!-- | = 1. Task Meetings = <!-- | ||
Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes. | Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes. | ||
Line 25: | Line 28: | ||
There were no ActiveMQ upgrades in this quarter. APEL SSM client released as part of UMD 3 is using the production ActiveMQ broker network. In order to enable authentication of gLite-APEL nodes component for retrieving list of gLite-APELs DNs from GOCDB was deployed on production message brokers. | There were no ActiveMQ upgrades in this quarter. APEL SSM client released as part of UMD 3 is using the production ActiveMQ broker network. In order to enable authentication of gLite-APEL nodes component for retrieving list of gLite-APELs DNs from GOCDB was deployed on production message brokers. | ||
Deployment of the GOCDB 5 was postponed due to the requirement of SAM team to keep site and service endpoint IDs. Other operational tools performed tests of | Deployment of the GOCDB 5 was postponed due to the requirement of SAM team to keep site and service endpoint IDs from the version 4. Other operational tools performed tests of new GOCDB 5 features. | ||
Operations portal's development of the new A/R calculation continued and the focus was shifted to fetaures requested by the new mini-project "A new approach to Computing Availability and Reliability Reports". Due to the new developments release of Operations Portal was postponed. | Operations portal's development of the new A/R calculation continued and the focus was shifted to fetaures requested by the new mini-project "A new approach to Computing Availability and Reliability Reports". Due to the new developments release of Operations Portal was postponed. | ||
Line 60: | Line 63: | ||
Deployment of the Operations Portal with the new A/R calculations is expected by the end of the year. | Deployment of the Operations Portal with the new A/R calculations is expected by the end of the year. | ||
SAM Update-22 is scheduled to start staged rollout at the beginning of September. | SAM Update-22 is scheduled to start staged rollout at the beginning of September. | ||
Latest revision as of 18:53, 6 January 2015
EGI Inspire Main page |
Inspire reports menu: | Home • | SA1 weekly Reports • | SA1 Task QR Reports • | NGI QR Reports • | NGI QR User support Reports |
1. Task Meetings
Date (dd/mm/yyyy) | Url Indico Agenda | Title | Outcome |
---|---|---|---|
... | .... | ... | ... |
2. Main Achievements
There were no ActiveMQ upgrades in this quarter. APEL SSM client released as part of UMD 3 is using the production ActiveMQ broker network. In order to enable authentication of gLite-APEL nodes component for retrieving list of gLite-APELs DNs from GOCDB was deployed on production message brokers.
Deployment of the GOCDB 5 was postponed due to the requirement of SAM team to keep site and service endpoint IDs from the version 4. Other operational tools performed tests of new GOCDB 5 features.
Operations portal's development of the new A/R calculation continued and the focus was shifted to fetaures requested by the new mini-project "A new approach to Computing Availability and Reliability Reports". Due to the new developments release of Operations Portal was postponed.
SAM Update-22 release was finalized and it contains significant changes compared to the previous release. Detailed list of test changes can be found here: https://tomtools.cern.ch/confluence/display/SAMDOC/FAQs#FAQs-WhichmetricshavebeenchangedbetweenSAMUpdate20andSAMUpdate22%3F. In order to clear out bugs before the staged rollout it was decided to have a testing phase. Testing phase started on June 21st. In the testing phase NGIs deployed additional instance and tested the SAM. Detailed list of SAM/Nagios instances can be found on the following page: SAM Instances.
Monitoring instance midmon was extended with the new set of tests monitoring middleware compliance to SHA-2 certificates.
Operations tests were extended with the following tests:
- operations tests performed by ops-monitor.cern.ch SAM instance
- user DN publishing tests performed by midmon.egi.eu instance
- SHA-2 compliance tests for service types CREAM-CE, VOMS and WMS performed by midmon.egi.eu instance
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|
4. Plans for the next period
GOCDB v5 is planned to be released to production in the next quarter.
Deployment of the Operations Portal with the new A/R calculations is expected by the end of the year.
SAM Update-22 is scheduled to start staged rollout at the beginning of September.