From Fedora Project Wiki
m (change format of page.) |
m (fix action description) |
||
| Line 17: | Line 17: | ||
|actions= | |actions= | ||
# Execute <pre>boxgrinder-build /boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -p ec2 -d ebs --trace</pre> | # 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 | # 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> | ||
# 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]] | ||
| Line 23: | Line 23: | ||
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 #1 completes without error (indicated on console) | # Step #1 completes without error (indicated on console) | ||
# Program completes with exit code 0 | # 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, and instance data survives reboots | # AMI boots successfully, and can log into the EBS AMI appliance without error, and instance data survives reboots | ||
# [[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:10, 23 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
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.
- Prepare the instance's environment
- Put the following BoxGrinder config into a file named:
/root/boxgrinder/config. Insert appropriate values, 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:
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
- The JEOS EBS AMI is present in the AWS console
- AMI boots successfully, and can log into the EBS AMI appliance without error, and instance data survives reboots
- QA:Network_basic_test_case is performed successfully on the new appliance