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

Christopher Yeoh cbkyeoh at gmail.com
Fri Jul 26 13:13:36 UTC 2013

Hi Phil,

On Fri, Jul 26, 2013 at 9:55 PM, Day, Phil <philip.day at hp.com> wrote:

>  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 ?***
> *
 We're not meant to be porting anything that can be done via neutron or
only supports nova-network anyway. Someone who wants to use nova-network
will have to use the V2 api (and nova-network is meant to be going away
soon anyway). I think that means ips.py will stay, but fixedips will be
removed (fixed_ips was the first extension to be ported before we'd decided
what we were going to do).

-          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)

We hadn't managed to work out what was going to be core and what wasn't
before we'd ported most of the extensions so there is still some work going
on to move stuff in (and more importantly out) of core. The concept of
"core" is a bit different in V3 because everything is now a
"plugin/extension". Core is essentially just the hardcoded list of
extensions which are always loaded. We do have to do make some changes
where a plugin contains a mix of core and non-core functionality to
separate the two.

** **
> 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 ?****
> **

Yes, post Havana release we will have to start bumping the version numbers
when we make changes (and even then we are limited to what we can do). So
if anyone sees anything that doesn't look right, please yell :-)


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

More information about the OpenStack-dev mailing list