18:05:50 #startmeeting savanna 18:05:50 Meeting started Thu Aug 8 18:05:50 2013 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:05:51 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:05:53 The meeting name has been set to 'savanna' 18:05:56 <_tmckay> I am not here :) jk 18:06:27 are there anyone from Hortonworks? 18:07:12 let's wait for several minutes 18:08:37 #topic Agenda 18:08:37 #info News / updates 18:08:37 #info Roadmap cleanup / update 18:08:37 #info Action items from the last meeting 18:08:37 #info General discussion 18:08:58 #topic News / updates 18:09:53 the only update from me is that we are working on finalizing conductor module 18:10:26 what's about EDP news? 18:10:56 small news, I should have a commit for job origin REST api today, and hopefully database objects tomorrow 18:11:11 maybe implementation of "get" to hdfs early next week... 18:11:13 tmckayrh, great! 18:11:21 that's great, tmckayrh 18:11:28 you're too kind :) 18:11:29 I have some dummy skeleton impl done for the EDP UI. I'll be tweaking the forms over the next few days. 18:11:52 I have one question for all edp mates: did we agree to use savanna sql db to store binaries? 18:11:59 for EDP we add a model not it is on review 18:12:06 in Joborigin I mean 18:12:23 #link https://review.openstack.org/#/c/40227/ 18:12:35 want to ask everyone to split big changes to small ones 18:12:43 also we start working on conductor layer for EDP 18:13:04 #link https://review.openstack.org/#/c/40591/ 18:13:07 also I have one patch on the review to creating map-reduce workflow.xml 18:13:17 aignatov_, yes, I think we agreed to look at savanna db storage for binaries to support sites that don't have swift 18:13:32 aignatov_, I can pursue that first... 18:13:42 great, thx 18:13:51 now we have two workflows one for pig and classic for jar files 18:13:59 let's move edp to separated section 18:14:05 only news here, please 18:14:21 #link https://review.openstack.org/#/c/40590/ 18:14:38 are there any other updates on edp? 18:15:10 mattf, are there any news about savanna in fedora? 18:15:46 anyone have opinions about giving savanna-api it's own uid/gid? 18:15:54 s/it's/its/ 18:16:10 mm, nope :) 18:16:29 fedora has two options for user/group, you can be added to the setup rpm and have a static id in /etc/passwd|groups, or you can have a dynamic id created when the package is installed. 18:16:51 mattf, I think static one could be helpful 18:17:05 i'm honestly ambivalent when it comes to using a static uid/gid. the package reviewer would like a static one to go along with other static ids for openstack components. 18:17:18 how would a static one be helpful? 18:18:21 mattf, no ideas now, just I think that it would be no worse than dynamic ones 18:18:51 mattf, btw have no expertise in areas around this topic 18:19:03 my trajectory is to say we'll be dynamic for now, static if we find a specific need in the future. the fedora folks are sticklers when it comes to handing out static ids. 18:19:43 i do. typically shared files across a network filesystem need static ids. 18:19:43 mattf, yep, I think it's reasonable, agreed 18:19:54 I think, mattf, you only know the best way how to do that in a right way :) 18:19:57 but the savanna-api service should be able to operate on local files 18:20:24 in any event. sounds like we're all kinda ambivalent. let's move on. 18:20:31 yep 18:20:41 are there any other updates? 18:21:29 ok, next topic 18:21:31 #info Roadmap cleanup / update 18:21:41 #link https://wiki.openstack.org/wiki/Savanna/Roadmap 18:21:57 we have several discussions about it and decided to update it with bps 18:22:42 additionally, we decided to update it by discussions on our weekly irc meetings 18:22:55 so, the question is 18:23:04 are there any missed points in bp? 18:23:21 so as far as roadmap is concerned I have some comments and concerns about the current api 18:23:51 I haven't gotten to documenting it all but want to discuss it sooner rather than later 18:24:19 i'm comfortable w/ the roadmap items for this week. i do think we should keep buckets for the next two releases on the roadmap, e.g. 1.0 and 1.1 since we're working on 0.3 18:24:54 mattf, yes, I think it'll be good 18:24:54 do we plan to move from 0.3 right to 1.0,1.1? 18:25:13 aignatov_, that's pretty much what the roadmap says 18:25:30 ok)) 18:25:42 I think that it'll be clear in sep-oct, because maybe it'll be better to use icehouse-1, icehouse-2 releases and etc. 18:26:14 additionally, I'm proposing the roadmap style update 18:26:25 here is a draft of it - https://wiki.openstack.org/wiki/Savanna/RoadmapNew 18:26:32 (for only 0.3 section) 18:27:13 the contents section will display some main goals and in each section we can add small description and links to bps 18:27:22 any concerns? 18:27:57 overkill imho. if we have roadmap items link to relevant BPs, we don't necessarily need to list out each sub bullet. 18:28:12 +1 18:28:30 i'm a fan of keeping the roadmap as high level highlights, very lightweight 18:28:39 I mean that we can have a description if it's needed and we'll a place to list links to bps 18:29:02 I'd think just having the blueprints marked for a service should be more than enough 18:29:08 service/series 18:29:15 ok, sounds reasonable to keep it lightweight 18:29:34 ex: Enhanced scalability through scale-out architecture (bp1) (bp2) 18:29:40 so, just list bps under the each item 18:29:47 if there are 5 bps, then have a bp to aggregate 18:30:05 ok, lgtm 18:30:12 any other comments / thoughts? 18:30:38 * mattf shakes 18:31:02 #action aignatov to update edp-related part of roadmap (cleanup, add links to bps) 18:31:22 #action slukjanov to update architecture-related part of roadmap (cleanup, add links to bps) 18:31:34 ok. will do 18:32:15 #info Update roadmap with links to bps, if there are 5 bps, then have a bp to aggregate [ex: Enhanced scalability through scale-out architecture (bp1) (bp2)] 18:32:32 ok, next topic 18:32:32 #topic Action items from the last meeting 18:32:40 btw, 5 was arbitrary. use good judgment. 18:33:18 1. _crobertsrh create blueprint for EDP Horizon dashboard (since Robert is working on UI part) 18:33:50 crobertsrh, ^^ 18:33:55 2. akuznetsov will rename the Job Source Component to Job Origin Component 18:34:01 2. tmckayrh will make a blueprint for an uncompiled source code management component 18:34:06 4. tmckayrh will update sequence diagrams and etherpad to show proper flow and the rename of Job Source Component to Job Origin Component 18:34:14 I did that...looking for link now 18:34:21 3 and 4 done 18:34:24 #link https://blueprints.launchpad.net/savanna/+spec/edp-savanna-dashboard-ui 18:34:33 guys, if action items was completed, please ack it and publish links (if needed) 18:35:07 my link was from crobertsrh 18:35:11 https://blueprints.launchpad.net/savanna/+spec/edp-job-build-component 18:35:32 https://wiki.openstack.org/wiki/Savanna/EDP_Sequences 18:35:38 thanks aignatov_ 18:35:57 akuznetsov? 18:36:43 if we are talking about corresponding bp 18:36:46 it's here 18:36:48 https://blueprints.launchpad.net/savanna/+spec/edp-job-origin-component 18:36:51 #link https://blueprints.launchpad.net/savanna/+spec/edp-job-origin-component 18:36:57 ok, thanks 18:37:04 great, looks like all action items resolved 18:37:08 yes I renamed this blueprint and made correction 18:37:14 ah, I forgot the pound link. Should I repaste? 18:37:36 no 18:37:39 yep 18:37:50 lol, which is it? 18:37:51 no or yep? :) 18:37:54 ^) 18:38:05 ok, I will repaste.... 18:38:05 tmckayrh, please, repost them with #link ... 18:38:18 tmckayrh, thx, it's needed to add them to meeting minutes 18:38:19 it is not needed to add #link if message contains http 18:38:49 #link https://blueprints.launchpad.net/savanna/+spec/edp-job-build-component 18:39:04 #link https://wiki.openstack.org/wiki/Savanna/EDP_Sequences 18:39:08 for sure then :) 18:39:15 tmckayrh, thx! 18:39:18 #topic General discussion 18:39:39 may I begin? 18:39:44 yes, sure! 18:39:57 I have one question about oozie+hive. Is it the normal case to start hive as a separate service and use it during oozie's workflow running? We have some conserns about it: it is not clear how to run metastore server and is it really needed? Maybe someone has an expertise in it? 18:41:25 I'm going to send the question on mail-list. but maybe someone is already here :) 18:41:31 hmm not sure don't think I've ever tried it without the metastore 18:42:09 Since Oozie already has some Hive libs it may work witout separate hive service 18:42:17 in my opinion) 18:42:51 i may be wrong 18:42:58 anyway we should check it 18:43:14 so those are listed as optional components 18:43:45 possible if we deal we external data we should use a external metastore 18:43:46 what is listed as optional? 18:43:55 metastore server 18:44:08 really? interesting... 18:44:34 ok. Let's continue discussions in mailing list 18:44:43 yep 18:46:00 ok, are there any other questions to discuss? 18:46:12 so I wanted to briefly talk about the current api 18:46:14 #idea we should setup a Savanna PTL election 18:46:59 obviously not official w/i openstack, but an elected representative for the savanna community 18:47:22 the person should function as if they were an official openstack ptl, including attending tc meetings etc 18:47:27 thoughts? 18:47:54 mattf, is there any sense to make it before incubation? 18:48:36 for one, well the incubation request needs to specify a ptl 18:49:00 btw tc will be reelected soon and we'll not automatically contain all ptls 18:49:04 we can also follow the standard OS process here and demonstrate our commitment and ability to fit into it 18:49:13 (afaik in sep) 18:50:12 Is it time to choose :)? 18:50:35 or there will be a separate meeting? 18:50:51 if we think it's a good idea. i'm happy to go off and make a proposal for how we'd go about it. 18:50:55 +1 for following OpenStack process 18:51:18 i've only lightly reviewed how it has happened in the past, but deciding now is probably not the way to go. 18:51:19 I think this is a good idea 18:51:33 mattf, we can follow the OS-style electing process 18:51:45 SergeyLukjanov, that would be best 18:52:05 mattf, I mail ttx about it 18:52:07 is anyone already familiar with how that election process works? 18:52:13 I like the idea to have ptl election 18:52:34 nope but we can find out from newly incubated projects like trove 18:53:05 mattf: if you're interested talk to hub_cap on #openstack-trove 18:53:07 also we should have core team elecations 18:53:15 *elections 18:53:22 mattf, I read the doc about elections several days ago and mail ttx about it to ensure 18:53:27 heyo 18:53:32 https://wiki.openstack.org/wiki/Governance/TieBreaking 18:53:44 feel free to chat w me mattf 18:53:55 hub_cap, will do 18:54:04 SergeyLukjanov, will yuo cc me on the ttx thread? 18:54:43 mattf, ok 18:55:17 sounds like no objections. i'll take the action to come back next week w/ a more formal proposal. 18:55:24 hub_cap, please, could we talk about elections after the meeting? 18:55:27 in some channel 18:55:36 sure i can join your channel, 18:55:39 just tell me where to go 18:55:42 we're #savanna 18:56:18 #action slukjanov to prepare ptl / core team elections proposals 18:56:55 ? 18:57:11 mattf, oops, missed your msg 18:57:23 #action mattf, slukjanov to prepare ptl / core team elections proposals 18:57:31 ok 18:57:48 you can #undo things too 18:57:52 if you make a mistake 18:58:04 and it will remove them so you dont have > 1 of the same #action 18:58:14 :D 18:58:19 let's try it 18:58:19 how how? 18:58:36 hub_cap, could it be done twice? 18:58:52 yes 18:58:53 #undo 18:58:53 Removing item from minutes: 18:58:54 try it 18:58:56 #undo 18:58:57 Removing item from minutes: 18:59:01 now redo 18:59:12 #action mattf,slukjanov to prepare ptl / core team elections proposals 18:59:31 SergeyLukjanov, imho, it's better if you just assist w/ the proposals 18:59:32 nice that's nifty 18:59:36 yar 19:00:23 in any event, we've successfully consumed all the time for api discussion. sorry. continue that on #savanna? 19:00:50 let's move discussions to #savanna channel 19:00:58 +1 19:01:27 that's fine :) 19:01:28 #info JFYI you can always use openstack-dev@lists.openstack.org mailing lists and #savanna irc channel to find us and ask your questions 19:01:34 #endmeeting