L3: make use of namespaces by agent configurable
Bug #1042104 reported by
dan wendlandt
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Gary Kotton |
Bug Description
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.
Changed in quantum: | |
status: | New → Confirmed |
Changed in quantum: | |
importance: | Undecided → Medium |
Changed in quantum: | |
milestone: | none → folsom-rc1 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | folsom-rc1 → 2012.2 |
tags: | added: folsom-backport-potential in-stable-folsom |
tags: | removed: in-stable-folsom |
tags: | removed: folsom-backport-potential |
To post a comment you must log in.
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.