releng RHEL5 Migration
What is the releng1 to RHEL5 migration?
releng1 is the xen guest that Fedora Release Engineering uses for various tasks related to the day to day release engineering tasks for Fedora.
releng1 used by the following people:
releng1 hosts the following services:
- Fedora package signing
- rawhide creation
- writing to Fedora's public netapp
The migration will happen in phases.
- Creation of releng2 guest
- Install RHEL5 on releng2 guest
- Modify and test above services (as best one can) on releng2
- Shut down releng1
- Bring up releng2 as releng1 and mount Fedora public netapp as rw
- Validate services in production environment
- Monitor closely each service for proper operation
- releng2 created and running
- rawhide creation service scripts have been modified
- rawhide creation scripts partially tested
- chroot creation
- additional packages installed into chroot
- package signing scripts modified
- package signing verified
Various notes about the setup, to be documented elsewhere for SOPs perhaps
- The createrepo calling scripts should pass the --unique-md-filenames option, which will change the repodata to have names like "de6f00e3dd09cfb297da614f6b5dffb60d61f3e7-primary.xml.gz" instead of just "primary.xml.gz". This makes HTTP (esp. proxies) happier. Note that YUM before 3.2.14 did not deal well with this, so this can't be turned on in anything earlier than Fedora 9.
- Scripts come from git://git.fedorahosted.org/releng git repo, under scripts/
- Required koji certs put in place for the person doing the signing/importing
- Requires a ~/.rpmmacros setup:
%_signature gpg %_gpg_path ~/.gnupg %_gpgbin /usr/bin/gpg
- Requires ~/.gnupg setup with the Fedora keys imported.
- Requires /srv/releng/signing path created, /srv/releng should have
relenggroup ownership and group write, sticky group permissions