Administration of the site BDII

From Gridkaschool
Revision as of 17:20, 28 December 2012 by Pweber (talk | contribs) (Created page with "The main configuration file next to site-info.def is the file site-urls.conf located in directory /opt/glite/etc/gip/. All site resources have to be listed in this central confi…")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The main configuration file next to site-info.def is the file site-urls.conf located in directory /opt/glite/etc/gip/.

All site resources have to be listed in this central configuration file. Insert for each service a line:

UNIQUENAME ldap://<hostname of resource>:2170/mds-vo-name=resource,o=grid

e.g.:

SBDII ldap://gks-0-146.gridka.de:2170/mds-vo-name=resource,o=grid
WMS   ldap://gks-0-127.gridka.de:2170/mds-vo-name=resource,o=grid
BDII  ldap://gks-0-145.gridka.de:2170/mds-vo-name=resource,o=grid

To ensure that the file site-urls.conf contains the correct information after a yaim configuration all site services should be listed in the site-info.def. To this end, in the site-info.def you have to

  • add the UNIQUENAME to the BDII_REGIONS list
  • specify the ldap contact string in the BDII_UNIQUENAME_URL
BDII_REGIONS="WMS"
BDII_WMS_URL="ldap://gks-0-127.gridka.de:2170/mds-vo-name=resource,o=grid"

GIP configuration

GIP is the grid information provider. All interesting data is located in directory /opt/glite/etc/gip/. Here you find few files and three directories

[root@gks-0-243 ~]# ll /opt/glite/etc/gip/
-rw-r--r-- 1 root root  287 Aug 29 15:34 glite-info-generic.conf
drwxr-xr-x 2 root root 4096 Aug 30 10:18 ldif
drwxr-xr-x 2 root root 4096 Nov 15  2007 plugin
drwxr-xr-x 2 root root 4096 Aug 30 10:18 provider
-rw-r--r-- 1 root root  204 Aug 30 21:34 site-urls.conf

In the ldif directory static information can be found. In the plugin and provider directory scripts are located which gather information about the site.

The static information for the site BDII stored in /opt/glite/etc/gip/ldif/glite-info-site.ldif can be changed without running the yaim configuration. At this moment the content of this file should look similar to

dn: GlueSiteUniqueID=GKSXYZ,mds-vo-name=resource,o=grid
objectClass: GlueTop
objectClass: GlueSite
objectClass: GlueKey
objectClass: GlueSchemaVersion
GlueSiteUniqueID: GKSXYZ
GlueSiteName: GKSXYZ
GlueSiteDescription: GridKa School - gLite Administration Course
GlueSiteEmailContact: mailto:root@localhost
GlueSiteUserSupportContact: mailto:root@localhost
GlueSiteSysAdminContact: mailto:root@localhost
GlueSiteSecurityContact: mailto:root@localhost
GlueSiteLocation: Karlsruhe, Germany
GlueSiteLatitude: 49.0963
GlueSiteLongitude: 8.4321
GlueSiteWeb: http://gridka-school.scc.kit.edu/
GlueSiteSponsor: none
GlueSiteOtherInfo: CONFIG=yaim
GlueSiteOtherInfo: GRID=GKS
GlueSiteOtherInfo: GRID=DECH
GlueForeignKey: GlueSiteUniqueID=GKSXYZ
GlueSchemaVersionMajor: 1
GlueSchemaVersionMinor: 3

In file /opt/glite/etc/gip/glite-info-generic.conf the settings for used directories and time limits can be found:

temp_dir = /opt/glite/var/tmp/gip
cache_dir = /opt/glite/var/cache/gip
lock_dir = /opt/glite/var/lock/gip
plugin_dir  = /opt/glite/etc/gip/plugin
static_dir =  /opt/glite/etc/gip/ldif
provider_dir = /opt/glite/etc/gip/provider
freshness = 60
cache_ttl = 300
response = 115
timeout = 150

Go back to gLite Administration Course and continue with the next service.