[RFE] Allow operator control of "on-link" routes for subnets in the same Neutron network
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Wishlist
|
Kevin Benton |
Bug Description
When adding multiple subnets on a single network the dhcp agent will set dhcp-options to advertise "on-link"
A couple of use cases where these on-link/link-local routes are undesirable:
a) When using Ironic for baremetal provisioning the baremetal nodes might be on a different L2 broadcast segment with a DHCP-relay.
b) In a Spine-Leaf deployed Openstack, a pattern is to use identical VLAN id's for provider networks in each leaf. Same VLAN id, but different L2 domain and different IP subnets.
IMO, creating these routes are a bit opinionated. If we don't create them by default, the operator/end-user is fully able to create them if they are desired on a per-subnet basis. But since we decided these "should" be there, the operator loose the ability to control this.
Changed in neutron: | |
assignee: | nobody → Harald Jensås (harald-jensas) |
status: | New → In Progress |
Changed in neutron: | |
assignee: | Harald Jensås (harald-jensas) → nobody |
summary: |
- Allow the end user control of "on-link" routes for subnets in the same + Allow operator control of "on-link" routes for subnets in the same Neutron network |
summary: |
- Allow operator control of "on-link" routes for subnets in the same + [RFE] Allow operator control of "on-link" routes for subnets in the same Neutron network |
tags: | added: l3-ipam-dhcp rfe |
Changed in neutron: | |
assignee: | nobody → Harald Jensås (harald-jensas) |
status: | New → In Progress |
Changed in neutron: | |
assignee: | Kevin Benton (kevinbenton) → Brian Haley (brian-haley) |
Changed in neutron: | |
assignee: | Brian Haley (brian-haley) → Kevin Benton (kevinbenton) |
Fix proposed in review:
https:/ /review. openstack. org/#/c/ 438171/