QA:TestCase boxgrinder deliver ebs

From FedoraProject

Jump to: navigation, search

Contents

Description

Deliver an appliance to Amazon EBS, from an Amazon EC2 instance. You cannot deliver to EBS outside of an EC2 instance.

Setup

Note.png
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
Warning (medium size).png
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