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 @

HOWTO07 How to change the Site-BDII

From EGIWiki
Revision as of 09:54, 14 May 2013 by Krakow (talk | contribs) (Protected "HOWTO07 How to change the Site-BDII" ([edit=sysop] (indefinite) [move=sysop] (indefinite)))
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Documentation menu: Home Manuals Procedures Training Other Contact For: VO managers Administrators

Change the Site-BDII

What have I to do to move the site-bdii on another machine?

  1. be sure the new site-bdii is working fine and publishing all the necessary site information
    1. 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.
  2. put the old site-bdii in scheduled downtime on GOC-DB for a couple of hours
  3. register the new service on GOC-DB by adding a new Service Endpoint:
    1. select "Site-BDII" in "Service Type" field
    2. fill in at least the hostname
    3. select "Y" for production and monitoring, "N" for beta service field
  4. properly modify the "Giis Url" field with the new SITE-BDII ldap url
    1. Note that the site name in the GIIS URL is case-sensitive
  5. mark the old site-bdii as not production and turn off its monitoring
  6. 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
  7. when the new site-bdii is appeared on nagios and the old one is disappeared, turn off the old site-bdi and remove it from GOC-DB

What if I have just to turn off a site-bdii cohosted with an lcg-CE:

  1. service bdii stop
  2. yum remove glite-BDII glite-yaim-bdii
  3. delete some info-providers and ldif file:

4.reconfigure with yaim without specifying the BDII_site profile