EGI-InSPIRE:SA1.3-QR13

From EGIWiki
(Redirected from SA1.3-QR13)
Jump to: navigation, search
EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports


Contents


1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
22.07.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1782 Grid Operations Meeting Regular operations meeting
08.07.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1773 UMD Release Team Regular meeting
08.07.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1745 Grid Operations Meeting Regular operations meeting
08.07.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1746 UMD Release Team Regular meeting
24.06.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1730 Grid Operations Meeting Regular operations meeting
24.06.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1723 UMD Release Team Regular meeting
10.06.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1719 Grid Operations Meeting Regular operations meeting
10.06.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1689 UMD Release Team Regular meeting
27.05.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1688 UMD Release Team Regular meeting
15.05.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1720 Grid Operations Meeting Regular operations meeting
06.05.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1659 Grid Operations Meeting Regular operations meeting
06.05.2013 https://indico.egi.eu/indico/conferenceDisplay.py?confId=1656 UMD Release Team Regular meeting

2. Main Achievements

During this quarter it was made a major release of the UMD (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
It was found a security vulnerability in WMS

This release solves a vulnerability bug.

Urgent release of a new release WMS v. 3.5.1 achieved and UMD 3.1.1.

4. Plans for the next period

For the next quarter, the SA1.3 activities will suffer and important change since some of the PT's, previously integrated in the EMI project, will start release software in third party repositories like EPEL. This will completely change the way UMD gets the new releases, with and consequent increase in the complexity for the UMD release. During next quarter BDII and DPM product teams will start making there releases into EPEL testing repository and PT's will only move into production after the approval from EGI.

We foreseen that after this a new SW provisioning workflow will be needed in order to embrace that changes.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export