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

From EGIWiki
Jump to: navigation, search
Line 41: Line 41:
 
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)
 
-->  
 
-->  
 +
 +
*Release of four UMD2 updates: 2.1.0, 2.1.1, 2.2.0 and 2.2.1
 +
*Release of two UMD1 updates: 1.8.1 and 1.9.0
 +
*UMD2 release and updates have included most of EMI2 components as well as several IGE components.
 +
*EA teams are now covering most of EMI2 and IGE components.
 +
*New portal developed at LIP containing a list of all staged rollout tests, can be used by the NGI's to fill the respective metrics:
 +
**http://www.lip.pt/computing/apps/EGI_EA/index.php?option=1
 +
*SW provisioning of components are ongoing towards the release of UMD 2.3.0 in November.
  
 
= 3. Issues and Mitigation = <!-- fill the table below
 
= 3. Issues and Mitigation = <!-- fill the table below
Line 50: Line 58:
 
! scope="col" | Mitigation Description
 
! scope="col" | Mitigation Description
 
|-
 
|-
|  
+
|Dependency problems between EMI and IGE packages in the UMD production repositories
|  
+
|Urgent release of UMD2 (2.2.1) has been done to get back coherence in the UMD repository
 
|-
 
|-
 
|  
 
|  
Line 58: Line 66:
  
 
= 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) -->  
 +
 +
*Continuation of SW provisioning of components from EMI and IGE.
 +
*Start preparing EA teams for EMI3 release.
 +
*Work in the SW provisioning workflow to get packages not only form EMI and IGE repositories but also from EPEL. Towards the changes needed when EMI and IGE projects end (first quarter 2013).
  
 
[[Category:SA1_Task_QR_Reports]]
 
[[Category:SA1_Task_QR_Reports]]

Revision as of 16:59, 30 October 2012

1. Task Meetings

Date (dd/mm/yyyy) Url Indico Agenda Title Outcome
20/08/2012 https://www.egi.eu/indico/conferenceDisplay.py?confId=1146 Grid Operations Meeting
10/09/2012 https://www.egi.eu/indico/conferenceDisplay.py?confId=1158 Grid Operations Meeting
24/09/2012 https://www.egi.eu/indico/conferenceDisplay.py?confId=1167 Grid Operations Meeting
08/10/2012 https://www.egi.eu/indico/conferenceDisplay.py?confId=1198 Grid Operations Meeting
22/10/2012 https://www.egi.eu/indico/conferenceDisplay.py?confId=1219 Grid Operations Meeting

2. Main Achievements

  • Release of four UMD2 updates: 2.1.0, 2.1.1, 2.2.0 and 2.2.1
  • Release of two UMD1 updates: 1.8.1 and 1.9.0
  • UMD2 release and updates have included most of EMI2 components as well as several IGE components.
  • EA teams are now covering most of EMI2 and IGE components.
  • New portal developed at LIP containing a list of all staged rollout tests, can be used by the NGI's to fill the respective metrics:
  • SW provisioning of components are ongoing towards the release of UMD 2.3.0 in November.

3. Issues and Mitigation

Issue Description Mitigation Description
Dependency problems between EMI and IGE packages in the UMD production repositories Urgent release of UMD2 (2.2.1) has been done to get back coherence in the UMD repository

4. Plans for the next period

  • Continuation of SW provisioning of components from EMI and IGE.
  • Start preparing EA teams for EMI3 release.
  • Work in the SW provisioning workflow to get packages not only form EMI and IGE repositories but also from EPEL. Towards the changes needed when EMI and IGE projects end (first quarter 2013).