14:01:10 <tosky> #startmeeting sahara 14:01:11 <openstack> 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 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:01:15 <openstack> The meeting name has been set to 'sahara' 14:01:19 <shuyingya> o/ 14:01:26 <tosky> hi! Telles may not be around, so I will chair this time 14:02:05 <tosky> it looks like it may be quick, but let's see 14:02:12 <tosky> #topic News/Updated 14:03:06 <tosky> 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 <tosky> 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 <shuyingya> 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 <tosky> oh, it's the first meeting with shuyingya as core, congratulation again! 14:04:30 <shuyingya> haha, thanks tosky 14:05:46 <tosky> 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 <tellesnobrega> o/ hey guys, made it a little bit late but made it 14:06:23 <shuyingya> col 14:06:30 <tosky> oh, good! 14:06:32 <shuyingya> cool 14:06:54 <tosky> 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 <tellesnobrega> please keep going, you are in charge today tosky 14:07:05 <tellesnobrega> thanks 14:07:15 <shuyingya> :) 14:07:35 <shuyingya> tosky, we don't have sahara-ci anymore? 14:08:00 <tosky> shuyingya: not the old one 14:08:28 <tosky> 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 <tosky> Jeremy knows better the status of the hardware 14:08:54 <tosky> but even without the sahara-ci we can set some jobs on the main infra 14:09:05 <tellesnobrega> I sent out the requested email to MOC people but haven't got a response 14:10:18 <tosky> I guess we may go quickly through the status of the plugins 14:10:24 <tosky> #topic Plugin update status 14:10:40 <tosky> shuyingya just mentioned the upgrade of vanilla 14:11:06 <shuyingya> most of the task has been finished. 14:11:07 <tosky> Spark 2.2 was merged 14:11:38 <shuyingya> still some bugs need further investigate 14:12:19 <tosky> oh, no, Spark 2.2 is still not merged in s-i-e 14:12:29 <tosky> no, sorry, misread 14:12:33 * tosky rewinds 14:12:42 <tosky> Spark 2.2.0 and Storm 1.1.1 merged 14:12:55 <tosky> shuyingya: something that can be fixed in few days of work? 14:13:44 <shuyingya> about vanilla, do you have any idea about the version of other services like hive, oozie, spark on yarn? 14:13:48 <shuyingya> tosky, sure. 14:14:42 <shuyingya> I think it can be fixed in next few days if there is no new bugs :) 14:14:47 <tosky> perfect! 14:15:28 <tellesnobrega> shuyingya, you mean what versions should be on vanilla for those services? 14:15:28 <shuyingya> 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 <tosky> 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 <shuyingya> yes 14:16:04 <tellesnobrega> I agree with tosky, just make sure the the version is supported 14:16:39 <shuyingya> ok, I will confirm it tomorrow. 14:17:13 <tosky> anything else about the plugin versions? 14:17:33 <tellesnobrega> I haven't started working on ambari yet 14:17:42 <tellesnobrega> will take a look on that hopefully by next week 14:18:15 <tosky> yeah, and hopefully we can unify the version of ambari (spawning different HDP with the same ambari) 14:19:20 <tellesnobrega> tosky, HDP/Ambari always confuses me 14:19:29 <tellesnobrega> but will read on it 14:20:30 <tosky> eheh, that's why I think that using only one ambari version would be better for everyone 14:21:26 <tosky> ok, if there is nothing else on this topic, I would (ab)use my chair position for an unexpected topic 14:21:54 <tellesnobrega> go for it 14:21:56 <tosky> #topic Longer OpenStack release cycles? 14:22:03 <tosky> soo, really quick 14:22:32 <tosky> there is an big discussion (>=40 emails in 1 day) about changing the release schedule of OpenStack to 1 year 14:23:09 <tosky> 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 <tellesnobrega> yeah, a bit overwhelming 14:23:27 <tosky> if you haven't seen the discussion, please take a look at it 14:23:56 <tosky> it would be interesting to hear from the "not-usual" contributors 14:24:26 <tosky> for example, shuyingya and all the people that he is trying to bring aboard 14:24:51 <tellesnobrega> exactly what I thought when I first read some of the ideas at the thread 14:25:02 <tosky> my really personal view is that I'd welcome a longer release cycle, but without reducing the requirements for features freeze 14:25:13 <tosky> it would give me more time to work properly - but that's me :) 14:25:28 <tosky> so if you want to share your ideas now, feel free to 14:25:42 <tellesnobrega> I like the idea of a longer cycle as well 14:26:55 <tellesnobrega> BUT, I fear that longer cycles with no structure can delay a lot development because we just have more time 14:27:27 <tellesnobrega> it would take a little more effort from PTLs, core team to keep the work flowing smoothly 14:27:33 <tellesnobrega> not sure what the solution is 14:27:48 <shuyingya> I am not reading it carefully, but it would be good for core team or ATC who focusing on it. 14:28:00 <tosky> 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 <tosky> but 9 months is not possible, so... 14:28:28 <tellesnobrega> true 14:30:18 <tosky> (anyway, I miscounted, more than 80 emails in the thread) 14:31:37 <tosky> any other comments on this topic? And also: any other topics before the Open discussion? 14:33:15 <tellesnobrega> not from me 14:33:47 <tosky> #topic Open Discussion 14:34:30 <tosky> 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 <tellesnobrega> job removal? 14:35:11 <tellesnobrega> instance removal, right? 14:35:49 <tellesnobrega> I'm evaluating how to add regardless of the API, but you are right, we need APIv2 first 14:37:26 <tosky> instance removal, yes 14:37:33 <tosky> ok, I guessed so :) 14:38:14 <tosky> 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 <tosky> but let's see 14:38:37 <tellesnobrega> that would actually be good 14:39:03 <tellesnobrega> as I said to you, but making it official here, jeremey is working on adding APIv2 discovery on the client 14:41:11 <tellesnobrega> I want to officially welcome shuyingya to the core team 14:41:20 <tellesnobrega> congrats and well deserved :) 14:42:18 <tosky> yep :) 14:42:36 <tosky> anything else to share? 14:42:44 <tellesnobrega> not from me 14:43:44 <shuyingya> thanks for your warm welcoming :) 14:44:04 <shuyingya> just get a phone call. not from me too 14:46:24 <tellesnobrega> I guess you can close tosky 14:46:38 <tosky> yep, I was waiting for the 5-minutes timeout 14:46:43 <tosky> but we are good enough 14:46:56 <tosky> thanks all, see you on the normal channel 14:47:03 <tosky> #endmeeting