Difference between revisions of "EGI-InSPIRE:SA1.3-QR15"
Line 64: | Line 64: | ||
== Staged Rollout == | == Staged Rollout == | ||
During this quarter there were a total of three releases two regarding UMD-3 ([http://repository.egi.eu/2013/12/13/release-umd-3-3-0/],[http://repository.egi.eu/2013/10/11/release-umd-3-2-1/ 3.2.1]) and one for UMD-2 ([http://repository.egi.eu/2013/10/22/release-umd-2-7-0/ 2.7.0]). In total 24 products and sub-components were deployed and tested covering not only all of EMI / IGE products but also incorporated a new product team the QCG [http://www.qoscosgrid.org/qcg-packages/sl5/x86_64/ team]. | |||
Of notice that along this quarter, SA1.3 activities suffered one of the most important changes since the project started due to the end of the EMI project. Now, most of the PT's previously integrated in the EMI project, started to release his software in third party repositories like EPEL. This change completely changed the way UMD gets the software, with a consequent increase in the complexity during the release process. During this quarter DPM/LFC product team made the first release into EPEL repository followed by Gfal which were successfully incorporated into UMD. | |||
UMD release process experienced a lot of issues 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 in order to find a solution to the problem. | UMD release process experienced a lot of issues 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 in order to find a solution to the problem. | ||
The new RC without the UI for SL5 is being tested in this moment and should work. The new UI in SL5 will be released together with the Globus 5.2.5 to solve the dependency issues. | The new RC without the UI for SL5 is being tested in this moment and should work. The new UI in SL5 will be released together with the Globus 5.2.5 to solve the dependency issues. |
Revision as of 16:49, 27 January 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 (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
Staged Rollout
During this quarter there were a total of three releases two regarding UMD-3 ([1],3.2.1) and one for UMD-2 (2.7.0). In total 24 products and sub-components were deployed and tested covering not only all of EMI / IGE products but also incorporated a new product team the QCG team.
Of notice that along this quarter, SA1.3 activities suffered one of the most important changes since the project started due to the end of the EMI project. Now, most of the PT's previously integrated in the EMI project, started to release his software in third party repositories like EPEL. This change completely changed the way UMD gets the software, with a consequent increase in the complexity during the release process. During this quarter DPM/LFC product team made the first release into EPEL repository followed by Gfal which were successfully incorporated into UMD. UMD release process experienced a lot of issues 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 in order to find a solution to the problem. The new RC without the UI for SL5 is being tested in this moment and should work. The new UI in SL5 will be released together with the Globus 5.2.5 to solve the dependency issues.
Participation in the Middleware Readiness Working Group. The meeting purpose is to:
- 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.
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.
Integration
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
Integration
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.