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

Cloud SIG Fedora Test Day
Fedora on EC2, BoxGrinder
Date	2011-04-28
Time	all day
Website	QA/Fedora_15_test_days
IRC	#fedora-test-day (webirc)
Mailing list	cloud

Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on BoxGrinder Build

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

• Development - Marek Goldmann (mgoldmann)
• Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4), Tester3 (irc_nick5)

Prerequisite for Test Day

• An updated Fedora 15 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
• 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

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).

Those with very slow Internet connections, or small bandwidth allowances
Be aware that you may transfer several GB of files in the course of testing.

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.

• Install rubygem-boxgrinder-build and git via your favoured package manager. For instance, in YUM:

   su -c "yum install -y git rubygem-boxgrinder-build" 

How to test?

Test Day Virtual Image

Virtual Images not yet available
The Virtual Images will appear nearer the date of the Test Day

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 favourite virtualization software.

Update your machine to Fedora 15

If you're running Fedora <=14, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide.

Test Cases

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

Cloud Delivery

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

QA:TestCase_boxgrinder_platform_ec2 Amazon AWS

QA:TestCase_boxgrinder_deliver_s3 (do we need this or just do AMI?)

QA:TestCase_boxgrinder_deliver_ami Amazon AWS

QA:TestCase_boxgrinder_deliver_ebs Amazon AWS

QA:TestCase_boxgrinder_deliver_cloudfront Cloudfront

Test Results

Construct a table or list to allow testers to post results. Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:

If you have problems with any of the tests, report a bug to JIRA usually for the component BGBUILD. 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.

User	Smolt Profile	JEOS	Modular	vmware	virtualbox	local	sftp	ec2	s3	ami	ebs	cloudfront	References
Sample User	HW	pass	pass	warn	fail	pass	pass	pass	pass	pass	pass	none