Adding service endpoints

Adding service endpoints information into Configuration Database

For monitoring purposes, each service endpoints registered into the Configuration Database, and having the flags production and monitored should include the endpoint URL information in order to be contacted by the corresponding service-specific nagios probe.

The information needed for service type are:

  • SRM: the value of the attribute GlueServiceEndpoint published in the Configuration Database or BDII (e.g. httpg://
  • Cloud:
    • org.openstack.nova: The endpoint URL must contain the Keystone v3 URL: https://hostname:port/url/v3
    • org.openstack.swift:The endpoint URL must contain the Keystone v3 URL: https://hostname:port/url/v3
    • for the host sending the records to the accounting repositority
  • Other service types: the value of the attribute GlueServiceEndpoint published in the BDII

It is also possible to register additional endpoints for every services, they will also be monitored if the “Monitored” flag is set.

For having more information about managing the Service endpoints in the Configuration Database, please consult the service endpoints documentation.

Retrieving the information

For retrieving the queue URL from the BDII, you can use the command lcg-infosites, to be executed from an UI. Be sure to query a production Top BDII: you can either use the one provided by your Operations Centre or choose one from the Configuration Database

For example:

$ export

$ lcg-infosites --vo ops ce | grep nikhef
  5680      15          0            0       0
  5680      17          1            1       0
  5680      15          0            0       0
  5680      15          0            0       0
  5680      16          0            0       0

In order to find the GlueServiceEndpoint URL of your SRM service, you can launch a LDAP query to your Site BDII (or directly to the SRM service):

$ ldapsearch -x -LLL -H ldap:// \
  -b "mds-vo-name=NCG-INGRID-PT,o=grid" \
  '(&(objectClass=GlueService)(GlueServiceType=SRM))' \

dn: GlueServiceUniqueID=httpg://,Mds-Vo-name=NCG-INGRID-PT,o=grid
GlueServiceEndpoint: httpg://

In a similar way, by just changing the value of GlueServiceType, you can retrieve the endpoint URLs of other services.

An alternative way for retrieving the GlueServiceEndpoint URL is using the GLUE2 information browser provided by VAPOR: select your NGI, then your site and hence the Storage service; click on the endpoint details button for finding the URL associated to the SRM interface.

Filling the information in

URLs information are completely missing

Editing the services information

  • Site overview

This is the home page regarding your site. You need to fill in the URL information.

Click on a service for displaying its page (e.g. the CREAM-CE).

Site overview

  • Editing a service

Click on the EDIT button on the top right corner

Service overview

  • Adding a Service URL

fill in the Service URL field with the queue URL

Service Edition

  • Reviewing the site

Now the CREAM-CE service endpoint contains the required queue information.

Proceed in a similar way for the other services.

Completed service overview

Additional endpoints information

In case you need to register an additional endpoint for a service, go on the service summary page and add the proper information. In the example below it is shown the case of a computing element.

  • Service summary page

This is the service summary page.

You need to click on the Add endpoint button for registering additional endpoint URLs.

Service summary page

  • Adding an endpoint

Fill in the proper information and don’t forget to select the “Monitored” flag for making nagios to detect the new endpoint.

Adding and endpoint

  • Reviewing the endpoint description

The summary page of the endpoint just added should look like this one.

Service endpoint page

  • Reviewing the service description

And this is the summary page of the service reporting the information about all its endpoints registered: the first one in the Grid Information section and the additional ones in the Service Endpoints section.

Service summary page



In order to properly monitor your webdav endpoint:

  • you should register a new service endpoint with the webdav service type, separated from the SRM one;
  • fill in the webdav URL containing also the VO ops folder, for example: or
    • it corresponds to the value of GLUE2 attribute GLUE2EndpointURL (containing the used port and without the VO folder);
  • verify that the webdav URL (for example: is properly accessible.


In order to properly monitor your gridftp endpoint for ops VO

  • register a new service endpoint, associating the storage element hostname to the service type globus-GRIDFTP, with the “production” flag disabled;
  • in the “Extension Properties” section of the service endpoint page, fill in the following fields:
    • Name: SE_PATH
    • Value: /dpm/ (this is an example, set the proper path)
  • check if the tests are OK (it might take some hours for detecting the new service endpoint) and then switch the production flag to “yes”

SURL value for SRM

The SURL value needed by the SRM monitoring probes is the following structure:

srm://<hostname>:<port>/srm/managerv2?SFN=<GlueSAPath or GlueVOInfoPath>

For example:


  • As explained in previous sections, you can retrieve the port number from the GlueServiceEndpoint URL information.
  • If your SE provides GlueSAPath information, use that. To retrieve it:
$ ldapsearch -x -LLL -H <ldap://> \
  -b "mds-vo-name=NCG-INGRID-PT,o=grid" \
  '(&(objectClass=GlueSA)(GlueSAAccessControlBaseRule=VO:ops))' \
  GlueSAPath GlueChunkKey

dn: GlueSALocalID=opsdisk:replica:online,,Mds-Vo-name=NCG-INGRID-PT,o=grid
GlueSAPath: /gstore/t2others/ops
  • if your SE doesn’t provide GlueSAPath information, use instead the GlueVOInfoPath one:
$ ldapsearch -x -LLL -H <ldap://> \
  -b "Mds-Vo-name=TW-NTU-HEP,o=grid" \
  (&(objectClass=GlueVOInfo)(GlueVOInfoAccessControlBaseRule=VO:ops)) \
  GlueVOInfoLocalID GlueChunkKey

dn: GlueVOInfoLocalID=ops:SRR,GlueSALocalID=SRR:SR:replica:*****,,Mds-Vo-name=TW-NTU-HEP,o=grid
GlueVOInfoPath: /dpm/
GlueChunkKey: GlueSALocalID=SRR:SR:replica:*****
GlueVOInfoLocalID: ops:SRR

dn: GlueVOInfoLocalID=ops:data01,GlueSALocalID=data01:replica:online,,Mds-Vo-name=TW-NTU-HEP,o=grid
GlueVOInfoPath: /dpm/
GlueChunkKey: GlueSALocalID=data01:replica:online
GlueVOInfoLocalID: ops:data01
  • Pay attention to use the storage path for the ops VO
  • On GOCDB, in the “Extension Properties” section of the SRM service endpoint page, fill in the following fields:
    • Name: SURL
    • Value: the actual SURL value, for example: srm://