[openstack-dev] [tripleo] Recap of Python 3 testing session at PTG

Alfredo Moralejo Alonso amoralej at redhat.com
Tue Mar 20 17:29:25 UTC 2018

On Sat, Mar 17, 2018 at 9:34 AM, Emilien Macchi <emilien at redhat.com> wrote:

> During the PTG we had some nice conversations about how TripleO can make
> progress on testing OpenStack deployments with Python 3.
> In CC, Haikel, Alfredo and Javier, please complete if I missed something.
> ## Goal
> As an OpenStack distribution, RDO would like to ensure that the OpenStack
> services (which aren't depending on Python 2) are packaged and can be
> containerized to be tested in TripleO CI.

> ## Challenges
> - Some services aren't fully Python 3, but we agreed this was not our
> problem but the project's problems. However, as a distribution, we'll make
> sure to ship what we can on Python 3.
> - CentOS 7 is not the Python 3 distro and there are high expectations from
> the next release but we aren't there yet.
> - Fedora is Python 3 friendly but we don't deploy TripleO on Fedora, and
> we don't want to do it (for now at least).
> To be clear, python3 packages will be only provided for Fedora ini RDO
Trunk repos and, unless it's explicitely changed in future, RDO's policy
is not to support deployments in Fedora using python2 nor python3. The main
goal of this effort is to make transition to python3 smoother in future
CentOS releases and using fedora as a testbed for it.

> ## Proposal
> - A fedora stabilized repository will be created by RDO to provide a
stable and working set of fedora packages to run RDO OpenStack services
using python3.

- Continue to follow upstream projects who support Python3 only and ship
> rpms in RDO.
> - Investigate the build of Kolla containers on Fedora / Python 3 and push
> them to a registry (maybe in the same namespace with different name or
> maybe a new namespace).
> - Kick-off some TripleO CI experimental job that will use these containers
> to deploy TripleO (maybe on one basic scenario for now).
> ## Roadmap for Rocky
> For Rocky we agreed to follow the 3 steps part of the proposal (maybe
> more, please add what I've missed).
The services enabled for python3  during rocky will depend on the progress
of the different tasks and i guess we will adapt the order of the services
depending on the technical issues we find.

> That way, we'll be able to have some early testing on python3-only
> environments (thanks containers!) without changing the host OS.
> Just for awareness, we may hit issues running services closely coupled to
kernel modules as openvswitch.

> Thanks for your feedback and comments, it's an open discussion.
> --
> Emilien Macchi

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180320/c4bc667d/attachment.html>

More information about the OpenStack-dev mailing list