Add 2-leg configuration to Radware LBaaS Driver

[Jason Walker]

Radware's LBaaS driver currently supports a configuration where:

* the load balancer's VIP and PIP are identical and on the same network as the application servers
* the load balancer's HA backup (if used) is on a dedicated private network

The driver needs to support a new network configuration where:

* The load balancer's VIP is on its own network, open to NAT
* The load balancer's PIP and the HA backup (if used) are on the same network as the application servers

[OpenStack Infra (hudson-openstack)]

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

[Openstack Gerrit (openstack-gerrit)]

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

commit dc0e8ef62b4a91392af0307e0dc946e5ea28c54a
Author: jasonrad <email address hidden>
Date: Fri Jan 24 15:43:24 2014 -0500

    Add 2-leg configuration to Radware LBaaS Driver

    Radware's load balancer currently supports three network interfaces.
    Prior to this code addition, the configuration of those three
    interfaces was: one interface for management, one for high
    availability backup, and one for load balancing servers where the
    IP that the outside world sees (VIP) and the IP that the servers
    respond to (PIP) are identical.

    This change adds a new "2-legged" configuration: one interface for
    management, one interface for a VIP network, and one interface for the
    PIP and the high availability backup network.

    During VIP creation, the LBaaS driver detects if the incoming
    configuration is "2-legged" by comparing VIP and PIP networks. If they
    are different it allocates a new port on the PIP network in order to
    obtain an IP address for the PIP and names that port after its
    associated VIP ID. vDirect is then directed to create a load balancer
    with the PIP network also used as the HA network instead of using the
    vDirect container's default HA network configuration.

    During VIP deletion, the LBaas driver detects if a port for the PIP
    had been previously allocated by searching for and deleting port names
    that map to the VIP ID.

    Change-Id: Ifb93159c654f16958842f646c119479c465230f9
    Closes-Bug: 1268728