EMITarball

From GridPP Wiki
Jump to: navigation, search

The EMI WN UI Tarball project is on going, headed by members of GridPP - particularly Matt Doidge at Lancaster University. Sadly we lost much of our old wiki pages, hopefully this will answer any questions. Please pardon our mess.

Overview

The EMI3 Worker Node and User Interface tarball is produced for SL6 using tools originally written by David Smith (CERN). The goal of the tarball is to allow the EMI WN or UI to be served over a remote export (such as NFS) on a SL6 machine, without installation of any extra packages or rpms. The tarballs can also be exported over cvmfs, and the latest versions of the tarball are available in the grid.cern.ch repository.

Currently only the SL6 versions of the EMI WN and UI tarballs are being developed. Work on an SL7 version will start later in 2015.

Where to Download

The latest versions of the EMI3 WN and UI Tarballs can be found here:

http://repository.egi.eu/mirrors/EMI/tarball/test/sl6/emi3-emi-wn/

(lastest emi-wn-3.10.0-1_v2, September 2014)

http://repository.egi.eu/mirrors/EMI/tarball/test/sl6/emi3-emi-ui/

(latest emi-ui-3.14.0-1_v1, January 2015)

Select version of both can be found in the grid.cern.ch cvmfs repository.

Tarball Structure

Each tarball currently comes in two parts:

  • The core tarball, containing the unpacked packages from the EMI repository.
  • The "os-extras" tarball, built from packages from the SL and epel repositories.

The rpms that went into building each tarball are listed in "rpmlist.txt" and "os-extras.txt" respectively. A "halfway" approach to the tarball, installing packages from the "os-extras" list and only using the core tarball, is supported and does work.

This structure is currently under review and may change.

Tarball Versions

The tarball versions listed may look convoluted, but there is a system to them! The first part denotes what middleware was used to build the tarball (emi-ui or emi-wn), the second is the version of that middleware built as denoted by the rpm. The _vX is native to the tarball version, denoting the iteration of the tarball for that particular middleware release (things don't always go right first time).

How to install

(work in progress)

1. Download the tarball.
2. Unpack the tarball (tar -xzf ....) to an exported volume or onto the node itself. If using the os-extras tarball you will need to download and unpack it in the same directory.
3. Write or edit a script that points such variables as PATH, LD_LIBRARY_PATH, VOMS_USERCONF etc at the tarball. An example setup script is placed in etc/profile.d/ in each tarball.
4. That's it - you should have a working set of the UI and WN middleware. Some extra work is needed for the vomsdir, vomses, CA and CRLs. For a WN you will have to set up the users and batch system yourself.

If wanting to access the tarball in the grid.cern.ch cvmfs repo, simply replace the unpacking of the tarball with setting up cvmfs, enable the grid.cern.ch repository, and have your scripts point there instead. Examples are stored in the repository, which is maintained by the tarball team.

How to contact us

The EMI tarball has its own GGUS support group, this one of the better ways of getting in touch, and of course the place to submit tickets to - either about the regular tarball or the tarballs within grid.cern.ch.

https://wiki.egi.eu/wiki/GGUS:UI_WN_Tarball_FAQ

There is a tarball email address:

tarball-grid-support atSPAMNOT cern.ch

Old docs

The old docs have been secreted here. We hope to improve the documentation over time, when we have time!