Comment 14 for bug 1365473

You are correct Assaf.. but I am always am optimist... Let me rephrase what I wanted to say. The basic functionality of the server and agent is pretty far along. Currently the agent side can handle receving a router with distributed=True and ha=True, and it goes ahead and setups the router in the service node (snat node i.e it brings up the external gatway port (qg) and internal snat gateway (sg) in the correct namespaces. It also setups up the keepalive process to monitor them and configures them with the correct l3 information. My tetsting so far shows that it fails over correctly.
It can also handle the different combination of create router, set gateway, add interface, remove interface, repeat in different order, etc...

The server sid is obvisouly sending the correct information for the routers as well.

In other words, currently the two patches setup the router interfaces correctly and allow for the manipulation of the router, now weather or not the full system can correctly utilize the routers is a different story. For that, as you say, we need a few other fixes to line up.

We do need to test this on a full stack. internally I have been testing on a setup with three nodes (two service and one compute) but I agree with you that there needs to be a full stack test for it so we can make sure it works. Currently I am frankly focusing on making sure it did not break any of the current functionality with dvr and ha by themselves. In other workds "do no evil". We need to make sure this does not break any current functionality.

I will create the dependency. of the server patch on the agent patch as the agent patch can actually exist on its own, since it won't do anything with out the server patch allowing for the creation of a dvr/ha router.