EGI-InSPIRE:SA1.3-QR14
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 |
---|---|---|---|
28.10.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1918 | Grid Operations Meeting | Regular operations meeting |
21.10.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1910 | UMD Release Team | Regular operations meeting |
03.10.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1875 | UMD Release Team | Regular operations meeting |
23.09.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1874 | Grid Operations Meeting | Regular meeting |
18.09.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1870 | UMD Release Team F2F meeting | Technical Forum |
02.09.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1847 | Grid Operations Meeting | Regular meeting |
19.08.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1806 | Grid Operations Meeting | Regular operations meeting |
26.08.2013 | https://indico.egi.eu/indico/conferenceDisplay.py?confId=1805 | UMD Release Team | Regular meeting |
2. Main Achievements
During this quater there were a total of three releases two regarding UMD-3 (3.2.0,3.2.1) and one for UMD-2 (2.7.0).
The overall activity for this quarter, both in terms of reports and products released, was low taken even to account the summer period. This can be explained by the fact that in the last quarter (QR13) it was launched the first release of UMD-3 which forced sites and product teams to make a huge effort in order to scope with all the changes and now we are facing a transition period on which product teams are also adapting there release schedules.
this quarter activity suffered During this quarter there were released three updates in the UMD. Those updates were divided into
(UMD-3) which incorporated all the EMI-3 products. After the major release two updates were already released UMD-3.1.0 and UMD-3.1.1. In total over 50 products and sub-components were deployed and tested covering all of EMI products with a total of 2 rejections, gridsite 2.1.0 and apel 4.0.0 .
It also started the collaboration with SA2 in the new UMD Release Team (URT) activity. URT is a new lightweight coordination run by EGI SA2 in order to fill some gaps left after the end of the European middleware projects. This activity started in May of 2013 and main purpose is to keep open the communication channels between the product teams, as they existed previously within the middleware projects, and open new lines of communications between EGI and the product teams, as before they were mediated by the middleware projects technical coordination. SA1.3 responsibilities in this team is to provide feedback about the current issues found during the software provisioning, verification and stage rollout.
There was also some close collaboration between staged rollout activites and CSIRT team in order to check the readiness of the software towards the SHA-2 implementation and Argus interoperability. As an outcome of this work two wiki pages were create and constantly updated with relevant information regarding both cases. The wiki page for Middleware-argus-interoperability can be consulted here and the regarding the SHA-2 compliance here
To finally this intense QR it was made several campaigns to gather new EA for some products like glexec and cream and also gathering EA for new products like slurm and the full QCG products.
3. Issues and Mitigation
Issue Description | Mitigation Description |
---|---|