Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "EGI-InSPIRE:SA1.3-QR14"

From EGIWiki
Jump to navigation Jump to search
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Op menubar}} {{Template:Inspire_reports_menubar}} {{TOC_right}}  
{{Template:EGI-Inspire menubar}}
 
{{Template:Inspire_reports_menubar}}
{{TOC_right}}
= 1. Task Meetings = <!--
= 1. Task Meetings = <!--
Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes.  
Notes. Report here all task-specific meetings held. This includes (a) face-to-face meetings and (b) phone meetings. Make sure that for all task meetings participants are ALWAYS recorded either on indico from the registrants’ list, or in the minutes.  
Line 58: Line 61:
Note. This is a detailed account of progress over the previous quarter of activities within  the  task.  
Note. This is a detailed account of progress over the previous quarter of activities within  the  task.  
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)
-->
-->  
 
<br> During this quarter there were a total of three releases two regarding UMD-3 ([http://repository.egi.eu/2013/09/12/release-umd-3-2-0/ 3.2.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.


During this quater there were a total of three releases two regarding UMD-3 ([http://repository.egi.eu/2013/09/12/release-umd-3-2-0/ 3.2.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])
<br>


The activity After the huge activity of last quarter (QR13) on which it was launched the first release of UMD-3 and forced sites to make a huge effort in order to scope with all the changesthis quarter activity suffered During this quarter there were released three updates in the UMD. Those updates were divided into 
Intergation activites during quarter 14 were focused on planing of EGI Cloud Infrastructure integration with production Infrastructure which one of the main result was succesful certification of first cloud-only site. Another area of work was collaboration with XSEDE project to enable COMPCHEM and WeNMR VOs on both infrastructures. <br>
([http://repository.egi.eu/2013/05/14/release-umd-3-0-0/ UMD-3]) which incorporated all the EMI-3 products. After the major release two updates were already released [http://repository.egi.eu/2013/06/26/release-umd-3-1-0/ UMD-3.1.0] and [http://repository.egi.eu/2013/07/01/release-umd-3-1-1/ 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.
With EUDAT a study case within ENVRI project was set up wich aim is to enable EISCAT 3D community to benefit from both projects in terms of dealing with the big data produced by EISCAT 3D project. [https://wiki.egi.eu/wiki/EGI_ENVRI https://wiki.egi.eu/wiki/EGI_ENVRI]


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  [https://wiki.egi.eu/wiki/Middleware_argus_interoperability  here] and the regarding the SHA-2 compliance [https://wiki.egi.eu/wiki/Middleware_products_verified_for_the_support_of_SHA-2_proxies_and_certificates here]
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 is being repared.&nbsp;


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.
Finelly edupert was integrated into GGUS for network troubleshoointg.


= 3. Issues and Mitigation = <!-- fill the table below
= 3. Issues and Mitigation = <!-- fill the table below
Line 80: Line 85:
! scope="col" | Mitigation Description
! scope="col" | Mitigation Description
|-
|-
|  
| Readiness of the software towards the SHA-2 
|  
| After release of storm 1.11.2 release in UMD [http://repository.egi.eu/2013/10/11/release-umd-3-2-1/ 3.2.1], all products in UMD are SHA-2 compliant.
|-
|-
|
|
|}
|}


= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) -->  
= 4. Plans for the next period = <!-- provide your text below. PLEASE PROVIDE TEXT IN A GOOD EDITED FORM (NO BULLET LISTS OF SHORT ITEMS THAT REQUIRE EXPANSION WHEN INSERTED IN A REPORT) -->  


[[Category:SA1_Task_QR_Reports]]
The most important issue for the next quarter will be on how to improve the software provisioning process and in particular the SR in order to handle the way product teams deploy the new software. Also important is to investigate how to incorporate the WLCG software tests into the SR EGI activities. Continuation of the collaboration with CSIRT team in order to check implementation and Argus interoperability.
 
As a long term objective prepare the software provisioning to the end of the EGI-Inspire project.
 
 
 
During next quarter intergation activities will be focused on ongoing EGI&nbsp;Cloud, XSEDE&nbsp;and EUDAT integration. It is also planed to integrate Desktop Grid resources as infrastrcuture represented as separate Operation Center.<br>

Latest revision as of 18:49, 6 January 2015

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
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 quarter 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). 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.


Intergation activites during quarter 14 were focused on planing of EGI Cloud Infrastructure integration with production Infrastructure which one of the main result was succesful certification of first cloud-only site. Another area of work was collaboration with XSEDE project to enable COMPCHEM and WeNMR VOs on both infrastructures.

With EUDAT a study case within ENVRI project was set up wich aim is to enable EISCAT 3D community to benefit from both projects in terms of dealing with the big data produced by EISCAT 3D project. https://wiki.egi.eu/wiki/EGI_ENVRI

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 is being repared. 

Finelly edupert was integrated into GGUS for network troubleshoointg.

3. Issues and Mitigation

Issue Description Mitigation Description
Readiness of the software towards the SHA-2 After release of storm 1.11.2 release in UMD 3.2.1, all products in UMD are SHA-2 compliant.

4. Plans for the next period

The most important issue for the next quarter will be on how to improve the software provisioning process and in particular the SR in order to handle the way product teams deploy the new software. Also important is to investigate how to incorporate the WLCG software tests into the SR EGI activities. Continuation of the collaboration with CSIRT team in order to check implementation and Argus interoperability.

As a long term objective prepare the software provisioning to the end of the EGI-Inspire project.


During next quarter intergation activities will be focused on ongoing EGI Cloud, XSEDE and EUDAT integration. It is also planed to integrate Desktop Grid resources as infrastrcuture represented as separate Operation Center.