Sounds like you already have a django-centric solution in mind, but what you want might be found in a distributed filesystem solution like Gluster (http://www.gluster.org/) or a distributed object store like Swift (http://swift.openstack.org/) accessed via django-storages. Or put them on CloudFiles or S3? Replication is good because the MTBF plummets as you add bits.
Brian Schott bfsch...@gmail.com On Dec 27, 2011, at 9:02 PM, Cameron wrote: > Greetings all- > > I have a django site which is referencing about 1TB of static files at the > moment and growing fast. I am running out of affordable upgrade options and > need to scale the file storage out to multiple machines once it hits 3TB. I > have a pretty good idea about what needs to be done for this but I wanted to > ask here first incase someone has a snippet / custom storage already written > that does something similar? > > I have seen django-dust and django-resto however these are both replicated > storage for load balancing / HA. I actually want to be able to split the > storage of the files between servers and control when certain servers are > full and can no longer write to etc. > > Any advice would be much appreciated. Cheers. > - > Cameron > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/J-sDi9ah1NMJ. > To post to this group, send email to django-users@googlegroups.com. > To unsubscribe from this group, send email to > django-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
