14:00:11 <SergeyLukjanov> #startmeeting sahara
14:00:12 <openstack> Meeting started Thu Feb 26 14:00:11 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:16 <SergeyLukjanov> #link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda
14:00:16 <NikitaKonovalov> o/
14:00:17 <openstack> The meeting name has been set to 'sahara'
14:00:23 <SergeyLukjanov> #topic sahara@horizon status (crobertsrh, NikitaKonovalov)
14:00:30 <SergeyLukjanov> folks, please
14:00:31 <SergeyLukjanov> #link https://etherpad.openstack.org/p/sahara-reviews-in-horizon
14:00:38 <elmiko> yo/
14:00:56 <crobertsrh> Many merged patches, which is good.
14:01:01 <NikitaKonovalov> we've got a status description change merged this week
14:01:08 <egafford> o/
14:01:08 <crobertsrh> Still need reviews on the cluster/job execution guides
14:01:29 <NikitaKonovalov> job executions fix is still pending
14:01:36 <crobertsrh> I believe that the blueprint for adding an events tab to the cluster view will be approved.
14:01:50 <NikitaKonovalov> crobertsrh: It's already approved
14:01:56 <NikitaKonovalov> on yesterdays meeting
14:02:14 <crobertsrh> Ah, yep.  I know it was discussed
14:02:20 <NikitaKonovalov> the change is WIP as the backend API is going to change soon
14:02:57 <NikitaKonovalov> vgridnev is working on that
14:03:17 <SergeyLukjanov> nice
14:03:30 <NikitaKonovalov> no more updates from me here
14:03:36 <SergeyLukjanov> so, overall status is good, yeah?
14:03:48 <vgridnev> yes
14:03:51 <NikitaKonovalov> SergeyLukjanov: yep
14:04:00 <SergeyLukjanov> okay, let's move on
14:04:01 <SergeyLukjanov> #topic News / updates
14:05:04 <elmiko> working on barbican integration and investigating hadoop secure mode
14:05:09 <vgridnev> i'm working with updating events backend
14:05:12 <sreshetnyak> i'm working on migration to openjdk
14:05:24 <huichun_> working on Add a common HBase lib in hdfs on cluster start
14:05:25 <tosky> still working on tempest (a bit put aside) and now trying to push sahara/horizon integration tests based on the new framework
14:05:40 <kchen> I am still working on adding cm api library into cdh
14:05:41 <sreshetnyak> please review: #link https://review.openstack.org/#/c/146434/
14:06:28 <egafford> Creating the Oozie shell job type. Passing tests; working on doc now.
14:06:46 <vgridnev> intel folks, it would be nice if you put your review for patches with names Applying event log for CDH - part X
14:06:50 <SergeyLukjanov> tosky, how is it going?
14:07:20 <tosky> SergeyLukjanov: for horizon? Few pieces still needs to go in place
14:07:53 <huichun_> vgridnev: ok
14:09:14 <SergeyLukjanov> tosky, yeah, I mean horizon
14:09:28 <SergeyLukjanov> anyything else?
14:09:49 <SergeyLukjanov> #topic Open discussion
14:10:09 <SergeyLukjanov> #link https://wiki.openstack.org/wiki/Kilo_Release_Schedule
14:10:15 <SergeyLukjanov> #info March 5 is FPF
14:11:02 <elmiko> :cough: https://review.openstack.org/#/c/157432/ :cough:
14:11:06 <elmiko> ;)
14:11:19 <egafford> A question: Sahara states that distributed mode is in alpha when you start in that mode. Are there known problems w/ distributed mode, and is there a roadmap toward maturity for this feature?
14:12:29 <egafford> (Or is it just "wait a while, and if no problems are reported, take off the warning?")
14:13:32 <elmiko> at this point i think we have to talk about roadmap to full feature
14:13:44 <egafford> elmiko: +1
14:14:19 <elmiko> i would think before we declare it production ready we will need a ci test for it?
14:14:30 <SergeyLukjanov> I think we should remove this warning in Kilo
14:14:36 <SergeyLukjanov> we're already testing it a lot
14:14:47 <SergeyLukjanov> (half of the sahara-ci jobs are running in distrib mode)
14:14:52 <elmiko> ok, so yea maybe time to remove the warning
14:14:56 <egafford> SergeyLukjanov: Perfect.
14:15:15 * pino|work politely raises his hand
14:15:15 <elmiko> should we make a bug to remove the warning?
14:16:05 <pino|work> i just wanted to note that (due to other work) i've been testing sahara-image-elements (both juno and master) with diskimage-builder master
14:16:49 <elmiko> pino|work: aside from the duplicate naming issue, any other problems?
14:16:51 <pino|work> squashed few bugs related to that (1 in s-i-e, and 3 in d-i-b)
14:17:12 <SergeyLukjanov> pino|work, cool!
14:17:14 <pino|work> https://review.openstack.org/158347 (in s-i-e, merged)
14:17:30 <pino|work> https://review.openstack.org/159050 (in d-i-b, merged)
14:17:40 <pino|work> https://review.openstack.org/158383 (in d-i-b, merged)
14:17:54 <SergeyLukjanov> re s-i-e we've tried to build the RHEL based image for CDH and it works ok after some fixes, I think sreshetnyak proposed them already
14:18:14 <pino|work> https://review.openstack.org/158386 (in d-i-b, still missing, affecting ubuntu guests)
14:18:35 <SergeyLukjanov> pino|work, so, we could switch to the latest d-i-b after that?
14:19:31 <pino|work> i so far haven't been able to test many combination of sahara-related components/images
14:19:58 <pino|work> mostly vanilla 2.4.1 and hdp 2.0
14:20:15 <pino|work> (thanks to tosky too)
14:20:23 <egafford> SergeyLukjanov: Just to validate assumptions, re: trying to build the RHEL based image for CDH: you're using a RHEL 6 build host to build a RHEL 6 image using upstream (not packaged) DIB and SIE code. Is that correct?
14:21:02 <tosky> egafford: during last meeting the answer was "ubuntu"
14:21:07 <tosky> but let's see :)
14:21:35 <egafford> tosky: Ah, building from Ubuntu using upstream code. Good good. Just wanted to make sure I understood.
14:22:01 <pino|work> there may be more issues for rhel6/centos6, both as guests built and as build hosts
14:22:17 <sreshetnyak> egafford, i use ubuntu 14.04 as host system for build RHEL CDH image
14:22:38 <pino|work> part of it is touched by https://review.openstack.org/#/c/158820/ (the part about excuding --xattrs parameters)
14:22:58 <pino|work> (still referring to d-i-b/master)
14:23:50 <egafford> pino|work: Right; understood.
14:27:36 <SergeyLukjanov> anything else to discuss?
14:28:03 <pino|work> just a note: what would be a possible time schedule to migrate to a newer-ish d-i-b?
14:28:30 <pino|work> like, ASAP, or not earlier than ..., etc
14:28:46 <elmiko> could be done very quickly
14:29:06 <elmiko> just make a bug to update DIB_REPO_BRANCH, then propose a patch
14:29:11 <elmiko> i think it would get good support
14:29:36 <pino|work> is there a minimum set of images which are considered "must build"?
14:29:59 <elmiko> hmm, probably all the plugin images that are current
14:30:14 <tosky> current == master/kilo, right?
14:30:18 <elmiko> (for example not 2.4.0 since it's deprecated)
14:30:21 <elmiko> tosky: yea
14:30:26 <tosky> (as you can go back to the previous tag if you want to use the old ones)
14:30:32 <elmiko> exactly
14:30:37 <SergeyLukjanov> IMO it'll be great to upgrade to the lastest dib in kilo
14:31:02 <elmiko> should we make an action item ?
14:31:13 <tosky> especially the "support matrix"
14:31:15 <pino|work> so all the plugin types specified in diskimage-create.sh?
14:31:40 <elmiko> pino|work: yes, for all the plugins that are currently supported in kilo
14:31:43 <tosky> combination of plugin type and distribution type, I guess
14:31:48 <pino|work> elmiko: oki
14:33:01 <pino|work> another possibly dumb question: is having a tag in d-i-b with all the needed fixes/features a requirement, or a git commit within releases can be acceptable as well?
14:33:19 <elmiko> my preference would be a tag
14:34:07 <egafford> pino|work: Yeah, in theory anything that matches will work, but we'd love to build on something recognized by the DIB community as a supported release.
14:34:37 <elmiko> technically, DIB_REPO_BRANCH can be set to a commit sha
14:34:51 <pino|work> yeah, that's why i was asking
14:35:13 <elmiko> the dib crew seems pretty good about creating tags though, so it probably won't be an issue
14:36:12 <pino|work> makes sense, thanks for your answers!
14:37:16 <egafford> SergeyLukjanov: A very minor note: we may want to check group permissions on sahara-dashboard's stable/icehouse branch. It doesn't seem to pull review perms from sahara-stable-maint at present.
14:37:33 <SergeyLukjanov> egafford, I'll check it
14:38:09 <elmiko> yea, and somehow i got +2 perms on the dashboard for stable/icehouse only. very strange...
14:38:19 <egafford> SergeyLukjanov: Thanks.
14:38:56 <SergeyLukjanov> probably not all permission rules applied, I'll check them for all our repos
14:42:46 <SergeyLukjanov> sounds like end of the meetings ;)
14:42:49 <SergeyLukjanov> thx folks
14:45:12 <elmiko> SergeyLukjanov: thanks!
14:45:18 <SergeyLukjanov> #endmeeting