<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br>Hi.<br><br>Implementing API on Pecan is a subthread of unification of openstack components<br>activity.<br>In this context we have to do the job in any case.<br>
I totally agree with cases Roman Prykhodchenko described.<br>If we swap versions now we'll have this part of work done. At that moment, when<br>we'll need new API versions we'll have to implement just controllers, not whole<br>
WSGI application.<br>In addition, when v3 will be provided and v1 deleted whole API service will work<br>on Pecan.<br>It is still a question if v3 ever been required... So, seems wrong to delay<br>unification until v3.<br>
Finally, it will be difficult to implement v3 and migrate v2 to Pecan same time.<br><br><br>Regards.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Oleh Anufriiev.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">
<br></div><div class="gmail_quote"><div style="word-wrap:break-word"><div><blockquote type="cite"><div><div dir="ltr">This time, with content!<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 10, 2014 at 4:51 AM, Flavio Percoco <span dir="ltr"><<a href="mailto:flavio@redhat.com" target="_blank">flavio@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Greetings,<br>
<br>
More discussions around the adoption of Pecan.<br>
<br>
I'd like to know what is the feeling of other folks about migrating<br>
existing APIs to Pecan as opposed to waiting for a new API version as<br>
an excuse to migrate the API implementation to Pecan?<br>
<br>
We discussed this in one of the sessions at the summit, I'd like to<br>
get a final consensus on what the desired migration path is for the<br>
overall community.<br>
<br>
IIRC, Cinder has a working version of the API with Pecan but there's<br>
not a real motivation to release a new version of it that will use<br>
the new implementation. Am I right?<br>
<br>
Nova, instead, will start migrating some parts but not all of them and<br>
it'll happen as part of the API v3. AFAIU.<br>
<br>
Recently a new patch was proposed in glance[0] and it contains a base<br>
implementation for the existing API v2. I love that patch and the fact<br>
that Oleh Anufriiev is working on it. What worries me, is that the<br>
patch re-implements an existing API and I don't think we should just<br>
swap them.<br></blockquote><div><br></div><div>Yes, I'm a bit worried about just swapping in a new implementation, too, much as I think the approach using Pecan is superior to the way we initially went. At this time I don't see a really compelling reason to switch. It would be neat however if there are any people who actually want to run the Pecan implementation of the v2 API--if so it might be worth taking it on into upstream. But unless we actually think there is some future development in v2.0 that will be substantially eased by using Pecan I think we should probably not switch implementations until there is a major version bump.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Yes, we have tests (unit and functional) and that should be enough to<br>
make sure the new implementation works as the old one - Should it?<br>
Should it? - but...<br>
<br>
This most likely has to be evaluated in a per-project basis. But:<br>
<br>
- What are the thoughts of other folks on this matter?<br>
<br>
Cheers,<br>
FF<br>
<br>
[0] <a href="https://review.openstack.org/#/c/62911/" target="_blank">https://review.openstack.org/#<u></u>/c/62911/</a><span><font color="#888888"><br>
<br>
-- <br>
@flaper87<br>
Flavio Percoco<br>
</font></span><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>
_______________________________________________<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>
</div></blockquote></div><br></div></div><br></div>