08:01:57 #startmeeting Mistral 08:01:58 Meeting started Fri Aug 31 08:01:57 2018 UTC and is due to finish in 60 minutes. The chair is d0ugal. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:01:59 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:01 The meeting name has been set to 'mistral' 08:02:02 Who is around today for the office hour? 08:02:13 https://etherpad.openstack.org/p/mistral-office-hours 08:02:22 PING rakhmerov, apetrich, bobh, mcdoker181818, akovi, hardikjasani 08:03:43 As usual, add or remove your name from the pinglist in the etherpad if you do or don't wany pings :) 08:05:26 We have one new bug - it looks like the unit tests are failing in Python 3.7 08:05:30 https://bugs.launchpad.net/mistral/+bug/1790001 08:05:30 Launchpad bug 1790001 in Mistral "Py3.7 tests result in core dump" [Undecided,New] 08:05:41 I actually noticed this before, but forgot to report a bug :) 08:07:00 d0ugal: hey 08:07:22 Hi! 08:07:27 Is Openstack mandating compat of all projects with py3.7? 08:07:38 hardikjasani: no, not yet 08:07:50 Rocky targets 3.5, Stein 3.6 (iirc) 08:07:59 but we will want to support 3.7 eventually 08:08:04 :) 08:10:43 That is a fast move for a big project. I think py2.7 requirement will not be dropped for foreseeable future. 08:11:01 hardikjasani: Adopting new 3.X versions is generally easy 08:11:10 hardikjasani: and I suspect 2.7 will be dropped sooner than you think 08:11:20 The goal for stein is to be "python 3 first" 08:12:05 hardikjasani: https://governance.openstack.org/tc/goals/stein/python3-first.html 08:12:18 Need major enterprise distro to move to python3 first say RHEL, CentOS, debian & derivatives 08:12:51 hardikjasani: well, yes, but you can get Python 3 on all of these already 08:13:00 and that is the problem of the downstream companies :) 08:13:44 hardikjasani: Python 2 is also not supported at the end of this year, none of these distros want to take on that problem 08:13:52 so the motivation to move is stronger than ever 08:14:11 There is a bug with SSHAction not working under py3, did you run into that? 08:14:31 I seen a bug report. I don't use that action. 08:16:03 Neither do we, but someone is going to run into that eventually. 08:16:20 Indeed 08:17:09 Fixes welcome :-D 08:17:49 hardikjasani: there is also this btw: https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html#python2-deprecation-timeline 08:19:59 Renat Akhmerov proposed openstack/mistral master: Performance: remove unnecessary workflow execution update https://review.openstack.org/598501 08:20:16 "Python 2 is also not supported at the end of this year" - I did mean to write "end of next year" 08:21:15 so based on that last link, we should be dropping support for Python 2 in the U cycle, which will release early 2020 08:21:54 so not very soon, but it is a forseeable future at least :) 08:23:19 d0ugal: hey 08:23:24 discussing anything? 08:23:28 Hi rakhmerov 08:23:48 I just realized that I wasn't joined to the channel :) 08:24:01 rakhmerov: Only a little bit of discussion about Python 3 support (and deprecating python 2) with hardikjasani 08:24:05 and how are things going in general? 08:24:09 ok 08:24:19 Everything is good, Rocky release this week! 08:24:28 yeah! 08:24:30 awesome 08:24:40 please review https://review.openstack.org/#/c/598501 08:24:51 another huge improvement (bugfix actually) 08:25:01 rakhmerov: did you know the goal is to drop Python 2 support in the U cycle? 08:25:14 d0ugal: nope, I didn't! 08:25:30 See these two links... 08:25:32 and we're still using Py2 in the company (the fact that I hate) 08:25:33 https://governance.openstack.org/tc/goals/stein/python3-first.html 08:25:35 ok 08:25:36 https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html#python2-deprecation-timeline 08:25:42 ok 08:26:00 The goal for Stein is to be "python 3 first" 08:26:04 so 1.5 years more 08:26:07 yeah 08:26:08 yep 08:26:29 now everyone defaults to python 2, changing that default to 3 is a good start 08:26:45 ok, I think that's going to be enough time for people to move to Py3 08:26:52 agree 08:27:28 It is going to be lots of fun digging out Python 2 compat code and deleting it :) 08:27:37 yeah :) 08:27:47 lot of easy karma for someone ) 08:27:53 haha, yeah 08:27:57 well, maybe not so easy though ) 08:28:17 Probably some easy places, but I guess that is more in the oslo code 08:28:31 hope so 08:28:33 oh and deleting all the "six" imports :) 08:29:38 :) 08:30:19 d0ugal: so just FYI, https://review.openstack.org/598501 makes highly parallel workflows twice as fast (e.g. when we have hundreds of parallel branches) 08:30:28 we absolutely need it in Rocky 08:31:20 Nice 08:31:44 rakhmerov: Rocky already released, so it will need to be backported and released as 7.0.1 08:31:49 rlease note and bug report please 08:33:14 Dougal Matthews proposed openstack/python-mistralclient stable/rocky: Revert "Make Tripleo non-voting on Rocky" https://review.openstack.org/598532 08:34:40 d0ugal: yes, sure 08:34:43 I'll do it 08:38:13 Dougal Matthews proposed openstack/python-mistralclient stable/rocky: Revert "Make Tripleo non-voting on Rocky" https://review.openstack.org/598532 08:39:26 d0ugal: so I assign the bug to S-1 now, right? 08:39:33 rakhmerov: Yeah 08:39:36 ok 08:39:41 I'm just about to close the rc2 milestone :) 08:40:59 Renat Akhmerov proposed openstack/mistral master: Performance: remove unnecessary workflow execution update https://review.openstack.org/598501 08:46:33 d0ugal: ok 08:47:36 d0ugal: btw, we (Nokia) don't need 7.0.1 release. We use the latest builds (RDO RPMs) made out of the stable/rocky branch 08:48:03 rakhmerov: okay, cool 08:48:23 I didn't know that RDO included unreleased patches 08:48:27 :) 08:48:39 but we should do the release anyway, makes things clearer 08:50:57 Renat Akhmerov proposed openstack/mistral master: Performance: remove unnecessary workflow execution update https://review.openstack.org/598501 08:51:29 d0ugal: yes, I agree 08:51:34 it was just FYI 08:51:56 d0ugal: so the bug report and the release note are ready 08:51:57 sure 08:52:08 great, thanks! 09:01:23 #endmeeting