14:00:24 <tellesnobrega> #startmeeting sahara
14:00:25 <openstack> Meeting started Thu Mar 23 14:00:24 2017 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:26 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:29 <openstack> The meeting name has been set to 'sahara'
14:01:35 <zemuvier> o/
14:01:39 <jeremyfreudberg> o/
14:02:06 <shuyingya> hi o/
14:02:24 <vgridnev> o/
14:02:26 <tosky> o/
14:02:44 <tellesnobrega> #topic News/Updates
14:03:20 <tosky> fire! The gates for sahara-image-elements are now unlocked (I have few reviews there, you can guess what I'm testing)
14:03:49 <tosky> the gates for sahara.git are still broken, it's an eventlet change which removed a method and it probably requires a change in the way the monkey patching is done
14:03:56 <tosky> if I understood it correctly
14:04:14 <zemuvier> esikachev and I are trying to return sahara-ci to live again
14:04:17 <vgridnev> nothing new to me; I have ready version of sahara with Apache + testing multinode sahara
14:04:34 <vgridnev> #link https://review.openstack.org/#/c/443568/
14:04:36 <tellesnobrega> SotK, first I will start with the summit updates, zemuvier I talked with TSP people and I don't have any influence on who gets it, so it is totally up to the tsp
14:05:06 <shuyingya> nothing from my side, working on internal stuff.
14:05:07 <zemuvier> tellesnobrega: so we well get the results in the end of march, am I right?
14:05:16 <zemuvier> will*
14:05:21 <tellesnobrega> i think so
14:05:35 <zemuvier> so we should only wait
14:05:44 <zemuvier> let's hope on the best
14:05:54 <tellesnobrega> on more technical update, I'm working on image gen and got a couple patches yesterday but they still need work, cdh is close to being ready
14:06:04 <tellesnobrega> ambari needs a lot of work
14:06:52 <zemuvier> btw, I think it's ready https://review.openstack.org/#/c/443554/
14:07:15 <tellesnobrega> other than that, I'm starting to look into micro versions for api v2, I talked with tosky and raissa yesterday about it and there are some definitions that need detailing so I will be sending a patch upstream so we all can pitch in
14:07:44 <tellesnobrega> zemuvier, great
14:09:05 <tellesnobrega> about the boston summit, you all probably saw that there was a request for forum topics for discussion in more of a horizontal way
14:10:07 <tellesnobrega> I didn't start a brainstorm for sahara because I don't believe we will have people there to do a lot of discussing, if anyone has any topic that strongly believe I should bring it up there please let me know and I will try to do so, otherwise I won't propose topics for sahara
14:10:20 <tellesnobrega> and will work on the onboarding and speed mentoring
14:11:35 <tellesnobrega> About outreachy, I was contacted by around 4 or 5 people interested in working on sahara, I can only work with one, and if anyone of you would like to propose a project for the outreachy and try to score someone else to work on it let me know and I will try to see if it is still possible
14:12:24 <tellesnobrega> mariannelm is not around today, but she asked me to ask people to review https://review.openstack.org/#/c/427480/
14:13:07 <tellesnobrega> this is part of the pluggability work and we should try to get it ready asap
14:14:08 <tellesnobrega> anyone else has news or updates?
14:15:23 <tellesnobrega> #topic Specs / features status
14:15:41 <tellesnobrega> shuyingya, are you still working on api v2 right?
14:16:27 <tellesnobrega> as I said, I'm working on microversions, but I will send an email on it before I can move on it
14:17:01 <shuyingya> yep, I have nearly finished the job-binary-internal but mariannelm posted yet. and I am little busy with internal stuff recently
14:17:28 <tellesnobrega> I ask of everyone here to take some time to review shuyingya's patches on api v2, so we can continue moving on with it
14:17:49 <tellesnobrega> shuyingya, you can sync with her so she won't redo stuff you already have done, and you can merge it
14:18:21 <shuyingya> so I think we should mark our state on wiki before working on it.
14:18:37 <tellesnobrega> shuyingya, yes, this would be the best approach for sure
14:19:03 <tellesnobrega> I mean about the work you already have done, you can increment her patch or send her tips on how to get it better
14:19:14 <tellesnobrega> I trust your judgment there
14:19:17 <shuyingya> yep. I will
14:19:20 <tellesnobrega> thanks
14:19:24 <shuyingya> np
14:19:28 <shuyingya> ^^
14:19:39 <tellesnobrega> also we need review on esikachev's spec
14:20:13 <tellesnobrega> is anyone working on plugin updates?
14:20:36 <tellesnobrega> #link https://review.openstack.org/#/c/443554/
14:20:40 <tellesnobrega> to review ^
14:20:54 <shuyingya> I will review these patches after meeting.
14:21:08 <tosky> we had few new plugin versions in Ocata, but probably we need more testing
14:21:18 <tellesnobrega> shuyingya, great
14:21:25 <tellesnobrega> tosky, true
14:21:28 <shuyingya> I think jiasen can work on CDH 5.10, but he is preparing on his paper in school
14:21:31 <tosky> for example: https://bugs.launchpad.net/bugs/1672218
14:21:31 <openstack> Launchpad bug 1672218 in Sahara "Using ambari 2.4 with 2.4.0.1 image - inconsistent server/agent version" [Undecided,New]
14:23:32 <tellesnobrega> I believe we agreed to bring new versions of CDH to 5.10 and Spark to 2.1.0 and Storm to its newest version
14:23:40 <tellesnobrega> I think I can work on spark and storm
14:24:23 <tellesnobrega> this is prio, so we need to get started on that
14:24:52 <jeremyfreudberg> tellesnobrega, seems like hadoop 2.8.x release timeframe was finally announced last week: https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release
14:25:38 <tellesnobrega> jeremyfreudberg, interesting, lets take a look and add it to our list to update it as well
14:25:47 <shuyingya> jeremyfreudberg \o/
14:25:49 <tosky> oh, is it me or theis releases took more time than 2.6->2.7?
14:26:13 <jeremyfreudberg> tosky, this release took very long time...
14:26:18 <tosky> 3.0.0 GA	2017-08-15 uh
14:26:25 <tosky> that overlaps with Pike
14:26:56 <jeremyfreudberg> tosky, I think Pike release *is* August, so I think 3.x will be for us Q release?
14:26:59 <tellesnobrega> tosky, yes, looks like this will be a work for queen
14:27:28 <tosky> and it could easily sleep
14:28:15 <tellesnobrega> what do you mean?
14:28:48 <tellesnobrega> does it make sense to update to 2.8.0 now and to 3.0 in queen?
14:29:38 <jeremyfreudberg> tellesnobrega, I think 3.0 is more important. 2.8 only if we have the extra resources/time
14:30:43 <tellesnobrega> vgridnev, tosky ^
14:31:35 <tosky> I mean that the release dates usually are delayed, seldom happens earlier than planned
14:32:07 <tosky> so if they say GA for August, even if there is a rc for July, it's not something too reliable with our schedule
14:32:23 <tosky> especially as they plan 2.8 (now), 2.8.1 (ok) and 2.9
14:33:18 <tellesnobrega> 3.0 in unreasonable for pike
14:33:40 <tellesnobrega> queen for sure if the maintain the schedule
14:33:57 <tellesnobrega> about 2.8 makes sense to have people working on it for pike?
14:34:44 <tosky> vanilla it's the baseline, it would be nice (but I can't personally commit on it)
14:35:01 <tellesnobrega> I think so too
14:35:11 <vgridnev> I don't have strict opinion on what we should support first. Actually support of 2.8 should be really easy.
14:35:45 <jeremyfreudberg> I think 2.8 would be nice. But not as high priority as refactor CDH, Spark 2.x
14:36:04 <tellesnobrega> vgridnev, true, let's see, if someone steps up and can work on it great. I will have this added to our schedule and figure out who can do it or even do it myself
14:37:35 <tellesnobrega> SotK, lets move on
14:37:48 <tellesnobrega> #topic Open Discussion
14:38:18 <tellesnobrega> anyone has anything that want to discuss at this point?
14:38:27 <jeremyfreudberg> tellesnobrega - just want to remind you about investigating the pig-oozie thing
14:38:57 <tellesnobrega> jeremyfreudberg, right, can you remind me what am I investigating, can't remember now
14:40:12 <jeremyfreudberg> tellesnobrega, lol, sure, basically the issue is pig libs are only installed when oozie is also installed. also those pig libs live in HDFS (oozie sharelib) so regular user can't even access them without oozie workflow
14:40:31 <jeremyfreudberg> so this is explaining why Pig works on EDP but not "manually" for regular user
14:41:16 <tellesnobrega> ok, we want to decouple this right? you want to know if its possible right?
14:41:48 <jeremyfreudberg> well it's definitely possible to divorce pig and oozie. we just want to know first why it was done like that. and then figure out a way to do it cleanly
14:42:46 <tellesnobrega> jeremyfreudberg, awesome. I will write it down so I won't forget it again
14:43:18 <jeremyfreudberg> cool, thanks (I need to go afk now)
14:44:06 <tellesnobrega> anyone else? I will leave the microversion discussion for ML so we can have an easier register and input from people that have done it already
14:44:20 <tellesnobrega> if not, we can have 15 minutes back
14:45:49 <tellesnobrega> ok guys, thanks for coming
14:46:04 <tellesnobrega> lets keep up the good work :)
14:46:22 <tellesnobrega> #endmeeting