Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Hi, Le 13/07/2016 à 21:17, Denis Makogon a écrit : I have free capacity to work on porting code to Py3. So, if any PTL is running out of team capacity i can help to work on project to enable Py3 support. If you would like to help, you can try to run functional tests on DevStack. Begin with projects which have their unit tests already ported to Python 3. https://wiki.openstack.org/wiki/Python3#Functional_and_Integration_Tests Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Hello to All. I have free capacity to work on porting code to Py3. So, if any PTL is running out of team capacity i can help to work on project to enable Py3 support. Kind regards, Denys Makogon 2016-07-06 13:01 GMT+03:00 Flavio Percoco: > On 24/06/16 12:17 -0400, Sean Dague wrote: > >> On 06/24/2016 11:48 AM, Doug Hellmann wrote: >> >>> Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200: >>> On 06/23/2016 11:21 PM, Clark Boylan wrote: > On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: > >> Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: >> >>> On 06/23/2016 06:11 PM, Doug Hellmann wrote: >>> I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. As Tony points out, it's a bit late to have this as a priority for Newton, though work can and should continue. But given how close we are to having the initial phase of the port done (thanks Victor!), and how far we are from discussions of priorities for Ocata, it seems very reasonable to set a community-wide goal for our next release cycle. Thoughts? Doug >>> >>> +1 >>> >>> Just think about it for a while. If we get Nova to work with Py3, and >>> everything else is working, including all functional tests in >>> Tempest, >>> then after Otaca, we could even start to *REMOVE* Py2 support after >>> Otaca+1. That would be really awesome to stop all the compat layer >>> madness and use the new features available in Py3. >>> >> >> We'll need to get some input from other distros and from deployers >> before we decide on a timeline for dropping Python 2. For now, let's >> focus on making Python 3 work. Then we can all rejoice while having >> the >> discussion of how much longer to support Python 2. :-) >> >> >>> I really would love to ship a full stack running Py3 for Debian >>> Stretch. >>> However, for this, it'd be super helful to have as much visibility as >>> possible. Are we setting a hard deadline for the Otaca release? Or is >>> this just a goal we only "would like" to reach, but it's not really a >>> big deal if we don't reach it? >>> >> >> Let's see what PTLs have to say about planning, but I think if not >> Ocata then we'd want to set one for the P release. We're running >> out of supported lifetime for Python 2.7. >> > > Keep in mind that there is interest in running OpenStack on PyPy which > is python 2.7. We don't have to continue supporting CPython 2.7 > necessarily but we may want to support python 2.7 by way of PyPy. > PyPy folks have been working on python 3 support for some time already: http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html It's an alpha, but by the time we consider dropping Python 2 it will probably be released :) >>> >>> We're targeting Python >=3.4, right now. We'll have to decide as >>> a community whether PyPy support is a sufficient reason to keep >>> support for "older" versions (either 2.x or earlier versions of 3). >>> Before we can have that discussion, though, we need to actually run on >>> Python 3, so let's focus on that and evaluate the landscape of other >>> interpreters when the porting work is done. >>> >> >> +1, please don't get ahead of things until there is real full stack >> testing running on python3. >> >> It would also be good if some of our operators were running on python 3 >> and providing feedback that it works in the real world before we even >> talk about dropping. Because our upstream testing (even the full stack >> testing) only can catch so much. >> >> So next steps: >> >> 1) full stack testing of everything we've got on python3 - (are there >> volunteers to get that going?) >> 2) complete Nova port to enable full stack testing on python3 for iaas >> base >> 3) encourage operators to deploy with python3 in production >> 4) gather real world feedback, develop rest of plan >> > > > Just one to +1 the above steps. I'd be very hesitant to make any plan > until we > are able to get not only nova but all the projects in the > starter-kit:compute[0] > running pn python3 (and w/ a full stack test). > > [0] > https://governance.openstack.org/reference/tags/starter-kit_compute.html > > > Flavio > > -- > @flaper87 > Flavio Percoco > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ OpenStack Development Mailing List (not for usage
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 24/06/16 12:17 -0400, Sean Dague wrote: On 06/24/2016 11:48 AM, Doug Hellmann wrote: Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200: On 06/23/2016 11:21 PM, Clark Boylan wrote: On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: On 06/23/2016 06:11 PM, Doug Hellmann wrote: I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. As Tony points out, it's a bit late to have this as a priority for Newton, though work can and should continue. But given how close we are to having the initial phase of the port done (thanks Victor!), and how far we are from discussions of priorities for Ocata, it seems very reasonable to set a community-wide goal for our next release cycle. Thoughts? Doug +1 Just think about it for a while. If we get Nova to work with Py3, and everything else is working, including all functional tests in Tempest, then after Otaca, we could even start to *REMOVE* Py2 support after Otaca+1. That would be really awesome to stop all the compat layer madness and use the new features available in Py3. We'll need to get some input from other distros and from deployers before we decide on a timeline for dropping Python 2. For now, let's focus on making Python 3 work. Then we can all rejoice while having the discussion of how much longer to support Python 2. :-) I really would love to ship a full stack running Py3 for Debian Stretch. However, for this, it'd be super helful to have as much visibility as possible. Are we setting a hard deadline for the Otaca release? Or is this just a goal we only "would like" to reach, but it's not really a big deal if we don't reach it? Let's see what PTLs have to say about planning, but I think if not Ocata then we'd want to set one for the P release. We're running out of supported lifetime for Python 2.7. Keep in mind that there is interest in running OpenStack on PyPy which is python 2.7. We don't have to continue supporting CPython 2.7 necessarily but we may want to support python 2.7 by way of PyPy. PyPy folks have been working on python 3 support for some time already: http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html It's an alpha, but by the time we consider dropping Python 2 it will probably be released :) We're targeting Python >=3.4, right now. We'll have to decide as a community whether PyPy support is a sufficient reason to keep support for "older" versions (either 2.x or earlier versions of 3). Before we can have that discussion, though, we need to actually run on Python 3, so let's focus on that and evaluate the landscape of other interpreters when the porting work is done. +1, please don't get ahead of things until there is real full stack testing running on python3. It would also be good if some of our operators were running on python 3 and providing feedback that it works in the real world before we even talk about dropping. Because our upstream testing (even the full stack testing) only can catch so much. So next steps: 1) full stack testing of everything we've got on python3 - (are there volunteers to get that going?) 2) complete Nova port to enable full stack testing on python3 for iaas base 3) encourage operators to deploy with python3 in production 4) gather real world feedback, develop rest of plan Just one to +1 the above steps. I'd be very hesitant to make any plan until we are able to get not only nova but all the projects in the starter-kit:compute[0] running pn python3 (and w/ a full stack test). [0] https://governance.openstack.org/reference/tags/starter-kit_compute.html Flavio -- @flaper87 Flavio Percoco signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/24/2016 12:13 PM, Amrith Kumar wrote: >> -Original Message- >> From: Doug Hellmann [mailto:d...@doughellmann.com] >> Sent: Thursday, June 23, 2016 5:16 PM >> To: openstack-dev <openstack-dev@lists.openstack.org> >> Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3 >> > [... snip ...] >> >> Let's see what PTLs have to say about planning, but I think if not >> Ocata then we'd want to set one for the P release. We're running >> out of supported lifetime for Python 2.7. >> >> Doug >> > > Doug, I believe py27 will be supported till end of 2020 but distribution > vendors (os people) are not yet deploying py3 as the default. *I* am not (in Debian) doing Py3 by default because there's no functional test yet. As soon as there is, and I can prove that Debian packages can work with Py3, I'll flip the switch. > Could someone share the best information on when we may see Python3 > be the default from the various os distribution providers. In Debian, we're suppose to deprecate Py3 in Stretch (aka: Debian 9, the next stable, currently testing), and remove support for Py3 in Buster (aka: Debian 10). From my stand point, the sooner we switch to Py3 the better. On 06/24/2016 05:43 PM, Doug Hellmann wrote: > Some of the distros are starting to split the version of python > they use for their operating system tools from the packages > applications use, so the "default" version of Python isn't necessarily > what we care about Exactly! What counts isn't what interpreter (ie: Py2 or Py3) is the default implementation for /usr/bin/python. What counts is what we decide to use for as shebang for let's say /usr/bin/trove-conductor. That, I can switch to Py3 whenever I decide. On 06/24/2016 12:13 PM, Amrith Kumar wrote: > The date of 2020 for EOS leads me to believe that we're good until about > the U or V release (assuming two per year) but I don't believe that's > the correct way to plan for this, yes? That would be significantly too late from a distribution vendor perspective. For Debian, we will have Stretch frozen early next year, so Buster may be frozen in 2019, but we may remove Py2 before that. So, IMO, it'd be reasonable to at least deprecate Py2 support for the "Q" release of OpenStack (that's the first release of 2018). So, altogether, it would make a lot of sense to make sure everything is working correctly with Py3 for the O or P release of OpenStack, so we have enough time to make sure everything is in order. Therefore, the current goal of having everything (including functional tests) Py3 ready for the O release is completely realistic, so we can have all functional tests gating on Py3 for the P release. On 06/24/2016 05:10 PM, Clint Byrum wrote: > Fedora, Ubuntu, and Gentoo are already defaulting to python3 for all > of their OS tools, so you can have a fully functioning system without > python2. Debian doesn't have Python in its default install (ie: if you debootstrap a system without additional packages, Python isn't there). Our own tooling are in the way of being ported, and even most are indeed already Py3 by default (python3-debian is a good example). On 06/24/2016 10:25 AM, Daniel P. Berrange wrote: > Please lets not derail discussions about completing Py3 support by > opening up the can of worms wrt dropping Py2. The point I was trying to make is that the foreseeable drop of Py2 should be a great incentive to quickly finish the work on Py3, so we can use features only seen on Py3. And indeed, dropping Py2 can only happen after everything fully runs on Py3, including in distros and deployments. Cheers, Thomas Goirand (zigo) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 27 June 2016 at 13:20, Jens Rosenboomwrote: > 2016-06-22 9:18 GMT+02:00 Victor Stinner : >> Hi, >> >> Current status: only 3 projects are not ported yet to Python 3: >> >> * nova (76% done) >> * trove (42%) >> * swift (0%) >> >>https://wiki.openstack.org/wiki/Python3 > > How should differences between python3.4 and python3.5 be handled? Like most minor version differences - write code that handles them. The test in https://bugs.launchpad.net/neutron/+bug/1559191is overly literal, since it depends on the string of the error from Python, which is not a stable interface -Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
2016-06-22 9:18 GMT+02:00 Victor Stinner: > Hi, > > Current status: only 3 projects are not ported yet to Python 3: > > * nova (76% done) > * trove (42%) > * swift (0%) > >https://wiki.openstack.org/wiki/Python3 How should differences between python3.4 and python3.5 be handled? Ubuntu Xenial contains only python3.5 and no packages for 3.4 anymore, so when planning to run services with python3, one would have to support 3.5, but there are unsolved issues like https://bugs.launchpad.net/neutron/+bug/1559191 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/24/2016 11:48 AM, Doug Hellmann wrote: > Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200: >> On 06/23/2016 11:21 PM, Clark Boylan wrote: >>> On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: >> I'd like for the community to set a goal for Ocata to have Python >> 3 functional tests running for all projects. >> >> As Tony points out, it's a bit late to have this as a priority for >> Newton, though work can and should continue. But given how close >> we are to having the initial phase of the port done (thanks Victor!), >> and how far we are from discussions of priorities for Ocata, it >> seems very reasonable to set a community-wide goal for our next >> release cycle. >> >> Thoughts? >> >> Doug > > +1 > > Just think about it for a while. If we get Nova to work with Py3, and > everything else is working, including all functional tests in Tempest, > then after Otaca, we could even start to *REMOVE* Py2 support after > Otaca+1. That would be really awesome to stop all the compat layer > madness and use the new features available in Py3. We'll need to get some input from other distros and from deployers before we decide on a timeline for dropping Python 2. For now, let's focus on making Python 3 work. Then we can all rejoice while having the discussion of how much longer to support Python 2. :-) > > I really would love to ship a full stack running Py3 for Debian Stretch. > However, for this, it'd be super helful to have as much visibility as > possible. Are we setting a hard deadline for the Otaca release? Or is > this just a goal we only "would like" to reach, but it's not really a > big deal if we don't reach it? Let's see what PTLs have to say about planning, but I think if not Ocata then we'd want to set one for the P release. We're running out of supported lifetime for Python 2.7. >>> >>> Keep in mind that there is interest in running OpenStack on PyPy which >>> is python 2.7. We don't have to continue supporting CPython 2.7 >>> necessarily but we may want to support python 2.7 by way of PyPy. >> >> PyPy folks have been working on python 3 support for some time already: >> http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html >> It's an alpha, but by the time we consider dropping Python 2 it will >> probably be released :) > > We're targeting Python >=3.4, right now. We'll have to decide as > a community whether PyPy support is a sufficient reason to keep > support for "older" versions (either 2.x or earlier versions of 3). > Before we can have that discussion, though, we need to actually run on > Python 3, so let's focus on that and evaluate the landscape of other > interpreters when the porting work is done. +1, please don't get ahead of things until there is real full stack testing running on python3. It would also be good if some of our operators were running on python 3 and providing feedback that it works in the real world before we even talk about dropping. Because our upstream testing (even the full stack testing) only can catch so much. So next steps: 1) full stack testing of everything we've got on python3 - (are there volunteers to get that going?) 2) complete Nova port to enable full stack testing on python3 for iaas base 3) encourage operators to deploy with python3 in production 4) gather real world feedback, develop rest of plan -Sean -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Excerpts from Daniel P. Berrange's message of 2016-06-24 09:25:35 +0100: > On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote: > > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > > I'd like for the community to set a goal for Ocata to have Python > > > 3 functional tests running for all projects. > > > > > > As Tony points out, it's a bit late to have this as a priority for > > > Newton, though work can and should continue. But given how close > > > we are to having the initial phase of the port done (thanks Victor!), > > > and how far we are from discussions of priorities for Ocata, it > > > seems very reasonable to set a community-wide goal for our next > > > release cycle. > > > > > > Thoughts? > > > > > > Doug > > > > +1 > > > > Just think about it for a while. If we get Nova to work with Py3, and > > everything else is working, including all functional tests in Tempest, > > then after Otaca, we could even start to *REMOVE* Py2 support after > > Otaca+1. That would be really awesome to stop all the compat layer > > madness and use the new features available in Py3. > > Please lets not derail discussions about completing Py3 support by > opening up the can of worms wrt dropping Py2. > > Lets get the Py3 support completed and in the hands of users and > proven acceptable before we talk about dropping support for the python > platform that every single deployment runs on today. > > > Regards, > Daniel +1 Let's take this one step at a time. Those steps are big and take time, during which a lot of other things may change. When we're ready to claim full support for Python 3, then we'll look at the current support ecosystem and discuss dropping support for 2. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 23/06/16 12:11 -0400, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: On 06/22/2016 09:18 AM, Victor Stinner wrote: > Hi, > > Current status: only 3 projects are not ported yet to Python 3: > > * nova (76% done) > * trove (42%) > * swift (0%) > >https://wiki.openstack.org/wiki/Python3 > > Number of projects already ported: > > * 19 Oslo Libraries > * 4 Development Tools > * 22 OpenStack Clients > * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) > * 12 OpenStack services approved by the TC > * 17 OpenStack services (not approved by the TC) > > Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, > we are so close! ;-) > > The next steps are to port the 3 remaining projects and work on > functional and integration tests on Python 3. > > Victor Hi Victor, Thanks a lot for your efforts on Py3. Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? Cheers, Thomas Goirand (zigo) I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. As Tony points out, it's a bit late to have this as a priority for Newton, though work can and should continue. But given how close we are to having the initial phase of the port done (thanks Victor!), and how far we are from discussions of priorities for Ocata, it seems very reasonable to set a community-wide goal for our next release cycle. Thoughts? Sounds good to me! We should start working with PTL's/Teams in advance to make sure we have enough attendance at the summit session to (I'd hope to see one happening, at least) so that we can work on a more realistic plan for Ocata. Flavio -- @flaper87 Flavio Percoco signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200: > On 06/23/2016 11:21 PM, Clark Boylan wrote: > > On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: > >> Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > >>> On 06/23/2016 06:11 PM, Doug Hellmann wrote: > I'd like for the community to set a goal for Ocata to have Python > 3 functional tests running for all projects. > > As Tony points out, it's a bit late to have this as a priority for > Newton, though work can and should continue. But given how close > we are to having the initial phase of the port done (thanks Victor!), > and how far we are from discussions of priorities for Ocata, it > seems very reasonable to set a community-wide goal for our next > release cycle. > > Thoughts? > > Doug > >>> > >>> +1 > >>> > >>> Just think about it for a while. If we get Nova to work with Py3, and > >>> everything else is working, including all functional tests in Tempest, > >>> then after Otaca, we could even start to *REMOVE* Py2 support after > >>> Otaca+1. That would be really awesome to stop all the compat layer > >>> madness and use the new features available in Py3. > >> > >> We'll need to get some input from other distros and from deployers > >> before we decide on a timeline for dropping Python 2. For now, let's > >> focus on making Python 3 work. Then we can all rejoice while having the > >> discussion of how much longer to support Python 2. :-) > >> > >>> > >>> I really would love to ship a full stack running Py3 for Debian Stretch. > >>> However, for this, it'd be super helful to have as much visibility as > >>> possible. Are we setting a hard deadline for the Otaca release? Or is > >>> this just a goal we only "would like" to reach, but it's not really a > >>> big deal if we don't reach it? > >> > >> Let's see what PTLs have to say about planning, but I think if not > >> Ocata then we'd want to set one for the P release. We're running > >> out of supported lifetime for Python 2.7. > > > > Keep in mind that there is interest in running OpenStack on PyPy which > > is python 2.7. We don't have to continue supporting CPython 2.7 > > necessarily but we may want to support python 2.7 by way of PyPy. > > PyPy folks have been working on python 3 support for some time already: > http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html > It's an alpha, but by the time we consider dropping Python 2 it will > probably be released :) We're targeting Python >=3.4, right now. We'll have to decide as a community whether PyPy support is a sufficient reason to keep support for "older" versions (either 2.x or earlier versions of 3). Before we can have that discussion, though, we need to actually run on Python 3, so let's focus on that and evaluate the landscape of other interpreters when the porting work is done. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/24/2016 10:10 AM, Clint Byrum wrote: > Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: >> >>> -Original Message- >>> From: Doug Hellmann [mailto:d...@doughellmann.com] >>> Sent: Thursday, June 23, 2016 5:16 PM >>> To: openstack-dev <openstack-dev@lists.openstack.org> >>> Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3 >>> >> [... snip ...] >>> >>> Let's see what PTLs have to say about planning, but I think if not >>> Ocata then we'd want to set one for the P release. We're running >>> out of supported lifetime for Python 2.7. >>> >>> Doug >>> >> >> Doug, I believe py27 will be supported till end of 2020 but distribution >> vendors (os people) are not yet deploying py3 as the default. >> >> Could someone share the best information on when we may see Python3 be the >> default from the various os distribution providers. The date of 2020 for EOS >> leads me to believe that we're good until about the U or V release (assuming >> two per year) but I don't believe that's the correct way to plan for this, >> yes? >> > > Fedora, Ubuntu, and Gentoo are already defaulting to python3 for all > of their OS tools, so you can have a fully functioning system without > python2. Also, _defaulting_ to python3 in the distro is different than python3 being available to be installed. Even with Ubuntu Trusty and RHEL7 you can apt-get install python3 | yum install python3. So I do not think it is important whether or not python3 is the default python on the machine. The important thing is that on all of our supported platforms, python3 is easily available. That means that our distros can package OpenStack components and do the things that packages need to do to make sure that they run with python3. We're already at that point, so moving forward with python3 for OpenStack should not be blocked on distro support at this point. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Excerpts from Clint Byrum's message of 2016-06-24 08:10:18 -0700: > Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: > > > > > -Original Message- > > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > > Sent: Thursday, June 23, 2016 5:16 PM > > > To: openstack-dev <openstack-dev@lists.openstack.org> > > > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python > > > 3 > > > > > [... snip ...] > > > > > > Let's see what PTLs have to say about planning, but I think if not > > > Ocata then we'd want to set one for the P release. We're running > > > out of supported lifetime for Python 2.7. > > > > > > Doug > > > > > > > Doug, I believe py27 will be supported till end of 2020 but distribution > > vendors (os people) are not yet deploying py3 as the default. > > > > Could someone share the best information on when we may see Python3 be the > > default from the various os distribution providers. The date of 2020 for > > EOS leads me to believe that we're good until about the U or V release > > (assuming two per year) but I don't believe that's the correct way to plan > > for this, yes? > > > > Fedora, Ubuntu, and Gentoo are already defaulting to python3 for all > of their OS tools, so you can have a fully functioning system without > python2. > That's right. Some of the distros are starting to split the version of python they use for their operating system tools from the packages applications use, so the "default" version of Python isn't necessarily what we care about -- as an application, we're not supposed to use that version. The important thing is that it is possible to get Python 3.4 or 3.5 packages for all of the major distros through normal and supported mechanisms. So, there is no longer any reason to use distro support as a reason to put off porting. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: > > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Thursday, June 23, 2016 5:16 PM > > To: openstack-dev <openstack-dev@lists.openstack.org> > > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3 > > > [... snip ...] > > > > Let's see what PTLs have to say about planning, but I think if not > > Ocata then we'd want to set one for the P release. We're running > > out of supported lifetime for Python 2.7. > > > > Doug > > > > Doug, I believe py27 will be supported till end of 2020 but distribution > vendors (os people) are not yet deploying py3 as the default. > > Could someone share the best information on when we may see Python3 be the > default from the various os distribution providers. The date of 2020 for EOS > leads me to believe that we're good until about the U or V release (assuming > two per year) but I don't believe that's the correct way to plan for this, > yes? > Fedora, Ubuntu, and Gentoo are already defaulting to python3 for all of their OS tools, so you can have a fully functioning system without python2. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Thursday, June 23, 2016 5:16 PM > To: openstack-dev <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3 > [... snip ...] > > Let's see what PTLs have to say about planning, but I think if not > Ocata then we'd want to set one for the P release. We're running > out of supported lifetime for Python 2.7. > > Doug > Doug, I believe py27 will be supported till end of 2020 but distribution vendors (os people) are not yet deploying py3 as the default. Could someone share the best information on when we may see Python3 be the default from the various os distribution providers. The date of 2020 for EOS leads me to believe that we're good until about the U or V release (assuming two per year) but I don't believe that's the correct way to plan for this, yes? -amrith __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/23/2016 11:21 PM, Clark Boylan wrote: On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: On 06/23/2016 06:11 PM, Doug Hellmann wrote: I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. As Tony points out, it's a bit late to have this as a priority for Newton, though work can and should continue. But given how close we are to having the initial phase of the port done (thanks Victor!), and how far we are from discussions of priorities for Ocata, it seems very reasonable to set a community-wide goal for our next release cycle. Thoughts? Doug +1 Just think about it for a while. If we get Nova to work with Py3, and everything else is working, including all functional tests in Tempest, then after Otaca, we could even start to *REMOVE* Py2 support after Otaca+1. That would be really awesome to stop all the compat layer madness and use the new features available in Py3. We'll need to get some input from other distros and from deployers before we decide on a timeline for dropping Python 2. For now, let's focus on making Python 3 work. Then we can all rejoice while having the discussion of how much longer to support Python 2. :-) I really would love to ship a full stack running Py3 for Debian Stretch. However, for this, it'd be super helful to have as much visibility as possible. Are we setting a hard deadline for the Otaca release? Or is this just a goal we only "would like" to reach, but it's not really a big deal if we don't reach it? Let's see what PTLs have to say about planning, but I think if not Ocata then we'd want to set one for the P release. We're running out of supported lifetime for Python 2.7. Keep in mind that there is interest in running OpenStack on PyPy which is python 2.7. We don't have to continue supporting CPython 2.7 necessarily but we may want to support python 2.7 by way of PyPy. PyPy folks have been working on python 3 support for some time already: http://doc.pypy.org/en/latest/release-pypy3.3-v5.2-alpha1.html It's an alpha, but by the time we consider dropping Python 2 it will probably be released :) Clark __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote: > > > Le 23/06/2016 02:42, Tony Breeds a écrit : > > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > > > Do you think it looks like possible to have Nova ported to Py3 during > > > > the Newton cycle? > > > It doesn't depend on me: I'm sending patches, and then I have to wait for > > > reviews. The question is more how to accelerate reviews. > > Clearly I'm far from authorative but given how close we are to R-14 which is > > the Nova non-priority feature freeze[1] and the python3 port isn't listed as > > a priority[2] I'd guess that this wont land in Newton. > > > > [1] > > http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze > > [2] > > http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html > > Well, IIRC we discussed in the previous year on some of those blueprints > (including the Py3 effort) that are not really features (rather refactoring > items) and which shouldn't be hit by the non-priority feature freeze. > That doesn't mean we could merge those anytime of course, but I don't think > we would procedurally -2 them. Certainly anything which is merely fixing unit tests is valid to be merged pretty much any time. Stuff which touches actual functional code can be evaluated on a case by case basis to decide whether it is reasonable to merge at the particular point in the release process we're at. IOW, I see no reason to arbitrarily block Py3 work on non-prio freeze - we'll just carry on with it as part of our natural review process - it'll just have to take back-seat to reviews for priority features. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Le 22/06/2016 à 09:18, Victor Stinner a écrit : Current status: only 3 projects are not ported yet to Python 3: * nova (76% done) * trove (42%) * swift (0%) If you want to help, please review my patches! I sent patches to these projects. Nova: https://review.openstack.org/#/c/332686/ Swift: https://review.openstack.org/#/c/333297/ Trove: https://review.openstack.org/#/c/333262/ https://review.openstack.org/#/c/333267/ https://review.openstack.org/#/c/184400/ PyMySQL! (Since december 2015, Trove already merged 17 of my patches for py3!) Others wrote Python 3 patches, please review these patches too! Nova: https://review.openstack.org/#/q/topic:bp/nova-python3-newton+status:open Swift: https://review.openstack.org/#/q/project:openstack/swift+branch:master+topic:py3+status:open Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a priority for > > Newton, though work can and should continue. But given how close > > we are to having the initial phase of the port done (thanks Victor!), > > and how far we are from discussions of priorities for Ocata, it > > seems very reasonable to set a community-wide goal for our next > > release cycle. > > > > Thoughts? > > > > Doug > > +1 > > Just think about it for a while. If we get Nova to work with Py3, and > everything else is working, including all functional tests in Tempest, > then after Otaca, we could even start to *REMOVE* Py2 support after > Otaca+1. That would be really awesome to stop all the compat layer > madness and use the new features available in Py3. Please lets not derail discussions about completing Py3 support by opening up the can of worms wrt dropping Py2. Lets get the Py3 support completed and in the hands of users and proven acceptable before we talk about dropping support for the python platform that every single deployment runs on today. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Le 23/06/2016 à 23:04, Thomas Goirand a écrit : Just think about it for a while. If we get Nova to work with Py3, and everything else is working, including all functional tests in Tempest, Hum, that's a long list of expectations :-) then after Otaca, we could even start to *REMOVE* Py2 support after Otaca+1. That would be really awesome to stop all the compat layer madness and use the new features available in Py3. Even if everything works well, I disagree that we must drop immediately Python 2 support. We should give time to deployers to prepare their migration to Python 3. We need at least have one cycle *fully* compatible with Python 3 to be able to *prepare* dropping Python 2 support. In practice, we already support Python 2 and Python 3 in the same code base. We already paid the price of supporting both major versions. Once all code is ported, it shouldn't be too expensive to maintain both versions. One concrete issue is that running tests on Python 2 *and* Python 3 multiply the risk of random failures by 2. It's just math... In my experience, fixing random failures is not the most favorite task of developers... If you want to deprecate Python 2, the first question is *when* we can start to make Python 2 checks non-voting. However, for this, it'd be super helful to have as much visibility as possible. Are we setting a hard deadline for the Otaca release? Or is this just a goal we only "would like" to reach, but it's not really a big deal if we don't reach it? In my experience, Python 3 work is seen as background refactoring work, and it is rarely seen as high-priority. You should be prepared to have to wait :-) Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Le 23/06/2016 à 18:11, Doug Hellmann a écrit : I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. We can already experiment functional tests right now ;-) I expect to get many small issues in all projects, but it may take time to fix all these small issues, before being to fix the real (Python 3) bugs in applications. According to a recent discussion on #openstack-nova, I don't think that it will be possible to have Nova ported at the end of the Newton cycle. So I guess that we will run nova and swift on Python 2 for these functional tests at the beginning, right? Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
+1 on the idea of running function tests to see the fallout. Right now python-memcached is labelled as py3 compatible and in keystone our unit tests pass, but I'm skeptical about its behavior in functional and tempest tests. On Jun 23, 2016 1:14 PM, "Sean Dague"wrote: So, given that everything in base iaas is over besides Nova, and there is some python 3 support in Devstack, before Newton is over one could get a python 3 (except Nova) job running, and start seeing the fallout of full stack testing. We could even prioritize functional changes in Nova to get full stack python 3 working (a lot of what is holding Nova back is actually unit tests that aren't python 3 clean). That seems like the next logical step, and I think would help add incentive to full stack testing to show this actually working outside of just isolated test suites. On 06/23/2016 12:58 PM, Davanum Srinivas wrote: > +1 from me as well Doug! ("community to set a goal for Ocata to have Python > 3 functional tests running for all projects.") > > -- Dims > > On Thu, Jun 23, 2016 at 12:11 PM, Doug Hellmann wrote: >> Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: >>> On 06/22/2016 09:18 AM, Victor Stinner wrote: Hi, Current status: only 3 projects are not ported yet to Python 3: * nova (76% done) * trove (42%) * swift (0%) https://wiki.openstack.org/wiki/Python3 Number of projects already ported: * 19 Oslo Libraries * 4 Development Tools * 22 OpenStack Clients * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) * 12 OpenStack services approved by the TC * 17 OpenStack services (not approved by the TC) Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, we are so close! ;-) The next steps are to port the 3 remaining projects and work on functional and integration tests on Python 3. Victor >>> >>> Hi Victor, >>> >>> Thanks a lot for your efforts on Py3. >>> >>> Do you think it looks like possible to have Nova ported to Py3 during >>> the Newton cycle? >>> >>> Cheers, >>> >>> Thomas Goirand (zigo) >>> >> >> I'd like for the community to set a goal for Ocata to have Python >> 3 functional tests running for all projects. >> >> As Tony points out, it's a bit late to have this as a priority for >> Newton, though work can and should continue. But given how close >> we are to having the initial phase of the port done (thanks Victor!), >> and how far we are from discussions of priorities for Ocata, it >> seems very reasonable to set a community-wide goal for our next >> release cycle. >> >> Thoughts? >> >> Doug >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > > I'd like for the community to set a goal for Ocata to have Python > > > 3 functional tests running for all projects. > > > > > > As Tony points out, it's a bit late to have this as a priority for > > > Newton, though work can and should continue. But given how close > > > we are to having the initial phase of the port done (thanks Victor!), > > > and how far we are from discussions of priorities for Ocata, it > > > seems very reasonable to set a community-wide goal for our next > > > release cycle. > > > > > > Thoughts? > > > > > > Doug > > > > +1 > > > > Just think about it for a while. If we get Nova to work with Py3, and > > everything else is working, including all functional tests in Tempest, > > then after Otaca, we could even start to *REMOVE* Py2 support after > > Otaca+1. That would be really awesome to stop all the compat layer > > madness and use the new features available in Py3. > > We'll need to get some input from other distros and from deployers > before we decide on a timeline for dropping Python 2. For now, let's > focus on making Python 3 work. Then we can all rejoice while having the > discussion of how much longer to support Python 2. :-) > > > > > I really would love to ship a full stack running Py3 for Debian Stretch. > > However, for this, it'd be super helful to have as much visibility as > > possible. Are we setting a hard deadline for the Otaca release? Or is > > this just a goal we only "would like" to reach, but it's not really a > > big deal if we don't reach it? > > Let's see what PTLs have to say about planning, but I think if not > Ocata then we'd want to set one for the P release. We're running > out of supported lifetime for Python 2.7. Keep in mind that there is interest in running OpenStack on PyPy which is python 2.7. We don't have to continue supporting CPython 2.7 necessarily but we may want to support python 2.7 by way of PyPy. Clark __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a priority for > > Newton, though work can and should continue. But given how close > > we are to having the initial phase of the port done (thanks Victor!), > > and how far we are from discussions of priorities for Ocata, it > > seems very reasonable to set a community-wide goal for our next > > release cycle. > > > > Thoughts? > > > > Doug > > +1 > > Just think about it for a while. If we get Nova to work with Py3, and > everything else is working, including all functional tests in Tempest, > then after Otaca, we could even start to *REMOVE* Py2 support after > Otaca+1. That would be really awesome to stop all the compat layer > madness and use the new features available in Py3. We'll need to get some input from other distros and from deployers before we decide on a timeline for dropping Python 2. For now, let's focus on making Python 3 work. Then we can all rejoice while having the discussion of how much longer to support Python 2. :-) > > I really would love to ship a full stack running Py3 for Debian Stretch. > However, for this, it'd be super helful to have as much visibility as > possible. Are we setting a hard deadline for the Otaca release? Or is > this just a goal we only "would like" to reach, but it's not really a > big deal if we don't reach it? Let's see what PTLs have to say about planning, but I think if not Ocata then we'd want to set one for the P release. We're running out of supported lifetime for Python 2.7. Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/23/2016 06:11 PM, Doug Hellmann wrote: > I'd like for the community to set a goal for Ocata to have Python > 3 functional tests running for all projects. > > As Tony points out, it's a bit late to have this as a priority for > Newton, though work can and should continue. But given how close > we are to having the initial phase of the port done (thanks Victor!), > and how far we are from discussions of priorities for Ocata, it > seems very reasonable to set a community-wide goal for our next > release cycle. > > Thoughts? > > Doug +1 Just think about it for a while. If we get Nova to work with Py3, and everything else is working, including all functional tests in Tempest, then after Otaca, we could even start to *REMOVE* Py2 support after Otaca+1. That would be really awesome to stop all the compat layer madness and use the new features available in Py3. I really would love to ship a full stack running Py3 for Debian Stretch. However, for this, it'd be super helful to have as much visibility as possible. Are we setting a hard deadline for the Otaca release? Or is this just a goal we only "would like" to reach, but it's not really a big deal if we don't reach it? Cheers, Thomas Goirand (zigo) P.S: Again, thanks Victor for your awesome work. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On Thu, Jun 23, 2016 at 12:58:23PM -0400, Davanum Srinivas wrote: +1 from me as well. I get questions on support for these often enough. > +1 from me as well Doug! ("community to set a goal for Ocata to have Python > 3 functional tests running for all projects.") > > -- Dims > > On Thu, Jun 23, 2016 at 12:11 PM, Doug Hellmannwrote: > > Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: > >> On 06/22/2016 09:18 AM, Victor Stinner wrote: > >> > Hi, > >> > > >> > Current status: only 3 projects are not ported yet to Python 3: > >> > > >> > * nova (76% done) > >> > * trove (42%) > >> > * swift (0%) > >> > > >> >https://wiki.openstack.org/wiki/Python3 > >> > > >> > Number of projects already ported: > >> > > >> > * 19 Oslo Libraries > >> > * 4 Development Tools > >> > * 22 OpenStack Clients > >> > * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) > >> > * 12 OpenStack services approved by the TC > >> > * 17 OpenStack services (not approved by the TC) > >> > > >> > Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, > >> > we are so close! ;-) > >> > > >> > The next steps are to port the 3 remaining projects and work on > >> > functional and integration tests on Python 3. > >> > > >> > Victor > >> > >> Hi Victor, > >> > >> Thanks a lot for your efforts on Py3. > >> > >> Do you think it looks like possible to have Nova ported to Py3 during > >> the Newton cycle? > >> > >> Cheers, > >> > >> Thomas Goirand (zigo) > >> > > > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a priority for > > Newton, though work can and should continue. But given how close > > we are to having the initial phase of the port done (thanks Victor!), > > and how far we are from discussions of priorities for Ocata, it > > seems very reasonable to set a community-wide goal for our next > > release cycle. > > > > Thoughts? > > > > Doug > > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > -- > Davanum Srinivas :: https://twitter.com/dims > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
So, given that everything in base iaas is over besides Nova, and there is some python 3 support in Devstack, before Newton is over one could get a python 3 (except Nova) job running, and start seeing the fallout of full stack testing. We could even prioritize functional changes in Nova to get full stack python 3 working (a lot of what is holding Nova back is actually unit tests that aren't python 3 clean). That seems like the next logical step, and I think would help add incentive to full stack testing to show this actually working outside of just isolated test suites. On 06/23/2016 12:58 PM, Davanum Srinivas wrote: > +1 from me as well Doug! ("community to set a goal for Ocata to have Python > 3 functional tests running for all projects.") > > -- Dims > > On Thu, Jun 23, 2016 at 12:11 PM, Doug Hellmannwrote: >> Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: >>> On 06/22/2016 09:18 AM, Victor Stinner wrote: Hi, Current status: only 3 projects are not ported yet to Python 3: * nova (76% done) * trove (42%) * swift (0%) https://wiki.openstack.org/wiki/Python3 Number of projects already ported: * 19 Oslo Libraries * 4 Development Tools * 22 OpenStack Clients * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) * 12 OpenStack services approved by the TC * 17 OpenStack services (not approved by the TC) Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, we are so close! ;-) The next steps are to port the 3 remaining projects and work on functional and integration tests on Python 3. Victor >>> >>> Hi Victor, >>> >>> Thanks a lot for your efforts on Py3. >>> >>> Do you think it looks like possible to have Nova ported to Py3 during >>> the Newton cycle? >>> >>> Cheers, >>> >>> Thomas Goirand (zigo) >>> >> >> I'd like for the community to set a goal for Ocata to have Python >> 3 functional tests running for all projects. >> >> As Tony points out, it's a bit late to have this as a priority for >> Newton, though work can and should continue. But given how close >> we are to having the initial phase of the port done (thanks Victor!), >> and how far we are from discussions of priorities for Ocata, it >> seems very reasonable to set a community-wide goal for our next >> release cycle. >> >> Thoughts? >> >> Doug >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > -- Sean Dague http://dague.net __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
+1 from me as well Doug! ("community to set a goal for Ocata to have Python 3 functional tests running for all projects.") -- Dims On Thu, Jun 23, 2016 at 12:11 PM, Doug Hellmannwrote: > Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: >> On 06/22/2016 09:18 AM, Victor Stinner wrote: >> > Hi, >> > >> > Current status: only 3 projects are not ported yet to Python 3: >> > >> > * nova (76% done) >> > * trove (42%) >> > * swift (0%) >> > >> >https://wiki.openstack.org/wiki/Python3 >> > >> > Number of projects already ported: >> > >> > * 19 Oslo Libraries >> > * 4 Development Tools >> > * 22 OpenStack Clients >> > * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) >> > * 12 OpenStack services approved by the TC >> > * 17 OpenStack services (not approved by the TC) >> > >> > Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, >> > we are so close! ;-) >> > >> > The next steps are to port the 3 remaining projects and work on >> > functional and integration tests on Python 3. >> > >> > Victor >> >> Hi Victor, >> >> Thanks a lot for your efforts on Py3. >> >> Do you think it looks like possible to have Nova ported to Py3 during >> the Newton cycle? >> >> Cheers, >> >> Thomas Goirand (zigo) >> > > I'd like for the community to set a goal for Ocata to have Python > 3 functional tests running for all projects. > > As Tony points out, it's a bit late to have this as a priority for > Newton, though work can and should continue. But given how close > we are to having the initial phase of the port done (thanks Victor!), > and how far we are from discussions of priorities for Ocata, it > seems very reasonable to set a community-wide goal for our next > release cycle. > > Thoughts? > > Doug > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/23/2016 11:11 AM, Doug Hellmann wrote: > Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: >> On 06/22/2016 09:18 AM, Victor Stinner wrote: >>> Hi, >>> >>> Current status: only 3 projects are not ported yet to Python 3: >>> >>> * nova (76% done) >>> * trove (42%) >>> * swift (0%) >>> >>>https://wiki.openstack.org/wiki/Python3 >>> >>> Number of projects already ported: >>> >>> * 19 Oslo Libraries >>> * 4 Development Tools >>> * 22 OpenStack Clients >>> * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) >>> * 12 OpenStack services approved by the TC >>> * 17 OpenStack services (not approved by the TC) >>> >>> Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, >>> we are so close! ;-) >>> >>> The next steps are to port the 3 remaining projects and work on >>> functional and integration tests on Python 3. >>> >>> Victor >> >> Hi Victor, >> >> Thanks a lot for your efforts on Py3. >> >> Do you think it looks like possible to have Nova ported to Py3 during >> the Newton cycle? >> >> Cheers, >> >> Thomas Goirand (zigo) >> > > I'd like for the community to set a goal for Ocata to have Python > 3 functional tests running for all projects. > > As Tony points out, it's a bit late to have this as a priority for > Newton, though work can and should continue. But given how close > we are to having the initial phase of the port done (thanks Victor!), > and how far we are from discussions of priorities for Ocata, it > seems very reasonable to set a community-wide goal for our next > release cycle. ++ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: > On 06/22/2016 09:18 AM, Victor Stinner wrote: > > Hi, > > > > Current status: only 3 projects are not ported yet to Python 3: > > > > * nova (76% done) > > * trove (42%) > > * swift (0%) > > > >https://wiki.openstack.org/wiki/Python3 > > > > Number of projects already ported: > > > > * 19 Oslo Libraries > > * 4 Development Tools > > * 22 OpenStack Clients > > * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) > > * 12 OpenStack services approved by the TC > > * 17 OpenStack services (not approved by the TC) > > > > Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, > > we are so close! ;-) > > > > The next steps are to port the 3 remaining projects and work on > > functional and integration tests on Python 3. > > > > Victor > > Hi Victor, > > Thanks a lot for your efforts on Py3. > > Do you think it looks like possible to have Nova ported to Py3 during > the Newton cycle? > > Cheers, > > Thomas Goirand (zigo) > I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. As Tony points out, it's a bit late to have this as a priority for Newton, though work can and should continue. But given how close we are to having the initial phase of the port done (thanks Victor!), and how far we are from discussions of priorities for Ocata, it seems very reasonable to set a community-wide goal for our next release cycle. Thoughts? Doug __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote: > > > Le 23/06/2016 02:42, Tony Breeds a écrit : > > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > > > Do you think it looks like possible to have Nova ported to Py3 during > > > > the Newton cycle? > > > It doesn't depend on me: I'm sending patches, and then I have to wait for > > > reviews. The question is more how to accelerate reviews. > > Clearly I'm far from authorative but given how close we are to R-14 which is > > the Nova non-priority feature freeze[1] and the python3 port isn't listed as > > a priority[2] I'd guess that this wont land in Newton. > > > > [1] > > http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze > > [2] > > http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html > > Well, IIRC we discussed in the previous year on some of those blueprints > (including the Py3 effort) that are not really features (rather refactoring > items) and which shouldn't be hit by the non-priority feature freeze. > That doesn't mean we could merge those anytime of course, but I don't think > we would procedurally -2 them. Sure I didn't mean to imply a proceedural -2 I meant to convey that at this point in the cycle review focus shifts to priority items. So getting attention for this effort will be hard. We did discuss that this (py3 support) was a great background task but we also noted that those tasks would have a cut-off point. I *thought* that was the Nova non-priority feature freeze but I can't find that written anywhere. Yours Tony. signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Le 23/06/2016 02:42, Tony Breeds a écrit : On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: Le 22/06/2016 à 10:49, Thomas Goirand a écrit : Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? It doesn't depend on me: I'm sending patches, and then I have to wait for reviews. The question is more how to accelerate reviews. Clearly I'm far from authorative but given how close we are to R-14 which is the Nova non-priority feature freeze[1] and the python3 port isn't listed as a priority[2] I'd guess that this wont land in Newton. [1] http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze [2] http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html Well, IIRC we discussed in the previous year on some of those blueprints (including the Py3 effort) that are not really features (rather refactoring items) and which shouldn't be hit by the non-priority feature freeze. That doesn't mean we could merge those anytime of course, but I don't think we would procedurally -2 them. My .02€ -Sylvain Yours Tony. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > Do you think it looks like possible to have Nova ported to Py3 during > > the Newton cycle? > > It doesn't depend on me: I'm sending patches, and then I have to wait for > reviews. The question is more how to accelerate reviews. Clearly I'm far from authorative but given how close we are to R-14 which is the Nova non-priority feature freeze[1] and the python3 port isn't listed as a priority[2] I'd guess that this wont land in Newton. [1] http://releases.openstack.org/newton/schedule.html#nova-non-priority-feature-freeze [2] http://specs.openstack.org/openstack/nova-specs/priorities/newton-priorities.html Yours Tony. signature.asc Description: PGP signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
Le 22/06/2016 à 10:49, Thomas Goirand a écrit : Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? It doesn't depend on me: I'm sending patches, and then I have to wait for reviews. The question is more how to accelerate reviews. Right now, I'm splitting the great work made by dims during the previous cycle, 2 giant patches for nova, into smaller patches which should be easier to review. When I will have enough changes, I will try to create to taskforce to review these changes. I don't expect that nova core reviewers have enough time to review all these changes. It would prefer to have a first review step made by contributors interested by Python 3. My current Python 3 patches for nova: https://review.openstack.org/#/q/status:open+project:openstack/nova+branch:master+topic:bp/nova-python3 dims patches: * (1/2) https://review.openstack.org/262083 * (2/2) https://review.openstack.org/261045 Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [all] Status of the OpenStack port to Python 3
On 06/22/2016 09:18 AM, Victor Stinner wrote: > Hi, > > Current status: only 3 projects are not ported yet to Python 3: > > * nova (76% done) > * trove (42%) > * swift (0%) > >https://wiki.openstack.org/wiki/Python3 > > Number of projects already ported: > > * 19 Oslo Libraries > * 4 Development Tools > * 22 OpenStack Clients > * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) > * 12 OpenStack services approved by the TC > * 17 OpenStack services (not approved by the TC) > > Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, > we are so close! ;-) > > The next steps are to port the 3 remaining projects and work on > functional and integration tests on Python 3. > > Victor Hi Victor, Thanks a lot for your efforts on Py3. Do you think it looks like possible to have Nova ported to Py3 during the Newton cycle? Cheers, Thomas Goirand (zigo) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [all] Status of the OpenStack port to Python 3
Hi, Current status: only 3 projects are not ported yet to Python 3: * nova (76% done) * trove (42%) * swift (0%) https://wiki.openstack.org/wiki/Python3 Number of projects already ported: * 19 Oslo Libraries * 4 Development Tools * 22 OpenStack Clients * 6 OpenStack Libraries (os-brick, taskflow, glance_store, ...) * 12 OpenStack services approved by the TC * 17 OpenStack services (not approved by the TC) Raw total: 80 projects. In fact, 3 remaining projects on 83 is only 4%, we are so close! ;-) The next steps are to port the 3 remaining projects and work on functional and integration tests on Python 3. Victor __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev