<div dir="ltr">I agreed with Jay. Nova is one of the consumer of Neutron project, someone from Nova project should participate reviewing related blueprint in neutron project.<div><br></div><div>Richard</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Aug 6, 2014 at 8:28 PM, Jay Pipes <span dir="ltr"><<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.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="">On 08/06/2014 07:54 PM, Kevin Benton wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm curious, how would having Nova reviewers look at this have helped?<br>
</blockquote>
<br></div>
As I mentioned on a previous email, Nova is the pre-eminent consumer of Neutron's API.<br>
<br>
Best,<br>
-jay<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
On Wed, Aug 6, 2014 at 5:41 PM, Jay Pipes <<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a><br></div><div class="">
<mailto:<a href="mailto:jaypipes@gmail.com" target="_blank">jaypipes@gmail.com</a>>> wrote:<br>
<br>
On 08/06/2014 07:08 PM, CARVER, PAUL wrote:<br>
<br>
On Aug 6, 2014, at 2:01 PM, Mohammad Banikazemi <<a href="mailto:mb@us.ibm.com" target="_blank">mb@us.ibm.com</a><br></div>
<mailto:<a href="mailto:mb@us.ibm.com" target="_blank">mb@us.ibm.com</a>><mailto:<a href="mailto:mb@us." target="_blank"><u></u>mb@us.</a>__<a href="http://ibm.com" target="_blank">ibm.com</a><div><div class="h5">
<br>
<mailto:<a href="mailto:mb@us.ibm.com" target="_blank">mb@us.ibm.com</a>>>><br>
wrote:<br>
<br>
Yes, indeed.<br>
I do not want to be over dramatic but the discussion on the<br>
original "Group<br>
Based Policy and the way forward" thread is nothing short of<br>
heartbreaking.<br>
After months and months of discussions, three presentations<br>
at the past three<br>
summits, a design session at the last summit, and (most<br>
relevant to this<br>
thread) the approval of the spec, why are we talking about<br>
the merits of the<br>
work now?<br>
<br>
I understand if people think this is not a good idea or this<br>
is not a good<br>
time. What I do not understand is why these concerns were<br>
not raised clearly<br>
and openly earlier.<br>
<br>
<br>
I have to agree here. I'm not sure whether my organization needs<br>
GBP or not.<br>
It's certainly not our top priority for Neutron given a variety<br>
of other more<br>
important functional gaps. However, I saw their demo at the<br>
summit and it was<br>
clear that a lot of work had gone into it even before Icehouse.<br>
From the demo<br>
it was clearly a useful enhancement to Neutron even if it wasn't<br>
at the top<br>
of my priority list.<br>
<br>
For people to be asking to justify the "why" this far into the<br>
Juno cycle<br>
when the spec was approved and the code was demoed at the summit<br>
really<br>
brings the OpenStack process into question. It's one thing to<br>
discuss<br>
technical merits of contributions but it's totally different to<br>
pull the rug<br>
out from under a group of contributors at the last minute after<br>
such a long<br>
period of development, discussion, and demo.<br>
<br>
Seeing this sort of last minute rejection of a contribution<br>
after so much<br>
time has been invested in it could very easily have a chilling<br>
effect on<br>
contributors.<br>
<br>
<br>
I don't disagree with you, Paul.<br>
<br>
I blame myself for not paying the attention I should have to this<br>
earlier in the process.<br>
<br>
FWIW, I had a good conversation with Sumit and Kevin on<br>
#openstack-neutron this afternoon about this particular topic. We<br>
agree on some things; disagree on others.<br>
<br>
Bottom line, I go back to what I said in a previous email: the Nova<br>
and Neutron development teams need to do a much better job in being<br>
directly involved in each other's spec discussions and design<br>
conversations.<br>
<br>
Best,<br>
-jay<br>
<br>
<br></div></div>
______________________________<u></u>___________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.<u></u>__org<br>
<mailto:<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.<u></u>openstack.org</a>><br>
<a href="http://lists.openstack.org/__cgi-bin/mailman/listinfo/__openstack-dev" target="_blank">http://lists.openstack.org/__<u></u>cgi-bin/mailman/listinfo/__<u></u>openstack-dev</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a>><div class="">
<br>
<br>
<br>
<br>
<br>
--<br>
Kevin Benton<br>
<br>
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div>