Staged rollout Release Check List

Responsible: Pablo Guerrero Backup person: Maria Alandes

Introduction

The following list must be used in combination with the Integration Procedure twiki that describes all the technical details involved in the release process. This twiki aims to list the necessary steps to create a staged rollout release helping to avoid mistakes and decrease human errors.

Pre requirements

Access to machine lxbrf2713 where you have:

• The necessary scripts to create repositories (https://svn.cern.ch/reps/grelscripts)
• The necessary scripts to create UI and WN tarballs (http://glite.cvs.cern.ch/cgi-bin/glite.cgi/glite-release/)

For gLite 3.2, you also need your GPG key installed to sign rpms.

How to install the GPG key:

• Copy the your ./gnupg folder in the machine where you are going to create the SR repo.
• Create the ~/.rpmmacros file with the following contents:

  %_signature gpg
  %_gpg_name  Gd Integration <gd-release-team@cern.ch>
  

Check List

1. For each service that is going into SR, remove the beta repository in the prepare area: /afs/cern.ch/project/gd/www/glite/prepare/beta/3.X/glite-XXX

2. For each standard patch in status Verified:

• Check in the list of associated bugs, if any, that the bug status is Fix certified or Fix not certified. Remove Invalid/Obsolete bugs. Contact certifiers if there are bugs in Ready for test since they should update this status after verifying the bug.

• Check the release notes again and ask for an improved text to the patch submitter if the quality is poor or the explanations are not very useful.

3. Move the patch to the internal repo and then to the preview repo (under /root/grelscripts):

patch_to_internal.py  -r <release> -o <os> -a <arch> <patch1 [... patchN]>

internal_to_preview.py  -r <release> -o <os> -a <arch> <patch1 [... patchN]>

Where:

• release: 3.1 or 3.2
• os: sl4 or sl5
• arch: i386 or x86_64

After that, it's important to check that the relevant rpms have been properly copied in the beta repository in /afs/cern.ch/project/gd/www/glite/prepare/beta/3.X/. You may want to run a clean installation test to check it, but this is not mandatory.

4. Publish the new repository:

cd /afs/cern.ch/project/gd/www/glite/beta
mv 3.X 3.X_old
cp -pR /afs/cern.ch/project/gd/www/glite/prepare/beta/3.X 3.X

5. One the repositories have been created, move the patches into Ready for Rollout with the following comment:

The Staged Rollout repository for this patch has been created, and it can be tested using the usual repo files. For this patch, you can use: 

http://grid-deployment.web.cern.ch/grid-deployment/glite/repos_beta/3.X/beta-glite-XXX.repo

6. Announce it on the EMT

Subject: New patches ready for rollout

Hi all,

The following patches have been moved into the staged rollout repository:

3.1:
<patches description>

3.2:
<patches description>

7. Update the Staged Rollout page to include the new patch:

• Edit /srv/glite_web/templates/releasenotes/staged_rollout.html in lxbrf2713 and include the new patch
• Restart the web server (changes will be visible after 5 minutes): /etc/init.d/httpd restart

8. If the release affects the UI or the WN, please, create also the tarballs.

Run the following scripts (under /root/glite-release/scripts/chroot_test_scripts):

./create_tarball -r 3.X -a arch -p glite-UI -b
./create_tarball -r 3.X -a arch -p glite-WN -b

The scripts create two tarball files under glite-release/scripts/chroot_test_scripts/tarballs:

glite-UI-3.X.Y-0.tar.gz 
glite-UI-3.X.Y-0-external.tar.gz 

glite-WN-3.X.Y-0.tar.gz 
glite-WN-3.X.Y-0-external.tar.gz 

These tarball files have to be copied in:

/afs/cern.ch/project/gd/www/download/relocatable/beta/glite-UI/(SL4_i686 or SL5_x86_64) 
/afs/cern.ch/project/gd/www/download/relocatable/beta/glite-WN/(SL4_i686,SL4_x86_64 or SL5_x86_64) 

Write a comment in the patch with the URLs from where the tarballs can be downloaded.