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:
GlueServiceEndpoint
published in the
Configuration Database or BDII (e.g. httpg://se.egi.eu:8444/srm/managerv2
)endpoint URL
must contain the Keystone v3 URL:
https://hostname:port/url/v3
endpoint URL
must contain the Keystone v3 URL:
https://hostname:port/url/v3
GlueServiceEndpoint
published in the BDIIIt 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.
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_GFAL_INFOSYS=egee-bdii.cnaf.infn.it:2170
$ lcg-infosites --vo ops ce | grep nikhef
5680 15 0 0 0 dissel.nikhef.nl:2119/jobmanager-pbs-infra
5680 17 1 1 0 gazon.nikhef.nl:8443/cream-pbs-infra
5680 15 0 0 0 juk.nikhef.nl:8443/cream-pbs-infra
5680 15 0 0 0 klomp.nikhef.nl:8443/cream-pbs-infra
5680 16 0 0 0 stremsel.nikhef.nl:8443/cream-pbs-infra
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://sbdii01.ncg.ingrid.pt:2170 \
-b "mds-vo-name=NCG-INGRID-PT,o=grid" \
'(&(objectClass=GlueService)(GlueServiceType=SRM))' \
GlueServiceEndpoint
dn: GlueServiceUniqueID=httpg://srm01.ncg.ingrid.pt:8444/srm/managerv2,Mds-Vo-name=NCG-INGRID-PT,o=grid
GlueServiceEndpoint: httpg://srm01.ncg.ingrid.pt:8444/srm/managerv2
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.
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).
Click on the EDIT button on the top right corner
fill in the Service URL field with the queue URL
Now the CREAM-CE service endpoint contains the required queue information.
Proceed in a similar way for the other services.
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.
This is the service summary page.
You need to click on the Add endpoint button for registering additional endpoint URLs.
Fill in the proper information and don’t forget to select the “Monitored” flag for making nagios to detect the new endpoint.
The summary page of the endpoint just added should look like this one.
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.
In order to properly monitor your webdav endpoint:
https://darkstorm.cnaf.infn.it:8443/webdav/ops
or
https://hepgrid11.ph.liv.ac.uk/dpm/ph.liv.ac.uk/home/ops/
GLUE2EndpointURL
(containing the used port and without the VO folder);https://darkstorm.cnaf.infn.it:8443/webdav
) is properly accessible.In order to properly monitor your gridftp endpoint for ops VO
globus-GRIDFTP
, with the “production” flag disabled;/dpm/ui.savba.sk/home/ops
(this is an example, set the proper path)The SURL value needed by the SRM monitoring probes is the following structure:
srm://<hostname>:<port>/srm/managerv2?SFN=<GlueSAPath or GlueVOInfoPath>
For example:
srm://ccsrm.in2p3.fr:8443/srm/managerv2?SFN=/pnfs/in2p3.fr/data/dteam/
GlueServiceEndpoint
URL information.GlueSAPath
information, use that. To retrieve it:$ ldapsearch -x -LLL -H <ldap://sbdii01.ncg.ingrid.pt:2170> \
-b "mds-vo-name=NCG-INGRID-PT,o=grid" \
'(&(objectClass=GlueSA)(GlueSAAccessControlBaseRule=VO:ops))' \
GlueSAPath GlueChunkKey
dn: GlueSALocalID=opsdisk:replica:online,GlueSEUniqueID=srm01.ncg.ingrid.pt,Mds-Vo-name=NCG-INGRID-PT,o=grid
GlueChunkKey: GlueSEUniqueID=srm01.ncg.ingrid.pt
GlueSAPath: /gstore/t2others/ops
GlueSAPath
information, use instead the
GlueVOInfoPath
one:$ ldapsearch -x -LLL -H <ldap://ntugrid5.phys.ntu.edu.tw:2170> \
-b "Mds-Vo-name=TW-NTU-HEP,o=grid" \
(&(objectClass=GlueVOInfo)(GlueVOInfoAccessControlBaseRule=VO:ops)) \
GlueVOInfoLocalID GlueChunkKey
dn: GlueVOInfoLocalID=ops:SRR,GlueSALocalID=SRR:SR:replica:*****,GlueSEUniqueID=ntugrid6.phys.ntu.edu.tw,Mds-Vo-name=TW-NTU-HEP,o=grid
GlueVOInfoPath: /dpm/phys.ntu.edu.tw/home/ops
GlueChunkKey: GlueSALocalID=SRR:SR:replica:*****
GlueChunkKey: GlueSEUniqueID=ntugrid6.phys.ntu.edu.tw
GlueVOInfoLocalID: ops:SRR
dn: GlueVOInfoLocalID=ops:data01,GlueSALocalID=data01:replica:online,GlueSEUniqueID=ntugrid6.phys.ntu.edu.tw,Mds-Vo-name=TW-NTU-HEP,o=grid
GlueVOInfoPath: /dpm/phys.ntu.edu.tw/home/ops
GlueChunkKey: GlueSALocalID=data01:replica:online
GlueChunkKey: GlueSEUniqueID=ntugrid6.phys.ntu.edu.tw
GlueVOInfoLocalID: ops:data01
srm://srm01.ncg.ingrid.pt:8444/srm/managerv2?SFN=/gstore/t2others/ops