| Cloud SIG BoxGrinder Build Fedora Test Day | |
|---|---|
| |
| BoxGrinder Build | |
| Date | 2011-04-28 |
| Time | all day |
| Website | BoxGrinder |
| IRC | #fedora-test-day (webirc) |
| Mailing list | cloud |
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), 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).
Be aware that you may transfer several GB of files in the course of testing.
Some of the Test Cases require the availability of cloud services such as Amazon's AWS that you may not have access to. However, please complete those you can, many of the important cases still possible!
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, git and createrepo via your favoured package manager. For instance, in YUM:
yum install git rubygem-boxgrinder-build createrepo
How to test?
Test Day Virtual Image
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 are already running or want to try the pre-release of Fedora 15, install Fedora 15 Beta and then update to the latest packages.
Test Cases
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 Amazon AWS
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 usually for the component BGBUILD. After submitting a ticket, attach the relevant data from log file log/boxgrinder.log.
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 | elastichosts | References |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Sample User | HW |  |
|
 |
 |
|
|
|
|
|
|