Test Day:2013-04-02 OpenStack

OpenStack Test Day
Date	2013-04-02
Time	all day
IRC	#fedora-test-day (webirc)

Can't make the dates?
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.

Who's available

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

• Development - Pbrady (pixelbeat)
• Development - Mrunge (mrunge)
• Development - Eglynn (eglynn)
• Development - Apevec (apevec)
• Development - GKotton (garyk)
• Development - eharney (eharney)
• Deployment - Vaneldik (vaneldik), spstarr (spstarr)
• Test - kashyapc (kashyap), spstarr (spstarr)

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.

Hardware Requirements
You can do basic testing of OpenStack in a virtual machine, which is auto detected by the install script below

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

• Fedora 19 Alpha live image can be used to install a virtual machine.
• Currently bare metal installs are not supported #928228
• 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, since F19 is branched, you can update to f19 using the below way:

yum update yum; yum clean all ; yum --releasever=19 distro-sync --nogpgcheck -y;

Fedora 18

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.

Configure sudo

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

SELinux

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:

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

Enable Quantum networking

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

Test Cases

Basic setup:

1. Add SSH keypair
2. Register guest images
3. Create nova network

Core functionality:

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

Nova boot-from-volume:

1. Create a builder instance
2. Create and boot from a bootable volume
3. Create an image from a running volume-backed instance

Quantum functionality:

1. Configure and use a network topology in Quantum

Swift functionality:

1. Upload and download files
2. Upload Segmented File
3. Test Auditor/Replicator
4. Add Storage Device to ring

Dashboard functionality:

1. Basic dashboard setup and login
2. Launch/terminate an instance with the dashboard
3. Managing projects and users with the dashboard
4. VNC access to instances through the dashboard

Heat basic functionality (recommended for all developers):

1. Basic heat setup and configuration
2. Launch a basic wordpress stack
3. Stop Heat services and uninstall Heat

Heat advanced functionality (recommended for all developers):

1. Run nose unit tests
2. Run Load Balancing testcase
3. Run Relational Database service testcase
4. Run EIP testcase
5. Run EBS testcase
6. Run EBS and EIP testcase
7. Run Single Instance Wordpress testcase
8. Run Compsed Instances testcase
9. Run 2 instance EBS testcase
10. Run 2 instances with EBS and EIP
11. Run 2 instance Wordpress testcase
12. Run HAProxy Single Instance testcase
13. Run CFN API actions testcase
14. Run AutoScaling testcase

Ceilometer functionality (recommended for all developers):

1. Install ceilometer
2. Enable metering of glance
3. Enable metering of nova

Extra credit:

1. Tempest tests
2. Build an image with Oz
3. 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, 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.

Basic setup:

User	openstack-demo-install	Create Cinder Volumes	Add SSH keypair	Register images	Create nova network	References
Sample User	none	none	pass	warn	fail
Rami Vaknin	none Packstack installation fails due to "/etc/init.d/xinetd reload" command that it runs	none	none	none	fail
Rami Vaknin	none Packstack installation fails due to syntax error in /etc/httpd/conf.d/ssl.conf (Fedora bug)	none	none	none	fail
Mario Ceresa	none Packstack on f18 VM	pass	pass	warn Directly register a Fedora 16 appliance image got stuck for more than 2h with no network activity on iftop tty images failed with "Could not resolve host: images.ansolabs.com; Name or service not known" Manually downloading a cirros image + glance add name=cirros is_public=true disk_format=qcow2 container_format=bare < cirros-0.3.0-x86_64-disk.img worked.	pass

Core functionality:

User	Launch an instance	Attach a volume	Floating IPs	Separate compute node	References
Mario Ceresa	pass	fail	none	pass

Nova boot-from-volume:

User	Create a builder instance	Create and boot from a bootable volume	Create an image from a running volume-backed instance	References

Quantum functionality:

User	Configure and use a network topology in Quantum	References

Swift functionality:

User	Upload and download files	Upload Segmented File	Test Auditor/Replicator	Add Storage Device to ring	References

Dashboard functionality:

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
Mario Ceresa	fail	none	none	none

heat functionality:

User	Basic heat setup and login	Launch a basic wordpress stack	Stop Heat services and uninstall Heat	References

Ceilometer functionality:

User	Install ceilometer	Enable metering of glance	Enable metering of nova	References
Eoghan Glynn	pass	pass	pass

Extra credit:

User	Tempest tests	Build an image with Oz	Smoke tests	References