Open Stack

As far as I always like the idea of dropping Python 2, I dread more
the potential mayhem that this will bring in bifrost stable branches.
If this change needs to move forward, we need to be sure of the impact
and have a plan in place *before* the change happen.

On Tue, May 19, 2020 at 9:20 AM Mark Goddard <mark at stackhpc.com> wrote:
>
> On Mon, 18 May 2020 at 16:56, Iury Gregory <iurygregory at gmail.com> wrote:
> >
> > @Pierre, I think we can change stable branches in bifrost to use a specific tag from diskimage-builder and the problem would be solved =)
>
> I would urge caution over dropping Python 2 from branchless projects.
> We tried it for Tenks, and within weeks had created a branch from the
> last release supporting Python 2 for bug fixes.
>
> >
> > Em seg., 18 de mai. de 2020 às 17:28, Pierre Riteau <pierre at stackhpc.com> escreveu:
> >>
> >> This might break bifrost stable branches, as bifrost uses DIB from master by default, even for older releases.
> >>
> >> On Mon, 18 May 2020 at 15:41, Monty Taylor <mordred at inaugust.com> wrote:
> >>>
> >>> Heya,
> >>>
> >>> I just pushed up:
> >>>
> >>>   https://review.opendev.org/728889 Drop support for python2
> >>>
> >>> Which drops support for installing diskimage-builder using python2. It doesn’t drop support for in-image python2, that would be a whole different story. It seems that since the two largest DIB users, OpenStack and Zuul, are both now python3 only, it’s a safe move to make.
> >>>
> >>> IBM PowerKVM CI is running third-party CI with python2-based tests. We should probably either update those or just drop it?
> >>>
> >>> Thoughts?
> >>> Monty
> >
> >
> >
> > --
> > Att[]'s
> > Iury Gregory Melo Ferreira
> > MSc in Computer Science at UFCG
> > Part of the puppet-manager-core team in OpenStack
> > Software Engineer at Red Hat Czech
> > Social: https://www.linkedin.com/in/iurygregory
> > E-mail:  iurygregory at gmail.com
>