From Fedora Project Wiki

(Created page with "{{Infobox_group | name = Fedora Test Days | image = link=QA/Fedora_16_test_days | caption = OpenStack Test Day | date = 2012-03-08 | time = all day...")
(Change Instructions to use the Qpid broker)
Line 49: Line 49:
   $> sudo yum update -y
   $> sudo yum update -y
=== '''Enable RabbitMQ''' ===
=== '''Enable the Qpid Broker''' ===
  $> sudo yum install --enablerepo=updates-testing -y rabbitmq-server
  $> sudo yum install --enablerepo=updates-testing -y qpid-cpp-server
  $> sudo service rabbitmq-server start
  $> sudo service qpidd start
  $> sudo chkconfig rabbitmq-server on
  $> sudo chkconfig qpidd on
=== '''Enable libvirt''' ===
=== '''Enable libvirt''' ===

Revision as of 18:11, 27 January 2012

Fedora Test Days
OpenStack Test Day

Date 2012-03-08
Time all day

Website QA/Fedora_17_test_days
IRC #fedora-test-day (webirc)

Mailing list

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

Prerequisite for Test Day

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 update -y

Enable the Qpid Broker

$> sudo yum install --enablerepo=updates-testing -y qpid-cpp-server
$> sudo service qpidd start
$> sudo chkconfig qpidd on

Enable libvirt

$> sudo yum install --enablerepo=updates-testing -y @virtualization
$> sudo service libvirtd start
$> sudo chkconfig libvirtd on

Load nbd

So that we can later inject files into qcow2 images

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

Test Cases

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

Basic setup:

  1. Install the packages
  2. Start glance services
  3. Start nova services
  4. Create user, project and network
  5. Add SSH keypair
  6. Register tty images

Core functionality:

  1. Launch an instance
  2. Attach a volume
  3. Floating IPs
  4. MySQL
  5. Separate compute node

Extra credit:

  1. Build an image with Oz
  2. Smoke tests

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.

Basic setup:

User Install the packages Start glance services Start nova services Create user, project and network Add SSH keypair Register tty images References

Core functionality:

User Launch an instance Attach a volume Floating IPs MySQL Separate compute node References

Extra credit:

User Build an image with Oz Smoke tests References