Joshua M. Boniface f9b126a106 Make zkhandler accept failures more robustly ...

Most of these would silently fail if there was e.g. an issue with the ZK
connection. Instead, encase things in try blocks and handle the
exceptions in a more graceful way, returning None or False if
applicable. Except for locks, which should retry 5 times before
aborting.

2020-08-17 13:03:36 -04:00

..

__init__.py

Use consistent naming of components

2020-02-08 19:34:07 -05:00

CephInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

common.py

Clean up imports

2020-08-11 12:09:10 -04:00

Daemon.py

Use logger for debug output

2020-08-17 12:46:52 -04:00

DNSAggregatorInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

dnsmasq-zookeeper-leases.py

Use consistent naming of components

2020-02-08 19:34:07 -05:00

fencing.py

Tie fence timers to keepalive_interval

2020-08-15 12:38:03 -04:00

log.py

Use logger for debug output

2020-08-17 12:46:52 -04:00

MetadataAPIInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

NodeInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

VMConsoleWatcherInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

VMInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

VXNetworkInstance.py

Clean up imports

2020-08-11 12:09:10 -04:00

zkhandler.py

Make zkhandler accept failures more robustly

2020-08-17 13:03:36 -04:00