<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>Yes, but.... if stuff like dvr is the only viable replacement to nova-network in production, then learning the non representitive config of neutron with linuxbridge might be misleading/counter productive since ovs looks very very different.<br>
<br>
Kevin <strong>
<div><font face="Tahoma" color="#000000" size="2"> </font></div>
</strong>
<hr tabindex="-1">
<font face="Tahoma" size="2"><b>From:</b> Tom Fifield<br>
<b>Sent:</b> Wednesday, April 15, 2015 5:58:43 PM<br>
<b>To:</b> openstack-dev@lists.openstack.org<br>
<b>Subject:</b> Re: [openstack-dev] [Nova][Neutron] Linuxbridge as the default in DevStack [was: Status of the nova-network to Neutron migration work]<br>
</font><br>
<div></div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
<br>
On 14/04/15 23:36, Dean Troyer wrote:<br>
> On Tue, Apr 14, 2015 at 7:02 AM, Miguel Angel Ajo Pelayo<br>
> <mangelajo@redhat.com <<a href="mailto:mangelajo@redhat.com">mailto:mangelajo@redhat.com</a>>> wrote:<br>
><br>
> Why would operators install from devstack? that’s not going to be<br>
> the case.<br>
><br>
><br>
> If they do they need more help than we can give...<br>
<br>
So, ummm, there is actually a valid use case for ops on devstack: it's <br>
part of the learning process.<br>
<br>
In my rounds, I've had feedback from more than a few whose first <br>
OpenStack experience was to run up a devstack, so they could run ps <br>
aufx, brctl, iptables, etc just to see what was going on under the <br>
covers before moving on to something more 'proper'.<br>
<br>
<br>
While acknowledging that the primary purpose and audience of devstack is <br>
and should remain development and developers, if there is something we <br>
can do to improve the experience for those ops first-timers that doesn't <br>
have a huge impact on devs, it would be kinda nice.<br>
<br>
After all, one of the reasons this thread exists is because of problems <br>
with that ramp up process, no?<br>
<br>
<br>
><br>
> I believe we should have both LB & OVS well tested, if LB is a good<br>
> option for<br>
> some operators willing to migrate from nova, that’s great, let’s<br>
> make sure LB<br>
> is perfectly tested upstream.<br>
><br>
><br>
> +1<br>
><br>
> But by doing such change we can’t let OVS code rot and we would be<br>
> neglecting<br>
> a big customer base which is now making use of the openvswitch<br>
> mechanism.<br>
> (may be I’m miss understanding the scope of the change).<br>
><br>
><br>
> Changing DevStack's default doesn't remove anything OVS-related, nor<br>
> does it by itself remove any OVS jobs. It gives everyone who is happy<br>
> with nova-net (or more correctly doesn't think about it) a new default<br>
> that changes their experience the least for when nova-net disappears.<br>
><br>
> dt<br>
><br>
> --<br>
><br>
> Dean Troyer<br>
> dtroyer@gmail.com <<a href="mailto:dtroyer@gmail.com">mailto:dtroyer@gmail.com</a>><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font>
</body>
</html>