14:01:37 #startmeeting sahara 14:01:37 Meeting started Thu Feb 28 14:01:37 2019 UTC and is due to finish in 60 minutes. The chair is tellesnobrega_. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:41 The meeting name has been set to 'sahara' 14:01:44 o/ 14:01:49 #chair tosky tellesnobrega 14:01:50 Warning: Nick not in channel: tellesnobrega 14:01:51 Current chairs: tellesnobrega tellesnobrega_ tosky 14:02:04 just in case my nick changes at some point 14:02:12 is jeremyfreudberg around? 14:02:18 yep 14:02:21 o/ 14:02:32 hey jeremyfreudberg and Gaasmann 14:02:36 lets get it started 14:02:41 #topic News/Updates 14:02:41 hi 14:04:12 I've been busy with python 3 work 14:04:39 finally found the mains source of the issue and have a patch that still needs work, but I'm glad we moved on with it 14:05:57 i've been working on filling in the gaps for the new apiv2 features in osc 14:06:08 I've been working more on the native zuulv3 grenade job; you may have seen a DNM review for sahara, which I used to test that job 14:07:18 Gaasmann, want to share anything? 14:08:03 Well, I'm trying to automate image generation for my needs so I'm using the scripts to generate images a lot 14:08:28 So far I'm running into issue that are not Sahara related, so it's good :-) 14:08:38 only sahara-image-elements or sahara-image-pack as well? 14:09:06 both, I'm using sahara-image-elements for vanilla/storm/spark and sahara-image-pack for the others 14:09:23 awesome 14:09:44 We have spark on image-pack now as well, but still need some verifications 14:09:56 I will try to make it for vanilla and storm soon as well 14:09:56 oh, good to know 14:10:18 spark on centos as well on sahara-image-pack 14:10:22 ok great, I'll test thoses 14:10:45 awesome 14:10:58 anything else here? 14:11:07 I have a couple topics to discuss today 14:11:38 #topic APIv2 14:11:41 moving on 14:11:44 (I have few smaller announcements/reports, but they can go to the end) 14:11:55 thanks 14:12:03 I'll save some time for it 14:12:31 on apiv2, I would like to hear from jeremyfreudberg how ready are we, and remind that M3 is next week and we need to make the switch soon 14:12:36 do you think we can make it? 14:13:10 switch, and also release of the client 14:13:48 yes 14:14:37 yeah, i think we will be fine, the client work should be straightforward enough. and on the server-side i haven't uncovered any thing i want to change yet, so flipping to stable very soon seems likely 14:14:52 awesome 14:15:05 about the policies, did you get a chance to double check? 14:15:22 no, i still need to double check it... 14:16:04 jeremyfreudberg, sure, please make sure you do, we need that as well 14:16:15 yep 14:16:26 :) 14:16:27 thanks 14:16:40 anything else on apiv2? tosky? 14:17:16 there is one change related to APIv2 for sahara-tests still open - again (sorry!) on jeremyfreudberg :) 14:17:29 nothing else from me 14:17:40 oh, i'll look at it 14:19:17 moving on 14:19:27 #topic Split Plugins 14:19:38 on this front we are actually really good 14:20:01 but we need to release each plugin 14:20:19 tosky, you can explain better than me 14:20:51 we need to have the the pip version of the plugins to fix the deployers (mostly puppet-openstack and openstack-ansible) 14:21:02 because as far as I know they can deploy from git but also from pip 14:21:12 deploy packages from 14:21:56 I will create the patch to release the plugins, I would like to see some reviews on the mapr patch so we don't have to do another release with bug fixes 14:22:05 so, please take a look at that soon 14:22:13 #link https://review.openstack.org/#/c/634764/ 14:22:24 #https://review.openstack.org/#/c/634799/ 14:22:26 #link https://review.openstack.org/#/c/634799/ 14:22:27 sure, it will be fixed by GA 14:22:36 we can still release the plugins as beta 14:22:45 yes 14:23:51 anything else on the split from anyone? 14:24:52 not right now - I will ping the people from puppet and ansible once the pip packages are available; I may also help with the patches, let's see 14:25:11 for the record, tripleo should be working even now, thanks to the RPM dependencies 14:25:16 cook 14:25:34 cool 14:25:37 I meant 14:25:47 moving on 14:25:56 #topic Python 3 14:26:21 so, after a week at a staring contest with sahara code and pickle I found that our issue wasn't pickle at all 14:26:28 It was at first 14:26:52 but the main reason is that subprocess stdout/stderr are bytes on python3 14:27:11 there were also some file writing and reading issues that I'm looking into 14:27:34 but looks like we will have a fix and sahara will work nicely with python3 14:28:49 decoding the output works, I switched to utf-8 and it worked as well 14:29:29 I need to check that code with python2 to see if I'll need to add some try except for the decoding 14:30:18 there is not much on this, just wanted to let everyone know what I found out and let go of the frustration of last week :) 14:30:24 yay \o/ 14:30:55 tosky: is there any reason to backport these python 3 fixes (maybe for some distro's sake?) 14:32:21 jeremyfreudberg: which python 3 fixes? 14:32:54 all fixes that tellesnobrega_ is working on and the previous ones? 14:33:15 as far as I know as openstack globally we don't support python3 before Stein 14:33:42 even if I suspect that Debian may have packaged OpenStack using python3 14:33:46 I think stein is the python 3 first starting point 14:33:47 yep, they did 14:33:54 yeah, i meant this current one, plus enable_lazy and anything else that came before 14:34:03 i was thinking of debian, yes 14:34:18 but if the real starting point is Stein, then no need too 14:35:30 backporting them later is not complicated, let's focus on having all of the first; we can create a cumulative patch 14:35:34 if needed 14:35:35 let's see 14:35:43 yep 14:36:19 I think that is all the topics I have 14:36:41 does anyone have specific topics or can I change to Open Discussion? 14:37:04 I'd say open discussion, I have few points but I don't think that they will require much discussion 14:37:10 ok 14:37:17 #topic Open Discussion 14:37:54 you have the floor tosky 14:38:10 sahara-dashboard - you may have noticed a backport of the native zuulv3 integration test job on rocky, the idea is to get rid of the legacy job so that it can be removed from openstack-zuul-jobs 14:38:40 but it seems that the backport (even if experimental) is failing even more, and I suspect that the required changes to the integration test infrastructure in horizon haven't been backported to rocky 14:39:13 so if this was confirmed, would you agree with dropping the integration tests job from all the stable branches (rocky, queens, pike and, yes, ocata) 14:39:31 so that we can nuke the definition of legacy job forever? 14:39:49 does this have a downside? 14:40:18 those tests are not running anyway, so no 14:40:28 I would say drop it 14:40:36 i'm fine with dropping from stable branches 14:40:40 okidoki, I will recheck with horizon maintainers 14:40:44 then 14:41:03 awesome 14:41:06 thanks tosky 14:41:07 py37 - there are few of them, I could have single-merged them, but I didn't know - we can merge them 14:41:13 and then propose the missing ones 14:41:34 they are not strictly needed for stein, but they will be useful later and they don't use too many resources 14:41:52 and that's it for this point, unless you have questions 14:42:05 can you paste the links to the py37 patches? 14:43:09 https://review.openstack.org/#/q/project:%255Eopenstack/sahara.*+topic:py37-job+status:open 14:43:30 I will propose the missing ones for the other plugins and the other repositories 14:43:38 another small point: 14:44:08 we have few lingering patches for stable/pike, blocked on a tempest issue (https://bugs.launchpad.net/tempest/+bug/1816022) 14:44:09 Launchpad bug 1816022 in tempest "Incompatible requirements break tempest (at least) on stable/pike" [Undecided,In progress] - Assigned to Ghanshyam Mann (ghanshyammann) 14:45:03 gmann, QA PTL, kindly investigated and found a fix, so as long as the required patches are merged, we can merge those stable/pike patches (and few more backports that I will propose) 14:45:15 so they are not forgotten 14:45:18 and that's it 14:45:24 great 14:45:32 I will keep an eye on that 14:46:07 I don't have other points 14:46:12 I have something else to say 14:46:39 next week starts the PTL self-nominations and the week after are the elections 14:47:16 I'm officially announcing that I'm not running 14:47:34 it is way past time someone else do this job 14:48:04 keep an eye for a candidacy from jeremyfreudberg :) 14:48:15 thanks for all the efforts so far, tellesnobrega_ 14:48:28 yes, thanks for all your hard work, tellesnobrega_ 14:48:29 thanks a lot 14:48:36 i am excited to take up the helm 14:48:41 I really appreciate having you all on the team 14:48:53 jeremyfreudberg, as you should, it is fun :) 14:49:00 :) 14:49:09 that is it from me 14:49:29 does anybody have anything else to share today? 14:49:45 not on my side 14:50:14 not from me 14:50:34 I guess we can close a bit early and we all get 10 more minutes 14:50:39 thanks everyone 14:51:19 thanks everyone 14:51:23 see you next week and lets keep an eye for the M3 deadline, we have to merge everything by next Wednesday to be safe 14:51:32 see you all, thanks again 14:51:33 yup 14:51:44 thanks, see you 14:51:51 #endmeeting