From Fedora Project Wiki

(initial boxgrinder delivery EBS test case)
 
mNo edit summary
 
(7 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.
* Install BoxGrinder Build and git on the instance: <pre>yum install -y git rubygem-boxgrinder-build</pre>
# [[Test_Day:2011-04-28_Cloud_SIG_BoxGrinder_Build#Prepare your environment|Prepare the instance's environment]]
* 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>/root/.boxgrinder/config</code>. See http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#EBS_Delivery_Plugin, for more information.
* Put the following BoxGrinder config into a file named: <code>~/.boxgrinder/config</code>. Insert appropriate values, see: http://boxgrinder.org/tutorials/boxgrinder-build-plugins/#EBS_Delivery_Plugin, for more information.
<pre>
<pre>
plugins:
plugins:
Line 15: 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=
# Navigate to directory <code>boxgrinder-appliances/testing-appliances/jeos-appls/</code>
# Execute <pre>boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -p ec2 -d ebs --trace</pre>   
# Execute <pre>boxgrinder-build fedora-15-jeos.appl -p ec2 -d ebs</pre>   
# Once completed, a JEOS EBS is available.  Launch the instance.  
# Once completed, a JEOS EBS should be available.  Launch an 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]]
|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 #2 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  
# AMI boots successfully, and can log into the EC2 appliance without error
# 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
# [[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

AWS account required
You need an Amazon AWS account to perform this Test Case
  1. Launch the JEOS AMI built in the AMI test case: QA:TestCase_boxgrinder_deliver_ami, or any other Fedora 15 AMI.
  2. Prepare the instance's environment
  3. 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
BoxGrinder Build config file location
The default location for this file is /root/.boxgrinder/config. You can put this file in different location by specifying BG_CONFIG_FILE environment variable.

How to test

  1. Execute 
    boxgrinder-build boxgrinder-appliances/testing-appliances/jeos-appls/fedora-15-jeos.appl -p ec2 -d ebs --trace
  2. Once completed, a JEOS EBS is available. Launch the instance.
  3. Log into the EBS instance via SSH with user: ec2user password: boxgrinder
  4. 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.

  1. Step #1 completes without error (indicated on console)
  2. Program completes with exit code 0
  3. The JEOS EBS AMI is present in the AWS console
  4. AMI boots successfully, and can log into the EBS AMI appliance without error
  5. QA:Network_basic_test_case is performed successfully on the new appliance
  6. Instance data survives reboot



Retrieved from "https://fedoraproject.org/w/index.php?title=QA:TestCase_boxgrinder_deliver_ebs&oldid=234075"