<br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 10:43 AM, Russell Bryant <span dir="ltr"><<a href="mailto:rbryant@redhat.com" target="_blank">rbryant@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/04/2013 01:19 PM, Dan Wendlandt wrote:<br>
><br>
><br>
> On Mon, Mar 4, 2013 at 8:00 AM, Jay Pipes <<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a><br>
</div><div class="im">> <mailto:<a href="mailto:jaypipes@gmail.com">jaypipes@gmail.com</a>>> wrote:<br>
><br>
> On Mon, Mar 4, 2013 at 10:47 AM, Russell Bryant <<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:rbryant@redhat.com">rbryant@redhat.com</a>>> wrote:<br>
><br>
> One area that I<br>
> think could use some additional attention is the collaboration<br>
> between<br>
> Nova and Quantum. I would like to step up the effort to get to<br>
> where we<br>
> are no longer maintaining two networking stacks.<br>
><br>
><br>
> +10<br>
><br>
> Instead of focusing on the ability to entirely replace internal Nova<br>
> networking with Quantum, unfortunately feature development in<br>
> Quantum has been the focus over the last two release cycles.<br>
><br>
><br>
> I'm actually surprised to hear this comment. If you look at the 'high'<br>
> or 'critical' features for quantum in folsom or grizzly, reaching full<br>
> parity with nova use cases has been the highest priority.<br>
><br>
> Nova Parity In Folsom:<br>
> - IPAM<br>
> - L3 + floating IPs<br>
> - basic metadata<br>
><br>
> Nova Parity In Grizzly:<br>
> - security groups<br>
> - better metadata integration<br>
> - multi-host like L3 + dhcp model<br>
><br>
> The only thing I see as missing is a cloudpipe VPN equivalent, and to be<br>
> honest the reason for this is that no one seems very interested in using<br>
> this capability. It was targeted for Folsom, but no one showed up to<br>
> write any code. I've heard a few people coordinating on plans for<br>
> Havana for VPN, so achieving it seems more likely.<br>
<br>
</div></div>This progress is great. It seems like we should be considering making<br>
Quantum the default for Havana if the VPN functionality isn't widely<br>
used. What do you think?<br>
<br>
Also, what do you think of the idea of having some design summit time<br>
where we make sure that Nova and Quantum people can be in the same room<br>
at the same time? At a minimum, we could have one session on "Making<br>
Quantum the default in Nova". If there are more Nova<->Quantum<br>
integration topics, we could extend the time.<br></blockquote><div><br></div><div>I'm definitely in favor of this, and hopefully the Quantum PTL for havana will be as well :) </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
> Are there other key gaps you see? When I had talked with Vish about<br>
> this in the past, the model was to freeze nova-network to allow Quantum<br>
> to reach parity, and then push people away from nova-network toward<br>
> Quantum.<br>
<br>
</div>What you have listed already are all of the things I knew about.<br>
<br>
I'm not sure if freezing nova-network has really happened. There isn't<br>
big feature development going on, but there has certainly been an<br>
ongoing noticeable maintenance burden just supporting what we have. I'd<br>
like to kill that as soon as we can. I'm sure you wouldn't mind that<br>
either!<br></blockquote><div><br></div><div>Yup, on the same page there :)</div><div><br></div><div>Dan</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Russell Bryant<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>Dan Wendlandt <div>Nicira, Inc: <a href="http://www.nicira.com" target="_blank">www.nicira.com</a><br><div>twitter: danwendlandt<br>
~~~~~~~~~~~~~~~~~~~~~~~~~~~<br></div></div>