[User-committee] app dev on-boarding experience report
Sun, Yih Leong
yih.leong.sun at intel.com
Wed Jan 20 20:01:21 UTC 2016
Please note that there is two different api, one for Compute API and one for Neutron API.
http://developer.openstack.org/api-ref-compute-v2.1.html#os-security-groups-v2.1
/v2.1/{tenant_id}/os-security-groups
http://developer.openstack.org/api-ref-networking-v2-ext.html#security_groups
/v2.0/security-groups
-----Original Message-----
From: Tom Fifield [mailto:tom at openstack.org]
Sent: Sunday, January 17, 2016 8:53 PM
To: user-committee at lists.openstack.org
Subject: Re: [User-committee] app dev on-boarding experience report
On 16/01/16 00:48, Stefano Maffulli wrote:
> On 01/14/2016 02:29 PM, Bonell Manjarrez, Marcela wrote:
>> >So, what I noticed is that even using openstack or rackspace driver,
>> >the problem is in the same file, same line, same request:
>> >
>> >File
>> >"/usr/local/lib/python2.7/dist-packages/libcloud/compute/drivers/ope
>> >nstack.py", line 1769, in ex_list_security_groups
>> >self.connection.request('/os-security-groups').object)
>> >
>> >
>> >As you can see the request uses '/os-security-groups' and in the RAX
>> >documentation[1] the networking requests uses '/security-groups’
>> >that’s why libcloud fails, both drivers use the same request:
>> >self.connection.request('/os-security-groups').object)
> Yep, looks like a bug. Something must have changed at RAX for the
> security groups and nobody has updated libcloud...
Data: with a quick look at the code (see eg nova/tests/functional/api_sample_tests/test_security_groups.py ), and the docs @ http://developer.openstack.org/api-ref-compute-v2.1.html#os-security-groups-v2.1,
it seems libcloud is correct to use os-security-groups for the openstack driver.
Regards,
Tom
_______________________________________________
User-committee mailing list
User-committee at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
More information about the User-committee
mailing list