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-QR4"
| Line 70: | Line 70: | ||
<span style="font-size: 11pt; line-height: 115%; font-family: Calibri;">Update on EMI-1 releasing | <span style="font-size: 11pt; line-height: 115%; font-family: Calibri;">Update on EMI-1 releasing | ||
process </span> | process </span> | ||
Staged Rollout for EMI<br> | Staged Rollout for EMI<br> | ||
| Line 77: | Line 77: | ||
= 2. Main Achievements = | = 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: | |||
*https://wiki.egi.eu/wiki/Staged-Rollout | |||
*https://wiki.egi.eu/wiki/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. | |||
= 3. Issues and Mitigation = | = 3. Issues and Mitigation = | ||
| Line 86: | Line 104: | ||
|- | |- | ||
| | | | ||
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 in total) without any EA team | |||
| Second call for these components. | |||
|} | |} | ||
= 4. Plans for the next period = | = 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. | |||
Revision as of 18:03, 26 April 2011
1. Task Meetings
| Date (dd/mm/yyyy) | Url Indico Agenda | Title | Outcome |
|---|---|---|---|
| 14 Feb 2011 |
https://www.egi.eu/indico/conferenceDisplay.py?confId=328 | Grid Operations Meeting |
Participants: 27 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" /> |
| 14 Mar 2011 | https://www.egi.eu/indico/conferenceDisplay.py?confId=428 | Grid Operations Meeting |
30 Update on status of the EMI 1.0 release Transition from lcg-‐CE to CREAM-‐CE phasing out of EGEE |
| 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 |
| 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:
- https://wiki.egi.eu/wiki/Staged-Rollout
- https://wiki.egi.eu/wiki/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.
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 in total) without any EA team | Second call for these components. |
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.