Test Day:2012-09-18 OpenStack
|OpenStack Test Days|
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Apevec (apevec)
- Development - Derekh (derekh)
- Development - eglynn (eglynn)
- Deployment - gkotton (garyk)
- Consulting - kensey (kensey)
- Development - markmc (markmc)
- Development - mrunge (mrunge)
- Development - Pbrady (pixelbeat)
- Deployment - rbuilta (rbuilta)
- Development - sdake (sdake)
- Deployment - sten (sten)
- Deployment - Vaneldik (vaneldik)
- Development - ndipanov (ndipanov)
Prerequisite for Test Day
- 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.
This is a Fedora 18 test day, but we have OpenStack Folsom packages available for both Fedora 18 and Fedora 17.
Fedora 18 Alpha live image can be used to install a bare metal or virtual machine. Please record common Fedora 18 issues here:
- Video doesn't work in a VM unless video type is set to 'vga' #848930
- Auto partitioning wipes the disk without warning #855976
- The installing packages step can take over 30 minutes #856993
Alternatively, try updating from Fedora 17 to Fedora 18 using yum.
Recent Fedora 17 live image respins can be used to install a bare metal or virtual machine.
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; echo "non_root_user 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
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
While SELinux mostly works with OpenStack services there are a few issues
sudo sed -i 's/^SELINUX=.*/SELINUX=permissive/' /etc/selinux/config sudo setenforce permissive
Please do note any AVC _denials_ you see in /var/log/audit/audit.log and file them in bugzilla, and update this list:
Install and setup all Openstack services on a single node
sudo wget http://repos.fedorapeople.org/repos/openstack/openstack-folsom/fedora-openstack-folsom.repo -O /etc/yum.repos.d/fedora-openstack-folsom.repo sudo yum install http://kojipkgs.fedoraproject.org/packages/openstack-utils/2012.2/2.fc18/noarch/openstack-utils-2012.2-2.fc18.noarch.rpm
So now the yum repositories are in place as is the openstack-demo-install script. This script will install all OpenStack services on a single node, including: nova, glance, quantum, cinder, swift, keystone, dashboard. Note it configures and enables all but the quantum service at this time:
Note this is a major test in itself, so please record any issues encountered.
Setup OpenStack volumes
The OpenStack volume service provides persistent block level storage to instances. This is a commonly used service, so please enable using QA:Testcase_Create_Cinder_Volumes
Install and setup Quantum on a single node
As an option, you can replace the network manager internal to the OpenStack Nova project with Quantum. To enable follow QA:Testcase_Quantum_V2#Setup
- Basic dashboard setup and login
- Launch/terminate an instance with the dashboard
- Managing projects and users with the dashboard
- VNC access to instances through 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, openstack-cinder 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.