<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Apr 23, 2013 at 6:22 PM, 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 04/23/2013 07:34 PM, Doug Hellmann wrote:<br>
><br>
><br>
><br>
> On Mon, Apr 22, 2013 at 10:33 AM, Christopher Yeoh <<a href="mailto:cyeoh@au1.ibm.com">cyeoh@au1.ibm.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:cyeoh@au1.ibm.com">cyeoh@au1.ibm.com</a>>> wrote:<br>
><br>
>     Hi Russell,<br>
><br>
>     The following are the blueprints I've created based on the Nova V3 API<br>
>     discussions. As requested I've split them into multiple blueprints to<br>
>     make working out when we've actually finished parts of the V3 API work<br>
>     easier.<br>
><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/nova-v3-api-filter" target="_blank">https://blueprints.launchpad.net/nova/+spec/nova-v3-api-filter</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-cleanup-misc" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-cleanup-misc</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-core-as-extensions" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-core-as-extensions</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-expected-errors" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-expected-errors</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-extension-versioning" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-extension-versioning</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-inconsistencies" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-inconsistencies</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-return-codes" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-return-codes</a><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-multi-status-support" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-multi-status-support</a><br>
><br>
>     The following is the blueprint for the new API Extension framework<br>
><br>
>     <a href="https://blueprints.launchpad.net/nova/+spec/v3-api-extension-framework" target="_blank">https://blueprints.launchpad.net/nova/+spec/v3-api-extension-framework</a><br>
><br>
>     There is an initial WIP patch for the barebones bits of the framework<br>
>     here:<br>
><br>
>     <a href="https://review.openstack.org/#/c/27276/" target="_blank">https://review.openstack.org/#/c/27276/</a><br>
><br>
>     Regards,<br>
><br>
>     Chris<br>
><br>
><br>
> If there are plans to build a new API anyway, would it make sense to<br>
> look at Pecan/WSME for nova at the same time as the other projects that<br>
> were going to investigate it during this release cycle?<br>
<br>
</div></div>I would like to see this seriously considered.  I also understand that<br>
it's more work and those driving the v3 API want to make sure it gets<br>
completed.  What do you guys think?  How much extra work would this be?<br>
 Would recruiting someone else to help make it manageable?<br></blockquote><div><br></div><div style>I'm available to at least offer advice about getting started, debugging, and code reviews. I should have some cycles for coding in a few weeks, too.</div>
<div style><br></div><div style>Doug</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></blockquote></div><br></div></div>