Bug 1027210

+++ This bug was initially created as a clone of Bug #1026723 +++

The health servlet is a legacy interface that IMO should not be used at all,
marked obsolete and removed as soon as we can.

Please make the notification service use the formal supported API to pull
engine status.

This applies to both setup and hosted.

Thanks!

--- Additional comment from Sandro Bonazzola on 2013-11-06 04:24:11 EST ---

(In reply to Alon Bar-Lev from comment #0)
> Please make the notification service use the formal supported API to pull
> engine status.

 import ovirtsdk.api
 ovirtapi=ovirtsdk.api.API(
   url='https://sbonazzo.csb/api',
   username='admin@internal',
   password='****',
   ca_file='/etc/pki/ovirt-engine/ca.pem',
 )
 once connection is established (engine running), how may I know if DB is Up?

--- Additional comment from Alon Bar-Lev on 2013-11-06 04:35:27 EST ---

our application is not initialized if database connection is down... or do you suggest otherwise...?

# systemctl stop ovirt-engine
# systemctl stop postgresql
# systemctl start ovirt-engine
# curl -v -k https://admin%40internal:engine@localhost/api
# systemctl start postgresql
# curl -v -k https://admin%40internal:engine@localhost/api

BTW: I do not see our application recovering from database down anyway...