Unable to add/remove pool members upon failure of F5 agent in HA deployment

[mattgreene]

Agent Version

1.0.12 rc3

Operating System

Not specified

OpenStack Release

Kilo

Description

Attempting to create Pools, Members & VIP using 1 agent and manage them using other agents.

Steps:
Stop 2 agents (1 & 2); ensure agent 3 is running
Create Pool
Start agents 1 & 2; stop Agent 3
Add member & Assign VIP

Results:
Pool creation was successful.
Could not add or remove Members; Could not assign VIP; Could not delete Pool.

Deployment

Three OpenStack controllers in HA, each with one F5 agent managing a single BIG-IP appliance

[jputrino]

comments provided for #80:

• in one real private cloud /public cloud case , no end user will have only one stand alone network controller , it must be Cluster Controller .
• as LBaaS public cloud service , the service can't stop working just because one LBaaS agent down
• the design binding pool to one special agent-host is not support multi-agent solution , need re-design the whole multi-agent architecture
• rabbit messsage queues are mirrored , but lack of lock/unlock method , need to design one way to sync between all the LBaaS agents