Release notes for the gLite 3.1 UI for SL4 as provided to PPS

These notes describe the initial release to PPS of the gLite 3.1 UI for SL4

What's new?

  • The binaries have been natively built on SL4
  • The codebase is gLite 3.1, not gLite 3.0 (in practise the changes here are small)
  • There are updated dependencies, most notably
    • VDT1.6 which provides GT4
    • Java 1.5
  • There is updated configuration based on yaim 3.1
  • Many obsolete components have been removed

This release has been tested only on 32 bit. Nevertheless, feedback on attempts at 64 bit installation are welcomed.

Installation

You will have to install a java 1.5 rpm first. Get this from sun

Please use the following repository to install

http://grid-deployment.web.cern.ch/grid-deployment/glite/pps/3.1/glite-UI/sl4/i386/

The following meta-package is available

  • PPS-glite-UI

Note that installation via yaim for this version is not (yet) supported, please use native package management tools (yum is strongly recommended).

To use yum, create glite.repo in /etc/yum.repos.d with the following contents (please note that this information has changed since the original release).

[pps-glite-ui]
name=gLite 3.1 User Interface (PPS)
baseurl=http://grid-deployment.web.cern.ch/grid-deployment/glite/pps/3.1/glite-UI/sl4/i386
enabled=1

[glite]
name=gLite 3.1 (production)
baseurl=http://glitesoft.cern.ch/EGEE/gLite/R3.1/generic/sl4/i386
enabled=1

[CA]
name=CAs
baseurl=http://linuxsoft.cern.ch/LCG-CAs/current
enabled=1

You will have to reference a jpackage repository too (for example in jpackage.repo);

[main]
[jpackage17-generic]
name=JPackage 1.7, generic
baseurl=http://mirrors.dotsrc.org/jpackage/1.7/generic/free/
enabled=1
protect=1

[main]
[jpackage5-generic]
name=JPackage 5, generic
baseurl=http://mirrors.dotsrc.org/jpackage/5.0/generic/free/
enabled=1
protect=1

More information on java and jpackage with gLite 3.1 can be found here

Then you can do

# yum install PPS-glite-UI

You can also install CA packages

# yum install lcg-CA

Configuration

The YAIM configuration for gLite 3.1 doesn't differ from the 3.0.1 from the configuration point of view. All configuration files used with YAIM 3.0.1 should be compatible with the YAIM 3.1.0 The yaim 3.1 is currently in finalization state and there is still a list of known problems and imperfections we are fixing. There are several modifications between yaim 3.0.1 and 3.1:

  • the configure_node, install_node and run_function are obsoleted although they are still located in the "/opt/glite/yaim/scripts" directory, please do not use them The configuration will very probably fail. All these commands will be removed in the next release. Their functionality has been replaced by new command yaim which has been introduced in yaim 3.0.1 and in yaim version 3.1 it became the only way to configure gLite middleware using yaim.
  • changes in the yaim packaging. Yaim 3.1 has a modular structure (glite-yaim-core, glite-yaim-clients) in contrary to the monolithic distribution of yaim 3.0.1 (glite-yaim package)
  • added service and node based configuration
The detailed documentation for yaim 3.1 is currently prepared and will be accessible soon from the : yaim 3.1 page.

Please configure your UI as follows

 
/opt/glite/yaim/bin/yaim -c -s <site-info.def> -n glite-UI

Tarball release

There is a tarball release available, it is described here

Known issues

  • config_globus_devel: WARNING: The following flavours are not supported for this platform: gcc32, gcc32pthr, gcc32dbg, gcc32dbgpthr. And configure: error: C++ preprocessor "/usr/bin/gcc -E" fails sanity check. Installing gcc-c++ packages to solve it.

  • myproxy commands still return nonzero exit code

  • Runtime error with LFC Perl API reported as bug 26535 - workaround setenv MALLOC_CHECK_ 0

  • Yaim produces a massive amount of "INFO" messages like: INFO The function: config_upgrade_check hasn't been executed, because not defined. It is OK, don't worry.

  • PYTHONPATH is not configured correctly: It contains an entry "/lcg/lib/python" this should be "/opt/lcg/lib/python" Fix: In the file "/etc/profile.d/grid-env.sh" change the line gridpath_append "PYTHONPATH" "/lcg/lib/python" to gridpath_append "PYTHONPATH" "/opt/lcg/lib/python"

  • PERL5LIB is not configured correctly: This variable contains an entry "/lcg/lib/perl" which should be "/opt/lcg/lib/perl". Fix: In the file "/etc/profile.d/grid-env.sh" change the line gridpath_append "PERL5LIB" "/lcg/lib/perl" to gridpath_append "PERL5LIB" "/opt/lcg/lib/perl"

  • rgma-client-check used wrong log4j location as bug 26943

-- Main.okeeble - 04 Jun 2007

Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2007-06-15 - DiQing
 
    • 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