<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 2, 2018 at 3:28 AM, Harald Jensås <span dir="ltr"><<a href="mailto:hjensas@redhat.com" target="_blank">hjensas@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Requesting: <br>
Feuture Freeze Exception request for Routed Spine and Leaf Deployment<br>
<br>
Blueprints:<br>
<a href="https://blueprints.launchpad.net/tripleo/+spec/tripleo-routed-networks-
ironic-inspector" rel="noreferrer" target="_blank">https://blueprints.launchpad.<wbr>net/tripleo/+spec/tripleo-<wbr>routed-networks-<br>
ironic-inspector</a><br>
<a href="https://blueprints.launchpad.net/tripleo/+spec/tripleo-routed-networks-" rel="noreferrer" target="_blank">https://blueprints.launchpad.<wbr>net/tripleo/+spec/tripleo-<wbr>routed-networks-</a><br>
deployment<br>
<br>
All external dependencies for Routed Spine and Leaf Deployement have<br>
finally landed. (Except puppet module changes.)<br>
<br>
<br>
Pros<br>
====<br>
<br>
This delivers a feature that has been requested since the Kilo release.<br>
It makes TripleO more viable in large deployments as well as in edge<br>
use cases where openstack services are not deployed in one datacenter.<br>
<br>
The core piece in this is the neutron segments service_plugin. This has<br>
been around since newton. Most of the instack-undercloud patches were<br>
first proposed during ocata.<br>
<br>
The major change is in the undercloud. In tripleo-heat-templates we<br>
need just a small change to ensure we get ip addresses allocated from<br>
neutron when segments service plug-in is enabled in neutron. The<br>
overcloud configuration stays the same, we already do have users<br>
deploying routed networks in the isolated networks using composable<br>
networks so we know it works.<br>
<br>
<br>
Risks<br>
=====<br>
<br>
I see little risk introducing a regression to current functionality<br>
with these changes. The major part of the undercloud patches has been<br>
around for a long time and passing CI.<br>
<br>
The format of undercloud.conf is changed, options are deprecated and<br>
new options are added to enable multiple control plane subnets/l2-<br>
segments to be defined. All options are properly deprectated, so<br>
using a configuration file from pike will still work.<br>
<br>
<br>
<br>
==============================<wbr>=======<br>
The list of patches that need to land<br>
==============================<wbr>=======<br>
<br>
instack-undercloud<br>
------------------<br>
<br>
* Tripleo routed networks ironic inspector, and Undercloud<br>
<a href="https://review.openstack.org/#/c/437544/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/437544/</a><br>
* Move ctlplane network/subnet setup to python<br>
<a href="https://review.openstack.org/533364" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533364</a><br>
* Update config to use per network groups<br>
<a href="https://review.openstack.org/533365" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533365</a><br>
* Update validations to validate all subnets<br>
<a href="https://review.openstack.org/533366" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533366</a><br>
* Add support for multiple inspection subnets<br>
<a href="https://review.openstack.org/533367" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533367</a><br>
* Create static routes for remote subnets<br>
<a href="https://review.openstack.org/533368" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533368</a><br>
* Add per subnet network cidr nat rules<br>
<a href="https://review.openstack.org/533369" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533369</a><br>
* Add per subnet masquerading<br>
<a href="https://review.openstack.org/533370" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>533370</a><br>
* Install and enable neutron baremetal mech plugin<br>
<a href="https://review.openstack.org/537830" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>537830</a><br>
<br>
tripleo-heat-templates<br>
----------------------<br>
<br>
* Add subnet property to ctlplane network for server resources<br>
<a href="https://review.openstack.org/473817" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>473817</a> <br>
<br>
tripleo-docs<br>
------------<br>
<br>
* Documentation - TripleO routed-spine-and-leaf<br>
<a href="https://review.openstack.org/#/c/539939/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/539939/</a> <br>
<br>
puppet-neutron<br>
--------------<br>
<br>
* Add networking-baremetal ml2 plug-in<br>
<a href="https://review.openstack.org/537826" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>537826</a> <br>
* Add networking-baremetal - ironic-neutron-agent<br>
<a href="https://review.openstack.org/539405" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>539405</a><br>
<span class="gmail-HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br></div><div>I'm a bit concerned by the delay of this request. Feature freeze request deadline was 10 days ago:</div><div><a href="https://releases.openstack.org/queens/schedule.html#q-ff">https://releases.openstack.org/queens/schedule.html#q-ff</a></div><div><br></div><div>We're now in the process on producing a release candidate. The amount of code that needs to land to have the feature completed isn't small but it looks like well tested and you seems pretty confident.</div></div>I'm not sure what to vote on this one tbh because yeah the use-case is super important, and we know how Queens release is important to us. But at the same time there is a risk to introduce problems, and delay the potentially delay the release and after the delivery of other features...</div><div class="gmail_extra"><br></div><div class="gmail_extra">I guess I'm ok as long as all patches pass ALL CI jobs without exception and are carefully tested and reviewed.</div><div class="gmail_extra"><br>Thanks,</div><div class="gmail_extra">-- <br><div class="gmail_signature"><div dir="ltr">Emilien Macchi<br></div></div>
</div></div>