14:01:10 #startmeeting sahara 14:01:11 Meeting started Thu Dec 14 14:01:10 2017 UTC and is due to finish in 60 minutes. The chair is tosky. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:01:12 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:15 The meeting name has been set to 'sahara' 14:01:19 o/ 14:01:26 hi! Telles may not be around, so I will chair this time 14:02:05 it looks like it may be quick, but let's see 14:02:12 #topic News/Updated 14:03:06 Telles told me that he is working on ambari 2.3 and mapr 5.2 images (image-pack), and also fighting with the UI support for decommissioning nodes 14:03:50 I will have a bit more of free time to fix the zuul jobs, the remaining failing CLI tempest job, and hopefully adding new jobs 14:04:12 hi tosky, still working on vanilla upgrade, and cluster works now, but has some problem right now. Maybe affects 2.7.1 too 14:04:17 oh, it's the first meeting with shuyingya as core, congratulation again! 14:04:30 haha, thanks tosky 14:05:46 one of the reason why I'm watching closely the progress on native zuul multinode jobs, is to have at least a proper vanilla test and prevent regressions 14:06:21 o/ hey guys, made it a little bit late but made it 14:06:23 col 14:06:30 oh, good! 14:06:32 cool 14:06:54 tellesnobrega: so we just shared the updates, I wrote down what you told me (image-pack for two plugins and UI for horizon 14:07:03 please keep going, you are in charge today tosky 14:07:05 thanks 14:07:15 :) 14:07:35 tosky, we don't have sahara-ci anymore? 14:08:00 shuyingya: not the old one 14:08:28 there is some work in progress both on the scripts to set up (Evgeny sent a stream of reviews some time ago) and, more important, the hardware 14:08:39 Jeremy knows better the status of the hardware 14:08:54 but even without the sahara-ci we can set some jobs on the main infra 14:09:05 I sent out the requested email to MOC people but haven't got a response 14:10:18 I guess we may go quickly through the status of the plugins 14:10:24 #topic Plugin update status 14:10:40 shuyingya just mentioned the upgrade of vanilla 14:11:06 most of the task has been finished. 14:11:07 Spark 2.2 was merged 14:11:38 still some bugs need further investigate 14:12:19 oh, no, Spark 2.2 is still not merged in s-i-e 14:12:29 no, sorry, misread 14:12:33 * tosky rewinds 14:12:42 Spark 2.2.0 and Storm 1.1.1 merged 14:12:55 shuyingya: something that can be fixed in few days of work? 14:13:44 about vanilla, do you have any idea about the version of other services like hive, oozie, spark on yarn? 14:13:48 tosky, sure. 14:14:42 I think it can be fixed in next few days if there is no new bugs :) 14:14:47 perfect! 14:15:28 shuyingya, you mean what versions should be on vanilla for those services? 14:15:28 I would like to enable vanilla 2.8.2 includes: hive -> 1.2.2 oozie -> 4.30 and spark -> 2.2.0 14:15:33 about the other services, I'm not sure; my personal idea is: the most recent stable version that works with that version of vanilla and all the versions of the other components 14:15:36 yes 14:16:04 I agree with tosky, just make sure the the version is supported 14:16:39 ok, I will confirm it tomorrow. 14:17:13 anything else about the plugin versions? 14:17:33 I haven't started working on ambari yet 14:17:42 will take a look on that hopefully by next week 14:18:15 yeah, and hopefully we can unify the version of ambari (spawning different HDP with the same ambari) 14:19:20 tosky, HDP/Ambari always confuses me 14:19:29 but will read on it 14:20:30 eheh, that's why I think that using only one ambari version would be better for everyone 14:21:26 ok, if there is nothing else on this topic, I would (ab)use my chair position for an unexpected topic 14:21:54 go for it 14:21:56 #topic Longer OpenStack release cycles? 14:22:03 soo, really quick 14:22:32 there is an big discussion (>=40 emails in 1 day) about changing the release schedule of OpenStack to 1 year 14:23:09 or in general extending it, but 9 months is not possible due to the ongoing preparation for the Summit in the next 2 years 14:23:12 yeah, a bit overwhelming 14:23:27 if you haven't seen the discussion, please take a look at it 14:23:56 it would be interesting to hear from the "not-usual" contributors 14:24:26 for example, shuyingya and all the people that he is trying to bring aboard 14:24:51 exactly what I thought when I first read some of the ideas at the thread 14:25:02 my really personal view is that I'd welcome a longer release cycle, but without reducing the requirements for features freeze 14:25:13 it would give me more time to work properly - but that's me :) 14:25:28 so if you want to share your ideas now, feel free to 14:25:42 I like the idea of a longer cycle as well 14:26:55 BUT, I fear that longer cycles with no structure can delay a lot development because we just have more time 14:27:27 it would take a little more effort from PTLs, core team to keep the work flowing smoothly 14:27:33 not sure what the solution is 14:27:48 I am not reading it carefully, but it would be good for core team or ATC who focusing on it. 14:28:00 I agree about the structure: that's why I would prefer 9 months, because it gives "just" the more time needed from some stabilization, reducing the fixed costs associated with each releases 14:28:06 but 9 months is not possible, so... 14:28:28 true 14:30:18 (anyway, I miscounted, more than 80 emails in the thread) 14:31:37 any other comments on this topic? And also: any other topics before the Open discussion? 14:33:15 not from me 14:33:47 #topic Open Discussion 14:34:30 tellesnobrega: quick question about the UI support for the job removal; if it's linked to v2, don't we need saharaclient v2 support first? Or are you evaluating how to add it regardless of the API? 14:35:02 job removal? 14:35:11 instance removal, right? 14:35:49 I'm evaluating how to add regardless of the API, but you are right, we need APIv2 first 14:37:26 instance removal, yes 14:37:33 ok, I guessed so :) 14:38:14 landing an experimental 2.0 in Queens, if Rocky is going longer, we can probably kick it out from experimental status in one cycle only maybe 14:38:16 but let's see 14:38:37 that would actually be good 14:39:03 as I said to you, but making it official here, jeremey is working on adding APIv2 discovery on the client 14:41:11 I want to officially welcome shuyingya to the core team 14:41:20 congrats and well deserved :) 14:42:18 yep :) 14:42:36 anything else to share? 14:42:44 not from me 14:43:44 thanks for your warm welcoming :) 14:44:04 just get a phone call. not from me too 14:46:24 I guess you can close tosky 14:46:38 yep, I was waiting for the 5-minutes timeout 14:46:43 but we are good enough 14:46:56 thanks all, see you on the normal channel 14:47:03 #endmeeting