Comment 15 for bug 1375625

Like Assaf wrote it maybe is very specific situation but in my opinion that
L3 HA
implementation has huge amount of things which are working only with
Peacemaker.
There is lack of checks what is going one with connectivity to GW,
VRRP is not working completely - when router is rescheduled the FIP's are
left untouched.
In my opinion there is a huge amount of fixes to prepare to independent
that solution from
Peacemaker and this is one of the first steps to prepare L3 HA as a
production ready solution
without so huge dependency on Pacemaker.

On Mon, Mar 14, 2016 at 6:01 AM Assaf Muller <email address hidden> wrote:

> > not being able to rely on a robust HA solution
>
> I disagree.
>
> What's being described here is a very specific scenario. If the NIC to
> the tenant networks goes down, all of the routers lose connection to
> their VMs. Router replicas on other nodes will be become active, however
> the originals are still active, and still have connections to the
> external network via another NIC, duplicating FIPs. So this is a
> scenario of one NIC failing on one node, but not the other NIC on the
> same node. This scenario is not covered by L3 HA, while other scenarios
> are. Luckily, in most HA solutions (And any HA solution I've encountered
> myself) a tool like Pacemaker is used. In the RDO HA architecture, for
> example, Pacemaker is configured to fence a node with a dead NIC, which
> would resolve this specific error scenario. I don't see this as a high
> priority bug.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1375625
>
> Title:
> Problem in l3-agent tenant-network interface would cause split-brain
> in HA router
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/neutron/+bug/1375625/+subscriptions
>