HOWTO03 Site Certification GIIS Check
How to test a site before putting it into production grid
Be sure that its GIIS url is contained in the BDII you use for certification
Check the consistency of the published information
the main branches of the ldap tree are:
- GlueSiteUniqueID
- GlueSubClusterUniqueID
- GlueCEUniqueID
- GlueCESEBind
- GlueSEUniqueID
- GlueServiceUniqueID
Use a browser ldap in order to make easy your work. Anyway, it is shown in this wiki an example ldapsearch command with which check the several information
Under the branch GlueSiteUniqueID check the values of the following parameters:
- GlueSiteName
- GlueSiteUserSupportContact
- GlueSiteSysAdminContact
- GlueSiteSecurityContact
- GlueSiteOtherInfo
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://sibilla.cnaf.infn.it:2170 -b mds-vo-name=INFN-CNAF,o=grid 'objectClass=GlueSite' GlueSiteName GlueSiteUserSupportContact GlueSiteSysAdminContact GlueSiteSecurityContact GlueSiteOtherInfo dn: GlueSiteUniqueID=INFN-CNAF,Mds-Vo-name=INFN-CNAF,o=grid GlueSiteSecurityContact: mailto:grid-sec@cnaf.infn.it GlueSiteSysAdminContact: mailto:sitemanager@cnaf.infn.it GlueSiteName: INFN-CNAF GlueSiteUserSupportContact: mailto:sitemanager@cnaf.infn.it GlueSiteOtherInfo: CONFIG=yaim GlueSiteOtherInfo: EGEE_ROC=Italy GlueSiteOtherInfo: EGEE_SERVICE=prod GlueSiteOtherInfo: GRID=WLCG GlueSiteOtherInfo: GRID=EGEE
Under the branch GlueSubClusterUniqueID check the values of the following parameters:
- Check GlueHostApplicationSoftwareRunTimeEnvironment
- site name
- Current version of middleware
- R-GMA
- SI00MeanPerCPU_<value> e SF00MeanPerCPU_<value>
- if the site supports mpi jobs, MPICH (ant other related tags)
- (in case) AFS (and verify WNs mount /afs)
- GlueHostProcessorOtherDescription (for instance: Cores=2,Benchmark=7.92-HEP-SPEC06 )
- GlueHostOperatingSystemName (es. ScientificSL)
- GlueHostOperatingSystemVersion (es. Berillium)
- GlueHostOperatingSystemRelease (es. 4.5)
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://virgo-ce.roma1.infn.it:2170 -b mds-vo-name=resource,o=grid 'objectClass=GlueSubCluster' GlueHostProcessorOtherDescription dn: GlueSubClusterUniqueID=virgo-ce.roma1.infn.it,GlueClusterUniqueID=virgo-ce.roma1.infn.it,Mds-Vo-name=resource,o=grid GlueHostProcessorOtherDescription: Cores=4, Benchmark=7.83-HEP-SPEC06
Under the branch GlueCEUniqueID check the values of the following parameters:
- GlueCEInfoTotalCPUs: If there is a “0”, you have to worry!!
- GlueCEStateWaitingJobs: If there is a “44444”, red alarm!!
- GlueCEInfoLRMSType: pbs or lsf (or sge, …)
- GlueCEStateStatus: Production or Draining
- GlueCEAccessControlBaseRule: VOs enabled on the queue
- GlueCECapability
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://virgo-ce.roma1.infn.it:2170 -b mds-vo-name=INFN-ROMA1-VIRGO,o=grid 'objectClass=GlueCE' GlueCEInfoTotalCPUs GlueCEInfoJobManager GlueCEImplementationName dn: GlueCEUniqueID=virgo-ce.roma1.infn.it:2119/jobmanager-lcgpbs-theophys,Mds-Vo-name=INFN-ROMA1-VIRGO,o=grid GlueCEImplementationName: LCG-CE GlueCEInfoJobManager: lcgpbs GlueCEInfoTotalCPUs: 8 dn: GlueCEUniqueID=virgo-ce.roma1.infn.it:2119/jobmanager-lcgpbs-cert,Mds-Vo-name=INFN-ROMA1-VIRGO,o=grid GlueCEImplementationName: LCG-CE GlueCEInfoJobManager: lcgpbs GlueCEInfoTotalCPUs: 8 dn: GlueCEUniqueID=virgo-ce.roma1.infn.it:2119/jobmanager-lcgpbs-virgoglong,Mds-Vo-name=INFN-ROMA1-VIRGO,o=grid GlueCEImplementationName: LCG-CE GlueCEInfoJobManager: lcgpbs GlueCEInfoTotalCPUs: 8 dn: GlueCEUniqueID=virgo-ce.roma1.infn.it:2119/jobmanager-lcgpbs-argo,Mds-Vo-name=INFN-ROMA1-VIRGO,o=grid GlueCEImplementationName: LCG-CE GlueCEInfoJobManager: lcgpbs GlueCEInfoTotalCPUs: 8 dn: GlueCEUniqueID=virgo-ce.roma1.infn.it:2119/jobmanager-lcgpbs-virgogshort,Mds-Vo-name=INFN-ROMA1-VIRGO,o=grid GlueCEImplementationName: LCG-CE GlueCEInfoJobManager: lcgpbs GlueCEInfoTotalCPUs: 8
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://cmsrm-bdii.roma1.infn.it:2170 -b mds-vo-name=INFN-ROMA1-CMS,o=grid 'objectclass=GlueCE' GlueCECapability dn: GlueCEUniqueID=cmsrm-ce01.roma1.infn.it:2119/jobmanager-lcglsf-cmsgcert,Mds-Vo-name=INFN-ROMA1-CMS,o=grid GlueCECapability: CPUScalingReferenceSI00=1515 GlueCECapability: Share=cms:100 dn: GlueCEUniqueID=cmsrm-ce01.roma1.infn.it:2119/jobmanager-lcglsf-cmsglong,Mds-Vo-name=INFN-ROMA1-CMS,o=grid GlueCECapability: CPUScalingReferenceSI00=1515 GlueCECapability: Share=cms:100 dn: GlueCEUniqueID=cmsrm-ce01.roma1.infn.it:2119/jobmanager-lcglsf-cmsgshort,Mds-Vo-name=INFN-ROMA1-CMS,o=grid GlueCECapability: CPUScalingReferenceSI00=1515 GlueCECapability: Share=cms:100 dn: GlueCEUniqueID=cmsrm-ce02.roma1.infn.it:2119/jobmanager-lcglsf-cmsglong,Mds-Vo-name=INFN-ROMA1-CMS,o=grid GlueCECapability: CPUScalingReferenceSI00=1515 GlueCECapability: Share=cms:100 dn: GlueCEUniqueID=cmsrm-ce02.roma1.infn.it:2119/jobmanager-lcglsf-cmsgcert,Mds-Vo-name=INFN-ROMA1-CMS,o=grid GlueCECapability: CPUScalingReferenceSI00=1515 GlueCECapability: Share=cms:100 dn: GlueCEUniqueID=cmsrm-ce02.roma1.infn.it:2119/jobmanager-lcglsf-cmsgshort,Mds-Vo-name=INFN-ROMA1-CMS,o=grid GlueCECapability: CPUScalingReferenceSI00=1515 GlueCECapability: Share=cms:100
For each SE, on the CEs the following parameters have to be present:
- GlueCESEBindSEUniqueID
- GlueCESEBindCEAccesspoint and GlueCESEBindMountInfo
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://cremino.cnaf.infn.it:2170 -b mds-vo-name=resource,o=grid 'objectClass=GlueCESEBind' GlueCESEBindSEUniqueID GlueCESEBindCEUniqueID GlueCESEBindMountInfo dn: GlueCESEBindSEUniqueID=sunstorm.cnaf.infn.it,GlueCESEBindGroupCEUniqueID=cremino.cnaf.infn.it:8443/cream-pbs-cert,Mds-Vo-name=resource,o=grid GlueCESEBindSEUniqueID: sunstorm.cnaf.infn.it GlueCESEBindMountInfo: n.a GlueCESEBindCEUniqueID: cremino.cnaf.infn.it:8443/cream-pbs-cert dn: GlueCESEBindSEUniqueID=sunstorm.cnaf.infn.it,GlueCESEBindGroupCEUniqueID=cremino.cnaf.infn.it:8443/cream-pbs-prod,Mds-Vo-name=resource,o=grid GlueCESEBindSEUniqueID: sunstorm.cnaf.infn.it GlueCESEBindMountInfo: n.a GlueCESEBindCEUniqueID: cremino.cnaf.infn.it:8443/cream-pbs-prod
Under the branch GlueSEUniqueID check the values of the following parameters:
- GlueSALocalID: VO information
- GlueSEAccessProtocolLocalID: rfio, srm_v1, srm_v2, classic, gsiftp, gsidcap
- GlueSEType (deprecated)
- GlueSEArchitecture
- GlueSAStateUsedSpace
- GlueSAStateAvailableSpace
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://sunstorm.cnaf.infn.it:2170 -b mds-vo-name=resource,o=grid 'objectClass=GlueSE' dn: GlueSEUniqueID=sunstorm.cnaf.infn.it,Mds-Vo-name=resource,o=grid objectClass: GlueSETop objectClass: GlueSE objectClass: GlueInformationService objectClass: GlueKey objectClass: GlueSchemaVersion GlueSEUniqueID: sunstorm.cnaf.infn.it GlueSEName: INFN-CNAF:srm_v2 GlueSEArchitecture: multidisk GlueSEStatus: Production GlueSEImplementationName: StoRM GlueSEImplementationVersion: 1.5.6 GlueSESizeTotal: 649 GlueSESizeFree: 649 GlueSETotalOnlineSize: 649 GlueSEUsedOnlineSize: 0 GlueSETotalNearlineSize: 0 GlueSEUsedNearlineSize: 0 GlueInformationServiceURL: ldap://sunstorm.cnaf.infn.it:2170/mds-vo-name=resource,o=grid GlueForeignKey: GlueSiteUniqueID=INFN-CNAF GlueSchemaVersionMajor: 1 GlueSchemaVersionMinor: 3
$ ldapsearch -x -LLL -H ldap://prod-bdii-02.pd.infn.it:2170 -b mds-vo-name=INFN-PADOVA,o=grid 'objectClass=GlueSA' GlueSAAccessControlBaseRule
there is a branch GlueServiceUniqueID for each service published by the site (WMS, LFC, DPM, GRIDICE, LB, MYPROXY, BDII,…): what discriminate the services are the values of GlueServiceType, ex:
* lcg-file-catalog * org.glite.wms.WMProxy * org.glite.lb.Server * srm_v1, SRM
EXAMPLE:
$ ldapsearch -x -LLL -H ldap://gridit-ce-001.cnaf.infn.it:2170 -b mds-vo-name=INFN-CNAF,o=grid 'objectClass=GlueService' GlueServiceType GlueServiceEndpoint GlueServiceName