Test Day:2012-03-08 OpenStack Test Day: Difference between revisions

Revision as of 07:08, 26 December 2014

Fedora Test Days

OpenStack Test Day

Date	2012-03-08
Time	all day

Website	QA/Fedora_17_test_days
IRC	#fedora-test-day (webirc) - IRC Log
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?

This day is for testing the Essex release of OpenStack in Fedora. Check out the OpenStack Essex feature page for more details on what's new.

Who's available

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

Pádraig Brady (pixelbeat)
Bob Kukura (rkukura)
Mark McLoughlin (markmc)
Russell Bryant (russellb)
Alan Pevec (apevec)
Eoghan Glynn (eglynn)
Jan van Eldik (vaneldik)
Cole Robinson (crobinso)
Derek Higgins (derekh)
Steven Dake (sdake)

Prerequisite for Test Day

A fully updated Fedora 17 (virtual) machine.
Hardware virtualization support (e.g. Intel VT or AMD-V).
Up to 10-20Gb free disk space. Guest images take up a lot of space.

Hardware Requirements
You can do basic testing of OpenStack in a virtual machine, with specific config noted below

How to test?

Follow the steps below to prepare the machine, then follow each of the test cases in order.

Configure sudo

Add your account to sudoers, which can be done from a root prompt like:

 #> (umask 337; name=markmc; echo "$name ALL = (ALL) NOPASSWD: ALL" > /etc/sudoers.d/testday)

Update your machine

Make sure you have all the current updates for it installed:

 $> sudo yum --enablerepo=updates-testing clean all
 $> sudo yum update -y

Enable the Qpid Broker

$> sudo yum install --enablerepo=updates-testing -y qpid-cpp-server
$> sudo systemctl start qpidd.service
$> sudo systemctl enable qpidd.service

Enable libvirt

$> sudo yum install --enablerepo=updates-testing -y @virtualization
$> sudo systemctl start libvirtd.service
$> sudo systemctl enable libvirtd.service

Optionally Load nbd

If you don't perform this optional step, then libguestfs will be used to inject files into qcow2 images. Note however that is slower, especially if testing openstack within a VM

$> sudo modprobe nbd
$> echo nbd | sudo tee -a /etc/modules-load.d/nbd.conf

Put SELinux into Permissive Mode

Since we currently have a number of blocking AVC denials (e.g. in glance), we need to disable SELinux enforcing:

$> sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config
$> sudo setenforce permissive

Please do note any AVC denials you see and file them in bugzilla if they have not already been reported.

Test Cases

When ready, follow the instructions provided in each of the test cases:

Basic setup:

Core functionality:

Dashboard functionality:

Extra credit:

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for one of the openstack-nova, openstack-glance, openstack-keystone or openstack-swift components. 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. For each test case, use the result template to enter your result, as shown in the example result line.