[openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

[melanie witt]

Hi everyone,

We have an issue [1] in python-novaclient 2.32.0 where it's not working with 
rackspace cloud.

It's caused by a commit [2] that changed the default requested compute API 
version from "latest" to "client supported latest", a specific version. We have 
some logic in the discover_version method that does comparisons between a 
user-specified version and the server version. For rackspace, we get a "null" 
server version because the version list API isn't exposed. The discover_version 
falls back on compute API 2.0 when requested version is "latest" and server 
version is "null" but raises an error when requested version is 
"user-specified" and server version is "null". So more work is needed there to 
handle cases where version API isn't exposed.

Should we revert [2] for now? Any other thoughts?

Thanks,
-melanie (irc: melwitt)

[1] https://bugs.launchpad.net/python-novaclient/+bug/1508244
[2] https://review.openstack.org/#/c/230024/



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

[Alex Xu]

Looks like we use API_MAX_VERSION and DEFAULT_OS_COMPUTE_API_VERSION with
wrong way. This isn't broken with rackspace only, this broken novaclient
runing with nova legacy v2 api(legacy v2 api's behavior is no version
exposed).

API_MAX_VERSION is the max version of client supported, currently it should
be '2.5'

DEFAULT_OS_COMPUTE_API_VERSION is the default value of CLI option of
'--os-compute-api-version', ti should be '2.latest' which means let CLI to
negotiate with server side choice most recently version.

Not sure whether we need revert, but at least a new fix should come after
that.

Thanks
Alex

2015-10-21 7:52 GMT+08:00 melanie witt :

> Hi everyone,
>
> We have an issue [1] in python-novaclient 2.32.0 where it's not working
> with rackspace cloud.
>
> It's caused by a commit [2] that changed the default requested compute API
> version from "latest" to "client supported latest", a specific version. We
> have some logic in the discover_version method that does comparisons
> between a user-specified version and the server version. For rackspace, we
> get a "null" server version because the version list API isn't exposed. The
> discover_version falls back on compute API 2.0 when requested version is
> "latest" and server version is "null" but raises an error when requested
> version is "user-specified" and server version is "null". So more work is
> needed there to handle cases where version API isn't exposed.
>
> Should we revert [2] for now? Any other thoughts?
>
> Thanks,
> -melanie (irc: melwitt)
>
> [1] https://bugs.launchpad.net/python-novaclient/+bug/1508244
> [2] https://review.openstack.org/#/c/230024/
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

[Alex Xu]

I just work out a patch quickly for fixing this,
https://review.openstack.org/237850

2015-10-21 10:08 GMT+08:00 Alex Xu :

> Looks like we use API_MAX_VERSION and DEFAULT_OS_COMPUTE_API_VERSION with
> wrong way. This isn't broken with rackspace only, this broken novaclient
> runing with nova legacy v2 api(legacy v2 api's behavior is no version
> exposed).
>
> API_MAX_VERSION is the max version of client supported, currently it
> should be '2.5'
>
> DEFAULT_OS_COMPUTE_API_VERSION is the default value of CLI option of
> '--os-compute-api-version', ti should be '2.latest' which means let CLI to
> negotiate with server side choice most recently version.
>
> Not sure whether we need revert, but at least a new fix should come after
> that.
>
> Thanks
> Alex
>
> 2015-10-21 7:52 GMT+08:00 melanie witt :
>
>> Hi everyone,
>>
>> We have an issue [1] in python-novaclient 2.32.0 where it's not working
>> with rackspace cloud.
>>
>> It's caused by a commit [2] that changed the default requested compute
>> API version from "latest" to "client supported latest", a specific version.
>> We have some logic in the discover_version method that does comparisons
>> between a user-specified version and the server version. For rackspace, we
>> get a "null" server version because the version list API isn't exposed. The
>> discover_version falls back on compute API 2.0 when requested version is
>> "latest" and server version is "null" but raises an error when requested
>> version is "user-specified" and server version is "null". So more work is
>> needed there to handle cases where version API isn't exposed.
>>
>> Should we revert [2] for now? Any other thoughts?
>>
>> Thanks,
>> -melanie (irc: melwitt)
>>
>> [1] https://bugs.launchpad.net/python-novaclient/+bug/1508244
>> [2] https://review.openstack.org/#/c/230024/
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev