You are here

Port LCFG to Fedora 13

Project ID: 
160
Current stage: 
Manager: 
Unit: 
What: 

Description: Develop Inf level support for Fedora 13.

Deliverables: This project will deliver an Inf level managed version of the Fedora 13 distribution. It will target the 32 bit desktop but most packages will also be built and submitted for 64 bit. It will utilise DICE authentication/authorization and name services in client mode (no local services). AFS home directories will be supported.

Why: 

Customer: All DICE users. The current plan is to upgrade all DICE desktops to Fedora 13 in
late summer 2010.

Case statement: The current SL5 based DICE platform is significantly out of date and causing
problems for both teaching and research.

When: 

Status:

Timescales:

Priority:

Time:

How: 

Proposal:

Resources:

Plan: This is more or less how it should go:

  1. Install F13 (1 day)
    • Standard F12 desktop machine
    • Get onto the Informatics network.
    • Authentication with kerberos
    • Directory services from ldap.
    • AFS filesystem access.
    • Set up Mock for automated builds.
  2. RPM repositories (0.5 day)
    • Set up a site mirror of Fedora 13 (from which buckets will be populated and the package lists generated)
    • Create repository directory structure
    • Populate base, updates (if necessary)
  3. Package lists (2 days)
    • Create lists for F13 base, updates
    • Create empty lists for lcfg components
  4. Essential headers (0.5 day)
    • Create any essential headers for the platform
    • Add basics to lcfg/defaults/profile.h and lcfg/defaults/updaterpms.h
  5. Auto-build and run tests for all LCFG components (2 days). Also
    auto-build openssh with our patches.
  6. Create basic development platform (3 days)
    • Develop Inf level to create a basic profile with most components
      removed
    • lcfg-utils and lcfg-utils-devel
    • lcfg-pkgtools & lcfg-pkgtools-devel
    • perl-LCFG-PkgTools
    • perl-LCFG-PkgUtils
    • perl-LCFG-Utils
    • lcfg-ngeneric
    • lcfg-client
    • lcfg-file
    • lcfg-sysinfo
    • lcfg-logserver
    • lcfg-authorize
    • lcfg-om
    • pkgsubmit
    • updaterpms
    • lcfg-updaterpms
  7. Components necessary to keep a machine LCFG managed (2 days)
    • Go through boot procedure and check default configuration for platform
    • lcfg-auth
    • lcfg-boot
    • lcfg-cron
    • lcfg-etcservices
    • lcfg-init
    • lcfg-lcfginit
    • lcfg-nsu
    • lcfg-pam
    • lcfg-syslog
    • lcfg-tcpwrappers
    • lcfg-defetc-f13 (needed by lcfg-auth. Most things can be built from existing SRPMs but that package will have to be built from scratch using the passwd and group files from an F13 installation.)
  8. Components for auth/authz, directory services and dns in client mode. (2 days)
    • DNS (using lcfg-resolvconf)
    • DNS (using lcfg-dns)
    • Kerberos (not using lcfg-kerberos)
    • Kerberos (using lcfg-kerberos)
    • lcfg-openafs
    • lcfg-nsswitch
    • NTP (not using lcfg-ntp)
    • NTP (using lcfg-ntp)
    • LDAP (not using lcfg-openldap)
    • LDAP (using lcfg-openldap)
    • lcfg-openssh
    • lcfg-cyrussasl
  9. X support. (1 day)
    • lcfg-gdm -> replaced with lcfg-kdm
    • lcfg-xfree if necessary
  10. Other components, mainly just auto-build and install. (1 day)
    • lcfg-alias
    • lcfg-mailng -> lcfg-mail
    • lcfg-mailcap -> no longer required
    • lcfg-prelink
    • lcfg-sleep
  11. Installation systems (4 days)
    • lcfg-fstab and hackparts
    • lcfg-grub
    • lcfg-hardware
    • lcfg-install
    • lcfg-installfixups
    • lcfg-kernel
    • lcfg-network
    • Create installroot package list
    • Create installbase package list
    • Build, install and test lcfg-buildinstallroot
    • Set up PXE, installer, etc
  12. Port MPU managed resources to the DICE level. (3 days)
  13. Document new platforms (2 days)
  14. Package LCFG Build Tools for F13
  15. F13 64bit port
  16. Remove auto or devel buckets -> scheduled to be pulled on 04/11/10 stable
  17. Add Fedora 13 to the list of supported platforms on the LCFG website.
Other: 

Dependencies:

Risks:

Milestones

Proposed date Achieved date Name Description