Open Stack

As Leong mentioned libcloud is not supporting Networking API (Neutron). My patched was locally (only for security groups), so it’s not a simple bug, libcloud need to migrate all their API call from nova-network to neutron... a complete driver refactoring for networking.


I looked in the libcloud JIRA about this, but they are not pushing any effort to migrate to neutron.
https://issues.apache.org/jira/browse/LIBCLOUD-519 


Thanks Stefano for the Shade draft.

Marcela Bonell.





On 1/20/16, 7:02 PM, "Sun, Yih Leong" <yih.leong.sun at intel.com> wrote:

>The libcloud is using compute driver which comply with the Compute API.
>http://developer.openstack.org/api-ref-compute-v2.1.html#os-security-groups-v2.1
>/v2.1/{tenant_id}/os-security-groups
>
>Rackspace Public Cloud no longer using Compute API to manage security groups. It uses Networking API now.
>http://developer.openstack.org/api-ref-networking-v2-ext.html#security_groups
>/v2.0/security-groups
>
>You can point libcloud to use OpenStack provider, but that is still pointing to Compute API. Not Networking API.
>Looks like Libcloud is not supporting Networking API yet but still using Compute API for network management (such as security groups).
>
>
>
>-----Original Message-----
>From: Stefano Maffulli [mailto:stefano at openstack.org] 
>Sent: Wednesday, January 20, 2016 4:04 PM
>To: user-committee at lists.openstack.org
>Subject: Re: [User-committee] app dev on-boarding experience report
>
>On 01/20/2016 03:40 PM, Bonell Manjarrez, Marcela wrote:
>> This are the workarounds I did on libcloud (openstack driver with the 
>> Neutron API) trying to fix the problems we faced (networking) on the 
>> app dev experience report:
>> 
>> File updated:
>> /usr/local/lib/python2.7/dist-packages/libcloud/compute/drivers/openst
>> ack.py",
>
>If I understand correctly, you patched libcloud driver locally and you managed to get the SecurityGroup assigned on Rackspace Cloud? If so, consider filing a bug against libcloud and propose a patch to them (it's fairly easy and documented on
>https://libcloud.readthedocs.org/en/latest/development.html#contributing)
>
>> - Despite of the fact that I had the security group ready 
>> (all_in_one_security_group), it wasn’t assign to the instance at the 
>> moment when the instance was created.
>
>I have no idea why that failed, sorry. Maybe the Rackspace folks can help figure this one out.
>
>> - I connected to my instance thru ssh and I didn’t find the app code 
>> :(
>
>That may take some time to actually get on the virtual machine. You may want to look at the console logs to see why (if) the curl command failed.
>
>> Now, I’m moving to Shade, I only have this link:
>> http://git.openstack.org/cgit/openstack-infra/shade in case you have 
>> more material about Shade, can you share it with me? :) I’ll share 
>> this findings also in the libcloud maillist and I’ll keep you posted 
>> about my new journey with Shade.
>
>This is the place where you can find the same libcloud tutorial but adapted to shade:
>
>http://developer.openstack.org/draft/firstapp-shade/
>
>It's still in draft because it's missing a chapter (about Swift) but it should be enough for you to move forward.
>
>As a side note, I think the pieces of the first app tutorials that are completed should just be published on the home page, even if the whole book is not completed. Let's put a note in the doc to say "This section is not completed.... contribute it yourself or check again later" is a better service to the community than hiding documentation behind the draft/ site.
>
>/stef
>
>_______________________________________________
>User-committee mailing list
>User-committee at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>_______________________________________________
>User-committee mailing list
>User-committee at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee