[RFE] Add the ability to create lb vip and member with network_id
Bug #1465758 reported by
Brandon Logan
This bug affects 4 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Doug Wiegley |
Bug Description
For large deployments that use cells and provider networks, it may not make sense to only allow a user to specify the subnet in which to allocate a port because nova scheduling may not be able to allocate a port on the specified subnet. Specifying a subnet would create a conflict with that, especially when it comes to capacity management.
Allowing network_id to be specified, in addition to subnet_id, will give flexibility to deployers who only want to allow allocation by network_id.
tags: | added: lbaas rfe |
description: | updated |
tags: |
added: rfe-approved removed: rfe |
Changed in neutron: | |
importance: | Undecided → Wishlist |
Changed in neutron: | |
milestone: | none → mitaka-1 |
Changed in neutron: | |
status: | Expired → Confirmed |
Changed in neutron: | |
status: | New → Triaged |
milestone: | none → newton-1 |
Changed in neutron: | |
assignee: | nobody → Doug Wiegley (dougwig) |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
Changed in neutron: | |
milestone: | newton-2 → newton-3 |
tags: | added: rfe-approved |
summary: |
- Add the ability to create lb vip and member with network_id + [RFE] Add the ability to create lb vip and member with network_id |
Changed in neutron: | |
milestone: | newton-3 → newton-rc1 |
To post a comment you must log in.
Assuming the new fields are optional, go for it.