Changing the Site BDII
Moving the Site BDII to another machine
Ensure the new Site BDII is working fine and publishing all the necessary site information
- See MAN01 for general information about how to configure a Site BDII. In particular, remember that the Site BDII configuration must include the BDII node itself.
Put the old Site BDII in scheduled downtime in the Configuration Database for a couple of hours
Register the new service in the Configuration Database by adding a new Service Endpoint:
- select
Site BDII
inService Type
field - fill in at least the hostname
- select
Y
for production and monitoring,N
for beta service field
- select
Properly modify the
GIIS URL
field with the newSITE-BDII ldap URL
- Note that the site name in the GIIS URL is case-sensitive
Mark the old Site BDII as not production and turn off its monitoring
Top BDIIs updates their sites list every hour so the new Site BDII should be published in less than an hour; instead Nagios updates the monitored hosts every 3 hours
When the new Site BDII is appeared on Nagios and the old one is disappeared, turn off the old Site BDII and remove it from the Configuration Database
Turning off a Site BDII co-hosted with other services
Stop and remove the service
service bdii stop yum remove glite-BDII glite-yaim-bdii
Delete some info-providers and ldif file (
/opt/glite/etc/gip/ldif/stub-site.ldif
,/opt/glite/etc/gip/site-urls.conf
,/opt/glite/etc/gip/provider/glite-info-provider-site
,/opt/glite/etc/gip/provider/glite-info-provider-service-bdii-site-wrapper
,/opt/glite/etc/gip/ldif/glite-info-site.ldif
)Reconfigure with yaim without specifying the BDII_site profile