Thanks Tomaz. I was talking about storage and had been rather confused by the naming. I think CLOUDFILES_SWIFT might not be the best name because Rackspace calls their storage Cloud Files, but I've never heard any of the other providers use that term. That made me think the driver worked only with RackSpace. Not sure how easy it is to change the name, but I'd suggest as an alternative that OPENSTACK_SWIFT would be a better alternative (which would also make it easier for folks who don't realize that the OpenStack Object Storage is nicknamed Swift).
Thanks again for the help, Ben On Thu, Jul 11, 2013 at 6:12 AM, Tomaz Muraus <[email protected]> wrote: > Are you taking about compute or storage? > > In any case, it doesn't really matter because both of the APIs support > OpenStack installations. > > For compute you can find an example at > > https://libcloud.apache.org/docs/compute-examples.html#example-3-openstack-node-using-local-openstack > . > > For storage you can use a Provider.CLOUDFILES_SWIFT provider ( > > https://github.com/apache/libcloud/blob/trunk/libcloud/storage/providers.py#L41 > ). > Sadly there are no examples available at the moment, but the driver > constructor takes the same arguments as the compute driver. > > On Thu, Jul 11, 2013 at 6:47 AM, Ben McCann <[email protected]> wrote: > > > Actually, I was looking at libcloud a bit more today and couldn't figure > > out how to use it. It looks like it only has Rackspace support and not > > OpenStack support? Any chance that it could be made more general to > support > > OpenStack instead? > > > > > > On Wed, Jul 10, 2013 at 11:31 AM, Ben McCann <[email protected]> wrote: > > > > > Great! One other question. How does it handle a flaky connection / > > > backend? I looked through the code and didn't see any retry logic. I'd > > like > > > to upload a 100GB file, but have run into trouble with other tools that > > > don't retry. I'd like it to split it into < 5GB chunks which I see now > > that > > > libcloud supports, and then also retry each of those chunks a > > configurable > > > number of times. I'll have to talk to my hosting provider as well to > see > > > why uploading to object storage is so flaky, but I'm hoping I can also > > have > > > the client be resilient in that case. > > > > > > > > > On Tue, Jul 9, 2013 at 3:21 AM, Tomaz Muraus <[email protected]> wrote: > > > > > >> Yes, CloudFiles / Swift storage driver does support uploading large > > >> objects > > >> via the ex_multipart_upload_object method - > > >> > > >> > > > https://github.com/apache/libcloud/blob/trunk/libcloud/storage/drivers/cloudfiles.py#L463 > > >> > > >> And yes, you are right about the docs. I will try to update them and > add > > >> an > > >> example soon. > > >> > > >> On Mon, Jul 8, 2013 at 11:14 PM, Ben McCann <[email protected]> > wrote: > > >> > > >> > Hi, > > >> > > > >> > Does libcloud have large object > > >> > support< > > >> > > > >> > > > http://docs.openstack.org/trunk/openstack-object-storage/developer/content/large-object-creation.html > > >> > >for > > >> > OpenStack? I didn't see anything in the docs mentioning it one way > or > > >> > the other. > > >> > > > >> > Thanks, > > >> > Ben > > >> > > > >> > -- > > >> > about.me/benmccann > > >> > > > >> > > > > > > > > > > > > -- > > > about.me/benmccann > > > > > > > > > > > -- > > about.me/benmccann > > > -- about.me/benmccann
