Notes on the gLite 3.0 beta release to pre-production.

The gLite 3.0 PPS release is now available. It is based on LCG-2_7_0 with the addition of

gLite WMS/LB
gLite CE
Combined gLite/LCG WN
Combined gLite/LCG UI
FTS server

There is an apt-get repository for PPS which will only be updated with packages that have been tested. The schedule of updates is to be confirmed.

rpm http://lxb2042.cern.ch/gLite/APT/PPS rhel30 externals Release3.0 updates

The CAs have been decoupled from the release - further info on how to install them can be found here

http://grid-deployment.web.cern.ch/grid-deployment/lcg2CAlist.html

List of targets;

The metapackages available are;

Please don't use yaim's install_node script to install the above node types, just use apt-get install.

glite-UI (a combined LCG/gLite UI)
glite-WN (a combined LCG/gLite UI)
glite-file-transfer-service-config (FTS server plus related services)
glite-ce-config (the gLite CE)
glite-wms-config + glite-lb-config (recommended deployment of the WMS)

install_node work for the meta packages beginning by lcg-

lcg-BDII
lcg-CE
lcg-CE_torque
lcg-LFC_mysql
lcg-LFC_oracle
lcg-MON
lcg-PX
lcg-RB
lcg-SE_classic
lcg-SE_dpm_mysql
lcg-SE_dpm_oracle
lcg-SE_dpm_disk
lcg-SE_dcache
lcg-SE_dcache_gdbm
lcg-WN
lcg-WN_torque
lcg-UI
lcg-VOBOX
lcg-VOMS_mysql

The meta-rpm names will be rationlised in the near future. The lcg-* node types are as described in the manual install guide;

http://grid-deployment.web.cern.ch/grid-deployment/documentation/LCG2-Manual-Install/

Configuration

Configuration for all previous LCG-2_7_0 components is supported via yaim

Configuration for all 'gLite' components is supported via the native (XML) system.

There is new yaim functionality for the following;

glite CE (configure_node site-info.def gliteCE)
gLite WMS (configure_node site-info.def WMS)
Combined UI (configure_node site-info.def UI_combined)
FTS server (configure_node site-info.def FTS)

In WMS case the gLite WMS and LB will be configured, please make sure both components are installed on the node.

In the case of the FTS yaim will configure all related services such as crl downloads, info provider etc but the FTS server itself must be configured using the usual gLite system. A yaim component will follow.

Please don't use yaim's install_node script to install the above node types, just use apt.

Where yaim is configuring a gLite node type, it populates the XML files and runs the gLite config scripts. Please note that any modifications you make to the XML files, to parameters not managed by yaim, should be preserved. Parameters managed by yaim will be clearly marked in the XML after it has been run. The intention is that yaim offers a simple interface if prefered, but the ability to use the more powerful native machanism is retained.

Yaim will be integrated into the repository soon. In the meantime, please always use the latest lcg-yaim-2.9.9 which you can find here;

Pick up the latest yaim at http://grid-deployment.web.cern.ch/grid-deployment/gis/yaim-devel/

New Yaim parameters;

gliteCE_HOST - gLite CE
WMS_HOST - gLite WMS + LB
FTS_HOST - for building an FTS server
REPOSITORY_TYPE - defaults to apt, but yum can be used. Please note for gLite 3.0 the repo does not yet support yum!
BATCH_BIN_DIR - The path of the lrms commands, eg /usr/pbs/bin
BATCH_VERSION - The version of the Local Resource Managment System, eg OpenPBS_2.3

Notes on particular node types;

Combined UI

The yaim config for the glite-UI (ie the combined UI) has not yet been tested with the official metapackage. Nevertheless, please try it and send feedback. The separate UIs (lcg-UI and glite-ui-config) are still available and can be configured using their 'native' mechanisms.

On the combined node, please watch out for glite commands which are symlinked to edg commands and may appear earlier in the PATH than their edg counterparts. The extent to which the glite symlinks can provide the functionality of the edg commands they replace is untested.

The RPM based userland installation finished without conflicts but there are lots of warnings and errors due to install scripts which require root privilege.

WN

The safest WN strategy is to use the lcg-WN with yaim config. There is currently no integrated config for the combined node, glite-WN, but it could be used with a custom configuration.

gLite CE

There is an issue with configuration of VOMS support on the glite CE. The following (for example) has to be in /etc/grid-security/grid-mapfile;

/dteam/Role=lcgadmin dteamsgm
/alice/Role=lcgadmin alicesgm
/atlas/Role=lcgadmin atlassgm
/cms/Role=lcgadmin cmssgm
/lhcb/Role=lcgadmin lhcbsgm
/dteam .dteam
/dteam/* .dteam
/alice .alice
/alice/* .alice
/atlas .atlas
/atlas/* .atlas
/cms .cms
/cms/* .cms
/lhcb .lhcb
/lhcb/* .lhcb

but if you configure with yaim there is also a cron job which will overwrite any additions made to this file. Please turn the cron job off, temporarily, once the addition above has been made (yaim will configure this job in /etc/cron.d/edg-mkgridmap). Alternatively users/testers should use a normal proxy rather than a voms proxy.

Batch systems and the gLite CE

If you are installing your batch system server on the same node as the CE, and you want to use yaim or gLite to configure it, please choose one or the other and stick to it. If you use yaim and then make modifications via the gLite system, any rerun of yaim will reset the configuration. The same advice applies to management of WNs.

DPM

A VOMS enabled DPM will be made available as soon as it passes certification. For the moment, please do not install or upgrade a DPM.

dCache

The yaim script for configuring dCache has received many updates from GridPP. It offers extended functionality but is backward compatible.

Outstanding bugs

During the integration and testing process a list of outstanding issues was maintained. Here is a summary of the issues which have not yet been addressed and were considered important;

savannah issue 15050 - this has NOT been fixed. The impact is of the order of a few jobs (<5) per thousand.

savannah issue 15217 - fix is in the release, but has not been fully tested

Keep this one in mind too;

savannah issue 15189 - status not updated for nodes of a large collection

Notes

Other issues to remain aware of;

Between LCG-2_7_0 and gLite 3.0 MySQL has been upgraded from 4.0 to 4.1. There has been a change in the password encryption, please keep this in mind.

Pointers to documentation on the components of this release are being compiled here

http://www.grid.kfki.hu/afs/gdebrecz/web/LCG/the-LCG-directory.html