Rough plan of what still needs to be done before particular events in the gLite3.1/SL4 release story.

Taken from Markus' slides after discussion with Laurence and Oliver.


  • lcg-version/glite-version
  • publish glite 3.1 - yaim defaults
  • TORQUE_client

Release notes available here

WN -> production

  • Repositories (Now Joachim)
    • Now CVS based list + script to copy to repositories
      • New tree for the 3.1 release
      • How do we handle updates - separate updates directory - even at PPS stage - are externals handled properly? Do we call the externals repo RPMS.externals.unmaintained?
      • How to handle the PPS and Cert repositories
        • Patch/RPM links?
        • Ideal a script that allows to move Patches to different Repositories
        • The above is now linked to the MetaRPMs and documentation, the change will affect this.
        • Laurence to talk to Joachim to see which way the script will move (Juha has to be there) * Scripts need to be documented to describe how standard operations will work.

  • Upgrades
    • As the supported OS is different from gLite 3.0, do we need to support the 3.0->3.1 upgrade?

  • RPM lists for the quator and manual friends service/node type
    • Laurence script can do this in an easy way
      • Coding has to be done

  • Documentation
    • What has changed?
    • New repositories, text that explains 3.0 and 3.1, --> Oliver and the release notes

  • Removing VDT components as agreed by the TCG
    • Laurence list has to be modified (Markus gives him input)

  • TarBall
    • How? Via ETICS?
    • Package by package exit in the ETICS repository
    • List to locate components exist
    • First step: Andreas from installed node
    • Later: Fix scripts to be ported

  • AA client tar balls
    • Laurence repository script has to be modified (Oliver started) to move new clients to AA

  • Torque client separation from WN (Juha & Robert)
    • Meta RPM for the Torque Clients (WN)
    • Meta RPM for the Torque server
    • Meta RPM for the Torque utils
      • Information providers, DGAS logging and accounting parser ……
      • APEL (CE and site BDII, )
    • This will make releases for different batch systems look more consistent
    • Config modules are needed for each of them ( subsets of what we have)
    • WN exists

  • Configuration work
    • Environment setting scripts (Robert, Gergy, Gabriel??? ) 2 days
      • Short term with “profile.d”, compatible with future solutions (CE wrapper, multiple versions)
      • Medium term: Where and how has to be clarified, (CE) Architecture decision Robert/Oliver
    • UI: WMS config. There, but test are not possible
    • Globus (WN trivial, UI DI and Robert)

  • LCG-WMS clients (edg-job*)
    • Juha build in ETICS, but not packaged
    • Tarball there, but binaries are broken -------> How to proceed
      • Franceso G. has offered to help, blocked by lack of packaging (Juha, but release work!!)

  • Adaptation of rlease scripts to 3.1 -----> Joachim ( until end of 22) Juha??

  • YUM support
    • YAIM now uses APT
    • No APT on SL4 ---------> Fine, but YUM scripts in Yaim have to be tested or :
    • We decide: “NO support for installation in YAIM
    • Needs update of release and install guides

  • Cookbook to setup sites:
    • Contribution from the extension projects needed
    • Probably relatively short document (< 10 pages)

Production longer term

  • 3.1 32bit on 64 bit SL4
    • First WN available
      • Should we recommend it????
        • Oliver says: No, to focus on 64bit build
      • 32 bit applications on the 64bit nodes????
      • Makefiles need to be adapted to move libs in lib64!!!! (JRA1 needs to know -----> Oliver EMT)
      • Mechanism to switch:
        • Automatic for libs
        • Need environment switch? Needs to be investigated (Gabriel)
    • Metapackages?
      • How do we ensure that they pull both 32 and 64 bit versions in
      • We need 32 and 64 bit Metapackes -> Laurence & Louis

  • Re-introduction of the remote distribution of the client tarball
    • Selecting a version gLite-WMS/ LCG-RB -------> CE wrapper
    • Automatic Distribution mechanism
    • All with Andreas : _-----> Mr. Tarball

  • gLite-3.1 on SL3
    • Oliver: No need to get 3.1 (vdt 1.6) WNs and UIs running on SL3
    • Markus: I don’t think we get away with this.
    • Has to be understood ------> Maite: Ask the sites about their migration plan
    • gLite-3.1 (including VDT-1.6 ) on SL3 using ETICS (Uis and WNs)
    • Services: Need to know status
    • Plan of move away from old build system needed. Should meet after Maite has asked the sites about their plan
    • Joachim (old build) , Oliver, Claudio, Laurence, Alberto, Nick

-- Main.okeeble - 28 Mar 2007

Edit | Attach | Watch | Print version | History: r7 < r6 < r5 < r4 < r3 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r7 - 2007-06-14 - PeterJones
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl 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? Ask a support question or Send feedback