L3: make use of namespaces by agent configurable

[dan wendlandt]

we have discussed making the use of namespaces configurable with the existing l3-agent.

this change would not be that hard to make, code-wise, but the tricky part is how to actually put check in place such that this gives you something useful. For example, if namespaces are not in use, presumably the l3-agent limit itself to managing a single quantum router? If that is the case, are there way to prevent multiple router's from being configured via the API? Or ways of running multiple l3-agents?

Any significant changes are obviously out of scope for Folsom, but I am putting this in folsom-rc1 to start to see if there's something simple we want to do for Folsom.

[dan wendlandt (danwent)]

gary, you mentioned this as something you're interested in. Please either assign it to RC1 if you're planning on tackling it for Folsom, or unassign yourself and it will float to grizzly.

[Gary Kotton (garyk)]

I'll take a look at this...

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/12002
Committed: http://github.com/openstack/quantum/commit/3c8b8ce1013c739f8ed34053dc36ab0705f05884
Submitter: Jenkins
Branch: master

commit 3c8b8ce1013c739f8ed34053dc36ab0705f05884
Author: Gary Kotton <email address hidden>
Date: Mon Aug 27 07:30:22 2012 -0400

    L3: make use of namespaces by agent configurable

    Fixes bug 1042104

    The fix follows the patch that was done on the DHCP agent to enable
    the user to configure the usage of namespaces. In the event that
    namspaces are disabled the agent is limited to running only one
    router. The agent needs to define the router_id that is supported.
    The process in this case is:
    1. create router
    2. start agent with router id

    Change-Id: I2a71dc009c5aea285ff9f903b3faa99b0c9f820f