Open Stack

I think in the hopefully not too distant future we'll be able to make the v1_1 client handle both V2 and V2.1 (who knows. Maybe we can even rename it v2) - and that's what we should do because it will prove if we have full compatibility or not.

Right now the two things holding that back are the V3 -> V2.1 API  migration hasn't yet got to the point where the URLs include the tenant ID, and the URL still includes the "v3" tag - so the v3 client it the only easy way to exercise the v2.1 API in devstack.   For example I needed to do this to test the server group quota changes worked in devstack via V2.1 (I don't trust just getting the unit tests to pass).    To do that I had to get boot working and accepting hints, and add support for the limits API.   So in the short term it seemed worth pushing those kinds of things back in for now in case they are useful to others.   Its not a big overhead to fix the v3 API at the same time (its mostly copied or sub-classed code) until we can add v2.1 support via the v2 client.

Phil

> -----Original Message-----
> From: Matt Riedemann [mailto:mriedem at linux.vnet.ibm.com]
> Sent: 17 September 2014 15:59
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: [openstack-dev] [nova] are we going to remove the novaclient v3
> shell or what?
> 
> This has come up a couple of times in IRC now but the people that probably
> know the answer aren't available.
> 
> There are python-novaclient patches that are adding new CLIs to the v2
> (v1_1) and v3 shells, but now that we have the v2.1 API (v2 on v3) why do we
> still have a v3 shell in the client?  Are there plans to remove that?
> 
> I don't really care either way, but need to know for code reviews.
> 
> One example: [1]
> 
> [1] https://review.openstack.org/#/c/108942/
> 
> --
> 
> Thanks,
> 
> Matt Riedemann
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev