HOWTO03 Site Certification GIIS Check
Be sure that Resource Centre GIIS URL is contained in the BDII you use for certification.
Check the consistency of the published information
These are the main branches of the LDAP tree:
GlueSiteUniqueID
GlueSubClusterUniqueID
GlueCEUniqueID
GlueCESEBind
GlueSEUniqueID
GlueServiceUniqueID
It is recommended to use the
Apache Studio LDAP browser, although in
this page ldapsearch
queries are shown.
Contact information
Under the branch GlueSiteUniqueID
check the values of the following fields:
GlueSiteName
GlueSiteUserSupportContact
GlueSiteSysAdminContact
GlueSiteSecurityContact
GlueSiteOtherInfo
Example:
Information related to software environment
Under the branch GlueSubClusterUniqueID
check the values of the following
fields:
- Check that the
GlueHostApplicationSoftwareRunTimeEnvironment
contains a list of software tags supported by the site.- The list can include VO-specific software tags.
- In order to ensure backwards compatibility it should include the entry ‘LCG-2’, the current middleware version and the list of previous middleware tags (i.e. LCG-2 LCG-2_1_0 LCG-2_1_1 LCG-2_2_0 LCG-2_3_0 LCG-2_3_1 LCG-2_4_0 LCG-2_5_0 LCG-2_6_0 LCG-2_7_0 GLITE-3_0_0 GLITE-3_1_0 GLITE-3_2_0 R-GMA).
GlueHostProcessorOtherDescription
(see FAQ HEP SPEC06)GlueHostOperatingSystemName
,GlueHostOperatingSystemVersion
andGlueHostOperatingSystemRelease
(see publishing the OS name).
Example:
Publishing the OS name
It has been decided that the 3 fields
GlueHostOperatingSystemName
GlueHostOperatingSystemRelease
GlueHostOperatingSystemVersion
should be parsed from the output of /usr/bin/lsb_release
, like this:
GlueHostOperatingSystemName
:lsb_release -i | cut -f2
GlueHostOperatingSystemRelease
:lsb_release -r | cut -f2
GlueHostOperatingSystemVersion
:lsb_release -c | cut -f2
yielding values like
GlueHostOperatingSystemName
: CentOSGlueHostOperatingSystemRelease
: 7.9.2009GlueHostOperatingSystemVersion
: Core
This has been tested on various Linux flavours and should work on every serious GNU/Linux distribution.
Information about the batch system
Under the branch GlueCEUniqueID
check the values of the following fields:
GlueCEInfoTotalCPUs
: Check that the value is higher than 0.GlueCEStateWaitingJobs
: If there is a “44444”, the information providers are not working properly.GlueCEInfoLRMSType
: any supported batch system (sge, pbs, lsf…)GlueCEStateStatus
: Production, Draining, Queuing or Closed are accepted values.GlueCEAccessControlBaseRule
: VOs enabled on the queueGlueCECapability
Example:
Information on Computing Element about Storage Elements
For each SE, on the CEs the following values must be present:
GueCESEBindSEUniqueID
.GlueCESEBindCEAccesspoint
andGlueCESEBindMountInfo
.
Example:
Information on Storage Elements
Under the branch GlueSEUniqueID
check the values of the following fields:
GlueSALocalID
: VO informationGlueSEAccessProtocolLocalID
: rfio, srm_v2, gsiftp, gsidcapGlueSEImplementationName
(deprecated)GlueSEArchitecture
GlueSAStateUsedSpace
GlueSAStateAvailableSpace
GlueSACapability
Example:
Information about other services
There is a branch GlueServiceUniqueID
for each service published by the site
(WMS, LFC, DPM, GRIDICE, LB, MYPROXY, BDII, etc): what discriminates the
services are the values of GlueServiceType
, example:
lcg-file-catalog
org.glite.wms.WMProxy
org.glite.lb.Server
srm_v1, SRM
Example:
See the Site Certification Manual tests HOWTO04
See to Resource Centre registration and certification procedure PROC09.