Open Stack

Hello,

On August 20th the Infra team will be switching the default test node
from Ubuntu Precise to Ubuntu Trusty. This means that `tox -epy27`, `tox
-ecover`, `tox -epep8`, `tox -evenv -- python setup.py build_sphinx`
will run on Trusty build nodes intead of Precise nodes. This will not
affect python 2.6 or 3.3 tests as they will remain on Centos6 and
Precise as that is where those python versions are available.

Many projects have made the the switch to Trusty already and it has been
painless for the most part. The only things we have run into so far are
apache 2.2 vs apache 2.4 differences and Solum had rabbitmq problems in
their functional test on Trusty (this test will not move to Trusty as
part of this). If your project has not already made the transition to
Trusty you can make sure you are prepared by running `tox -epy27`, `tox
-epep8`, and `tox -evenv -- python setup.py build_sphinx`. I have been
trying to do this for as many projects as I can but only have so much
time :) your help is appreciated.

We will also be upgrading tox on our test slaves to tox 1.7.2. We have
pinned to version 1.6.1 for a long time because 1.7.0 broke
compatibility with many of our tox.ini files. That problem has since
been fixed but another minor issue has cropped up in 1.7.0. Details are
at
http://lists.openstack.org/pipermail/openstack-dev/2014-July/041283.html.
TL;DR is if your tests cannot handle a random python hashseed value you
will need to fix your tests or merge a change like
https://review.openstack.org/#/c/109700/ to your project. Again, I have
done my best to poke at this for as many projects as I can but there are
so many of them. Your help is appreciated with this as well.

Upgrading tox is important so that we can stop relying on a specific
version of tox that developers need to know to install. It will also
allow us to move our py33 testing to py34 on Trusty which gives python3
testing a long term home.

If you have any questions let me know. Thanks again,
Clark