[RFE] Implement neutron routed networks support in Ironic
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
Wishlist
|
Harald Jensås | ||
networking-baremetal |
Fix Released
|
Wishlist
|
Harald Jensås |
Bug Description
In many cases, physical data center networks are architected with a differentiation between layers 2 and 3. Said another way, there are distinct L2 network segments which are only available to a subset of compute hosts. Routing allows traffic to cross these boundaries. These topologies are used to manage network resource capacity (IP addresses, broadcast domain size, ARP tables, etc.) to allow for large scale networks.
Operators from the Large Deployers Team (LDT) and others would like an operator-
More info can be found: https:/
and https:/
Ironic node should become L2 segment aware (we should know which L2 segments are available for particular node) to correctly pick subnet (ip address) when doing provisioning/
tags: | added: rfe |
Changed in ironic: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in ironic: | |
assignee: | nobody → Sam Betts (sambetts) |
tags: |
added: rfe-approved removed: rfe |
Changed in ironic: | |
status: | Confirmed → In Progress |
assignee: | Sam Betts (sambetts) → Harald Jensås (harald-jensas) |
Changed in ironic: | |
status: | In Progress → Fix Released |
Changed in networking-baremetal: | |
status: | New → Fix Released |
importance: | Undecided → Wishlist |
assignee: | nobody → Harald Jensås (harald-jensas) |
@Sam,
Please read the following exchange between hjensas and kevinbenton: http:// eavesdrop. openstack. org/irclogs/ %23openstack- neutron/ %23openstack- neutron. 2017-05- 24.log. html#t2017- 05-24T22: 42:12
On the Neutron side, what we need Ironic to give us is a host_id. We maintain a segments to hosts map in Neutron. So, if we get the host id, we can do the rest. No need to duplicate the mapping