亚马逊EC2容量和放大器;工作流问题 [英] Amazon EC2 Capacity & Workflow Questions
问题描述
我使用的是亚马逊的EC2可以提供一些建议，希望你们中的一些有经验......当然，这将是主观的这是很好的，我是pretty的确保您的guestimate会比我的好。
I’m hoping some of you with experience using amazon EC2 could offer some advice… of course it’ll be subjective which is fine, I’m pretty sure your guestimate would be better than mine.
我打算将所有我的客户的网站，从共享主机环境到Amazon EC2。他们都是pretty的低流量的网站（最繁忙的网站收到约50天独立访问者）。有大约8点，但我承担更多的项目和承载更多的网站我可能会扩大这个...电流容量规划是说12个站点。
I am planning on moving all my client’s websites from shared hosting environments to Amazon EC2. They’re all pretty low traffic sites (the busiest site receives around 50 unique visitors a day). There’s about 8 sites, but I may expand this as I take on more projects and host more sites… current capacity planning is for say 12 sites.
每个站点运行在ASP.Net（一把umbraco CMS），并且需要一个SQL Server数据库。
Each site runs on ASP.Net (Umbraco CMS), and requires a SQL Server database.
我的想法是下列之一：
- 设置一个小型实例（1.7GB内存，1个EC2计算单元），并运行该服务器上的IIS和SQL Server防爆preSS。
- 在设置2微实例（每个613MB内存，最多2个EC2计算单元） - 一个用于IIS，另一个用于SQL Server
该装置，你认为会的工作最适合我的要求。我已经开始建立一个微型的实例与服务器2008，SQL Server的防爆preSS等...并发现它不应对内存需求，因此考虑扩大。我总是可以配置一个小实例，然后导出AMI和火起来后微实例，每个任何严重更改服务器都需要时间做同样的。我想我甚至可以做所有的更新等上的备用小光斑的实例，然后切换负载AMI在微型和整个传输的IP地址，所以我并不需要做在生产服务器上的工作太多了。我想如果我存储在EBS卷的所有我的网站上的数据文件，那么它应该很容易移动以最小的停机时间服务器之间的托管，而从来不工作在生产服务器上。
Which arrangement do you think would work the best for my requirements. I’ve started setting up a Micro instance with Server 2008, SQL Server Express, etc… and finding it not coping with the memory requirements, hence considering expanding. I could always configure on a Small instance, then export the AMI and fire it up in a Micro instance after, and do the same every time any serious changes to the server are required. I guess I could even do all updates etc on a spare Small Spot instance, then switch load that AMI up in a Micro and transfer the IP Address across, so I don’t need to do too much work on the production servers. I figure if I store all my website data files on EBS Volumes, then it should be fairly easy to move hosting between servers with minimal downtime, while never working on a production server.
我很想知道你们都认为，你使用等活动的升级，Windows更新，软件安装等什么样的战略。
I’m interested to know what you all think, and what strategies you employ for such activities as upgrades, windows updates, software installations, etc.
另外，你认为是什么身份我需要对我的要求。
And what capacity do you think I’d need for my requirements.
干杯 格雷格
推荐答案
嗯，首先向上，Server 2008中不会在613MB RAM的微型实例给你打得好。它运行，但它是一只狗，它大声吠叫的多个服务（IIS，SSE等），您层之上。我们用什么比一个小的小Server 2008中，实际上一般做环境配置在中型和向下扩展到小型一旦繁重的任务已经完成，操作系统就可以使用了。 Server 2003中，但是，似乎呼吸在微容易 - 但是我们还是做一个更大的实例配置和缩小
Well, first-up, Server 2008 doesn't play well in the 613MB RAM the Micro instance gives you. It runs, but it's a dog, and it barks louder the more services (IIS, SSE, etc) you layer on top. We using nothing smaller than a Small for Server 2008, and in fact typically do the environment config in a Medium and scale down to Small once the heavy lifting is complete and the OS is ready to use. Server 2003, however, seems to breathe easier on a Micro - but we still do the config on a larger instance and scale down.
我们在Server 2003 / IIS6在微型运行低流量的网站，用的是Server 2008 / SS上的共享，独立，小实例上安装。我们也有一个服务器2008 / IIS7 micro版本上运行，但只有提醒自己，为什么我们不使用它更广泛的应用。 ;）
We're running low-traffic websites on Server 2003/IIS6 in a Micro, with a Server 2008/SS install on a shared, separate, Small instance. We do also have one Server 2008/IIS7 Micro build running, but only to remind ourselves why we don't use it more widely. ;)
较大的网站，无论是在中小型实例上运行服务器2008 / IIS7，但几乎总是仍在使用共享的独立SS实例数据库服务。我们尽量不部署多个SS的安装，因为它使维护和备份更加复杂。
Larger websites run Server 2008/IIS7 in either Small or Medium instances, but almost always still using that shared separate SS instance for database services. We try not to deploy multiple SS installations, since it makes maintenance and backups more complex.
积攒内容和配置在EBS卷，当然是很好的做法，除非你喜欢重建整个系统只要实例消失。定期快照的实例也是很好的做法，因为你可以旋转，一个新的实例，从基线AMI和交换快照用于快速恢复在发生灾难时的引导卷。
Stashing content and config on EBS Volumes is of course good practice, unless you like rebuilding the entire system whenever an Instance disappears. Snapshotting your Instances periodically is also good practice, since you can spin-up a new Instance from a baseline AMI and swap the snapshot in as a boot Volume for fast recovery in the event of disaster.
这篇关于亚马逊EC2容量和放大器;工作流问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
