From Fedora Project Wiki
(initial boxgrinder delivery AMI test case) |
m (change format of page.) |
||
| Line 4: | Line 4: | ||
{{admon/note|You need an Amazon AWS account to perform this Test Case}} | {{admon/note|You need an Amazon AWS account to perform this Test Case}} | ||
* Clone the BoxGrinder test appliances into a convenient location using command <code>git clone https://github.com/msavy/boxgrinder-appliances.git</code> | * Clone the BoxGrinder test appliances into a convenient location using command <code>git clone https://github.com/msavy/boxgrinder-appliances.git</code> | ||
* Put the following BoxGrinder config into a file named: <code> | * Put the following BoxGrinder config into a file named: <code>/root/.boxgrinder/config</code>. Insert appropriate values, see: http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#S3_Delivery_Plugin, for more information. | ||
<pre> | <pre> | ||
plugins: | plugins: | ||
| Line 19: | Line 19: | ||
|actions= | |actions= | ||
# | # Execute <pre>boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -p ec2 -d ami --trace</pre> | ||
# Launch an instance of your new JEOS AMI, it should have been registered automatically | # Launch an instance of your new JEOS AMI, it should have been registered automatically | ||
# Log in via SSH with user: <code>ec2user</code> password: <code>boxgrinder</code> | # Log in via SSH with user: <code>ec2user</code> password: <code>boxgrinder</code> | ||
| Line 26: | Line 25: | ||
|results= | |results= | ||
The following must be true to consider this a successful test run. | The following must be true to consider this a successful test run. | ||
# Step # | # Step #1 completes without error (indicated on console) | ||
# Program completes with exit code 0 | # Program completes with exit code 0 | ||
# AMI boots successfully, and can log into the EC2 appliance without error | # AMI boots successfully, and can log into the EC2 appliance without error | ||
# [[QA:Network_basic_test_case]] is performed successfully on the new appliance | # [[QA:Network_basic_test_case]] is performed successfully on the new appliance | ||
}} | }} | ||
Revision as of 11:03, 23 April 2011
Description
Deliver an appliance to Amazon S3
Setup
You need an Amazon AWS account to perform this Test Case
- Clone the BoxGrinder test appliances into a convenient location using command
git clone https://github.com/msavy/boxgrinder-appliances.git - Put the following BoxGrinder config into a file named:
/root/.boxgrinder/config. Insert appropriate values, see: http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#S3_Delivery_Plugin, for more information.
plugins:
s3:
access_key: AWS_ACCESS_KEY # (required)
secret_access_key: AWS_SECRET_ACCESS_KEY # (required)
bucket: stormgrind-test # (required)
account_number: 0000-0000-0000 # (required)
path: /images # default: /
cert_file: /home/a/cert-ABCD.pem # required only for ami type
key_file: /home/a/pk-ABCD.pem # required only for ami type
host: http://host:8773/services/Walrus # default: http://s3.amazonaws.com; host used to upload AMI
How to test
- Execute
boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -p ec2 -d ami --trace
- Launch an instance of your new JEOS AMI, it should have been registered automatically
- Log in via SSH with user:
ec2userpassword:boxgrinder - Run the following Test Case in the VM: QA:Network_basic_test_case
Expected Results
The following must be true to consider this a successful test run.
- Step #1 completes without error (indicated on console)
- Program completes with exit code 0
- AMI boots successfully, and can log into the EC2 appliance without error
- QA:Network_basic_test_case is performed successfully on the new appliance