Posted by Vacilando on May 21, 2009 at 8:03pm
| Project: | CDN |
| Version: | 6.x-1.x-dev |
| Component: | Module |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
| Issue tags: | CloudFiles. CDN, CloudFront |
Issue Summary
With the excellent work going on in the emerging version for D6, are there plans to add support for Mosso/Rackspace's CloudFiles CDN?
According to their own words (OK, take a bucket of salt), it's a way better CDN than Amazon's CloudFront -- see http://blog.mosso.com/2009/02/a-quantitative-comparison-of-rackspace-and... and http://blog.mosso.com/2009/01/top-10-reasons-why-cloud-files-limelight-o...
(Sorry, I know 6.x dev exists now but it still does not appear in the version dropdown, so I've labelled this incorrectly.)
Comments
#1
Hm, weird, it appears for me. Maybe a cache issue? Or it's a d.o permission issue. Don't know. Let me know if it persists and I'll file an issue in the d.o issue queue.
And wow, are we moving fast or what? It seems somebody wrote a Django storage class for Mosso Cloud Files exactly one day ago! Amazing! So I've already posted back (http://code.welldev.org/django-storages/issue/8/mosso-cloud-files-storage) in the django-storages issue queue, reporting the existence and asking what the typical Django (or Python) policy is in these things.
If it works, it's about 15 minutes of work :)
Basically:
1) add
cumulus.storage.CloudFileStorageto the daemon:dependencies.storages.MossoCloudFileStorage.MossoCloudFileStorage2) write a thin transporter wrapper around it, like
transporters.transporter_ftp.TransporterFTP, but thentransporters.transporter_cloudfiles.TransporterCloudFilesThat's it. Note that this *only* requires changes in the daemon, not in the Drupal CDN integration module! But there's no issue queue for that yet, so until that exists, we'll abuse the d.o issue queue
Care to roll a patch? :) You'd be the first contributor (of hopefully many more)!
#2
So … only 10 days further … and it's been committed to django-storages! See https://bitbucket.org/david/django-storages/issue/8/mosso-cloud-files-st.... Rock on, open source!
I'll probably have enough time to incorporate this into the daemon as well.
#3
I haven't had the time and I have to finalize my bachelor thesis text today. I will add this after my thesis defense though! :)
#4
Hate to just bump an issue, but I'm excited to see CloudFiles support in the daemon so I can give it a go. Please let me know if there is any support I can lend.
#5
Will be done ASAP :)
#6
Bump. I'd love to use this module with Mosso's cloud files. Any progress update?
#7
Great work!
I'll be looking for this cloudfiles implementation.
Thanks!!!
#9
I added the support to publish to Mosso Cloudfiles, I'm talking to Wim to hand him the changes so he can update the daemon.
Nestor
#10
Hi Nestor
Is the support to publish to Mosso something that can be applied as a patch? Or is it better to wait for an official update to the daemon?
best wishes
scotjam
#11
I'm waiting for Nestor's patch :)
#12
Hi,
I created a patch over the changes I made.
Also the patch includes the cloudfiles library for python, I'm not sure if Win will want to add it or just keep instructions of how to download it.
Let me clarify that I'm not a python developer, so if you find something that can be improve it go for it. I based on some other files and what I was able to find out on the way.
modified transporters/transporter.pyadded dependencies/storages/mosso.py
added transporters/transporter_mosso.py
added cloudfiles/*
To configure the destination use something like this in the configuration file:
<servers><server name="blog push cloudfiles" transporter="mosso" >
<username>mymossoaccount</username>
<api_key>mymossoapikey</api_key>
<container>test_container</container>
</server>
</servers>
BTW, awsome work Win Leers, thanks a lot.
~Nestor
#13
I've moved the File Conveyor daemon to its own project at github: http://github.com/wimleers/fileconveyor. Please create a new issue there: http://github.com/wimleers/fileconveyor/issues.
Won't fixing it here.
Nestor, THANK YOU so much! :)
#14
I committed this already anyway, to prevent this from getting lost: http://github.com/wimleers/fileconveyor/commit/d7faa774d97f1269ba374346e....
Thanks again :)
#15
OOPS, I was looking at the wrong issue! It's #567890: Config.xml example for S3 and Cloudfront transports that got fixed: http://drupal.org/node/567890#comment-2162166.
Looking at this patch right now though :)
#16
Committed!
See the following commits: http://github.com/wimleers/fileconveyor/commit/1f85935389bd0e15a179fdfdb... and http://github.com/wimleers/fileconveyor/commit/fb5ba9d95a04b63c973ae4779.... First time using git and that's why there 2 commits: I made an error in the first commit.
Most of the changes you suggested, went in intact. I replaced some tabs by spaces and moved the "cloudfiles" directory into the "dependencies" directory. I also added the necessary information to README.txt about this new Transporter, as well as the corresponding license information. That's it!
Thanks again :)
#17
Automatically closed -- issue fixed for 2 weeks with no activity.