Open Stack

Team,

To recap:
* We have devstack/devstack-gate/tempest/rally have all gotten updates
to support python 3.5
* We have a bunch of jobs already running as non-voting against master branches:
    gate-devstack-dsvm-py35-updown-ubuntu-xenial-nv
    gate-rally-dsvm-py35-cinder-nv
    gate-rally-dsvm-py35-glance-nv
    gate-heat-dsvm-functional-orig-mysql-lbaasv2-py35-ubuntu-xenial-nv
    gate-keystone-dsvm-py35-functional-v3-only-ubuntu-xenial-nv
    gate-rally-dsvm-py35-neutron-neutron-ubuntu-xenial-nv
    gate-nova-tox-db-functional-py35-ubuntu-xenial
    gate-rally-dsvm-py35-rally-nova-nv
* Work is being tracked at
https://etherpad.openstack.org/p/support-python3.5-functional-tests
please use that to coordinate

It should now be easy quickly define new jobs and to spot what fails
under python3.5.

Hope this exercise over the last 2 weeks will help us all with our
collective Pike goal.

It's time to turn this over to all the individual projects. Please
don't hesitate to ping me if you need a hand with something.

Thanks,
Dims


On Sun, Jan 8, 2017 at 2:27 PM, Davanum Srinivas <davanum at gmail.com> wrote:
> Folks,
>
> Here's where we track the work for a little while:
> https://etherpad.openstack.org/p/support-python3.5-functional-tests
>
> There's lots of work to be done to get stuff working properly. What we
> have now is the ability to just startup a bunch of services using
> py35. Does not mean they all work.
>
> Teams that do not have functional tests in their own projects may
> still be able to look for, find and fix bugs. Example, the heat
> functional tests exercises Nova, Oslo etc. So look for tracebacks
> there and get going!
>
> This is a good chance for newbies to get involved as well. Find a
> traceback to fix, propose a fix with a python3 unit test :)
>
> Thanks,
> Dims
>
> --
> Davanum Srinivas :: https://twitter.com/dims



-- 
Davanum Srinivas :: https://twitter.com/dims