[goals][Drop Python 2.7 Support] Week R-6 Update
Hello Everyone, Below is the progress on "Drop Python 2.7 Support" at end of R-6 week. Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sch... Highlights: ======== * This is very close to mark as complete. * We merged many of charm repo patches and few more projects. * Few ansible repo failing on centos7 and waiting for migration on centos8 * I tried to reach out to team for pending patches. Project wise status and need reviews: ============================ Phase-1 status: All the OpenStack services have dropped the python2.7. Phase-2 status: * Pending Tempest plugins: ** cyborg-tempest-plugin: https://review.opendev.org/#/c/704076/ ** kuryr-tempest-plugin: https://review.opendev.org/#/c/704072/ * Pending pythonclient: ** python-barbicanclient: https://review.opendev.org/#/c/699096/2 *** gate is already broken waiting for gate to be fixed. ** python-zaqarclient: https://review.opendev.org/#/c/692011/4 ** python-tripleoclient: https://review.opendev.org/#/c/703344 * Few more repo patches need to merge: ** masakari-specs: https://review.opendev.org/#/c/698982/ ** cyborg-specs: https://review.opendev.org/#/c/698824/ ** nova-powervm: https://review.opendev.org/#/c/700683/ ** paunch: https://review.opendev.org/#/c/703344/ * Started pushing the required updates on deployment projects. ** Completed or no updates required: *** Openstack-Chef - not required *** Packaging-Rpm - Done *** Puppet Openstack- Done *** Tripleo - except python client, all is done. ** In progress: *** Openstack Charms - Most of them merged, few failing on func job. debugging. *** Openstackansible - In-progress. centos7 jobs are failing on few projects. ** Waiting from projects team to know the status: *** Openstack-Helm (Helm charts for OpenStack services) * Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open Phase-3 status: This is audit and requirement repo work which is not started yet. I will start the audit in parallel to finishing the pending things listed above. How you can help: ============== - Review the patches. Push the patches if I missed any repo. -gmann
On Thu, Apr 2, 2020 at 5:53 AM Ghanshyam Mann <gmann@ghanshyammann.com> wrote:
Hello Everyone,
Below is the progress on "Drop Python 2.7 Support" at end of R-6 week.
Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sch...
Highlights: ======== * This is very close to mark as complete. * We merged many of charm repo patches and few more projects. * Few ansible repo failing on centos7 and waiting for migration on centos8 * I tried to reach out to team for pending patches.
Project wise status and need reviews: ============================ Phase-1 status: All the OpenStack services have dropped the python2.7.
Phase-2 status:
* Pending Tempest plugins: ** cyborg-tempest-plugin: https://review.opendev.org/#/c/704076/ ** kuryr-tempest-plugin: https://review.opendev.org/#/c/704072/
* Pending pythonclient: ** python-barbicanclient: https://review.opendev.org/#/c/699096/2 *** gate is already broken waiting for gate to be fixed. ** python-zaqarclient: https://review.opendev.org/#/c/692011/4 ** python-tripleoclient: https://review.opendev.org/#/c/703344
* Few more repo patches need to merge: ** masakari-specs: https://review.opendev.org/#/c/698982/ ** cyborg-specs: https://review.opendev.org/#/c/698824/ ** nova-powervm: https://review.opendev.org/#/c/700683/ ** paunch: https://review.opendev.org/#/c/703344/
* Started pushing the required updates on deployment projects.
** Completed or no updates required: *** Openstack-Chef - not required *** Packaging-Rpm - Done *** Puppet Openstack- Done *** Tripleo - except python client, all is done.
** In progress: *** Openstack Charms - Most of them merged, few failing on func job. debugging. *** Openstackansible - In-progress. centos7 jobs are failing on few projects.
** Waiting from projects team to know the status: *** Openstack-Helm (Helm charts for OpenStack services)
Disclaimer: I am not a part of the openstack-helm team/community in the full sense of it, so these are my personal thoughts on the OpenStack-Helm vs Py3 OpenStack-Helm is a bit odd here: - it does not have stable branches - it has single (very ancient, 3 years ago) tag of 0.1.0 - it still supports (as in deploys on CI) Ocata Given community goal of "Python3 first" was targeting and completed in Stein, I don't think that openstack-helm should drop support of Python2 in their startup/readiness/liveness and other scripts unless they are willing to drop support of OpenStack releases earlier that Stein and demand images built on Py3 exclusively - and AFAICT they don't. Best regards, Pavlo.
* Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open
Phase-3 status: This is audit and requirement repo work which is not started yet. I will start the audit in parallel to finishing the pending things listed above.
How you can help: ============== - Review the patches. Push the patches if I missed any repo.
-gmann
---- On Fri, 03 Apr 2020 04:41:46 -0500 Pavlo Shchelokovskyy <pshchelokovskyy@mirantis.com> wrote ----
On Thu, Apr 2, 2020 at 5:53 AM Ghanshyam Mann <gmann@ghanshyammann.com> wrote: Hello Everyone,
Below is the progress on "Drop Python 2.7 Support" at end of R-6 week.
Schedule: https://governance.openstack.org/tc/goals/selected/ussuri/drop-py27.html#sch...
Highlights: ======== * This is very close to mark as complete. * We merged many of charm repo patches and few more projects. * Few ansible repo failing on centos7 and waiting for migration on centos8 * I tried to reach out to team for pending patches.
Project wise status and need reviews: ============================ Phase-1 status: All the OpenStack services have dropped the python2.7.
Phase-2 status:
* Pending Tempest plugins: ** cyborg-tempest-plugin: https://review.opendev.org/#/c/704076/ ** kuryr-tempest-plugin: https://review.opendev.org/#/c/704072/
* Pending pythonclient: ** python-barbicanclient: https://review.opendev.org/#/c/699096/2 *** gate is already broken waiting for gate to be fixed. ** python-zaqarclient: https://review.opendev.org/#/c/692011/4 ** python-tripleoclient: https://review.opendev.org/#/c/703344
* Few more repo patches need to merge: ** masakari-specs: https://review.opendev.org/#/c/698982/ ** cyborg-specs: https://review.opendev.org/#/c/698824/ ** nova-powervm: https://review.opendev.org/#/c/700683/ ** paunch: https://review.opendev.org/#/c/703344/
* Started pushing the required updates on deployment projects.
** Completed or no updates required: *** Openstack-Chef - not required *** Packaging-Rpm - Done *** Puppet Openstack- Done *** Tripleo - except python client, all is done.
** In progress: *** Openstack Charms - Most of them merged, few failing on func job. debugging. *** Openstackansible - In-progress. centos7 jobs are failing on few projects.
** Waiting from projects team to know the status: *** Openstack-Helm (Helm charts for OpenStack services)
Disclaimer: I am not a part of the openstack-helm team/community in the full sense of it,so these are my personal thoughts on the OpenStack-Helm vs Py3 OpenStack-Helm is a bit odd here:- it does not have stable branches- it has single (very ancient, 3 years ago) tag of 0.1.0- it still supports (as in deploys on CI) Ocata Given community goal of "Python3 first" was targeting and completed in Stein, I don't think that openstack-helm should drop support of Python2 in their startup/readiness/liveness and other scripts unless they are willing to drop support of OpenStack releases earlier that Stein and demand images built on Py3 exclusively - and AFAICT they don't.
ok, I did not know that openstack-helm supports all the stable release with master version. If so then also we can go with tagging it and then drop the python2.7 which is what we did for other branchless projects like Tempest etc. Release a tag before dropping and use that tag for any older release than Ussuri. -gmann
Best regards,Pavlo.
* Open review: https://review.opendev.org/#/q/topic:drop-py27-support+status:open
Phase-3 status: This is audit and requirement repo work which is not started yet. I will start the audit in parallel to finishing the pending things listed above.
How you can help: ============== - Review the patches. Push the patches if I missed any repo.
-gmann
On 2020-04-13 11:02:09 -0500 (-0500), Ghanshyam Mann wrote: [...]
ok, I did not know that openstack-helm supports all the stable release with master version. If so then also we can go with tagging it and then drop the python2.7 which is what we did for other branchless projects like Tempest etc. Release a tag before dropping and use that tag for any older release than Ussuri. [...]
That would mean they'd need to branch from that tag if they want to backport any fixes to their support for earlier OpenStack versions. -- Jeremy Stanley
---- On Mon, 13 Apr 2020 11:07:33 -0500 Jeremy Stanley <fungi@yuggoth.org> wrote ----
On 2020-04-13 11:02:09 -0500 (-0500), Ghanshyam Mann wrote: [...]
ok, I did not know that openstack-helm supports all the stable release with master version. If so then also we can go with tagging it and then drop the python2.7 which is what we did for other branchless projects like Tempest etc. Release a tag before dropping and use that tag for any older release than Ussuri. [...]
That would mean they'd need to branch from that tag if they want to backport any fixes to their support for earlier OpenStack versions.
True but that depends if backport is what they wanted to support if they can or just ask users to move to py3 env if you want to use the latest things. I am ok with keeping py2 support also if there is no dependency on OpenStack or so. It is not in the list of not dropping projects but I am ok to reconsider this and would like to see what helm team think about this. gagehugo is going to check this tomorrow. As per him, they moved the infra from py2 to py3, but not the images. -gmann
-- Jeremy Stanley
participants (3)
-
Ghanshyam Mann
-
Jeremy Stanley
-
Pavlo Shchelokovskyy