To dial in to the conference:
a. Dial +41227676000
b. Enter access code 0140768
OR click HERE
(Please specify your name & affiliation in the web-interface)
Example: http://gstat.gridops.org/gstat/CERN-PROD shows prod-lfc-atlas-local.cern.ch as being present in the BDII as a GlueServiceType: lcg-local-file-catalog but in the BDII this host is entered as node type LFC. Assuming it is a local LFC it should be a node type Local-LFC
While this test does produce in Error in gstat it is not critical in the sense of availability or for the CODs. i.e fix it in your own time.
To pass this test the following comparison is made.
|Service||BDII Service Type||GOCDB Node Type|
|Service||GlueServiceType||GOCDB Node Type|
In the case of the top_bdii there is an existing bug that can make this harder to resolve than it should be when you wish to publish a host alias as the service endpoint. BUG:41361. A fix for this trivial bug will pushed forward.
Following recent requests from a VO member directly to sites to install a particular extra piece of OS software then a recap of the policy is made.
VOs wishing to change their needs to be supported by a site should of course use the VO cards as the definitive reference.
Any change to the VO card by any VO which would trigger site action should be discussed first at the weekly EGEE/WLCG operations meeting.
The purpose is to allow other VOs to sites to raise concerns. Also a sensible time line can be decided for the sites to implement the changes.
It is clear that sites and resource centres should have been notified about this. Thanks to all sites who propped up services during this time. To my knowledge only one 3.0 lcg-CE actually died.
Apologies for not informing the sites, all jobs should now have exited and be clear of the system.