14:00:07 #startmeeting sahara 14:00:07 Meeting started Thu Jan 18 14:00:07 2018 UTC and is due to finish in 60 minutes. The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:12 The meeting name has been set to 'sahara' 14:00:16 o/ 14:00:22 o/ 14:00:43 waiting for shuyingya to show hands 14:01:06 i'll need to leave at 45-50ish minutes past 14:01:21 ok, we might not have too long meeting today 14:01:29 #topic News/Updates 14:02:35 cleaning few reviews, sent the review which enables the build and upload of oozie on tarballs (please review!), some various testing 14:03:05 o/ 14:03:33 I'm working on file transfer bug that we talked about in Denver, during the work I found out that we have a swift - keystone v3 problem that I found a quick solution, I will send a patch soon on that 14:04:39 not much new to say, just trying to wrap up the client stuff (1 week till client freeze) and also finishing up force delete 14:05:17 oh right, and s3_hadoop fixes 14:05:28 working on image build bugs and xenial image python issues as jeremyfreudberg suggested. also fix downstream tempest tests etc, it also affects upstream 14:06:43 sounds we all have our hands full, we have 1 week until Q3 14:07:08 and then bugfixes all way 14:07:20 yes 14:07:38 anymore news? 14:08:03 purposely trying to not turn my news into a big question/discussion 14:08:16 please proceed 14:08:25 oh, it will be the next point I suspect 14:08:30 :) 14:08:33 cool (rushing so we can fit all we need) 14:08:46 #topic APIv2 (a.k.a jeremy's show and tell) 14:08:56 tosky, you have the floor 14:09:01 I have a question in fact 14:09:13 go ahead 14:10:05 it's a follow up to the discussion that we had yesterday 14:10:58 the conclusion was that the form of the endpoints does not matter, and that we should update the devstack code with the unversioned endpoint after the saharaclient patch lands 14:11:42 and only the unversioned endpoints, if I understand it correctly 14:11:42 the unversioned endpoint should come when a v2-compatible saharaclient is on pypi 14:11:53 yes, but what about the old client? 14:12:07 it is true that the new saharaclient will be able to deal with the new endpoint 14:12:27 but shouldn't we make sure that old clients still continue to work with v1 if the old endpoints are exposed? 14:12:33 if you remember, monty's email suggested old deployments keep versioned url in catalog until a long time from now 14:12:37 new deployments have the unversioned 14:12:51 when i talk about devstack, i treat it as a fresh (not long lived) deployment 14:13:47 that's an interesting question, but given that sahara/queens will depend on the new saharaclient, it should not be a problem 14:14:15 but on the other side we should check grenade, so that the new endpoints are added too 14:14:35 I don't know the internals of grenade too much, and our jobs are still failing now, but I hope to have them fixed for the PTG 14:14:52 (btw, i'm assuming that vendors will provide the latest saharaclient with queens, if we don't get our minimum requirements bump in) 14:15:20 yes - keep an eye on grenade for sure 14:15:32 yes, that should happen; I was just concerned about the backward compatibility 14:15:45 but it seems it should work then - thanks 14:16:21 yep 14:16:42 thanks for clarification jeremyfreudberg 14:17:09 any more on this topic? 14:17:19 should we ping mordred? :) 14:17:27 probably 14:17:30 we should 14:17:35 already did I guess 14:18:03 i mean, the client will work as it is but i'm sure mordred would prefer the endpoint code to be more proper there 14:18:29 and to easy his search in the log, we are talking about https://review.openstack.org/#/c/533066/ 14:18:47 yes, thanks tosky was getting that 14:19:10 indeed, it's a bit early in most of the USA, he's probably not around yet 14:19:33 since mordred is not around right now, we can move on and when available we can talk @ #openstack-sahara 14:19:45 yep 14:20:19 #topic Dublin PTG 14:20:45 I don't know if you all have seen, but we were allocated Thursday and Friday in Dublin 14:21:45 sadly I discovered that my flight leaves Dublin at 17:40h, so I probably won't be able to be around Friday afternoon, but I believe it should be enough time 14:22:07 you can leave shortly after lunch 14:22:17 around 14:00 should be enough 14:22:34 yes 14:22:36 that is the plan 14:22:41 yes, i think we can squeeze enough into that day 14:23:04 whatever is left I'm more than sure that tosky and jeremyfreudberg and work it out 14:23:24 also, we have the etherpad up, lets start feeding it 14:24:26 that closes PTG, any questions there? 14:25:00 * tosky has no questions for now 14:25:11 we can move on 14:25:23 #topic Open Discussion 14:25:49 I guess that is the last topic we have 14:26:25 the queue of incoming reviews is better, and all the tiny doc patches have been reviewed and were merged or waiting for some action from the submitter 14:26:43 well, some of them are waiting a +2 14:26:51 yes, a lot of small patches recently 14:27:02 i guess people want to get their name in before freeze 14:27:22 we are running out of http and spelling errors :) 14:27:30 getting very close 14:28:15 the other thing to mention, about s3_hadoop 14:28:28 after the oozie generation (thanks! let's see if it does what it should), now I'm personally waiting for the +1->+2 by jeremyfreudberg on the MapR review 14:28:36 oh, right, s3_hadoop 14:29:00 i think i need to fix it in two patches, right? one which is the minimal fix that we can backport to pike 14:29:14 and finally release 7.0.1 (which is desperately needed downstream) 14:29:22 and then a bigger fix for master only 14:29:30 sounds about right 14:29:36 yes, the patch to fix vanilla, we have a bug for that 14:29:50 that's more urgent; the rest can be postponed between queens-3 and the final release 14:29:54 in the bugfix phase 14:30:06 yes, exactly 14:30:48 my point is: we can backport something easy to pike that might not totally support s3 functionality but just gets clusters to work 14:31:22 yes 14:31:47 yes 14:31:50 btw, shuyingy_ what is happening with hbase element for vanilla image? 14:33:15 I don't have hands to take care of vanilla upgrade and habse integration. 14:34:04 vanilla upgrade is very close to finish. I will update them asap 14:34:22 shuyingy_, I would say focus on vanilla upgrade 14:34:28 we need that asap 14:34:31 yes, i would say vanilla upgrade is priority 14:34:50 we could get FFE for hbase maybe 14:34:57 probably 14:35:07 depends on its state and probability to break stuff 14:35:12 vanilla has last step to push is that oozie webUI need two jar packages conflict with tomcat. 14:35:40 java dependency hell is not fun 14:35:51 never 14:35:59 I will remove them when starting cluster. 14:37:01 is that the best solution? 14:37:06 FYI: The method getJspApplicationContext(ServletContext) is undefined for the type JspFactory. 14:37:30 I have tried to remove it from SIE. 14:38:47 didn't work I suppose 14:38:49 but found it doesn't have these files. these files are decompressed when executing "oozied.sh start" 14:38:59 shuyingy_, makes sense 14:38:59 yep 14:39:34 ok, that makes sense then 14:39:38 so we have to remove /opt/oozie/oozie-server/webapps/oozie/WEB-INF/lib/servlet-api-2.5.jar and jsp-api-2.0.jar from sahara side 14:40:01 s/dependency hell / 14:40:19 crazy :( 14:40:46 let us know if it works 14:40:55 the dawn is coming 14:41:08 it works now. 14:41:14 awesome lol 14:41:18 \o/ 14:41:39 that's all 14:42:14 another quick topic: is anyone proposing for the next summit? 14:42:17 in may 14:42:20 * tosky is not 14:42:36 not right now, do you have anything in mind? 14:43:24 not sure if i will propose anything, but i do have a lot to say about part-time contributions and attending university concurrently, stuff like that 14:43:33 cool 14:43:41 it would be interesting 14:43:46 I've done my share of that 14:44:11 good way to advertise myself as well 14:44:12 +1 would be interesting 14:44:19 of course 14:44:58 I'm thinking on topics, but nothing came to mind yet 14:46:29 anything else? 14:46:52 I think jeremyfreudberg is almost leaving, if we don't have anything more to discuss I will close the meeting 14:47:05 yes - i am almost leaving 14:47:18 and we are not far from the end of the hour anyway 14:47:41 yes 14:48:02 lets keep up the work, we have 1 week to finish all features. 14:48:18 see you all around 14:48:25 o/ 14:48:31 bye 14:49:12 bye 14:49:41 #endmeeting