From Fedora Project Wiki
m (fix action description) |
mNo edit summary |
||
(3 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
|description=Deliver an appliance to Amazon EBS, from an Amazon EC2 instance. You ''cannot'' deliver to EBS outside of an EC2 instance. | |description=Deliver an appliance to Amazon EBS, from an Amazon EC2 instance. You ''cannot'' deliver to EBS outside of an EC2 instance. | ||
|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}} | ||
# Launch the JEOS AMI built in the AMI test case: [[QA:TestCase_boxgrinder_deliver_ami]], or any other Fedora 15 AMI. | # Launch the JEOS AMI built in the AMI test case: [[QA:TestCase_boxgrinder_deliver_ami]], or any other Fedora 15 AMI. | ||
# [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare the instance's environment]] | # [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare the instance's environment]] | ||
# Put the following BoxGrinder config into a file named: <code>/root/boxgrinder/config</code>. | # Put the following BoxGrinder config into a file named: <code>/root/.boxgrinder/config</code>. See http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#EBS_Delivery_Plugin, for more information. | ||
<pre> | <pre> | ||
plugins: | plugins: | ||
Line 14: | Line 14: | ||
delete_on_termination: false # default: true | delete_on_termination: false # default: true | ||
</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 ebs --trace</pre> | ||
# Once completed, a JEOS EBS is available. Launch the instance. | # Once completed, a JEOS EBS is available. Launch the instance. | ||
# Log into the EBS instance via SSH with user: <code>ec2user</code> password: <code>boxgrinder</code> | # Log into the EBS instance via SSH with user: <code>ec2user</code> password: <code>boxgrinder</code> | ||
Line 25: | Line 27: | ||
# Program completes with exit code 0 | # Program completes with exit code 0 | ||
# The JEOS EBS AMI is present in the AWS console | # The JEOS EBS AMI is present in the AWS console | ||
# AMI boots successfully, and can log into the EBS AMI appliance without error | # AMI boots successfully, and can log into the EBS AMI 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 | ||
# Instance data survives reboot | |||
}} | }} |
Latest revision as of 07:37, 28 April 2011
Description
Deliver an appliance to Amazon EBS, from an Amazon EC2 instance. You cannot deliver to EBS outside of an EC2 instance.
Setup
- Launch the JEOS AMI built in the AMI test case: QA:TestCase_boxgrinder_deliver_ami, or any other Fedora 15 AMI.
- Prepare the instance's environment
- Put the following BoxGrinder config into a file named:
/root/.boxgrinder/config
. See http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#EBS_Delivery_Plugin, for more information.
plugins: ebs: access_key: AWS_ACCESS_KEY # required secret_access_key: AWS_SECRET_ACCESS_KEY # required account_number: AWS_ACCOUNT_NUMBER # required delete_on_termination: false # default: true
How to test
- Execute
boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -p ec2 -d ebs --trace
- Once completed, a JEOS EBS is available. Launch the instance.
- Log into the EBS instance 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
- The JEOS EBS AMI is present in the AWS console
- AMI boots successfully, and can log into the EBS AMI appliance without error
- QA:Network_basic_test_case is performed successfully on the new appliance
- Instance data survives reboot