Comment 28 for bug 1491317

Reviewed: https://review.openstack.org/533850
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=de9b39ed2c4423cfb1ea8b3b92f2b0b40e9c9d62
Submitter: Zuul
Branch: master

commit de9b39ed2c4423cfb1ea8b3b92f2b0b40e9c9d62
Author: ZhaoBo <email address hidden>
Date: Thu May 31 16:49:18 2018 +0800

    [agent side] L3 agent side Floating IP port forwarding

    This patch contains the l3 agent extension and agent part code.
    This patch introduce a new l3 agent extension named "port_forwarding",
    to process the binding of the port forwarding resources, manage its own
    floatingip configuration on router interface and floatingip status.
    Currrently, we support all Neutron Router reference implementations.

    This extension uses the period router sync task and PortForwarding OVO
    rpc.

    * The main idea about this new extension is using the generic router sync
      rpc to maintain the host port forwarding resources,
    * For a single port forwarding create/update/delete, process it one by one
      in smaller scope for forbidding refresh the iptables with a larger
      scope frequently.

    Partially-Implements: blueprint port-forwarding
    Partial-Bug: #1491317
    Change-Id: Ic56e67d428f6177099c285a9d1bccabc1e710f2b