Testbed Support for GridPP member institutes [mailto:TB-
> [log in to unmask]] On Behalf Of Stephen Jones said:
> We ran "glite-ce-disable-submission" at the start of the GOCDB downtime,
> which has the effect of changing the published value to "Draining". Once the
> system was newly rebuilt (i.e. once it boots) the database reverts to the
> "glite-ce-enable-submission"
> state, and publishing automatically reverts to Production (with no help from
> us), even though it is still in GOCDB downtime!
OK, but then presumably it is actually (supposed to be) working? The downtime is after all just an indicative estimate of when the system may be down, it should be common that services come back before the scheduled end time.
> Notes on this: First, as there are two sources to advertise the state of the CE
> (i.e. via BDII and/or GOCDB), then there is the chance of conflict. Second, this
> implies that it would be best to assume that one of these is canonical. And
> third, as the GOCDB is the only one which is fully in our control, then that
> what is recorded there should be the canonical status of the CE. The other
> choice, to make the BDII canonical, is not the best thing because it flip/flops
> automatically as described above. So, in short, trust the GOCDB downtimes.
As things stand that's basically not possible: the GOC DB is only used for monitoring, everything else uses the BDII. But since the content of the site BDII is completely under the site's control that shouldn't be a problem.
Stephen
--
Scanned by iCritical.
|