|
11 years ago | |
---|---|---|
.. | ||
azure | 12 years ago | |
common | 11 years ago | |
README.md | 11 years ago |
This directory contains tools and documentation to deploy the benchmark suite on cloud or self-hosted environments.
The deployment consists of two phases:
The provisioning phase varies according to the hosting environment: EC2, Windows Azure, dedicated hardware or other hosting.
The setup phase is, for the most part, the same for all environments, because the benchmark suite specifies particular versions of operating systems and tools that will be used.
For any hosting option, these are the operating systems and tools that should be provisioned for each role:
Linux client
Linux server
Windows server
SQL Server
To deploy the benchmark suite on Amazon Web Services (AWS) Elastic Compute Cloud (EC2):
Create the EC2 instances
Create one instance for each role described in the deploment overview above.
We tested on m1.large instances, but feel free to experiment with different configurations.
Give the instance that will act as the application server more then the default 8GB of disk capacity (we used 20GB).
Security Group
When prompted to create a security group for the instances, here are the ports that you'll need to open:
For Windows Azure deployment instructions see the Windows Azure Deployment README file.
If you have two servers or workstations lying around, then you can install and run the tests on physical hardware.
Please be aware that these setup instructions can overwrite software and settings, so it's best to follow these instructions on clean hardware.
Evaluation downloads
If you want to run the benchmark on Windows and/or SQL Server, you can download evaluation versions from Microsoft:
Prerequisites
Before you get started, there are a couple of steps you can take to make running the tests easier on yourself.
Since the tests can run for several hours, it helps to set everything up so that once the tests are running, you can leave the machines unattended and don't need to be around to enter ssh or sudo passwords.
The benchmark suite will work on physical or virtual servers that have local network connectivity between them and Internet access for software download.
In general, any private or public hosting can be used, following this procedure:
Specific provisioning instructions and/or scripts for particular hosting or cloud services providers are welcome!
After the servers are provisioned as described above, it's time to deploy the benchmark suite and its dependencies.