Remove constraint on network names
Bug #823841 reported by
Salvatore Orlando
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
Salvatore Orlando | ||
Bug Description
The db model currently contains a constraint that prevents two networks with the same name to be created for the same tenant. This has an impact on the API layer as well, as create network operations with the same network name for the same tenant will raise an error.
Unless there is a strong reason to keep this constraint, we should remove it.
Related branches
lp:~salvatore-orlando/neutron/quantum-api-alignment
- dan wendlandt: Approve
- Somik Behera: Approve (netstack-core)
- Tyler Smith: Approve
-
Diff: 1449 lines (+501/-259)21 files modifiedetc/quantum.conf (+1/-1)
quantum/api/__init__.py (+9/-3)
quantum/api/api_common.py (+9/-18)
quantum/api/attachments.py (+86/-0)
quantum/api/faults.py (+0/-17)
quantum/api/networks.py (+34/-43)
quantum/api/ports.py (+63/-84)
quantum/api/versions.py (+2/-2)
quantum/api/views/attachments.py (+37/-0)
quantum/api/views/networks.py (+9/-10)
quantum/api/views/ports.py (+6/-14)
quantum/cli.py (+11/-10)
quantum/client.py (+2/-5)
quantum/common/exceptions.py (+0/-10)
quantum/common/wsgi.py (+10/-4)
quantum/db/api.py (+8/-1)
quantum/db/models.py (+2/-1)
quantum/plugins/SamplePlugin.py (+2/-2)
tests/unit/test_api.py (+151/-15)
tests/unit/test_clientlib.py (+1/-1)
tests/unit/testlib_api.py (+58/-18)
| Changed in quantum: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Salvatore Orlando (salvatore-orlando) |
| Changed in quantum: | |
| status: | New → Fix Committed |
| Changed in quantum: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
