Status & plans

TODO:

new

• Extension of options database to policy database (with data where packages should go ?)
• Add possibility to move packages from testing repo to production repo
• Add Q&A info on testing->production transition (from RH, or manually)
• Check notification configuration from builder

monitor

• Do not build X.src.rpm package if X.cern.src.rpm is present
• Check if package has good signature (checksum) when monitor is scanning for incoming
• Deal with debuginfo packages, and check if RPM fetched from Fermi is that file which we wanted...

server/builder

• List available targets for which server can build
• Test stability -> check why server/builder hangs (seems to be a problem with python xmlrpc/ssl library)
• Check if chroots with "everything" installed really contains everything
• Remote yum install in chroot on some builder -> need to be decided what to do with that feature
• Add proper architecture handling (throw error, when user specified by hand default lists of architectures, and it can't be done because of spec file or not enough number of builders)
• Updates of builder chroots from temporary repository

client

• Better SRPM upload to server
• Put client script with necessary libraries into RPM package

status page

• adapt plague status page (http://lxdist-ia64.cern.ch/status/test/) to be main status page of system
• add information about state of system (how many builder are running,...)

other

• Generate certificates and configure setup on lxdist-* machines - need to move them to some place in OS

What was done (oldest on the top):

• Tests of plague as a build system
• Simple client-server (client-builder) prototype based on code taken from plague
• Adaptation of plague to be able to use CERN SSL certificates
• Adaptation of plague to older version of python (2.2 on SLC3 and 2.3 on SLC4)
• Replacing _mock_ by rpmbuild as builder engine
• Simple database of building options (pattern based), processing options by build system

• Tree scenario of running : mock within chroot, mock, rpmbuild
• Options/rules (pattern based) : target, builder type (mock,rpmbuild), chroot id (or no chroot at all), rpmbuild options (packager, vendor)

• Installation of SLC on 3 building machines (lxdist-[i386|amd64|ia64])
• Multiple builder management (as in plague)
• Test of builds in chroot environment (mock/rpmbuild)
• Correction of build target (i386/i686/..) management
• Queue management (as in plague)

• Prepare toy, prototype builder for Jan & Jarek (9.III)
• Prepare script for fetching package-version info from yum repository (needed for seeding DB) (30.III)
• Lemonization of lxdist-* machines (~20.IV)
• Delete of jobs mechanism (~7.V)
• Two builders per machine with own chroot dir (~11.V)
• Proper cleaning workspace directories (in base system) (~11.V)
• Script for updating builder chroots (~14.V)
• Passing builder options from command line (for building kernel modules) (~14.V)
• Exclusive locking when using DB (~14.V)
• Pushing packages with status=needsign to yum unstable repository (~14.V)
• Script checking if new packages are ready for building (~30.VI)
• Installation of koji&bodhi on lxxen0-? (SLC 4 and FC6) machines (~5.VII)
• Monitor script improvements: timestamps, reasonable output, move log to logs
• Change %vendor and %packager entries to correct ones
• Remove .foo.com from logs URL ?
• Separate client script from rest of package
• Error checking when automatically building packages from monitor script
• Checking if package was build in fermilab
• Prepare simple web page with online status of packages, with script doing same thing (static HMTL instead of psp) (13.VIII)
• Feed monitor script with updates incoming from RH (13.VIII)
• Proper DB locking system (13.VIII)
• Fetching advisories and saving them to DB, and periodically update
• Link advisories with our package DB
• Setting monitor script for building SLC3 packages
• Display history of errata for given package (?), advanced querying advisory DB

-- LeszekGrzanka - 12 Oct 2007