hi all,
the other action point from last monday's grid-overleg: why are downtime notifications sent only a day before they actually occur?
The short answer is: this is exactly as specified. If you read
https://edms.cern.ch/file/829986/0.1/EGEE-downtime-notification-procedure.pd... which in turn refers to https://edms.cern.ch/file/829986/0.1/EGEE-intervention-procedures.pdf then most downtime notifications fall into category C: − Send broadcast 1 day in advance − Broadcast targets: all ROCs, affected VOs, all production sites in the related ROC so the actual broadcast happens only 1 day in advance !!
of course , this makes the downtime notification procedure kinda useless for us. As far as I see there are 2 options:
1) create an email list infrastructure-announce@biggrid.nl to which all BigGrid downtime notifications must be sent (on penalty of death-by-tickling or something like that)
2) the GOCDB, where all site downtimes are entered, luckily has a programming interface where you can retrieve all downtimes for a particular site after a particular date: we could thus create a cron job that periodically checks the GOCDB and broadcasts any messages , as appropriate. For example, if I do curl --cert $X509_USER_PROXY --key $X509_USER_PROXY --CApath $X509_CERT_DIR -k \
"https://goc.gridops.org/gocdbpi/public/?method=get_downtime&topentity=SA..." I get <?xml version="1.0"?> <ROOT> <DOWNTIME ID="45205458" CLASSIFICATION="SCHEDULED"> <HOSTNAME>srm.grid.sara.nl</HOSTNAME> <SEVERITY>OUTAGE</SEVERITY> <DESCRIPTION> The tape backend will be down for the whole day due to maintenance. srm.grid.sara.nl will be up but data on tape cannot be accessed. </DESCRIPTION> <START_DATE>1251705600</START_DATE> <END_DATE>1251748800</END_DATE> <FORMATED_START_DATE>2009-08-31 08:00</FORMATED_START_DATE> <FORMATED_END_DATE>2009-08-31 20:00</FORMATED_END_DATE> </DOWNTIME> <DOWNTIME ID="43305437" CLASSIFICATION="SCHEDULED"> <HOSTNAME>ce.gina.sara.nl</HOSTNAME> <SEVERITY>OUTAGE</SEVERITY> <DESCRIPTION> maintenance to broken switch hardware </DESCRIPTION> <START_DATE>1251190800</START_DATE> <END_DATE>1251219600</END_DATE> <FORMATED_START_DATE>2009-08-25 09:00</FORMATED_START_DATE> <FORMATED_END_DATE>2009-08-25 17:00</FORMATED_END_DATE> </DOWNTIME> </ROOT>
so this API _does_ work... now we need a little XML scripting magic to turn it into a broadcast email - any takers? The upside of this approach is that we have a single entry point for downtimes , i.e. less chance of errors.
share and enjoy,
JJK