From Fedora Project Wiki

Revision as of 09:31, 22 April 2011 by Msavy (talk | contribs) (initial page, missing test results section, need to flesh out the test-cases. doing those next.)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Cloud SIG Fedora Test Day
Echo-testing-48px.png
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


Note.png
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 ...

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

Note.png
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

Note.png
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.

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