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

32 or 64

  • GlueHostArchitecturePlatformType

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.

For example


This is currently a proposal only.

-- Main.okeeble - 27 Jun 2007

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2011-06-22 - AndresAeschlimann
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback