<div dir="ltr"><div>Hello:<br><br></div><div>I agree with Slawek. Some options only introduce confusion and blur the results of the survey. For those in-tree drivers (LB, OVS, OVN, SRIOV), it doesn't make sense to have other than ML2-driver option. And for other drivers (Calico, Big Switch, OpenDaylight) it could be possible that the user is using it in the undelaying network, although that is not very common.</div><div><br></div><div>Regards.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 22, 2023 at 9:22 AM Slawek Kaplonski <<a href="mailto:skaplons@redhat.com">skaplons@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div><p style="margin:0px">Hi,</p>
<br><p style="margin:0px">Dnia poniedziałek, 21 sierpnia 2023 20:10:38 CEST Jeremy Stanley pisze:</p>
<p style="margin:0px">> On 2023-08-21 12:50:57 -0500 (-0500), Allison Price wrote:</p>
<p style="margin:0px">> [...]</p>
<p style="margin:0px">> > Even if something is not actively maintained upstream, it is often</p>
<p style="margin:0px">> > still put into production which is good knowledge for the</p>
<p style="margin:0px">> > community.</p>
<p style="margin:0px">> [...]</p>
<p style="margin:0px">> </p>
<p style="margin:0px">> For that matter, we tend to avoid removing options which were valid</p>
<p style="margin:0px">> for old releases, because many respondents are in fact running</p>
<p style="margin:0px">> (sometimes very) old releases.</p>
<p style="margin:0px">> -- </p>
<p style="margin:0px">> Jeremy Stanley</p>
<p style="margin:0px">> </p>
<br><p style="margin:0px">In this question there are actually mixed core plugins (like old Openvswitch) and ML2 plugin's mechanism drivers (like e.g. ML2-Openvswitch).</p>
<p style="margin:0px">Those old core plugins which we proposed to remove were removed from Neutron around version (2015.0.0 and 7.0.0 - I don't even remember what OpenStack version it was then).</p>
<p style="margin:0px">Currently we think that this may be confusing for people as we have seen pretty many people choosing it (Openvswitch 43% and ML2-Openvswitch 46% for example in 2022 survey) but I really doubt that 43% of responders are still using Neutron 2015.0.0 so they are really using old Openvswitch core plugin.</p>
<p style="margin:0px">And it's similar for other old core plugins which don't exists anymore for long time and have "duplicated" answers as ML2 driver in the same question.</p>
<br><p style="margin:0px">For us the best would be to have 2 separate questions related to that:</p>
<p style="margin:0px">1. What <strong>core</strong> <strong>plugin </strong>are You using?</p>
<p style="margin:0px">2. (Optional) If You choose <strong>ML2</strong> in previous question, what mechanism drivers are You using?</p>
<br><p style="margin:0px">And then in 1. we could keep all those very old and not existing core plugins like Openvswitch or Linuxbridge and in the second question have all the "ML2 - ...." answers.</p>
<p style="margin:0px">But I'm not sure if we can add yet another Neutron related question to the survey so that's why we though it will be better to not confuse people with very old core plugins and current ML2 drivers for the same backend technology.</p>
<br><p style="margin:0px">-- </p>
<p style="margin:0px">Slawek Kaplonski</p>
<p style="margin:0px">Principal Software Engineer</p>
<p style="margin:0px">Red Hat</p>
</div>
</blockquote></div>