<div dir="ltr">Hi,<div><br></div><div>I agree that Option 1 would be best way to make the GBP API available to operators and to make forward progress with the API.</div><div><br></div><div>Regards,</div><div>-hemanth</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 6, 2014 at 5:04 PM, Ivar Lazzaro <span dir="ltr"><<a href="mailto:ivarlazzaro@gmail.com" target="_blank">ivarlazzaro@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 dir="ltr">Hi Pedro,<div><br></div><div>I agree that having as much users/operators as possible using the API is the winner option.</div>
<div>I think you should move this comment also in the main thread since it looks that the Subject has been accidentally modified.</div>
<div><br></div><div>Cheers,</div><div>Ivar.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Aug 7, 2014 at 1:28 AM, Pedro Marques <span dir="ltr"><<a href="mailto:pedro.r.marques@gmail.com" target="_blank">pedro.r.marques@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 style="word-wrap:break-word"><br><div><div>On Aug 6, 2014, at 3:56 PM, Armando M. <<a href="mailto:armamig@gmail.com" target="_blank">armamig@gmail.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">
On 6 August 2014 15:47, Kevin Benton <span dir="ltr"><<a href="mailto:blak111@gmail.com" target="_blank">blak111@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<p dir="ltr">I think we should merge it and just prefix the API for now with '/your_application_will_break_after_juno_if_you_use_this/' <br>
</p><div>
<div class="gmail_quote"></div></div></blockquote><div><br></div>And you make your call based and what pros and cons exactly, If I am ask?<div><br></div><div>Let me start:</div><div><br></div><div>Option 1:</div><div>
- pros</div>
<div> - immediate delivery vehicle for consumption by operators</div></div></div></div></blockquote><div><br></div><div>Since our collective goal is to maximize the benefits for OpenStack users/operators, that seems to be the winner.</div>
<br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> - cons</div><div> - code is burder from a number of standpoints (review, test, etc)</div></div></div></div></blockquote>
<div><br></div>Any piece of code is a burden.</div><div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div><br></div><div>Option 2:</div><div> - pros</div>
<div> - enable a small set of Illuminati to iterate faster</div></div></div></div></blockquote><div><br></div><div>This is probably not intentional from your part ,but your choice of words make it seem that you are deriding the efforts of the team behind this effort. While i may disagree technically here and there with their current design, it seems to me that the effort in question is rather broad based in terms of support (from multiple different organizations) and that the team has put a non trivial effort in making the effort public. I don't think we can characterize the team either as a "secret group" or a "small set".</div>
<div><br></div><div> Pedro.</div><br><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div> </div><div> - cons</div><div> - integration burden with other OpenStack projects (keystone, nova, neutron, etc)</div>
<div><br></div><div>Cheers,</div><div>
Armando</div></div></div></div>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
</blockquote></div><br></div><br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br></div></div>