|Fedora Test Days|
|OpenStack Test Day|
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.
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)
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.
How to test?
Follow the steps below to prepare the machine, then follow each of the test cases in order.
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
$> 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.
When ready, follow the instructions provided in each of the test cases:
- Install the packages
- Setup Nova
- Setup Keystone
- Start glance services
- Start nova services
- Create nova user, project, and network
- Add SSH keypair
- Register guest images
- Create nova network
- Basic dashboard setup and login
- Launch/terminate an instance with the dashboard
- Managing projects and users with the dashboard
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.
|User||Install the packages||Setup Nova||Setup Keystone||Start glance services||Start nova services||Add SSH keypair||Register images||Create nova network||References|
|User||Launch an instance||Attach a volume||Floating IPs||Separate compute node||References|
|User||Tempest tests||Build an image with Oz||Run Nova with Quantum||Smoke tests||References|