Tools » teuthology

Tags: py3 python3 support migration

1. Gradually make teuthology code base py2/py3 compatible to avoid sepia lab out of service as much as possible
2. Make ceph qa/tasks and related code be py3 compatible for release branches like master (octopus), nautilus, mimic, luminous (this is required because in the workunit and tasks code is executed by a worker which is supposed to be the same virtualenv as teuthology/worker.
3. Add py3 deployment test to CI and manage the teuthology to work in py3 virtual env some basic test and later more complicated
4. Try and switch sepia teuthology server to py3
5. Wipe out py2 usage from teuthology code completely