Difference between revisions of "EGI-InSPIRE:SA1.4-QR13"
Line 23: | Line 23: | ||
--> | --> | ||
There were no ActiveMQ upgrades in this quarter. APEL SSM client released as part of UMD 3 is using production ActiveMQ. 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 GOCDB 5 was postponed due to the requirement of SAM team to keep site and service endpoint IDs. | Deployment of GOCDB 5 was postponed due to the requirement of SAM team to keep site and service endpoint IDs. |
Revision as of 20:20, 3 August 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
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 GOCDB 5 was postponed due to the requirement of SAM team to keep site and service endpoint IDs.
Operation portal's development of new A/R views 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 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.
SAM Update-22 is scheduled to start staged rollout at the beginning of September.