How to describe a subcluster's software installation
There are various pages describing how to advertise the characteristics of a subcluster's software installation. Now that we are dealing with a number of different platforms, agreement on a convention here is important.
This is intended as a useful summary page and does not itself represent policy.
Operating system name and version
-
GlueHostOperatingSystemName
-
GlueHostOperatingSystemRelease
-
GlueHostOperatingSystemVersion
https://wiki.egi.eu/wiki/Operations/HOWTO05
32 or 64
-
GlueHostArchitecturePlatformType
https://wiki.egi.eu/wiki/Operations/HOWTO06
Installed Middleware
-
GlueHostApplicationSoftwareRunTimeEnvironment
Remember that for gLite 3.0 WN you should have
GlueHostApplicationSoftwareRunTimeEnvironment: GLITE-3_0_2
And for gLite 3.1 you should have
GlueHostApplicationSoftwareRunTimeEnvironment: GLITE-3_1_0
The release of 'SL3 binaries for SL4' if you have it counts as gLite 3.0.
Different flavours of middleware and applications
Normally applications and middleware are advertised by the following Glue attribute
-
GlueHostApplicationSoftwareRunTimeEnvironment
As it is possible to have multiple varieties of a particular application (or the middleware) installed on one subcluster (32 and 64 bit varieties for example), further
precision could be achieved by appending the Application Area approved string.
https://twiki.cern.ch/twiki/bin/view/SPI/LcgTags
For example
VO-vo-group-version-slc4_amd64_gcc34
GLITE-3_1_0-slc4_amd64_gcc34
This is currently a proposal only.
-- Main.okeeble - 27 Jun 2007