我们有必要执行上把一些负担，我们的硬件资源，因为短短几周内，我们可能需要大量的服务器和客户端（Windows 2003和Windows 2008，Vista中，XP，红帽等本地化平台测试）多国语言。

We have the need to perform tests on localized platforms that put some burden on our hardware resources because for just a few weeks we might need plenty of servers and clients (Windows 2003 and Windows 2008, Vista, XP, Red Hat, etc) in multiple languages.

我们通常都依赖于刀片服务器与Windows 2003和VMWare，但有时这些都是杂草丛生由守的需求，也有这个问题，收购和部署过程中，如果环境需要成长相当缓慢。

We typically have relied on blades with Windows 2003 and VMWare, but sometimes these are overgrown by punctual needs and also have the issue that the acquisition and deployment process is quite slow if the environment needs to grow.

是Amazon EC2 / S3在以下情况下可以使用吗？

Is Amazon EC2/S3 usable in the following scenario?

我们更感兴趣的是非常容易地启动或停止的VMware snaphsots相对较短的测试的能力。这只是用于测试的配置，而不​​是一个生产环境，真正满足用户的工作负载。唯一真正的用户是测试。可能需要这些配置的短短几个星期，然后关闭了数月，直到下一个版本又需要他们。

We are more interested in the ability to very easily start or stop VMware snaphsots for relatively short tests. This is just for testing configurations, not a production environment to actually serve a user workload. The only real user is the tester. These configurations might be required for just a few weeks and then turned off for a few months until the next release requires them again.

时的EC2 / S3这种类型的测试目的，一个可行的替代方案？

Is EC2/S3 a viable alternative for this type of testing purpose?

推荐答案

你真的需要VMWare的，或者是你的测试运行在VMware虚拟机上的软件？你可能确实需要VMWare的，如果你正在测试如VMWare的部署策略，或者运行code，测试VMware的API的。后者的例子可能是你正在使用VMware来测试在许多平台上测试应用程序服务器堆栈和当前。

Do you actually need VMWare, or are you testing software that runs in the VMWare VMs? You might actually need VMWare if you are testing e.g. VMWare deployment policy, or are running code that tests the VMWare APIs. Examples of the latter might be you are testing an application server stack and currently using VMWare to test on many platforms.

如果你确实需要VMWare的，我不相信，你可以在EC2上安装VMWare。有人会纠正和放大器;开导我，如果不是这种情况。

If you actually need VMWare, I do not believe that you can install VMWare in EC2. Someone will correct & enlighten me if this is not the case.

如果你实际上并不需要VMWare的，你有更多的选择。如果您可以使用无数市民的AMI 的作为基线，克隆适当的AMI并进行自定义，以满足您的需求（保存定制版作为私人AMI为您的团队）。然后，你可以使用尽可能多的人，只要你喜欢。也许你已经有一大堆，你需要在你的测试，使用VMware图像。在这种情况下，您可以按照在谷歌不同的地方描述，例如您的VMware映像迁移到一个EC2 AMI：

If you don't actually need VMWare, you have more options. If you can use one of the zillion public AMIs as a baseline, clone the appropriate AMIs and customize them to suit your needs (save the customized version as a private AMI for your team). Then, you can use as many of them as you like. Perhaps you already have a bunch of VMWare images that you need to use in your testing. In that case, you can migrate your VMWare image to an EC2 AMI as described in various places in Google, for example:

http://thewebfellas.com/blog/2008/9/1/creating-an-new-ec2-ami-from-within-vmware-or-from-vmdk-files

（道歉的SO审查不粘贴整篇文章在这里它的pretty的长。）但是，这是一个快捷方式;你可以随时使用文件的AMI创建过程中的任何机（VMware或没有），转换为急性心肌梗死。执行过程对每个VMware虚拟机，你有，你将所有设置。请记住，当你创建一个AMI，你必须把它上传到S3，并且会占用大量的时间，大量的虚拟机。

(Apologies to the SO censors for not pasting the entire article here. It's pretty long.) But that's a shortcut; you can always use the documented AMI creation process to convert any machine (VMWare or not) to an AMI. Perform that process for each VMWare VM you have, and you'll be all set. Just keep in mind that when you create an AMI, you have to upload it to S3, and that will take a lot of time for large VMs.