Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "GGUS:OSG Topology Interface FAQ"

From EGIWiki
Jump to navigation Jump to search
Line 12: Line 12:
The interface is based on a PHP script “CheckSiteData_OIM”.This script retrieves the data from OIM DB using a dedicated URL provided by OIM DB API. The GGUS site data database is a BMC Remedy form called “Grid:RespUnitData”.
The interface is based on a PHP script “CheckSiteData_OIM”.This script retrieves the data from OIM DB using a dedicated URL provided by OIM DB API. The GGUS site data database is a BMC Remedy form called “Grid:RespUnitData”.
===Registration===
===Registration===
For retrieving data from OIM DB the certificate of the calling host has to be registered.
For retrieving data from OIM DB the certificate of the calling host has to be registered. OIM stores a list of DNs who can access GOC services. For example, OIM has the following record
for GGUS: "GGUS Contacts Reader" /C=DE/O=GermanGrid/OU=FZK/CN=prod-ars.ggus.eu
In case of changing the host or the certificate the OIM administrators have to be informed for updating the registration accordingly.
In case of changing the host or the certificate the OIM administrators have to be informed for updating the registration accordingly.
===Work flows===
===Work flows===

Revision as of 16:02, 23 March 2012

GGUS-logo.jpg


GGUS wiki / GGUS FAQ / GGUS Documentation / GGUS Helpdesk


FAQ for the Interface between GGUS and OIM

Updated
2011-10-12

Purpose

This document describes the OIM–GGUS interface. The OIM–GGUS interface is used for synchronizing the GGUS database for site data with the OIM DB.

Tools, Applications, Systems

The interface is based on a PHP script “CheckSiteData_OIM”.This script retrieves the data from OIM DB using a dedicated URL provided by OIM DB API. The GGUS site data database is a BMC Remedy form called “Grid:RespUnitData”.

Registration

For retrieving data from OIM DB the certificate of the calling host has to be registered. OIM stores a list of DNs who can access GOC services. For example, OIM has the following record for GGUS: "GGUS Contacts Reader" /C=DE/O=GermanGrid/OU=FZK/CN=prod-ars.ggus.eu In case of changing the host or the certificate the OIM administrators have to be informed for updating the registration accordingly.

Work flows

The CheckSiteData script is triggered by a cron job. It is executed every night. The script retrieves the complete dataset from OIM DB. The dump from OIM DB is checked for not being empty and having the typical “result” string inside. In case of failure the execution of the script is stopped and the data from the previous update is kept. Additionally GGUS keeps a local copy of the data on GGUS server for a quick restore in case of loosing data. OIM DB data is imported into local GGUS site data database. New sites in OIM DB are added to the GGUS database automatically. Updates on OIM DB site data are pushed to the GGUS site data database by modifying existing data sets. Removed sites are flagged and deleted by a cron job from GGUS database. The OIM DB site ID is used as primary key for the synchronization process. Attributes covered by the synchronization process are:

  • Contact Email,
  • Alarm Email,
  • Tier Level,
  • ROC and
  • Certification Status.

All updates in GGUS form “Grid:RespUnitData” are done using SOAP web services.

What if I have questions which are not dealt with by this FAQ?

Open a GGUS ticket

indicating that it should be directed at the GGUS team.

Search