<div dir="ltr">During the installation guide renovation process, we originally intended to support one path (neutron with Open vSwitch and tenant/external networks) given the imminent deprecation of nova-network. However, the latter didn't happen, so we kept the nova-network path and agreed to limit future development efforts to the neutron path.<div><br></div><div>The two different paths continue to cause confusion, particularly with the basic environment (host and network) requirements. Since I began working with OpenStack around the Havana release, neutron seems to generate the most frustration, particularly due to general lack of current, concise documentation and inexperience with Linux networking. Along came the networking guide that illustrates a variety of different deployment scenarios including the simple to understand and deploy provider networks with Linux bridge scenario that closely mimics nova-network. This scenario isn't new... just not widely known or understood until the documentation appeared for it.</div><div><br></div><div>I'm not privy to all of the discussions, but long story short, a variety of people think this scenario presents a viable alternative to nova-network for new installations and insist that we include it in the installation guide. However, given the issues with two paths, three will only increase confusion. Trying to retain two paths, we can't replace neutron with Open vSwitch and tenant/external networks with provider networks because the latter doesn't support self-service networking, a significant feature of cloud computing. So, I agree with replacing nova-network with the similar provider networks with Linux bridge scenario. It also makes sense to replace the existing neutron with Open vSwitch configuration with Linux bridge to flatten the learning curve with self-service networking and to provide better consistency between the two paths.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jul 15, 2015 at 6:31 AM, Anne Gentle <span dir="ltr"><<a href="mailto:annegentle@justwriteclick.com" target="_blank">annegentle@justwriteclick.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Tue, Jul 14, 2015 at 10:56 PM, Tom Fifield <span dir="ltr"><<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
We never did get a clear answer as to what the thinking is around<br>
dropping this option our users want from the install guide? As<br>
previously mentioned, it's damn simple to keep in and continues to work<br>
well, so difficult to understand.<br>
<br>
Perhaps the position has changed to one of keeping this useful option?<br>
<br>
<br></blockquote><div><br></div></span><div>From a Technical Committee standpoint, we thought a third option of the provider networks with Linux Bridge was a good way forward. So three networking options in the install guide:</div><div><br></div><div>Legacy nova-network</div><div>Provider networks with Linux Bridge</div><div>Provider networks with OVS</div><div><br></div><div>Then, point to the Networking Guide for additional configurations.</div><div><br></div><div>What does the team think?</div><div>Anne</div><div><div class="h5"><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Regards,<br>
<br>
<br>
Tom<br>
<div><div><br>
On 02/07/15 23:32, Tom Fifield wrote:<br>
> Hi Mark,<br>
><br>
> Welcome to a random discussion on the docs list! It seems like Matt K<br>
> and yourself might have had a chat at the neutron midcycle regarding the<br>
> install guide?<br>
><br>
> Regards,<br>
><br>
><br>
> Tom<br>
><br>
> On 02/07/15 23:27, Matt Kassawara wrote:<br>
>> Ask Mark McClain.<br>
>><br>
>> On Thu, Jul 2, 2015 at 9:04 AM, Tom Fifield <<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a><br>
>> <mailto:<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>>> wrote:<br>
>><br>
>> On 02/07/15 22:50, Matt Kassawara wrote:<br>
>> > With provider networks using the Linux bridge agent, neutron reaches the<br>
>> > simplicity of nova-network. Also, the installation guide will continue<br>
>> > to use the two-host architecture.<br>
>><br>
>> Close, but not quite :) Anyway, as noted - the question is why something<br>
>> our users want is being dropped, when it's damn simple to keep in and<br>
>> continues to work well?<br>
>><br>
>> > On Tue, Jun 30, 2015 at 11:03 PM, Tom Fifield <<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a> <mailto:<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>><br>
>> > <mailto:<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a> <mailto:<a href="mailto:tom@openstack.org" target="_blank">tom@openstack.org</a>>>> wrote:<br>
>> ><br>
>> > On 30/06/15 21:37, Karin Levenstein wrote:<br>
>> > > Guide architecture change for Liberty<br>
>> > > =====<br>
>> > > At the Neutron meetup that Matt attended last week, there was discussion<br>
>> > > about dropping nova-net and standardizing Neutron on Linux bridge rather<br>
>> > > than OVS.<br>
>> > > The plan that came out of the meeting: changing networking architecture<br>
>> > > from nova-net/Neutron OVS to: provider networking (connect VMs to<br>
>> > > network) with Linux Bridge; standard tenant network w/ Linux bridge and<br>
>> > > not OVS. All distros will have to support this.<br>
>> > > This will not be addressed in the install guide until the RST conversion<br>
>> > > is complete.<br>
>> > > ACTION: Matt to add this information to install guide spec so that it<br>
>> > > can be captured in the planning for Liberty.<br>
>> ><br>
>> > Is there further discussion available around dropping a<br>
>> > simple-to-implement, commonly used and upstream-supported network<br>
>> > deployment model (nova-network)?<br>
>> ><br>
>> ><br>
>> ><br>
>> > Regards,<br>
>> ><br>
>> ><br>
>> > Tom<br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > OpenStack-docs mailing list<br>
>> > <a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a>><br>
>> > <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
>> <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a>>><br>
>> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
>> ><br>
>> ><br>
>><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-docs mailing list<br>
> <a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
><br>
<br>
<br>
_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org" target="_blank">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
</div></div></blockquote></div></div></div><span class="HOEnZb"><font color="#888888"><br><br clear="all"><div><br></div>-- <br><div><div dir="ltr"><div>Anne Gentle</div><div>Rackspace</div><div>Principal Engineer</div><div><a href="http://www.justwriteclick.com" target="_blank">www.justwriteclick.com</a></div></div></div>
</font></span></div></div>
</blockquote></div><br></div>