Before Starting

• SL5 / 64bit installation according to the generic guidelines

Service installation

# wget http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
# rpm -ivh epel-release-5-4.noarch.rpm

# wget http://emisoft.web.cern.ch/emisoft/dist/EMI/1/sl5/x86_64/base/emi-release-1.0.0-1.sl5.noarch.rpm
# rpm -ivh emi-release-1.0.0-1.sl5.noarch.rpm

# yum install emi-bdii-site emi-bdii-top 

Service Configuration

• Using YAIM for service configuration (skeleton below):

# /opt/glite/yaim/bin/yaim -c -s siteinfo.def -n BDII_site -n BDII_top

• reconfigure endpoints for top-level (a required step for Testbed case, most likely not needed for official production sites of EGI, WLCG, ...)
  • STOP bdii ( # /etc/init.d/bdii stop ) ASAP(!) after YAIM finishes its job (otherwise you have production Grid in infosystem - you may have to clean manually caches in /var/lib/bdii/gip/ )
  • modify /etc/glite/glite-info-update-endpoints.conf disabling EGI and OSG information sources, enable manual instead, setting properly references to top-url files, eg:

[configuration]
EGI  = False
OSG = False
manual = True
manual_file = /etc/bdii/gip/top-urls.conf
output_file = /opt/glite/etc/gip/top-urls.conf
cache_dir = /var/cache/glite/glite-info-update-endpoints

• • specify endpoints for top-level BDII in top-urls.conf eg:

EMITB-CERN ldap://cvitbrc02.cern.ch:2170/mds-vo-name=cert-tbrc-cern,o=grid

• reconfigure endpoints for site-level BDII - edit /etc/bdii/gip/site-urls.conf file providing resource bdii endpoints, eg.:

EMIRCBDII  ldap://cvitbrc02.cern.ch:2170/mds-vo-name=resource,o=grid

• (re-)start bdii - and try to query (you may need to wait a moment - it may have to gather / refresh its data)

YAIM config (site-info.def) skeleton:

##
## site information
##
MY_DOMAIN=$(hostname -d)


SITE_NAME="cert-tb-xxx"
SITE_DESC="Certification Testbed XXX"

SITE_EMAIL="siteadmin@yoursite"
SITE_CRON_EMAIL=$SITE_EMAIL  # not yet used will appear in a later release
SITE_SUPPORT_EMAIL=$SITE_EMAIL
SITE_SECURITY_EMAIL=$SITE_EMAIL

SITE_LOC="Geneva, Switzerland"
SITE_LAT="46.20" # -90 to 90 degrees
SITE_LONG="6.1"  # -180 to 180 degrees
SITE_WEB="https://twiki.cern.ch/twiki/bin/view/EMI/TestBed"

SITE_OTHER_GRID="EGEE"
SITE_OTHER_EGEE_SERVICE="cert"
SITE_OTHER_EGEE_ROC="CERN"


##
## top BDII
##
BDII_HOST=`hostname -f`
#BDII_HTTP_URL="http://lcg-bdii-conf.cern.ch/bdii-conf/bdii.conf"             # yaim default
BDII_HTTP_URL="http://grid-deployment.web.cern.ch/grid-deployment/emi/bdii/emitb-rc-top"

#BDII_FCR="http://lcg-fcr.cern.ch:8083/fcr-data/exclude.ldif"           # yaim default
BDII_FCR="http://grid-deployment.web.cern.ch/grid-deployment/emi/bdii/emitb-rc-fcr.ldif"


#
# site BDII
# 
#
# BDII
# 

SITE_BDII_HOST=$BDII_HOST

# things below go to site-urls.conf - we use web editor for this, putting only BDII here
#BDII_REGIONS="BDII CE CREAMCE SE DPM LFC PX FTS CE2 FTS VOBOX"  - example
BDII_REGIONS="EMIRCBDII"
BDII_EMIRCBDII_URL="ldap://${SITE_BDII_HOST}:2170/mds-vo-name=resource,o=grid"

Service Testing

Basic test:

• check running daemons (see links and service reference card for details)

Other commands with simple operations tests on a BDII are documented in the tutorial information

Links

• BDII Core
• BDII Site
• BDII Top
• EMI gLite Information System

-- TomaszWolak - 11-Aug-2011