Difference between revisions of "EGI-InSPIRE:SA1.3-QR16"
Line 74: | Line 74: | ||
--> | --> | ||
During this quarter there were a total of two releases ([http://repository.egi.eu/2014/02/20/release-umd-3-5-0/] 3.5.0) and | During this quarter there were a total of two releases for UMD-3 components ([http://repository.egi.eu/2014/02/20/release-umd-3-5-0/] 3.5.0) and ([http://repository.egi.eu/2014/04/07/release-umd-3-6-0/] 3.6.0) and one last release for UMD-2 ([http://repository.egi.eu/2014/02/11/release-umd-2-8-0/] 2.8.0). | ||
In total 13 products and sub-components were deployed and tested. Even if only one major release was deployed the number of staged rollout reports was in-line with the pos EMI scenario with a Total Number of 36 on which 17 different components were tested spread over 16 sites. | |||
Of relevance during this quarter was the issues found during the UMD 3 release process experienced with the latest Globus update (5.2.5), conflicting with the test installation of the products from the Release Candidate (RC). The release has been delayed some weeks in order to find a solution to the problem. The solution to the problem was to test the components individually before the RC so we could find the problematic rpm's. | Of relevance during this quarter was the issues found during the UMD 3 release process experienced with the latest Globus update (5.2.5), conflicting with the test installation of the products from the Release Candidate (RC). The release has been delayed some weeks in order to find a solution to the problem. The solution to the problem was to test the components individually before the RC so we could find the problematic rpm's. |
Revision as of 18:31, 29 April 2014
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 |
---|---|---|---|
Date (03/02/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2054 | EGI Operations meeting | Regular operations meeting |
(03/02/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2055 | UMD Release Team | Regular meeting |
(10/02/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2068 | EGI Operations meeting | Regular operations meeting |
(17/02/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2076 | UMD Release Team | Regular meeting |
(10/03/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2106 | EGI Operations meeting | Regular operations meeting |
(17/03/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2078 | UMD Release Team | Regular meeting |
(18/03/2014) | https://indico.cern.ch/event/306380/ | Middleware Readiness Working Group meeting | WLCG meeting |
(31/03/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2119 | UMD Release Team | Regular meeting |
(07/04/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2151 | EGI Operations meeting | Regular operations meeting |
(14/04/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2178 | UMD Release Team | Regular meeting |
(28/04/2014) | https://indico.egi.eu/indico/conferenceDisplay.py?confId=2192 | UMD Release Team | Regular meeting |
2. Main Achievements
During this quarter there were a total of two releases for UMD-3 components ([1] 3.5.0) and ([2] 3.6.0) and one last release for UMD-2 ([3] 2.8.0).
In total 13 products and sub-components were deployed and tested. Even if only one major release was deployed the number of staged rollout reports was in-line with the pos EMI scenario with a Total Number of 36 on which 17 different components were tested spread over 16 sites.
Of relevance during this quarter was the issues found during the UMD 3 release process experienced with the latest Globus update (5.2.5), conflicting with the test installation of the products from the Release Candidate (RC). The release has been delayed some weeks in order to find a solution to the problem. The solution to the problem was to test the components individually before the RC so we could find the problematic rpm's.
Also important to mention the participation in the Middleware Readiness Working Group. The main goal on participating in this meeting its to Keep the dialog open between EGI and WLCG communities, maybe bridging the processes used in the two communities, i.e. by making available the testing versions for sites which are both WLCG and participate in the EGI Staged Rollout. With experiments' agreement to participated in such tests, we can help to make the UMD production versions available sooner. The meeting accoured during December and the main topics discussed were:
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|
OpenSSL "Heartbleed" vulnerability | Follow this critical issue with Product teams and see if the updates does not broke the production infrastructure. |
4. Plans for the next period
End of project