Pike Test Day 3

We will be holding a RDO test day on August 3 and 4, 2017.

This will be coordinated through the #rdo channel on Freenode, and through this website and the rdo-list mailing list.

We'll be testing the second Pike milestone release. If you can do any testing on your own ahead of time, that will help ensure that everyone isn't encountering the same problems.

We will also be available for people that want to try the stable (Newton) release.


We plan to have packages for the following platforms:

You'll want a fresh install with latest updates installed. (Fresh so that there's no hard-to-reproduce interactions with other things.)

How to test?

$ yum -y install yum-plugin-priorities
$ cd /etc/yum.repos.d/
$ sudo curl -O https://trunk.rdoproject.org/centos7/delorean-deps.repo
$ sudo curl -O https://trunk.rdoproject.org/centos7/current-passed-ci/delorean.repo
$ sudo yum update -y
  • These steps apply to both RHEL 7 and CentOS 7.

Next steps

Test cases and results

The scenarios that should be tested are listed on the test matrix page. This will be copied to an etherpad the day of the test, for easier annotation during the event.

  1. Pick an item from the list.
  2. Go through the scenario as though you were a beginner, just following the instructions. (Check the workarounds page for problems that others may have encountered and resolved.)
  3. Keep good notes. You can use the test day etherpad for these notes. Reviewing other peoples' notes may help you avoid problems that they've already encountered.

If you have problems with any of the tests, report a bug to Bugzilla usually for one of the openstack-packstack, openstack-nova, openstack-glance, openstack-keystone, openstack-cinder, openstack-neutron, openstack-swift, python-django-horizon, 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 (#rdo, freenode.net) and we will help you.

Once you have completed the tests, add your results to the table on the test matrix page, following the examples already there. Be sure to check the workarounds page for things that may have already have fixes or workarounds.