DICE support for SL6 is now available (as of 28/4/11) for both i386 and x86_64 architectures. An LCFG profile for DICE SL6 is made in the same way as usual:


#include <dice/os/sl6.h>
#include <dice/hw/virtualbox.h>
#include <dice/options/office-forum.h>
#include <live/wire_forum.h>


!profile.release      mSET(develop)

There are some notes:

  • It has to be on the develop release.
  • There is currently no local DNS server, we’re still using the lcfg-resolvconf component rather than lcfg-dns. It might work, it has not been tested. Other than that, all the LCFG components which have been auto-built seem to be working. Even routing seems to be fine.
  • There is a live hacks header (live/sl6-fixups.h) which modifies the way the standard DICE environment works. Please only use this header if there is no other way to get things working, ideally we should be adding support directly into the dice headers now.

DICE SL6 buildhosts

There are two DICE SL6 build hosts, these are buildsl6 (leeds) and buildsl6_64 (kilmartin). These are using the desktop packages lists so have a large set of packages available to make building software easier. Wherever possible please use the pkgforge system to build your packages for SL6. This will help spot missing build-dependencies and thus improve packaging quality.

DICE Package Lists

In order to understand how the DICE SL6 package lists work you should first read through the notes on the LCFG wiki regarding how to manage optional sets of packages.

In DICE we have the following package lists:

  • dice_sl60_base.rpms
  • dice_sl60_desktop.rpms
  • dice_sl60_latex.rpms
  • dice_sl6_env.rpms
  • dice_sl6_unsupported.rpms

The base and desktop lists MUST only contain packages which are in the SL6.0 base bucket, they will have updates applied automatically. They should be considered to be dice-level extensions to the similarly named lcfg-level package lists.

The latex package list is for everything related to using LaTeX. This package list MUST be usable on machines which do not use the desktop packages list so care must be taken to get the dependencies correct.

The env list is for the following types of packages:

  • Required for the local DICE environment
  • Locally built/packaged
  • Taken from epel6
  • Overrides of versions for SL packages

The relevant sections of the list are clearly marked, please put the packages into the correct location, keep them in alphabetical order and add a comment saying who added each package. If a package comes from the SL6 repository it should not be in this package list unless a specific version must be fixed to satisfy the DICE environment requirements (please do not do this unless it is absolutely necessary). This package list is used on ALL SL6 machines so care must be taken to get the dependencies correct. Packages which can only be used on machines which have the desktop packages list can be wrapped in a conditional block using the DESKTOP_PACKAGES macro.

The epel6 packages are split into two sections. There is one section for those packages which must be kept at a particular version unless the CO who originally added the package decides it should be altered. The other section is for packages from epel6 where all that is required is the latest version. This section will be checked occasionally by MPU to keep the packages up-to-date. It is expected that most packages will be in the "floating" section and not have permanently fixed versions.

The unsupported list is for packages which do not come from the SL repository and do not come from epel. It is intended to be used for locally built/submitted packages which are primarily for personal use by COs but are added in case other users might like to have them.

Unlike previous platforms we are not intending to have any separate lists for each architecture (e.g. i386 or x86_64) at the DICE level. Macros are available for restricting packages to particular platforms, these are ARCH_I386 and ARCH_X86_64. There is also the ARCH macro which contains the name of the primary architecture (this will be either i686 or x86_64), this can occasionally be useful for generating package specifications. For example:

#ifdef ARCH_X86_64
#endif /* ARCH_X86_64 */

Software Repositories

The best place to get SRPMs is from koji for Fedora

The upstream (RHEL6) SRPMs can be found at http://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/os/SRPMS/

We have a local mirror of SL6 at /afs/inf.ed.ac.uk/pkgs/sites/sl6/ and a local mirror of epel6 at /afs/inf.ed.ac.uk/pkgs/sites/epel/6/

Current Status

Pretty much everything is working for the DICE layer.
SL6 is only available at the inf layer. This uses DICE authentication and authorisation services with AFS home directories (see instructions below for an example profile)

DICE specific burning issues

LCFG on SL6 (inf layer)

This page is for documentation pertaining to DICE SL6. As LCFG is now in wide use out-with Informatics, the main LCFG SL6 project documentation is on the LCFG wiki :-

How to install an inf layer machine

Your machine's profile should look something like this:

#include <inf/os/sl6.h>  /* or sl6_64.h*/
#include <inf/hw/virtualbox.h>  /* use the appropriate header for your model */
#include <inf/options/desktop.h> /* unless it's going to be a headless server */
#include <inf/options/devel.h>
#include <live/wire_forum.h>

!profile.release	mSET(develop)

dhclient.mac		/* your machine's MAC address */

-- AlastairScobie - 31 Mar 2011

Topic revision: r4 - 18 May 2011 - 08:22:21 - StephenQuinney
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies