[openstack-dev] Final decision on scope of v3 API ?

Day, Phil philip.day at hp.com
Fri Jul 26 12:25:18 UTC 2013

Hi Folks,

Finally got around to looking at some of the things I've added to the V2 api and wanted to move to V3 - and I'm confused about what is and isn't going to be moved from being an extension.  For example:

-          I added the extended_floating_ip extension to allow an floating IP to be assigned to a specific fixed IP (needed for multi nic set-ups),   and was assuming this would move into the main floating_ip extension, but there isn't one.   Looking at the etherpad (https://etherpad.openstack.org/NovaV3ExtensionPortWorkList ) its listed as "Probably not porting (but need to confirm)".   I see that fixedips.py and ips.py have already been ported - so does this mean that we are doing network APIs in V3 or Not, and how do we get that final decision made ?

-          The API to list scheduler hints I was thinking about merging into the scheduler_hints extension, but that is tagged as "move to core", but its also been already ported to a v3 pluggin.   Does this mean its not now going into core ?  (keypairs & console_output are in the same state BTW)

I'm not knocking all the great work that's been done on the V3 API - just a tad confused about what the end state by Havana 3 (which I assume is when the V3 API gets frozen) is meant to be ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130726/d0e9cd17/attachment.html>

More information about the OpenStack-dev mailing list