Skip to content

Commit

Permalink
Incorporate storage api based tests into object_storage_benchmarks. A…
Browse files Browse the repository at this point in the history
…fter this commit, we will have:

1. single byte upload and download API tests.
2. List after write consistency tests

In addition to this, I also did a number of refactoring of the existing object_storage_benchmark code.

And I also add the pkb/scripts/ directory to the default resource loader.
  • Loading branch information
stfeng2 committed Jan 29, 2015
1 parent b78f78b commit 0e8a56a
Show file tree
Hide file tree
Showing 7 changed files with 369 additions and 72 deletions.
1 change: 1 addition & 0 deletions MANIFEST.in
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
include perfkitbenchmarker/data/*
include perfkitbenchmarker/scripts/*
include LICENSE
include README.md
include ez_setup.py
Expand Down
28 changes: 28 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,6 +133,34 @@ Test that azure is installed correctly
```
$ azure vm list
```
## Create and Configure a .BOTO file for object storage benchmarks

In order to run object storage benchmark tests, you need to have a properly configured ~/.boto file.

Here is how:

* Create the ~/.boto file (If you already have ~/.boto, you can skip this step. Consider making a backup copy of your existing .boto file.)

To create a new ~/.boto file, issue the following command and follow the instructions given by this command:
```
$ gsutil config
```
As a result, a .boto file is created under your home directory.

* Open the .boto file and edit the following fields:
1. In the [Credentials] section:

gs_oauth2_refresh_token: set it to be the same as the "refresh_token" field in your gcloud credential file (~/.config/gcloud/credentials), which was setup as part of the 'gcloud auth login' step.

aws_access_key_id, aws_secret_access_key: set these to be the AWS access keys you intend to use for these tests, or you can use the same keys as those in your existing AWS credentials file (~/.aws/credentials).

2. In the [gsutil] section:

default_project_id: if it is not already set, set it to be the google cloud storage project ID you intend to use for this test. (If you used 'gsutil config' to generate the .boto file, you should have been prompted to supply this information at this step).

3. In the [OAuth2] section:
client_id, client_secret: set these to be the same as those in your gcloud credentials file (~/.config/gcloud/credentials), which was setup as part of the 'gcloud auth login' step.


## Install PerfKit dependencies
```
Expand Down
Loading

0 comments on commit 0e8a56a

Please sign in to comment.