<commit_before># Automated Deployment Onto Amazon Web Services

Scripts exist to setup either a development environment, or a benchmark-ready
production environment. The development environment uses one small instance to 
run all three TFB roles (app server, database server, client load generation). 
The production environment uses three different instances networked together. 
There are a number of environmental variables listed below that allow you to 
change features such as instance type, availability region, etc. 

We use [Vagrant](https://www.vagrantup.com) to launch/terminate EC2 instances, 
and we provide a python script to configure the network as needed. 

All amazon resources are tagged with `Project=FrameworkBenchmarks` and 
`TFB_Role=[database|network|client|app]` so you can easily get a breakdown on 
your bill. A default development setup costs about `$1/day`, while a default
production setup costs about TODO. 

## Prerequisites

* **A recent version of Vagrant**, like 1.6.3 (NOTE: `apt-get` is 
too old, download the newest `deb` directly). See 
[here](https://www.vagrantup.com/downloads.html) for downloads

* **Vagrant AWS Plugin** from [here](https://github.com/mitchellh/vagrant-aws)

* **Python 2.7** to run the amazon setup script

* **Amazon Command Line Interface**: From [here](https://github.com/aws/aws-cli)

## Using Vagrant to Run Amazon-powered Virtual Machine

The high level steps are 
1) clone this project 
2) set environment variables allowing us to log into your amazon account
3) Run amazon setup script to create network
4) Run `vagrant up --provider=aws` to launch into amazon
5) Run `vagrant ssh` to log into the application server

By default, your local git clone of this project will not by synced with the 
remote amazon machines.

## Required Environment Variables

These environment variables are always required: 

    TFB_AWS_ACCESS_KEY : Your Amazon Web Services Access Key
    TFB_AWS_SECRET_KEY : Your Amazon Web Services Secret Access Key
    TFB_AWS_KEY_NAME   : The name of the keypair you are using
    TFB_AWS_KEY_PATH   : Path to the *.pem file for the keypair you are using<commit_msg>Remove claim vagrant from apt-get is too old<commit_after># Automated Deployment Onto Amazon Web Services

Scripts exist to setup either a development environment, or a benchmark-ready
production environment. The development environment uses one small instance to 
run all three TFB roles (app server, database server, client load generation). 
The production environment uses three different instances networked together. 
There are a number of environmental variables listed below that allow you to 
change features such as instance type, availability region, etc. 

We use [Vagrant](https://www.vagrantup.com) to launch/terminate EC2 instances, 
and we provide a python script to configure the network as needed. 

All amazon resources are tagged with `Project=FrameworkBenchmarks` and 
`TFB_Role=[database|network|client|app]` so you can easily get a breakdown on 
your bill. A default development setup costs about `$1/day`, while a default
production setup costs about TODO. 

## Prerequisites

* **A recent version of Vagrant**, like 1.6.3. See 
[here](https://www.vagrantup.com/downloads.html) for downloads

* **Vagrant AWS Plugin** from [here](https://github.com/mitchellh/vagrant-aws)

* **Python 2.7** to run the amazon setup script

* **Amazon Command Line Interface**: From [here](https://github.com/aws/aws-cli)

## Using Vagrant to Run Amazon-powered Virtual Machine

The high level steps are 
1) clone this project 
2) set environment variables allowing us to log into your amazon account
3) Run amazon setup script to create network
4) Run `vagrant up --provider=aws` to launch into amazon
5) Run `vagrant ssh` to log into the application server

By default, your local git clone of this project will not by synced with the 
remote amazon machines.

## Required Environment Variables

These environment variables are always required: 

    TFB_AWS_ACCESS_KEY : Your Amazon Web Services Access Key
    TFB_AWS_SECRET_KEY : Your Amazon Web Services Secret Access Key
    TFB_AWS_KEY_NAME   : The name of the keypair you are using
    TFB_AWS_KEY_PATH   : Path to the *.pem file for the keypair you are using
{'fraction_non_alphanumeric': 0.0644709180098108, 'fraction_numerical': 0.005606166783461808, 'mean_word_length': 4.582790091264668, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 8, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 5, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1985588', 'n_tokens_mistral': 1196, 'n_tokens_neox': 1153, 'n_words': 562}