From Fedora Project Wiki
m (initial boxgrinder delivery ElasticHosts test case) |
mNo edit summary |
||
(5 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{QA/Test_Case | {{QA/Test_Case | ||
|description=Deliver an appliance to | |description=Deliver an appliance to an ElasticHost API compatible cloud provider | ||
|setup= | |setup= | ||
{{admon/note|You need an account | {{admon/note|Cloud account required|You need an ElasticHosts, Open Hosting, SKALI Cloud or Serverlove account to perform this Test Case}} | ||
# Launch the JEOS AMI built in the AMI test case: [[QA:TestCase_boxgrinder_deliver_ami]], or any other Fedora 15 AMI. | |||
# 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/#ElasticHosts_Delivery_Plugin, for more information. | |||
<pre> | <pre> | ||
plugins: | plugins: | ||
elastichosts: | elastichosts: | ||
endpoint: api.lon-p.elastichosts.com # required | endpoint: api.lon-p.elastichosts.com # required | ||
username: your-user-id # required | |||
password: your-secret-access-key # required | |||
chunk: 128 # default: 64 (in MB) | chunk: 128 # default: 64 (in MB) | ||
wait: 30 # default: 5 (in s) | wait: 30 # default: 5 (in s) | ||
retry: 2 # default: 3 | retry: 2 # default: 3 | ||
ssl: true # default: false | ssl: true # default: false | ||
</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 testing-appliances/jeos-appls/fedora-14-jeos.appl -d elastichosts --trace</pre> | ||
# Run an instance of the VM through your cloud providers tools, log on via SSH | |||
# | |||
# Run the following Test Case in the VM: [[QA:Network_basic_test_case]] | # Run the following Test Case in the VM: [[QA:Network_basic_test_case]] | ||
|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 | ||
# The new image has appeared in your cloud provider's management system | # The new image has appeared in your cloud provider's management system | ||
# Step #2 completes 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 | ||
}} | }} |
Latest revision as of 07:40, 28 April 2011
Description
Deliver an appliance to an ElasticHost API compatible cloud provider
Setup
- Launch the JEOS AMI built in the AMI test case: QA:TestCase_boxgrinder_deliver_ami, or any other Fedora 15 AMI.
- Put the following BoxGrinder config into a file named:
/root/.boxgrinder/config
. Insert appropriate values, see: http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#ElasticHosts_Delivery_Plugin, for more information.
plugins: elastichosts: endpoint: api.lon-p.elastichosts.com # required username: your-user-id # required password: your-secret-access-key # required chunk: 128 # default: 64 (in MB) wait: 30 # default: 5 (in s) retry: 2 # default: 3 ssl: true # default: false
How to test
- Execute
boxgrinder-build testing-appliances/jeos-appls/fedora-14-jeos.appl -d elastichosts --trace
- Run an instance of the VM through your cloud providers tools, log on via SSH
- 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
- The new image has appeared in your cloud provider's management system
- Step #2 completes without error
- QA:Network_basic_test_case is performed successfully on the new appliance