<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Mon, Aug 27, 2018 at 2:37 PM Doug Hellmann <<a href="mailto:doug@doughellmann.com">doug@doughellmann.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">This is week 3 of the "Run under Python 3 by default" goal<br>
(<a href="https://governance.openstack.org/tc/goals/stein/python3-first.html" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/goals/stein/python3-first.html</a>). <br>
<br>
== What we learned last week ==<br>
<br>
We have a few enthusiastic folks who want to contribute to the goal<br>
who have not been involved in the previous discussion with goal<br>
champions. If you are one of them, please get in touch with me<br>
BEFORE beginning any work.<br>
<a href="http://lists.openstack.org/pipermail/openstack-dev/2018-August/133610.html" rel="noreferrer" target="_blank">http://lists.openstack.org/pipermail/openstack-dev/2018-August/133610.html</a><br>
<br>
In the course of adding python 3.6 unit tests to Manilla, a recursion<br>
bug setting up the SSL context was reported.<br>
<a href="https://bugs.launchpad.net/manila/+bug/1788253" rel="noreferrer" target="_blank">https://bugs.launchpad.net/manila/+bug/1788253</a> (We could use some<br>
help debugging it.)<br>
<br>
Several projects have their .gitignore files set up to ignore all<br>
'.' files. I'm not sure why this is the case. It has caused some<br>
issues with the migration, but I think we've worked around the<br>
problem in the scripts now.<br>
<br>
We extended the scripts for generating the migration patches to<br>
handle the neutron-specific versions of the unit test jobs for<br>
python 3.5 and 3.6.<br>
<br>
The Storyboard UI has some performance issue when a single story<br>
has several hundred comments. This is an unusual situation, which<br>
we don't expect to come up for "normal" stories, but the SB team<br>
discussed some ways to address it.<br>
<br>
Akihiro Mitoki expressed some concern about the new release notes<br>
job being set up in horizon, and how to test it. The "new" job is<br>
the same as the "old" job except that it sets up sphinx using<br>
python3. The versions of sphinx and reno that we rely on for the<br>
release notes jobs all work under python3, and projects don't have<br>
any convenient way to install extra dependencies, so we are confident<br>
that the new version of the job works. If you find that not to be<br>
true for your project, we can help fix the problem.<br>
<br>
We have a few repos with unstable functional tests, and we seem to<br>
have some instability in the integrated gate as well.<br>
<br>
== Ongoing and Completed Work ==<br>
<br>
These teams have started or completed their Zuul migration work:<br>
<br>
+---------------------+------+-------+------+<br>
| Team | Open | Total | Done |<br>
+---------------------+------+-------+------+<br>
| Documentation | 0 | 12 | yes |<br>
| OpenStack-Helm | 5 | 5 | |<br>
| OpenStackAnsible | 70 | 270 | |<br>
| OpenStackClient | 10 | 19 | |<br>
| OpenStackSDK | 12 | 15 | |<br>
| PowerVMStackers | 0 | 15 | yes |<br>
| Technical Committee | 0 | 5 | yes |<br>
| blazar | 16 | 16 | |<br>
| congress | 1 | 16 | |<br>
| cyborg | 2 | 9 | |<br>
| designate | 10 | 17 | |<br>
| ec2-api | 4 | 7 | |<br>
| freezer | 26 | 30 | |<br>
| glance | 16 | 16 | |<br>
| horizon | 0 | 8 | yes |<br>
| ironic | 22 | 60 | |<br>
| karbor | 30 | 30 | |<br>
| keystone | 35 | 35 | |<br>
| kolla | 1 | 8 | |<br>
| kuryr | 26 | 29 | |<br>
| magnum | 24 | 29 | |<br>
| manila | 19 | 19 | |<br>
| masakari | 18 | 18 | |<br>
| mistral | 0 | 25 | yes |<br>
| monasca | 20 | 69 | |<br>
| murano | 25 | 25 | |<br>
| octavia | 5 | 23 | |<br>
| oslo | 3 | 157 | |<br>
| other | 3 | 7 | |<br>
| qinling | 1 | 6 | |<br>
| requirements | 0 | 5 | yes |<br>
| sahara | 0 | 27 | yes |<br>
| searchlight | 5 | 13 | |<br>
| solum | 0 | 17 | yes |<br>
| storlets | 5 | 5 | |<br>
| swift | 9 | 11 | |<br>
| tacker | 16 | 16 | |<br>
| tricircle | 5 | 9 | |<br>
| tripleo | 67 | 78 | |<br>
| vitrage | 0 | 17 | yes |<br>
| watcher | 12 | 17 | |<br>
| winstackers | 6 | 11 | |<br>
| zaqar | 12 | 17 | |<br>
| zun | 0 | 13 | yes |<br>
+---------------------+------+-------+------+<br>
<br>
== Next Steps ==<br>
<br>
If your team is ready to have your zuul settings migrated, please<br>
let us know by following up to this email. We will start with the<br>
volunteers, and then work our way through the other teams.<br>
<br></blockquote><div><br></div><div>The keystone team is ready. Just FYI - there are pre-existing patches proposed to our repositories, but they weren't initiated by one of the goal champions [0].</div><div><br></div><div>I can help work through issues on our end.</div><div><br></div><div>[0] <a href="https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+topic:python3-first">https://review.openstack.org/#/q/(status:open+OR+status:merged)+project:openstack/keystone+topic:python3-first</a></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
After the Rocky cycle-trailing projects are released, I will propose<br>
the change to project-config to change all of the packaging jobs<br>
to use the new publish-to-pypi-python3 template. We should be able<br>
to have that change in place before the first milestone for Stein<br>
so that we have an opportunity to test it.<br>
<br>
== How can you help? ==<br>
<br>
1. Choose a patch that has failing tests and help fix it.<br>
<a href="https://review.openstack.org/#/q/topic:python3-first+status:open+(+label:Verified-1+OR+label:Verified-2+)" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/topic:python3-first+status:open+(+label:Verified-1+OR+label:Verified-2+)</a> <br>
2. Review the patches for the zuul changes. Keep in mind that some of<br>
those patches will be on the stable branches for projects.<br>
3. Work on adding functional test jobs that run under Python 3.<br>
<br>
== How can you ask for help? ==<br>
<br>
If you have any questions, please post them here to the openstack-dev<br>
list with the topic tag [python3] in the subject line. Posting<br>
questions to the mailing list will give the widest audience the<br>
chance to see the answers.<br>
<br>
We are using the #openstack-dev IRC channel for discussion as well,<br>
but I'm not sure how good our timezone coverage is so it's probably<br>
better to use the mailing list.<br>
<br>
== Reference Material ==<br>
<br>
Goal description: <a href="https://governance.openstack.org/tc/goals/stein/python3-first.html" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/goals/stein/python3-first.html</a> <br>
Open patches needing reviews: <a href="https://review.openstack.org/#/q/topic:python3-first+is:open" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/topic:python3-first+is:open</a><br>
Storyboard: <a href="https://storyboard.openstack.org/#!/board/104" rel="noreferrer" target="_blank">https://storyboard.openstack.org/#!/board/104</a><br>
Zuul migration notes: <a href="https://etherpad.openstack.org/p/python3-first" rel="noreferrer" target="_blank">https://etherpad.openstack.org/p/python3-first</a><br>
Zuul migration tracking: <a href="https://storyboard.openstack.org/#!/story/2002586" rel="noreferrer" target="_blank">https://storyboard.openstack.org/#!/story/2002586</a><br>
Python 3 Wiki page: <a href="https://wiki.openstack.org/wiki/Python3" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Python3</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div></div>