FIP namespace should not track connections for DVR

[Rajeev Grover]

With DVR, connections to external network using floating ips flow through the router namespace into the fip namespace and then to the external network. These connections are tracked in router namespace for filter and nating purpose. Currently these connections are also being tracked in the fip namespace because tracking is turned on by default. To avoid unnecessary consumption of resources tracking of such connections should be turned off in fip namespace.

[Carl Baldwin (carl-baldwin)]

This should be an easy fix. This could be a scaling problem if it is not fixed.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/116412

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/116412
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0985ef78d43ae7d910669c3ca968fd977f2ea2ae
Submitter: Jenkins
Branch: master

commit 0985ef78d43ae7d910669c3ca968fd977f2ea2ae
Author: rajeev <email address hidden>
Date: Fri Aug 22 18:54:46 2014 -0400

    Stop tracking connections in DVR FIP Namespace

    For DVR, connections to external network using floating IPs do not
    need to be tracked in FIP namespace because they are being
    already tracked in router namespace.
    This fix adds iptable rules to not track connections.

    Change-Id: I378039e311763d114860cb70ded7349d6580855a
    Closes-bug: #1360395