Index of /install/poc
Name Last modified Size Description
![[DIR]](/icons/back.gif)
Parent Directory -
![[TXT]](/icons/text.gif)
IniFiles.pm 14-May-2003 03:30 68K
![[ ]](/icons/unknown.gif)
Xdialog 14-Mar-2002 16:25 69K
dialog 25-Jun-2001 16:47 68K
poc-install.pl 04-Aug-2004 14:43 25K
![[ ]](/icons/script.gif)
poc.conf 24-Feb-2005 12:43 4.9K
![[DIR]](/icons/folder.gif)
vl-e/ 16-Dec-2004 13:40 -
yum-1.0.3-1_73.noarch.rpm 09-Sep-2003 05:19 92K
yum-1.0.3-1_80.noarch.rpm 18-Sep-2003 14:20 94K
yum-2.0.5-1.centos.2.noarch.rpm 15-Mar-2004 23:49 111K
yum-2.0.5-1.noarch.rpm 01-Feb-2004 04:58 110K
VL-E Proof-of-Concept (PoC) Installer BETA release 0.1
------------------------------------------------------
If you are in a hurry, follow these steps:
* Install perl and wget on your system. There is a 99% chance you already
have these packages
* Download the PoC-installer:
wget http://www.dutchgrid.nl/install/poc/poc-install.pl
(if it succeeds, you are sure you have wget :-)
* Start the installer:
perl ./poc-install.pl
* Answer the questions and start running.
Three caveats:
* The system has been tested on a regular RedHat 7.3 and CentOS3.1 (that
is the same as RedHat Enterprise Linux 3) system.
* If you have a Java2 SDK installed and you also have /etc/java/java.conf,
and your RPM java installation does not "provide" you with
"j2sdk = 2000:1.4.2_04-fcs", you should move that file out of the
way temporarily.
* Before you can use the grid, you need a personal certificate and (if you run
services) also a host certificate.
Go to http://www.dutchgrid.nl/ca to obtain one.
All comments please to davidg@nikhef.nl for the time being. Or use
the PVIER list.
In-depth explanation
--------------------
The poc-installer is based on "yum", the rpm dependency manager that ships
by default with Fedora Linux and with CentOS. If your system does not have
yum installed already, the poc-installer will retrieve a copy and install
that one first.
+-----------------------------------------------------------------------+
| IF YOU DID NOT HAVE YUM YET |
| the yum installation provided by the poc-installer has some yum |
| repositories pre-configured in /etc/yum.conf. At times, these default |
| repositories can be rather slow. You can edit your /etc/yum.conf file |
| to point them to a better repository. |
| For RH73, such a repository is available from |
| http://www.dutchgrid.nl/mirror/ftp.redhat.com/linux/ ... |
| ... 7.3/en/os/i386/RedHat |
| and similarly for the RH73 upgrades |
+-----------------------------------------------------------------------+
The poc-installer is configured by a single file, "poc.conf" that is
retrieved automatically from the source web site. If you have your own
copy of poc.conf, you can specify that on the poc-install.pl command line
using the "--conf=<poc.conf>" argument.
In the poc.conf file, almost every possible thing is changeable. For
example, which package groups to install by default, and which high-level
RPMs these package groups contain. If you have a good poc.conf with which
you are happy, you can even run the installation un-attended.
Commandline arguments
---------------------
perl poc-install.pl <argument> ...
-q, --noint, --quiet Assume yes on every answer and show no dialogs
--nc, --installonly Only install the RPMs, and do not try to
configure anything
--ni, --configureonly Assume everything is installed and only do the
(re)configuration
--baseurl=URL The URL from which to download the poc.conf file
and any file obtained with wget that does not
have a full URL specification.
Also the place to get the "dialog" program if
that is not yet installed on the system.
default: http://www.dutchgrid.nl/install/poc
--conf=file Location of the poc.conf file to use
--dialog=file Name of the "dialog" program
--wget=file Name of the "wget" program
--tmp=path Basename of the installer scratch area for
downloads
-v[=i] Verbosity level
Grid Software to be Installed
-----------------------------
The poc-installer uses the concept of "package groups" and uses
the inherent dependencies of "high-level" RPMs to make it into a consistent
installation. If your system needs additional dependencies to be installed,
they will be taken from the per-OS default YUM repositories.
In case your OS is not yum-installed, the repository of mirror.dulug.duke.edu
is used by default to pick up those dependencies.
The following package groups are defines (in poc.conf):
Trusted Certification Authorities EUGridPMA
You /must/ install at least one trusted certification authority to be
able to use the grid. To help administrators evaluate such authorities,
the EUGridPMA established minimum standards and accredits authorities
that comply with these standards.
This package group installs all accredited authorities.
Basic grid security system utilities
The Certificate Authorities issue lists of revoked certificates that
should no longer be accepted. By policy, you should periodically
refresh your copy of these lists (CRLs).
This package crontains the cron jobs to retrieve CRLs every 6 hours.
Globus profile configuration
Adds profile scripts for users to find the Globus (GT2) utilities
LCG User profile configuration
Adds profile scripts for users to find the EU DataGrid and LCG
utilities.
Grid essential clients
This package provideds the basic Grid client (security and status)
Globus basic job tools (globusrun)
Provides the globusrun and globus-job-run commands to send grid jobs
to specific resource managers.
GridFTP command-line clients
The globus-url-copy command and the gridftp-ls, -exists, etc
tool to manipulate individual files on the grid.
EDG brokered job submission
EDG Replica Management
Globus Grid Information system client
MyProxy long-running-job support
GridFTP (Globus) Server
Note: this package group is not installed by default!
Service hosting VO Support
Note: this package group is not installed by default!
VO Management System client
Note: this package group is not installed by default!
Virtual Organisations
---------------------
These VOs have their default configuration parameters shipped as part of
the poc.conf file:
pvier ncf atlas alice lhcb cms dteam eo
Infrastructures
---------------
Moreover, the concept of an "infrastructure" defines a set of resources
that together recognise a common set of asseptable use policies (AUPs).
There are three "infrastructures" that you can enable if you are running
Grid services like a GridFTP server:
egee vle edg
Note that by default you will not be running any services and thus you
do not need to enable an infrastructure.
Finding out what is in the Grid
-------------------------------
As part of the Grid, you will be looking at an "Information Index",
normally maintained by your virtual organisation. As part of the PoC
infrastructure, you can use a common Index for many different
VOs. By default, you will be using an LCG2 production II.
The Grid-mapfile, allowing users in
-----------------------------------
Note that before you enable any service, you must refresh the grid-mapfile
using the edg-mkgridmap script (run from cron by default), AND create
all the appropriate local (lease) accounts.
Creating accounts is not done by the poc-installer, and you should set up
these accounts yourself.
If you are about to use poolaccounts, please have a look at
http://www.gridpp.ac.uk/gridmapdir/
for information on how to set these up and maintain accountability.
Of course, you can also use a single shared account per VO, and even
just one single account for all grid users, but do keep the accountability
and security issues in mind!