From Fedora Project Wiki
m (add slash) |
mNo edit summary |
||
(One intermediate revision by one other user not shown) | |||
Line 2: | Line 2: | ||
|description=Deliver an appliance to Amazon S3 | |description=Deliver an appliance to Amazon S3 | ||
|setup= | |setup= | ||
{{admon/note|You need an Amazon AWS account to perform this Test Case}} | {{admon/note|AWS account required|You need an Amazon AWS account to perform this Test Case}} | ||
# [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare your environment]] | # [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare your environment]] | ||
# 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. | # 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. | ||
Line 15: | Line 15: | ||
cert_file: /home/a/cert-ABCD.pem # required only for ami type | cert_file: /home/a/cert-ABCD.pem # required only for ami type | ||
key_file: /home/a/pk-ABCD.pem # required only for ami type | key_file: /home/a/pk-ABCD.pem # required only for ami type | ||
</pre> | </pre> | ||
{{admon/warning|BoxGrinder Build config file location|The default location for this file is <code>/root/.boxgrinder/config</code>. You can put this file in different location by specifying <code>BG_CONFIG_FILE</code> environment variable.}} | |||
|actions= | |actions= | ||
# Execute <pre>boxgrinder-build | # 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> |
Latest revision as of 07:37, 28 April 2011
Description
Deliver an appliance to Amazon S3
Setup
- Prepare your environment
- 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
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:
ec2user
password: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