Hi Joshua, we do not have public AMIs to offer, but if you logon to Amazon's Management Console and search for "django" under AMIs you find at least three public images: <https://console.aws.amazon.com>
I reckon this should be a good start. Best Joern ----------------------------------------------------------------------------------------------- beyond content GmbH Dipl.-Ing. Jörn Paessler Geschäftsführer Burgschmietstr. 10 90419 Nürnberg, Germany E-Mail: joern.paess...@beyond-content.de Web: www.beyond-content.de Fon: +49 (0)911 977 98162 Fax: +49-(0)911 787 2525 Geschäftsführer: Dipl.-Ing. Jörn Paessler Sitz der Gesellschaft: Nürnberg Handelsregister: Amtsgericht Nürnberg HRB 23740 USt-IdNr.: DE247571538 Am 30.04.2009 um 11:34 schrieb Joshua Partogi: > > Hi Jörn, > > Thank you very much for sharing your experience. We were going to use > it for a community site, but it seems that EC2 is not reliable though > scalable. This is a tough choice. :-( Any chance that you already > created an AMI for this that perhaps you can share with the > community? > > > Best regards, > > On Apr 29, 9:09 pm, Jörn Paessler <joern.paess...@beyond-content.de> > wrote: >> Hi Joshua, >> >> we have been hosting our django sites on EC2 for about 9 months now. >> >> We are quite happy with it but there are some things you have to take >> care of: >> - we recently had a downtime, because the host system crashed. We had >> a new instance up and running pretty fast but you have to keep in >> mind: there is no self-healing mechanism to e.g. broken HDD on EC2. >> You need to have a backup plan. An Amazon support employeee send me >> this reply afterwards: >> "Instances depend on the health of the underlying host. The component >> that breaks most often are hard disks, so if the instance had any >> data >> stored on the disk, it may not be recoverable if there was a fatal >> failure, so moving an instance is not easily possible. In general, we >> recommend that you architect your system in a way so that a single >> instance failure does not disrupt the overall operation of your >> system. We also recommend keeping current backups." >> - For planning your infrastructure this blogentry might be quite >> helpful: >> "Experiences deploying a large-scale infrastructure in Amazon >> EC2 " >> <http://agiletesting.blogspot.com/2009/04/experiences-deploying-large- >> ... >> > >> - we do manage every ressource with SVN. Even the SQL-dumps are >> periodically persisted via SVN. For our sites (90% corporate >> websites) >> this is a possible solution. I wouldn't recommend this for community >> websites. >> - On the high traffic sites we serve the media with Cloudfront. Runs >> very smooth. >> - Site data, logs and config-files are located on a mounted EBS. >> - The best deal for the buck is a medium instance, find more >> information here: >> <http://www.paessler.com/blog/2009/04/03/prtg-7/testing-cloud-computin >> ... >> > >> "Our conclusion of these tests is that we will mostly use the >> “c1.medium” instances (”High CPU Medium Instance”) for webhosting and >> other performance-relevant uses because it offers 150-300% more >> performance (for CPU, disk and memory) than “m1.small” instances >> while >> only costing 100% more." >> >> Hope that information helps! >> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
