make L3 agent handle multiple external networks

[dan wendlandt]

L3 agent does not properly handle multiple external networks. currently it just creates all gateway ports on a single bridge br-ex.

One model would be to automatically create a bridge for each external network, br-ex-<uuid> . The administrator could then attach the appropriate NIC (or virtual NIC for vlans) to that bridge. Such a fix should be very straightforward, unless I'm missing something.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/12309
Committed: http://github.com/openstack/quantum/commit/6606c6b288f6f92a9b8c865fcec01b841f9df7af
Submitter: Jenkins
Branch: master

commit 6606c6b288f6f92a9b8c865fcec01b841f9df7af
Author: Dan Wendlandt <email address hidden>
Date: Sun Sep 9 07:55:52 2012 -0700

    allow multiple l3-agents to run, each with one external gateway net

    bug #1042028

    Allows user to invoke L3-agent in a way that limits the agent to
    implementing only routers associated with a particular external network.
    Thus, it is possible to have a deployment with multiple external networks,
    since you can run one agent per external network.

    Also makes l3-agent pay attention to router admin_state_up field.

    Change-Id: Ia79d29301530718bc381c8e5a9d197de9452bce2