On Fri, Aug 17, 2018 at 5:18 PM, Alex Schultz <aschultz at redhat.com> wrote: > Ahoy folks, > > In order to get to a spot where can start evaluate the current status > of TripleO under python3 I've thrown together a set of ansible > playbooks[0] to launch a fedora28 node and build the required > python-tripleoclient (and dependencies) These playbooks will spawn a > VM on an OpenStack cloud, runs through the the steps from the RDO > etherpad[1] for using the fedora stablized repo and builds all the > currently outstanding python3 package builds[2] for > python-tripleoclient & company. Once the playblook has completed it > should be at a spot to 'dnf install python3-tripleoclient'. > > I believe from here we can focus on getting the undercloud[3] and > standalone[4] processes working correctly under python3. I think > initially we should use the existing CentOS7 containers we build under > the existing processes to see if we can't get the services deployed as > we work on building out all the required python3 packaging. > To follow up, I've started an etherpad[0] to track the various issues related to the python3 version of tripleoclient. [0] https://etherpad.openstack.org/p/tripleo-python3-tripleoclient-issues > Thanks, > -Alex > > [0] https://github.com/mwhahaha/tripleo-f28-testbed > [1] https://review.rdoproject.org/etherpad/p/use-fedora-stabilized > [2] https://review.rdoproject.org/r/#/q/status:open+owner:%22Alex+Schultz+%253Caschultz%2540next-development.com%253E%22+topic:python3 > [3] https://docs.openstack.org/tripleo-docs/latest/install/installation/installation.html > [4] https://docs.openstack.org/tripleo-docs/latest/install/containers_deployment/standalone.html