14:00:07 #startmeeting sahara 14:00:16 Meeting started Thu Apr 19 14:00:07 2018 UTC and is due to finish in 60 minutes. The chair is tenobreg. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:17 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:20 The meeting name has been set to 'sahara' 14:00:20 o/ 14:00:43 o/ 14:02:22 ok, let's start 14:02:36 #topic News/Updates 14:03:02 I'm still working on both plugins and boot from volume 14:04:01 i pushed a patchset with what i have so far for admin controlling stuff in other projects 14:04:31 I'm still mostly doing internal work, testing queens; and of course the usual reviews 14:04:47 (the commit message is intentionally empty for now -- i think a spec will explain it better while things are still WIP) 14:05:02 I didn't look at it yet, but I will soon 14:05:56 I am still preparing an examination. My boss ask me must pass it before 1st May. So I don't have spare time do upstream tasks :( 14:06:31 no worries shuyingya 14:06:40 I pushed a patch of vanilla 2.7.5 upgrade 14:06:50 thanks for your understanding 14:07:07 zchkun, do you have specific reason why you need 2.7.5? 14:07:28 tenobreg: I think that we discussed it some time ago: it's the last version of 2.7.x 14:07:44 ok, that makes sense 14:07:49 yeah, i think we discussed it a while ago: a new stable 2.7 series 14:07:53 with newer oozie and hive too 14:07:57 makes sense 14:08:10 yes 14:08:18 thank you for that, zchkun 14:08:44 we could all take a look at it today, because if it is good to merge we can still put it in R1 14:09:04 I would like to leave a question here (do we need upgrade oozie to 5.0 in vanilla 2.7.5 ? ) 14:09:14 we can talk about it later 14:09:22 uhm, while it could be good, it requires a change to sahara-extra and sahara-image-elements, in addition to sahara, in order to be useful 14:09:33 I upgrade oozie to 4.3 , the same with v2.8.2 14:09:36 shuyingya: what does the Hadoop project say/suggests? 14:10:01 and i want upgrade oozie 5.0 to vanilla 3.0 14:11:06 tosky, there is no suggestion about the version of oozie to vanilla 2.7.5 as I see 14:11:36 release log, to get an idea of the difference: https://github.com/apache/oozie/blob/master/release-log.txt 14:12:19 i guess there is not much coupling between hadoop and oozie version 14:12:49 5.0.0 is really new though (only two weeks) 14:12:50 I recommend oozie 5.0 just because it can solve the page can't open issue 14:13:00 ooh, the page can't open issue is a good one, though 14:13:09 i've seen it before 14:13:24 just a sec, let me change topic 14:13:31 #topic Oozie 5.0 14:14:01 sorry tenobreg, I mostly forget the topic 14:14:08 quick review, we are discussing if we should upgrade oozie to 5.0 on which version of hadoop that should happen 14:14:12 no worries 14:14:19 oozie 5.0 requires >=Hadoop 2.6.0 14:14:21 https://oozie.apache.org/docs/5.0.0/DG_QuickStart.html#System_Requirements: 14:14:30 for vanilla 2.7.5 zchkun upgrade to 4.3 14:14:42 which is the one we use for vanilla 2.8.2 14:14:51 4.3 14:15:14 I believe we can keep 4.3 for 2.7.5 and work on 5.0 to vanilla 3 14:15:33 does that seem like a good approach? 14:15:36 out of curiosity. is 4.3.x still supported by oozie developers? 14:15:38 tosky: i think the more important constraint there is jdk 1.8 (if i remember how that works "1.8" really means "8", no?) 14:15:44 right 14:16:10 tosky: i think 4.3 is still supported, it's the latest 4.x series (but that assumes that their versino numbers are logical) 14:17:00 that could be a problem 14:17:21 tenobreg, what could be? 14:17:31 jdk 1.8 14:17:47 I would be safe enough to keep 4.3.0 in 2.7.5. The only reason I recommend 5.0 just because of the oozie console page can't open 14:18:00 we could either specify that for that plugin that image has to be created with java 8 14:18:08 openjdk 1.8 is available on xenial and on centos7 14:18:14 yes 14:18:14 don't we use it already? 14:18:17 tenobreg about jdk, i just checked, we are good, i assume we don't care about fedora <=21, and we already don't care about centos/rhel6 14:18:19 we do 14:18:41 ok that should be great 14:19:01 lets get into a final decision here 14:19:11 fedora <= 25 is gone 14:19:20 tosky: good 14:19:26 tenobreg: yes, let's decide 14:19:27 2.7.5 with 4.3 and vanilla 3.0 with oozie 5? 14:19:36 agree 14:19:43 ok 14:19:45 agree 14:19:57 agree 14:20:03 for sure we could not have 5.0 with 2.7.5 but not with 2.8.2 :) 14:20:21 (tosky: that's my thought. it's easier to justify to the user this way) 14:20:56 great, let's move on 14:21:23 #topic Rocky 1 14:21:36 today I have to cut R1 14:21:57 already? We have 4 pending commits which just waits another +2 14:22:02 s/commits/reviews/ 14:22:36 I would like to get some reviews on the plugins split spec, and on those patches that tosky mentioned 14:22:57 basically everything with a +2 14:23:07 yes 14:23:20 lets get those merged so we have less work left over to R2 14:23:32 I also added some comments to all (I think) other open reviews which are still relevent, asking for an heads-up (shuyingya answered already on one of them) 14:25:42 lets move on, please take a look at the patches 14:26:08 does anyone have specific topics to discuss today? 14:26:36 would it be fine to add a co-gating job with openstack-ansible-os_sahara? 14:27:16 I don't really understand the problem 14:27:54 i don't know what their own job does 14:27:54 #topic Open Discussion 14:28:23 what job are you thinking to go-gate with os-ansible-os_sahara? 14:28:29 quick story: last week I opened a bug for puppet-sahara and openstack-ansible-os_sahara to add support for [trustee] section 14:28:50 tenobreg: the idea is that we check to see if their default configs actually work (spoiler: they don't). so we would want to run (i assume) the full scenario against a sahara set up by OSA 14:29:19 I ended up in the meeting of openstack-ansible (I didn't see meetings for puppet-openstack) for the bug triaging 14:29:42 that seems like a good job to have 14:29:54 and after the meeting I was asked about adding a co-gating job, so basically a tempest job (or other, if we want) which deploys with ansible instead of devstack 14:29:56 it is only failing on ansible? 14:30:18 no, it's not failing 14:30:55 I mean, they already have jobs which deploys sahara with openstack and ansible; adding it for each commit would prevent breakages for them 14:31:10 (we could do the same for tripleo too, even if their jobs are more resource-intensive) 14:31:16 +1 for me 14:31:40 (and puppet too, I think that tempest has non-voting puppet jobs triggered for each change) 14:32:01 okidoki, I will move forward at least with openstack-ansible then 14:32:06 thanks 14:33:01 I actually don't have more topics for today 14:33:20 jeremyfreudberg, shuyingya, zchkun, tosky? anything else? 14:33:31 jeremyfreudberg, do you have updates on sahara ci? 14:33:43 no, apart from a new "please vote on the jobs" and "thanks Jeremy for changing the topic of that commit" :P 14:34:09 tenobreg: no, i don't have an update, really 14:35:01 nope 14:35:06 nothing from me 14:35:08 ok 14:35:17 so we can close early today 14:36:12 thanks all, please review the patches and I will cut R-1 later today 14:36:44 o/ 14:37:04 #endmeeting