EGI-InSPIRE:SA1.3-QR4

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
4 Feb 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=309	Unicore Integration Taskforce Meeting	9 Participants Constitutional Meeting, Focus on GOCDB integration and accounting
14 Feb 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=328	Grid Operations Meeting	27 Participants DPM and LFC in glite31 EMI2 requirements New portal with EA table and components Batch system support
28 Feb 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=361	Grid Operations Meeting	16 Participants <span class="mw-headline" />
8 Mar 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=409	UNICORE Integration Taskforce Meeting	8 Participants Argus authorization framework Best Practices
14 Mar 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=428	Grid Operations Meeting	30 Participants Update on status of the EMI 1.0 release Transition from lcg-­‐CE to CREAM-­‐CE phasing out of EGEE Grid name
28 Mar 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=443	Grid Operations Meeting	27 participants Update on EMI-1 releasing process Cream and gLite-CLUSTER deployement model ARC, UNICORE and Globus Publish MW version in the information system
31 Mar 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=446	UNICORE Integration Taskforce Meeting	6 Participants Monitoring More active participation in the Grid Operations Meetings
18 Apr 2011	https://www.egi.eu/indico/conferenceDisplay.py?confId=454	Grid Operations Meeting	29 participants Update on EMI-1 releasing process Staged Rollout for EMI

2. Main Achievements

During the reporting period the “New SW Release Workflow” (NSRW) has been tested with dry run of EMI components (Release Candidate 3). SA2 runs/manages the RT queue "sw-rel" where the verififcation process occurs, and TSA1.3 manages the "staged-rollout" queue where the staged rollout occurs.

The staged rollout process was further detailed:

• Staged-Rollout
• Staged-rollout-procedures contains detailed step by step procedures for EA teams

The EA s are now managed in:

• https://www.egi.eu/earlyAdopters/table
• https://www.egi.eu/earlyAdopters/teams lists all components and and number of EA teams for each one

The total number of Early Adopter teams is now 45.

A request has been sent to all EAs to give their plans and schedules to change early adoption of glite 3.2 components to EMI1 given the upcoming release due end of April 2011.

Several teams already sent feedback that they would change from gLite 3.2 to EMI1.0 components.

Within interoperability the UNICORE integration task force has been started to keep an open dialogue between all involved parties and in order to keep more transparently track of the current ongoing efforts:

• UNICORE_integration_task_force
• unicore-integration-tf@mailman.egi.eu https://www.egi.eu/sso/groupView/unicore-integration-tf

An equivalent Globus integration task force is about to start to coordinate the efforts within the NGIs with IGE.

The ARC monitoring tests became operational on 7.04.2011.

• http://wiki.nordugrid.org/index.php/Nagios_Tests

3. Issues and Mitigation

Issue Description	Mitigation Description
Some EA teams have been unresponsive to the notification of staged rollout. This makes some components to be a long time in staged rollout state, or not being released to production.	One of the teams has had a shortage of man power, should be solved in the next quarter.
Still several EMI1 components: 10 with no EA team 10 with only 1 EA team	Second call for these components.
UNICORE integration in GOCDB still hampered which reduces motivation of active participation in other areas of UNICORE integration.	Another new alternative solution to add the needed ServiceEndPointURL is currently discussed which hopefully gives some result in less than 6 months.

4. Plans for the next period

Objective (repeated from last QR3): to have at least 2 EA teams per component. This is needed if:

• One team is unavailable (backup).
• Increase the probability to catch any problems or issues.
• Increase the heterogeneity of the testing, and eventually different deployment scenarios.

This is already partially fulfiled for some of the EMI1 components, and should extend to all. It is expected that a second call to EAs will bring most to complete this picture.

The begining of the next period coincindes with the first release of EMI, as such it is the objective of this task to do the staged rollout of as many as possible components, to be included in the first UMD release.

Plans for Interoperability are to continue the UNICORE integration task force. First relevant results in UNICORE monitoring are expected for the next quarter. The hopes are high that the about to start Globus integration task force is at least evenly fruitful. Furthermore in preparation of the summerhole and taking into account the number of people involved already first work on the next MS414 is planned to start.