create new tag
view all tags

SL6 Project Plan

Previously, when porting to new platforms, we have incrementally ported components etc on top of machines built by the upstream's native installer. Once the core components to install and keep a machine LCFG managed have been ported, we work on the LCFG install system and attempt an LCFG install of the new platform.

As SL6 is largely based on F13, we propose to auto build all LCFG components and attempt an LCFG install using the existing F13 LCFG installer. We will then go through all components checking for correct operation. We believe that this will be a faster process than that previously taken.

We shall work on both 32-bit and 64-bit ports in parallel.

  1. DONE Create a project blog
  2. DONE Create a project topic on LCFG wiki
  3. Install SL6 (1 day)
    • DONE Standard SL6 desktop machine
    • DONE Get onto the Informatics network.
    • DONE Authentication with kerberos
    • DONE Directory services from ldap.
    • DONE AFS filesystem access.
    • DONE Set up Mock for automated builds.
    • DONE Configure PkgForge (buildhost on F13 64bit building SL6 packages)
  4. Package infrastructure (0.5 day)
    • DONE Set up a site mirror of SL6 (from which buckets will be populated and the package lists generated)
    • DONE Create repository directory structure
    • DONE Populate base, updates (if necessary)
  5. Package lists (5 days)
    • DONE Create lists for SL6 base, updates, kernel, desktop (attempt to base on kickstart groups)
    • DONE Create lcfg_sl6_lcfg package list and update to reflect SL6 packages
    • DONE Create installbase package list
    • DONE Modify pkglist tools to support SL6
  6. Essential headers (0.5 day)
    • DONE Create any essential headers for the platform
    • DONE Add basics to lcfg/defaults/profile.h and lcfg/defaults/updaterpms.h
    • DONE Prepare inf layer headers
  7. Essential profiles (0.5 day)
    • DONE installbase-sl6 profile
  8. DONE Auto-build and run tests for all LCFG components (2 days)
  9. Create basic development platform (once Mock configured) (3 days)
    • DONE Develop Inf level to create a basic profile
    • DONE lcfg-utils and lcfg-utils-devel
    • DONE lcfg-pkgtools & lcfg-pkgtools-devel
    • DONE perl-LCFG-PkgTools
    • DONE perl-LCFG-PkgUtils
    • DONE perl-LCFG-Utils
    • DONE lcfg-ngeneric
    • DONE lcfg-client
    • DONE lcfg-file
    • DONE lcfg-sysinfo
    • DONE lcfg-logserver
    • DONE lcfg-authorize
    • DONE lcfg-om
    • DONE pkgsubmit
    • DONE updaterpms
    • DONE lcfg-updaterpms
  10. DONE Add PXE configuration for SL6 based on F13 (0.5 days)
  11. Produce any SL6 dependent RPMs ( 2 days )
    • DONE Check upstart config and any required hacks to upstream packages ( 1 days )
    • DONE lcfg-defetc-sl6 (needed by lcfg-auth. Package will have to be built from scratch using the passwd and group files from an F13(?) installation.)
    • DONE lcfg-release-sl6
    • DONE Add SL6 template to lcfg-etcservices
    • DONE Check native SL6 sysinit ordering and modify boot component configuration as appropriate
  12. DONE Attempt install of base inf machine using F13 installer ( 1 days )
  13. DONE Check components and modify as appropriate (5 days)
  14. Installation systems (4 days)
    • DONE Create installroot package list
    • DONE Build, install and test lcfg-buildinstallroot
    • DONE Produce CD iso installer
    • DONE Deploy PXE installer
  15. Port MPU managed resources to the DICE level. (3 days)
    • DONE dice kdm theme (ascobie)
  16. Investigate naturaldocs for marking up supported headers (ascobie)
  17. Document new platforms (2 days)
    • DONE How to install a machine, known issues (squinney)
    • DONE New package lists layout and profile.packages_more (squinney)
  18. DONE Package LCFG devel tools for SL6 (may be earlier if required) and add pkgforge client (1 day)
  19. DONE Check for issues on supported hardware types (can be CSO) and record in LCFG wiki ( 5 days )
  20. Remove inf layer dependence on devel buckets and test (1 day)
    • DONE MPU components
    • other units' components. Remaining - alias, mail, mailcap (ascobie chase)
  21. DONE Add SL6 to the list of supported platforms on the LCFG website.
  22. DONE DIYDICE (ascobie)
  23. Server support
    • fibre - pending SL6.1 ?
    • DONE bonding
    • DONE VLANs
    • multipath - pending SL6.1 ?
    • DONE apacheconf
    • DONE nfs
    • DONE amd (or autofs?)
    • remctl

PLUS the following

  • Make clear distinctions between servers and desktops, both at LCFG and DICE level and fully document which package lists are for what function.
  • Every unit is configuring nagios (and sysinfo resources) for their servers in different ways. We should agree on a standard approach and then create some headers to make it all work sensibly. (Strictly speaking a DICE only issue)
  • For those drivers which might be loaded into the initrd (eg qlogic), add their firmware RPMs to the kernel base list for both LCFG and DICE. The remaining firmware RPMs can be included by options files
  • Consider whether we still want to use prelink - there's a view that this no longer improves performance as it once did and it gets in the way when investigating suspected compromised machines.

-- Main.ascobie - 2011-02-21

Topic revision: r26 - 2011-06-07 - ascobie
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback