|OpenStack Test Day|
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Pbrady (pixelbeat)
- Mrunge (mrunge)
- Eglynn (eglynn)
- Apevec (apevec)
- GKotton (garyk)
- eharney (eharney)
- Vaneldik (vaneldik)
- spstarr (spstarr)
- kashyapc (Kashyap Chamarthy)
- spstarr (Shawn Starr)
- mrceresa (Mario Ceresa)
- mkollaro (Martina Kollarova)
- mpavlase (Martin Pavlasek)
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 19 test day, but we have OpenStack Grizzly packages available for both Fedora 19 and Fedora 18. It would be advisable to download and install your Fedora 18 or Fedora 19 test systems before the test day if possible.
- Fedora 19 Alpha live image can be used to install a virtual machine.
- TC2 doesn't support bare metal installs, but TC3 should #928228
- For the live install, VMs should have at least 2G RAM and 16G disk made available #928886
Please record common Fedora 19 issues here:
- System doesn't boot after install until /run is manually created #922988
- Screen blanking/locking can't be undone. So disable immediately on first boot #923364
- If you have an F18, machine, you can update to f19 using:
yum update yum; yum clean all ; yum --releasever=19 distro-sync --nogpgcheck -y;
Recent Fedora 18 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 clean all sudo yum --enablerepo=updates-testing update -y
SELinux should work with OpenStack services. If there are issues you can disable like:
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:
- RHBZ #123456 general - ....
Install and setup all Openstack services on a single node
Test day only Please use the official Fedora repositories otherwise
sudo curl http://repos.fedorapeople.org/repos/openstack/openstack-grizzly/fedora-openstack-grizzly.repo -o /etc/yum.repos.d/fedora-openstack-grizzly.repo
So now the yum repositories are in place, so we'll install packstack. This can install all OpenStack services on a single node, including: nova, glance, quantum, cinder, swift, keystone, dashboard, ceilometer. Note it configures and enables all but the quantum and ceilometer services at this time: Packstack is not working on F19 https://bugzilla.redhat.com/show_bug.cgi?id=927298
sudo yum install -y openstack-packstack sudo packstack --gen-answer-file=ans.txt # edit ans.txt as required sudo packstack --answer-file=ans.txt
packstack known issues :
# packstack fails to start keystone, if you hit a keystone error during the packstack run, change the permission of the keystone log file and rerun packstack (rhbz#946915) sudo chown keystone:keystone /var/log/keystone/keystone.log # if sometimes outputs an erorr when trying to start tdtd if this happens start it manually and rerun packstack sudo systemctl start tgtd
Alternatively one can use the openstack-demo-install script to do the install:
sudo yum install -y openstack-utils sudo openstack-demo-install
Note this is a major test in itself, so please record any issues encountered.
Now copy the keystonerc file created by the install script above to your home directory, so that it can be easily sourced to provide the credentials used by the various OpenStack command line utilities.
sudo cp /root/keystonerc ~ # or if using packstack sudo cp /root/keystonerc_admin ~
Setup OpenStack volumes
The OpenStack volume service provides persistent block level storage to instances.
This is a commonly used service automatically setup by packstack. If you ran openstack-demo-install instead please enable by following:
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.
Note if packstack was used then you need to terminate nova networking. This is done as follows:
service openstack-nova-network stop chkconfig openstack-nova-network off
- Create a builder instance
- Create and boot from a bootable volume
- Create an image from a running volume-backed instance
- 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
Heat basic functionality
- Basic heat setup and configuration
- Launch a basic wordpress stack
- Stop Heat services and uninstall Heat
Heat advanced functionality
- Run nose unit tests
- Run Load Balancing testcase
- Run Relational Database service testcase
- Run EIP testcase
- Run EBS testcase
- Run EBS and EIP testcase
- Run Single Instance Wordpress testcase
- Run Compsed Instances testcase
- Run 2 instance EBS testcase
- Run 2 instances with EBS and EIP
- Run 2 instance Wordpress testcase
- Run HAProxy Single Instance testcase
- Run CFN API actions testcase
- Run AutoScaling testcase
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,openstack-quantum, openstack-swift or openstack-heat or openstack-ceilometer 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||openstack-demo-install||Create Cinder Volumes||Add SSH keypair||Register images||Create nova network||References|
|User||Launch an instance||Attach a volume||Floating IPs||Separate compute node||References|
|User||Create a builder instance||Create and boot from a bootable volume||Create an image from a running volume-backed instance||References|
|User||Configure and use a network topology in Quantum||References|
|User||Upload and download files||Upload Segmented File||Test Auditor/Replicator||Add Storage Device to ring||References|
|User||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||References|
|User||Basic heat setup and login||Launch a basic wordpress stack||Stop Heat services and uninstall Heat||References|
|User||Install ceilometer||Enable metering of glance||Enable metering of nova||Explore the metering store||References|
|User||Tempest tests||Build an image with Oz||Smoke tests||References|
- If you get a wrong ip on the instance, remember to check if packstack silently configured an additional network or if the default nework of libvirtd is active
- horizon starts but halts when logging in. Setting DEBUG=true in local_settings showed that python-cinderclient hits the same error as in RHBZ #947463