Difference between revisions of "SA1.3-QR12"
Line 26: | Line 26: | ||
PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT) | PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (AVOID BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN AN OVERALL REPORT) | ||
--> | --> | ||
Along this quarter 3 UMD releases were achieved: [http://repository.egi.eu/2013/04/05/release-umd-2-4-1/ UMD 2.4.1], [http://repository.egi.eu/2013/02/18/release-umd-2-4-0/ UMD 2.4.1], [http://repository.egi.eu/2013/04/05/release-umd-1-10-1/ UMD 1.10.1] and [http://repository.egi.eu/2012/12/17/release-umd-2-3-1/ UMD 2.3.1]. While for the UMD 1 repository there was a single release, 1.10.1, which provided security fix for the CREAM-CE, in UMD 2 there were 2 releases. In total this quarter a total of 20 software components from both IGE and EMI Technological Providers were released into production taking notice that for WMS this was the first version ever deployed into UMD-2. Parallel to this work started the staged rollout of the UMD-3 products with a total of 50 products and the stage rollout of the WN-tarball with the collaboration between EGI and Matt Doidge from NGI_UK. | |||
In this quarter there was a close collaboration with SA2 regarding the end of EMI /IGE Tecnhological Providers and the future of the UMD which lead to a dedicated face to face meeting during the Community Forum in Manchester between EMI product team and all SA2 and SA1.3 team. | In this quarter there was a close collaboration with SA2 regarding the end of EMI /IGE Tecnhological Providers and the future of the UMD which lead to a dedicated face to face meeting during the Community Forum in Manchester between EMI product team and all SA2 and SA1.3 team. | ||
= 3. Issues and Mitigation = <!-- fill the table below | = 3. Issues and Mitigation = <!-- fill the table below |
Revision as of 15:02, 15 April 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
Along this quarter 3 UMD releases were achieved: UMD 2.4.1, UMD 2.4.1, UMD 1.10.1 and UMD 2.3.1. While for the UMD 1 repository there was a single release, 1.10.1, which provided security fix for the CREAM-CE, in UMD 2 there were 2 releases. In total this quarter a total of 20 software components from both IGE and EMI Technological Providers were released into production taking notice that for WMS this was the first version ever deployed into UMD-2. Parallel to this work started the staged rollout of the UMD-3 products with a total of 50 products and the stage rollout of the WN-tarball with the collaboration between EGI and Matt Doidge from NGI_UK.
In this quarter there was a close collaboration with SA2 regarding the end of EMI /IGE Tecnhological Providers and the future of the UMD which lead to a dedicated face to face meeting during the Community Forum in Manchester between EMI product team and all SA2 and SA1.3 team.
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|
Dependency problems for jclassads 2.4.3 in the UMD production repositories (affecting UI and WN). | Urgent release of UMD2 (2.4.1) has been done to get back coherence in the UMD repository |
An high security issue as been raised that affected all CREAM-CE's in production | Issue fixed in release UMD2 (2.4.1) with the release of the CREAM 1.14.4 and UMD (1.10.1) with cream version 1.13.5 |