This FeatureBackport BZ is about bringing this patchset in OSP 13: https://review.opendev.org/#/q/branch:master+topic:bp/tripleo-routed-networks-templates+(status:open+OR+status:merged) Moving back status as patches are only on master and stein/15 for now
To recap, this was about backporting routed provider networks for ctlplane + network isolation networks, implying (but probably not limited to): tripleo-heat-templates: https://review.opendev.org/#/q/topic:bp/tripleo-routed-networks-templates+(status:open+OR+status:merged) heat: https://review.opendev.org/568960 https://review.opendev.org/567206 https://review.opendev.org/567207 https://review.opendev.org/569053 https://review.opendev.org/568961 neutron: https://review.opendev.org/573896 https://review.opendev.org/570405 https://review.opendev.org/573897 https://review.opendev.org/523972 Implying API and DB changes etc Taking into account that we have mechanisms in place to handle Spine&Leaf/DCN deployments in 13 without this feature: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/spine_leaf_networking https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/deploying_distributed_compute_nodes_to_edge_sites I am closing this bug CANTFIX One important step to think about later is how to handle these 13 deployments in later versions like 16, that support routed networks. Should they still be supported the same way, or should we plan some migration to routed networks deployments (or both)?
While this bug originated as a clone of bug #1671811 there was a bit of confusion between dataplane routed networks support [0] and allowing Director/overcloud networks to be routed networks - controlplane scope, basically a backport request of [1] With recent comments like comment 23 having a lot of details on [1] backport I renamed title to clear confusion. So: * this BZ summarizes backport possibility of controlplane/overcloud networks being routed networks - this will not happen and OSP 13 deployments will continue to use separate L3 networks as describe in Spine&Leaf guide for 13 [2] * OSP 15 and newer (so 16) supports routed networks for the controlplane/overcloud networks [3]. Installation guides have been updated to reflect that (check the 16 equivalent versions of [2]) * you can use dataplane routed networks on this type of deployment, feature is enabled in Director for OSP 13 z9 and newer * testing validation will be tracked in OSP 16 [1] and OSP 13 [4] separate bugs I hope this clears things a bit, feel free to ask if anything is not clear yet! [0] https://docs.openstack.org/neutron/pike/admin/config-routed-networks.html [1] https://bugzilla.redhat.com/show_bug.cgi?id=1671811 [2] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/spine_leaf_networking/index - DCN install guide is also worth a read at https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html-single/deploying_distributed_compute_nodes_to_edge_sites/index [3] https://bugzilla.redhat.com/show_bug.cgi?id=1601576 [4] https://bugzilla.redhat.com/show_bug.cgi?id=1808502