Thanks ever so much to all for the helpful + enlightening feedback.
It *sounds* like folks have said, "Yes, put it in GOC-DB, it should
auto-propagate" (IOW there's nothing more we need to do to put a new
Site-BDII into production)
Although others have pointed out: the auto-propagate appears to have
broken - around, what, Feb 2018??
RAL-LCG2 still lists the OLD Site-BDII in its info, not the new.
root@lcgui02> ldapsearch -x -H ldap://lcgbdii.gridpp.rl.ac.uk:2170 -b o=grid > /tmp/r; wc /tmp/r
916595 1733664 37427712 /tmp/r
root@lcgui02> grep -c lcgbdii02.phy.bris.ac.uk /tmp/r
9
root@lcgui02> grep -c lcgbdii.phy.bris.ac.uk /tmp/r
0
Other than ticketing RAL-LCG2 (#138461) (there's been no action on it)
anything we can do? We want to retire the old Site-BDII & its old VM-host!
So this is a Site-BDII (with a different name; several have said "just
setup a DNS alias of the new Site-BDII with the old name!"), but what if
someone had tried to put a new CE or SE, PerfSONAR node, or what have you,
into production (= put it in the GOC-DB) & discovered, their new Service
Node just wasn't being found in The Information System.... because the
Top-BDII are not refreshing info from GOC-DB?
Guess that hasn't happened, but it could, right? (I think / maybe)
########################################################################
To unsubscribe from the LCG-ROLLOUT list, click the following link:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=LCG-ROLLOUT&A=1
|