multiple external networks

[Simon]

I have multiple external networks, and therefore each l3-agent is running with a particular ext network ID.

When I create a lrouter, which is scheduled to be on one l3-agent randomly. If I set the ext-gw for that lrouter later on to be an external network different from the ext-net the l3-agent is on, the entire lrouter somehow goes down, both internal and external interfaces.

I would prefer to see:
1) the operation of putting the lrouter onto the "wrong" ext-net is disallowed;
2) or better, we can move the lrouter to the right l3-agent with the correct ext-net.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

commit b5092af696131e611e20f17c6b9aa4f321a854df
Author: Sylvain Afchain <email address hidden>
Date: Sat Nov 30 00:49:02 2013 +0100

    L3 Agent can handle many external networks

    With this patch a l3 agent can handle
    any networks by setting the neutron
    parameter external_network_bridge
    and gateway_external_network_id to
    empty.

    Related-Bug: #1234750
    Related-Bug: #1194350

    Change-Id: Id260a239df23951da730513f40cda490002effc3

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/havana
Review: https://review.openstack.org/68601

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/havana
Review: https://review.openstack.org/71825

[OpenStack Infra (hudson-openstack)]

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

commit 5f749768676e6739db1e01a03ddb7f3cb43d48f8
Author: Oleg Bondarev <email address hidden>
Date: Wed Oct 16 17:51:04 2013 +0400

    Reschedule router if new external gateway is on other network

    An L3 agent may be associated with just one external network.
    If router's new external gateway is on other network then the router
    needs to be rescheduled to the proper l3 agent

    Change-Id: Ia0ed924403137ac4578ca562b57988292c41c1fe
    Closes-Bug: #1234750

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/68601
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=9397d9aeeed4291a9a34f233c71f91ecded52664
Submitter: Jenkins
Branch: stable/havana

commit 9397d9aeeed4291a9a34f233c71f91ecded52664
Author: Sylvain Afchain <email address hidden>
Date: Sat Nov 30 00:49:02 2013 +0100

    L3 Agent can handle many external networks

    With this patch a l3 agent can handle
    any networks by setting the neutron
    parameter external_network_bridge
    and gateway_external_network_id to
    empty.

    cherry picked from commit b5092af696131e611e20f17c6b9aa4f321a854df

    Related-Bug: #1234750
    Related-Bug: #1194350
    Change-Id: Id260a239df23951da730513f40cda490002effc3