Adam Harwell 96cce3ed74 Fix amp failover where failover already failed ... If a failover ran on an amphora and was unsuccessful and reverted, it would mark the amp status "DELETED" and un-busy the health record. It would then be picked up on the next failover check, start failing over, and break early since it appeared to be "unallocated". Also, housekeeping can now clean up expired amphora records based on the amphora's updated_at time instead of the health record's time, which means the records won't be immediately cleaned up anymore after they go through failover flows. Change-Id: I848b7fc69b977fcb39f8a07e2ea5fc7bd37b5c7a		2018-06-05 14:10:00 -07:00
..
__init__.py	Adds a process to generate key flow documentation	2016-08-10 21:39:38 +00:00
coding-checks.sh	Support pylint	2017-10-16 09:32:41 +08:00
create_flow_docs.py	Fix amp failover where failover already failed	2018-06-05 14:10:00 -07:00
flow-list.txt	Allow PUT to /pools/<id>/members to batch update members	2017-09-20 18:14:53 -07:00
misc-sanity-checks.sh	Setup translation for octavia	2016-12-15 00:48:02 +00:00
pkcs7_to_pem.py	Add support for PKCS7 bundles and encrypted keys	2016-10-05 19:51:51 -07:00