|EGI Inspire Main page|
|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 (14/01/2014)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=2028||EGI Operations meeting||Regular operations meeting|
|(13/01/2014)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=2027||UMD Release Team||Regular meeting|
|(12/12/2014)||https://indico.cern.ch/conferenceDisplay.py?confId=285681||Middleware Readiness Working Group meeting||WLCG meeting|
|(09/12/2014)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=2027||UMD Release Team||Regular meeting|
|(02/12/2013)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=1978||EGI Operations meeting||Regular operations meeting|
|(19/11/2013)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=1940||EGI Operations meeting||Regular operations meeting|
|(18/11/2014)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=1965||UMD Release Team||Regular meeting|
|(04/11/2014)||https://indico.egi.eu/indico/conferenceDisplay.py?confId=1921||UMD Release Team||Regular meeting|
2. Main Achievements
During this quarter there were a total of two releases one regarding UMD-3 ( 3.3.0) and one for UMD-2 (). 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:
- Evaluate successful methods of Middleware Readiness practices by selected middleware products.
- Discuss how to better involve the experiments in this effort.
- Find ways to reward the WLCG sites willing to participate in the testing of new middleware versions.
Integration activities during quarter 15 were focused on planing of EGI Cloud Infrastructure further integration with production Infrastructure. As a result new Cloud site started certification procedure.
With EUDAT a study case within ENVRI project was progressing and first proposal of joined set up for EISCAT 3D was proposed and discussed. Assessment of readiness of accounting and information publishing of ARC, UNICORE, QCG and GLOBUS software was performed and how-to documents for NGIs deploying these middlewares was prepared.
In addition EGI started a discussion with Helix Nebula on knowledge sharing between projects. EGI is going to provide a presentation on solutions implemented in the project. This is seen as a starting point to understand how both project can integrate with each other.
3. Issues and Mitigation
|Issue Description||Mitigation Description|
4. Plans for the next period
So far UMD processes resolved the dependencies in the EMI, IGE or QCG yum repositories to create the most complete product entries for the UMD framework. Even if some product team moved permanently to EPEL, other product teams are still releasing to EMI but not as a main repository, in many cases for UMD is impossible to resolve the dependencies getting a reasonable set of libraries (e.g. without downloading the EPEL dependencies not under the PT responsibility).
So UMD team has started at the end of last year to list directly the list of relevant RPMs that compose a product entry in the UMD release process. The rpm files are then downloaded with a direct wget into the UMD repositories. Even if this provides looks good there is still need to check the integrity of the dependencies in UMD until the products are tested for installation, it is important that product teams provide correct list of rpms once they want to submit their products to UMD. Even if working the process its still not automatic which leads to an high time consumption to create the release xml file so along this quarter we propose to improve the workflow in order to improve the process.
Along this this quarter we foreseen the participation in the decommission campaign for UMD-2 services. All UMD-2 components must be decommissioned or upgraded by the end of May 2014.
During next quarter integration activities will be focused on ongoing EGI Cloud, XSEDE and EUDAT integration. It is also planed to integrate Desktop Grid resources as infrastructure represented as separate Operation Center and investigate possible integration between Helix Nebula and EGI.