Test Day:2011-04-28 Cloud SIG BoxGrinder Build

What to test?
Today's instalment of Fedora Test Day will focus on BoxGrinder Build

New to BoxGrinder?
Don't worry. Please read this README or scan our BoxGrinder homepage. If something is still unclear, don't hesitate to ask us on IRC.

Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 * Development - Marek Goldmann (mgoldmann), Marc Savy (msavy)

Prerequisite for Test Day

 * Free time
 * An updated Fedora 15 pre-release
 * Your hardware profile uploaded to Smolt according to these instructions
 * At least 15GB of free space available on a storage device (or more, depending on your later definition choices)
 * Internet connectivity for the test machines (or an active local YUM repository mirror)
 * Standard Fedora repositories must be available
 * Some virtualization software such as KVM, VirtualBox OSE or VMware Player for local tests
 * For the cloud-based tests you should have access to the corresponding cloud provider (e.g. Amazon AWS, CloudFront).

Several GB of space may be required transiently during the build process, in addition to storage of appliances produced and caching. Any mountable storage with Read/Write access should be suitable (e.g. HDD, USB flash drive, eSATA disk).

Test Day Virtual Image
Optionally, a pre-prepared BoxGrinder Virtual Images are available in multiple formats for your architecture.
 * Download the Test Day Meta-Appliance in your preferred format, and run in your favorite virtualization software.

Update your machine to Fedora 15
If you are already running or want to try the pre-release of Fedora 15, install Fedora 15 Beta and then update to the latest packages.

Prepare your environment
If you're testing with the BoxGrinder Test Day Meta-Appliance, then everything is already prepared for you. Otherwise, it is a matter of a few simple steps to prepare your environment.

For Fedora 15
wget http://kojipkgs.fedoraproject.org/packages/rubygem-boxgrinder-core/0.3.1/1.fc15/noarch/rubygem-boxgrinder-core-0.3.1-1.fc15.noarch.rpm wget http://kojipkgs.fedoraproject.org/packages/rubygem-boxgrinder-build/0.9.1/1.fc15/noarch/rubygem-boxgrinder-build-0.9.1-1.fc15.noarch.rpm yum localinstall ./rubygem-boxgrinder-*

For Fedora 13/14
yum install --enablerepo=updates-testing rubygem-boxgrinder-core rubygem-boxgrinder-build

Install other tools
yum install git createrepo

Grab test appliances
git clone https://github.com/msavy/boxgrinder-appliances.git cd boxgrinder-appliances

Local Test Cases
These test cases require no access to cloud providers to perform.

QA:TestCase_boxgrinder_jeos_build

QA:TestCase_boxgrinder_modular_test_appliances_build

QA:TestCase_boxgrinder_platform_vmware

QA:TestCase_boxgrinder_platform_virtualbox

QA:TestCase_boxgrinder_deliver_local

QA:TestCase_boxgrinder_deliver_sftp

QA:TestCase_boxgrinder_xarch_pipeline

Cloud Test Cases
An account with a cloud provider is needed to enact the following test-cases

QA:TestCase_boxgrinder_platform_ec2 No AWS account needed

QA:TestCase_boxgrinder_deliver_s3 Amazon AWS

QA:TestCase_boxgrinder_deliver_ami Amazon AWS

QA:TestCase_boxgrinder_deliver_ebs Amazon AWS

QA:TestCase_boxgrinder_deliver_cloudfront Amazon AWS CloudFront

QA:TestCase_boxgrinder_deliver_elastichosts ElasticHosts API compatible hosts

Test Results
If you have problems with any of the tests, report a bug to JIRA or Bugzilla, although we prefer JIRA. After submitting a ticket, attach the relevant data from log file.

Need help?
If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.