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 "Transition"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
= Staged rollout process during the transition phase = | = Staged rollout process during the transition phase = | ||
This page is oriented to the EA sites, and describe the workflow for SR | This page is oriented to the EA sites, and describe the workflow for SR during this phase. | ||
during this phase. | The page [[Early Adopters]] contain a table showing the EA sites and the components they do SR. | ||
* The EA will work on the savannah project '''jra1mdw''' on the standard patches. These patches contain the tracking of "node types" or metapackages. [https://savannah.cern.ch/patch/?group=jra1mdw[https://savannah.cern.ch/patch/?group=jra1mdw]] | |||
* The EA will work on the savannah project '''jra1mdw''' on the standard patches. | |||
These patches contain the tracking of "node types" or metapackages. | |||
[https://savannah.cern.ch/patch/?group=jra1mdw[https://savannah.cern.ch/patch/?group=jra1mdw]] | |||
* The site is notified by savannah when the SR coordinator triggers a state transition | * The site is notified by savannah when the SR coordinator triggers a state transition | ||
| Line 16: | Line 11: | ||
* The patch contains the release notes that should be used by the EA. | * The patch contains the release notes that should be used by the EA. | ||
* The delta repos will still be created, so that's what EA's will use in | * The delta repos will still be created, so that's what EA's will use in the installation/upgrade. | ||
the installation/upgrade. | |||
* The patch will contain a comment field with a simplified report template, | * The patch will contain a comment field with a simplified report template, which each EA doing the SR for a given node should fill (copy/paste it to a new comment) | ||
which each EA doing the SR for a given node should fill (copy/paste it to a new comment) | |||
Site Name: | Site Name: | ||
| Line 29: | Line 22: | ||
Comments: | Comments: | ||
* This means that EA's will work on the patch, if there are more than one EA | * This means that EA's will work on the patch, if there are more than one EA doing SR on a node/metapackage, they all should work on the same savannah jra1mdw patch. | ||
doing SR on a node/metapackage, they all should work on the same savannah jra1mdw | |||
patch. | |||
* After an EA is notified, it should set a comment in the patch saying that it either "Accepts" or "Rejects" | * After an EA is notified, it should set a comment in the patch saying that it either "Accepts" or "Rejects" the SR, and the site name: | ||
the SR, and the site name: | |||
<Site Name> <Accept|Reject> | <Site Name> <Accept|Reject> | ||
This processes make the possibility to have several patches into SR | This processes make the possibility to have several patches into SR independently, and to have both glite 3.1 and glite 3.2 at the same time. Moreover as soon as a patch is verified, the process is triggered without waiting for other patches. This, allows the the release to be more node type based, and not so much glite 3.2 updateXXX based | ||
independently, and to have both glite 3.1 and glite 3.2 at the same time | |||
Moreover as soon as a patch is verified, the process is triggered | |||
without waiting for other patches. This, allows the the release to be | |||
more node type based, and not so much glite 3.2 updateXXX based | |||
Revision as of 17:35, 21 May 2010
Staged rollout process during the transition phase
This page is oriented to the EA sites, and describe the workflow for SR during this phase. The page Early Adopters contain a table showing the EA sites and the components they do SR.
- The EA will work on the savannah project jra1mdw on the standard patches. These patches contain the tracking of "node types" or metapackages. [https://savannah.cern.ch/patch/?group=jra1mdw]
- The site is notified by savannah when the SR coordinator triggers a state transition
Ready for rollout -> Rolling out
- The patch contains the release notes that should be used by the EA.
- The delta repos will still be created, so that's what EA's will use in the installation/upgrade.
- The patch will contain a comment field with a simplified report template, which each EA doing the SR for a given node should fill (copy/paste it to a new comment)
Site Name: Release notes: <OK|WARN|FAIL> Installation/upgrading: <OK|WARN|FAIL> (Re)-configuration with YAIM: <OK|WARN|FAIL> Functionality: <OK|WARN|FAIL> Comments:
- This means that EA's will work on the patch, if there are more than one EA doing SR on a node/metapackage, they all should work on the same savannah jra1mdw patch.
- After an EA is notified, it should set a comment in the patch saying that it either "Accepts" or "Rejects" the SR, and the site name:
<Site Name> <Accept|Reject>
This processes make the possibility to have several patches into SR independently, and to have both glite 3.1 and glite 3.2 at the same time. Moreover as soon as a patch is verified, the process is triggered without waiting for other patches. This, allows the the release to be more node type based, and not so much glite 3.2 updateXXX based