Cannot send traffic to VIP on global namespace, but can on the VIP network's dhcp namespace

[Brandon Logan]

When a VIP is created on a network it cannot be reached through teh global namespace, it can be reached through that network's dhcp network namespace.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Change abandoned by Brandon Logan (<email address hidden>) on branch: master
Review: https://review.openstack.org/185244
Reason: Abandoning in favor of another review

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/205313
Committed: https://git.openstack.org/cgit/openstack/octavia/commit/?id=c2bdb48419238a7a40c16a70be8acfac76b9d46e
Submitter: Jenkins
Branch: master

commit c2bdb48419238a7a40c16a70be8acfac76b9d46e
Author: Brandon Logan <email address hidden>
Date: Wed Jul 22 21:31:23 2015 -0500

    Decouple amp driver from network using new models

    The amphora driver's post_vip_plug method required network specific information
    about the amphora to complete implementations. It was not accepting anything
    other than a loadbalancer object. Now it takes a dictionary of
    AmphoraNetworkConfig objects that is keyed of amphora id. Each instance
    contains network specific information required to set up the correct routing
    on the amphora.

    This patch sets up the routing correctly to solve the vip blackholing issue but
    only for the ssh_driver. The argument has only been added to the post_vip_plug
    method of the rest_api_driver but will need to be updated to handle this new
    information and to also fix the vip blackholing problems.

    Change-Id: I17ce89b6c050a2a36e0a802920e2dedb063f615b
    Closes-Bug: #1453951