Information System Providers

This twiki contains information about the existing Information System Providers.

Responsibility Matrix

	Product	Involved Packages	Plugin/Provider in the BDII	Responsible	Contact
Computing	Condor	info-dynamic-condor	info-dynamic-condor	Michel Jouvin, Guillaume Philippon	Unknown
	CREAM	1) dynsched-generic 2) Information providers distributed in cream-utils 3) YAIM functions (*)	1) glite-info-dynamic-scheduler-wrapper 2) glite-info-cream-glue2 glite-info-dynamic-software-wrapper glite-info-glue2-applicationenvironment-wrapper	Paolo Andreetto	GGUS
	HTCondorCE	htcondorce-cern	condor_ce_bdii_generate_glue2	Iain Bradford Steers	Unknown
	LSF	info-dynamic-scheduler-lsf	glite-info-dynamic-ce (using info-dynamic-lsf)	Ulrich Schwickerath	GGUS
	PBS	1) lcg-info-dynamic-scheduler-pbs 2) info-dynamic-pbs (removed in EMI 3)	glite-info-dynamic-ce (using info-dynamic-pbs)	Paolo Andreetto	GGUS
	SGE	glite-info-dynamic-ge	Unknown	ge-support@listasNOSPAMPLEASE.cesga.es	GGUS
	SLURM	info-dynamic-scheduler-slurm	info-dynamic-scheduler-slurm	Paolo Andreetto	GGUS
Storage	CASTOR	Unknown	Unknown	Different information providers at CERN and RAL. Unknown for ASGC	GGUS
	EOS	Unknown	Unknown	IT-DSS at CERN	GGUS
	dCache	Common GLUE1 and GLUE2 definitions GLUE 2.0 definitions	Unknown	Paul Millar	support@dcacheNOSPAMPLEASE.org
	DPM	dpm-listspaces Details	se-dpm service-srm2.2	DPM community	dpm-users-forum@cernNOSPAMPLEASE.ch
	LFC	lcg-info-provider-lfc	glite-lfc-provider	LFC developers	GGUS
	FTS	glue2-publisher	Unknown	FTS developers	GGUS
	StoRM	storm-dynamic-info-provider	Unknown	Elisabeth Ronchieri	storm-support@listsNOSPAMPLEASE.infn.it
All	-	glite-info-provider-service	glie-info-provider-service-*	Stephen Burke (bug fixes only, best effort)	GGUS
Cloud	OpenStack	cloud-info-provider-service python-novaclient (EPEL)	cloud-info-provider-service	Alvaro Lopez Garcia	fedcloud-tf@mailmanNOSPAMPLEASE.egi.eu
	OpenNebula	cloud-info-provider-service	cloud-info-provider-service	Boris Parak	fedcloud-tf@mailmanNOSPAMPLEASE.egi.eu

• (*) CREAM: The following YAIM functions are also used by the CREAM Information Providers:
  • config_cream_gip: GLUE 1.3 static configuration affecting GLUECluster, GlueSubCluster, GlueCE, GlueVOView and GlueCESEBind objects. This creates static LDIF files: static-file-Cluster.ldif, static-file-CE.ldif and static-file-CESEBind.ldif.
  • config_cream_gip_glue2: GLUE 2.0 static configuration affecting GLUE2ComputingService, GLUE2Endpoint, GLUE2ComputingManager, GLUE2ComputingShare, GLUE2ExecutionEnvironment, GLUE2Benchmark and GLUE2ToStorageService. This creates static LDIF files: ComputingService.ldif, ComputingEndpoint.ldif, ComputingManager.ldif, ComputingShare.ldif, ExecutionEnvironment.ldif, Benchmark.ldif and ToStorageService.ldif. This function also configures the dynamic part for GLUE2Endpoint.
  • config_cream_gip_info_dynamic: Dynamic plugin configuration for the batch systems affecting GLUECE/GLUE2ComputingManager and GLUE2ComputingShare objects. This function calls the batch system specific providers.
  • config_cream_gip_scheduler_plugin: Dynamic plugin configuration for the GLUECE/!GLUE2ComputingShare objects to calculate response times and free slots.
  • config_cream_gip_software_plugin: GlueHostApplicationSoftwareRunTimeEnvironment/GLUE2ApplicationEnvironment objects.

GLUE 2.0 Validation

Note that the validation documented in the sections below was carried out in 2013 and has not been updated since then in most cases. It could be information providers have been upgraded and are now GLUE 2 compliant. A more detailed and continuous activity has been carried out for Storage Services

In order to validate the published GLUE 2.0 information, a detailed review of the GLUE 2 LDAP tree published by the different services has been done. The glue-validator tool has also been run against the services to check whether they are properly implementing the EGI profile for GLUE 2.0 available in http://go.egi.eu/glue2-profile. This has been done looking at the EMI 3 testbed (querying emi3rc-sl6-bdii.cern.ch) and looking at production services.

For CREAM, DPM and StoRM, an LDIF template has been provided as well to support middleware developers in writing correct GLUE 2 information.

Detailed reports per service are listed below:

General

ARC

• Testbed host: piff.hep.lu.se
• Command: glue-validator -H piff.hep.lu.se -p 2135 -b GLUE2DomainID=urn:ad:NIIF_Testbed,o=glue -v 2
• Tracked in: Mail thread with Florido Paganelli

Affected GLUE2 attribute	Description of the problem	Comments
GLUE2ServiceAdminDomainForeignKey	UNDEFINEDVALUE is published instead of the correct domain	GGUS:107907 was expecting ARC developers to fix the problem but tickets have been created for every ARC site. i.e GGUS:107985

Most errors and warnings are due to mandatory and recommended attributes missing.

Argus

• Testbed host: emitestbed30.cnaf.infn.it
• Command: glue-validator -H emitestbed30.cnaf.infn.it -p 2170 -b o=glue -v 2
• Tracked in: GGUS:92422

Affected GLUE2 attribute	Description of the problem	Comments
GLUE2EndpointURL	Wrong URL type: http://localhost:8152/authz	Bug in the Information Service provider BUG:100822
GLUE2PolicyUserDomainForeignKey	Not published and it is recommended	The missing GLUE2PolicyUserDomainForeignKey is OK in this case - Argus is unusual because the endpoints aren't externally accessible so there are no associated VOs

CREAM

Check the CREAM GLUE 2 template for more details.

dCache

• Not tested.

DPM

Check the DPM GLUE 2 template for more details.

FTS

• Testbed host: emi2rc-sl5-fts.cern.ch
• Command: glue-validator -H emi2rc-sl5-fts.cern.ch -p 2170 -b o=glue -v 2
• Tracked in: GGUS:92451

The following table summarises issues found while validating site publication:

LB

See WMS (Both services deployed together under the same machine in the testbed)

LFC

• Testbed host: emi2rc-sl6-lfc.cern.ch
• Command: glue-validator -g egi-glue2 -H emi2rc-sl6-lfc.cern.ch  -p 2170 -b o=glue -s egi-profile -n -v 2
• Tracked in: (similar issues as in DPM)

Messaging

The following table summarises issues found while validating site publication:

Affected site	Description of the problem	Tracked in	Comments
CERN-PROD	Missing GLUE2EndpointImplementationName	GGUS:93301

MyProxy

• Testbed host: emitb-myproxy.civ.zcu.cz
• Command: glue-validator -H emitb-myproxy.civ.zcu.cz -p 2170 -b o=glue -v 2
• Tracked in: GGUS:92424

StoRM

Check the StoRM GLUE 2 template for more details.

VOMS

• Testbed host: emitestbed27.cnaf.infn.it
• Command: glue-validator -H emitestbed27.cnaf.infn.it  -p 2170 -b o=glue -v 2
• Tracked in: None

The following table summarises issues found while validating site publication:

Affected site	Description of the problem	Tracked in	Comments
CERN-PROD	Wrong syntax in GLUE2EndpointStartTime	GGUS:93298	Fixed in EMI 2 and EMI 3
	Missing GLUE2EndpointImplementationName, GLUE2ServiceCapability, GLUE2EndpointCapability

WMS

• Testbed host: wms008.cnaf.infn.it
• Command: glue-validator -H wms008.cnaf.infn.it -p 2170 -b o=glue -v 2
• Tracked in: GGUS:93196