Automate setup of development environment

[hamiltont]

This uses Vagrant to automatically setup a fully working TFB development environment inside a Virtualbox VM. The entire environment is contained in one virtual machine (app server, client server, database server), so you can do verification and benchmarking (not much reason to benchmark inside this setup, my point is just that there's no limitation).

Here's how to setup an environment based on github.com/TechEmpower/FrameworkBenchmarks:

# Go into the right directory
$ cd FrameworkBenchmarks/toolset/deployment/vagrant
# Setup the VM with all initial software (takes 15-20 minutes)
$ vagrant up
# SSH into the machine (you get a nice welcome message)
$ vagrant ssh
Welcome to the FrameworkBenchmarks project!

To get started, perhaps try this:
   $ cd FrameworkBenchmarks
   $ toolset/run-tests.py --install server --test go
   $ cat results/ec2/latest/logs/go/out.txt

You can get lots of help:
   $ toolset/run-tests.py --help

This Vagrant environment is already setup and ready to go, so you
can ignore any flags about users, hosts, or identity files

Here's how to setup an environment based on your local source code:

# Go into the right directory
$ cd FrameworkBenchmarks/toolset/deployment/vagrant
# Setup the VM with all initial software (takes 15-20 minutes)
$ SHELL_ARGS=dev vagrant up
<snip>

[hamiltont]

Closes #455. Built on top of #621

[hamiltont]

Closes #455. Built on top of #621

[hamiltont]

Update: This can now deploy to Amazon
Update 2: It now has a decent README

[hamiltont]

Update: This can now deploy to Amazon
Update 2: It now has a decent README

[hamiltont]

Update: This can now use three virtual machines, each configured for a unique role (app server, database server, client server)

[hamiltont]

Update: This can now use three virtual machines, each configured for a unique role (app server, database server, client server)

[hamiltont]

Ok, this is finally done. It can out of the box launch a one-VM VirtualBox development environment, or a 3-VM VirtualBox development environment. If you run vagrant-aws/setup.py it will configure your Amazon account with a network (a "Virtual private cloud") that can run our setup, and then it can run a one-VM development environment in Amazon or can run a benchmark-ready 3-VM environment. By default, the 3-VM Amazon environment uses m1.large and general purpose SSD drives. There are tons of variables to change the amazon settings (instance type, ebs type, delete ebs, etc), and a few variables to change the virtualbox setup (show virtual machine, memory for each vm, etc).

[hamiltont]

Ok, this is finally done. It can out of the box launch a one-VM VirtualBox development environment, or a 3-VM VirtualBox development environment. If you run vagrant-aws/setup.py it will configure your Amazon account with a network (a "Virtual private cloud") that can run our setup, and then it can run a one-VM development environment in Amazon or can run a benchmark-ready 3-VM environment. By default, the 3-VM Amazon environment uses m1.large and general purpose SSD drives. There are tons of variables to change the amazon settings (instance type, ebs type, delete ebs, etc), and a few variables to change the virtualbox setup (show virtual machine, memory for each vm, etc).

[methane]

Great Job!!

[methane]

Great Job!!

[pdonald]

This is great.

Note: if you are on Windows and autocrlf is true in Git then all bash scripts will have \r\n line endings and bootstrap scripts will fail.

[pdonald]

This is great.

Note: if you are on Windows and autocrlf is true in Git then all bash scripts will have \r\n line endings and bootstrap scripts will fail.

[hamiltont]

Pēteris,

This sounds problematic. Is there a fix we can apply?

[hamiltont]

Pēteris,

This sounds problematic. Is there a fix we can apply?

[pdonald]

You could check if one of the bootstrap bash scripts contains \r\n and then show a warning explaining that the user should set autocrlf to false in Git settings and check out all files again.

[pdonald]

You could check if one of the bootstrap bash scripts contains \r\n and then show a warning explaining that the user should set autocrlf to false in Git settings and check out all files again.