Tuesday, 2014-03-25

*** openstack has joined #openstack-sahara00:19
*** IlyaE has joined #openstack-sahara00:20
*** IlyaE has quit IRC00:26
*** alazarev has quit IRC00:33
*** bradd1 has joined #openstack-sahara01:47
*** elmiko has quit IRC02:51
*** witlessb has joined #openstack-sahara02:56
*** alazarev has joined #openstack-sahara04:01
*** alazarev has quit IRC04:48
*** Ch00k has joined #openstack-sahara05:24
*** IlyaE has joined #openstack-sahara05:31
*** alazarev has joined #openstack-sahara05:43
openstackgerritJenkins proposed a change to openstack/sahara: Imported Translations from Transifex  https://review.openstack.org/8271906:07
*** alazarev has quit IRC06:14
*** Ch00k has quit IRC06:38
*** bogdando has quit IRC07:05
openstackgerritA change was merged to openstack/sahara: Rename missed env variables in oslo code  https://review.openstack.org/8258207:07
*** IlyaE has quit IRC07:14
*** Ch00k has joined #openstack-sahara07:53
*** bogdando has joined #openstack-sahara08:03
openstackgerritSergey Reshetnyak proposed a change to openstack/sahara: WIP Add EDP integration tests for vanilla 2 plugin  https://review.openstack.org/8273308:05
openstackgerritSergey Reshetnyak proposed a change to openstack/sahara: Add EDP support for Vanilla 2 plugin  https://review.openstack.org/8247408:05
*** dmitryme has joined #openstack-sahara08:23
*** tmckay has quit IRC08:34
openstackgerritSergey Reshetnyak proposed a change to openstack/sahara: Add integration tests for vanilla 2 plugin  https://review.openstack.org/7708908:35
*** witlessb has joined #openstack-sahara08:56
*** tmckay has joined #openstack-sahara09:15
openstackgerritSergey Lukjanov proposed a change to openstack/sahara: Don't autocreate db on start  https://review.openstack.org/8275009:29
openstackgerritSergey Reshetnyak proposed a change to openstack/sahara: Add EDP support for Vanilla 2 plugin  https://review.openstack.org/8247409:35
openstackgerritDmitry Mescheryakov proposed a change to openstack/sahara: Remove agent remote  https://review.openstack.org/8275709:49
*** ruhe has left #openstack-sahara10:02
*** tosky has joined #openstack-sahara10:10
*** Ch00k has quit IRC10:11
*** Ch00k has joined #openstack-sahara10:13
*** eanxgeek|log is now known as eanxgeek10:52
openstackgerritSergey Reshetnyak proposed a change to openstack/sahara: Add EDP support for Vanilla 2 plugin  https://review.openstack.org/8247411:35
*** _crobertsrh has quit IRC11:38
*** IvanBerezovskiy has joined #openstack-sahara12:11
*** tmckay has left #openstack-sahara12:30
*** tmckay has joined #openstack-sahara12:31
*** dmitryme has quit IRC12:39
*** tosky has quit IRC12:47
*** _mattf is now known as mattf12:55
*** elmiko has joined #openstack-sahara12:59
*** crobertsrh has joined #openstack-sahara13:06
*** dmitryme has joined #openstack-sahara13:11
SergeyLukjanovtmckay, ping13:14
tmckayhi13:14
tmckaySergeyLukjanov, pong13:16
SergeyLukjanovtmckay, morning!13:19
tmckaymorning13:19
SergeyLukjanovtmckay, are you planning to fix https://bugs.launchpad.net/sahara/+bug/1273661 and https://bugs.launchpad.net/sahara/+bug/1272452 this week?13:19
SergeyLukjanovif not - I'm ready to take a look on them / reassign to someone else13:20
SergeyLukjanovRC1 will be next week, so, we need to fix such stuff13:20
SergeyLukjanovtmckay ^^13:20
mattfthere's a deeper issue there, that the credentials are being stored in the first place13:22
tmckaySergeyLukjanov, reassigning them is probably a good idea.  btw, mattf had concerns about having the credentials stored in the database, and suggested that fixing the returns from REST really doesn't address the issue fully13:22
tmckaywhat he said :)13:22
mattfsimply filtering them is really just papering over the issue13:22
mattftruly, someone should have smacked me harder when i deleted them from the cli output13:23
mattfthose bugs just hide that we have a deeper security issue to address13:23
* mattf end rant13:23
tmckaywell, you could argue for a database on a server where nobody has access but root13:23
tmckaybut that counts on deployment to cover it13:23
SergeyLukjanovtmckay, it fixes these issues, but it's not fixing architecture issue13:24
mattfi've never, has anyone used ssl to communicate w/ the service?13:24
tmckayI don't think I have13:24
SergeyLukjanovmattf, agreed with that it's a bigger problem13:24
crobertsrhI have not13:24
SergeyLukjanovmattf, I think you've created blueprint to not store credentials13:25
SergeyLukjanovmattf, /me not13:25
SergeyLukjanov(re ssl)13:25
mattfit's on my list of big things for juno: horizon merge, security, stable api13:25
SergeyLukjanovmattf, I've talked with David Lyle (ptl of Horizon) yesterday and he said that it's quite common approach for merging our plugin to horizon13:26
SergeyLukjanovand we could start doing it right after the horizon master will be open for Juno dev13:27
SergeyLukjanov(next week I think)13:27
tmckaySergeyLukjanov, okay, I'll fix those this week.  One is basically a copy of one already done13:27
SergeyLukjanovtmckay, yup, thank you13:27
tmckayThat should take just a few minutes.13:27
SergeyLukjanovtmckay, yeah13:27
tmckayThe other is slightly harder, but not much I think.13:27
mattfcrobertsrh, pls toss filing a horizon merge bp on your queue13:28
crobertsrhack13:28
SergeyLukjanovcrobertsrh, please, add me to this bp13:28
crobertsrhwill do13:28
SergeyLukjanovanyway it's low prio comparing to releasing Icehouse ;)13:29
SergeyLukjanovheh, renaming was quite difficult in the end of cycle but we've integrated and it's really great...13:29
mattflooks like we just have ci and puppet remaining13:32
*** bradd1 has quit IRC13:33
mattfit was a great cross team effort and example of collaboration13:33
mattfs/was/is/ since it's not done yet!13:33
mattfbbiab13:33
*** mattf is now known as _mattf13:33
crobertsrhSergeyLukjanov:  For https://review.openstack.org/#/c/82539/ in the compatibility module, there is some support for a folsom url.  Should I clean that up as part of this compatibility change, or file another CR to clean it up separately?13:37
SergeyLukjanovcrobertsrh, could you please cleanup < havana compat separately?13:38
crobertsrhno problem13:38
SergeyLukjanovcrobertsrh, thx!13:38
SergeyLukjanov_mattf, yup, it was awesome work done (mostly)13:39
openstackgerritChad Roberts proposed a change to openstack/sahara-dashboard: Fixing sahara image registry links  https://review.openstack.org/8253913:39
*** Ch00k has quit IRC13:41
*** Ch00k has joined #openstack-sahara13:42
*** rhodgin has joined #openstack-sahara13:43
crobertsrhSergeyLukjanov:  For filing the dashboard merge bp, should I file it against sahara or horizon?  I'm guessing horizon, but I don't want to be wrong.13:44
SergeyLukjanovcrobertsrh, against horizon13:45
crobertsrhthx13:45
SergeyLukjanovcrobertsrh, but you can duplicate it to sahara too, because it means removing sahara-dashboard13:45
crobertsrhOk, I'll do both13:45
openstackgerritDmitry Mescheryakov proposed a change to openstack/sahara: Remove agent remote  https://review.openstack.org/8275713:49
*** tosky has joined #openstack-sahara14:08
*** bradd1 has joined #openstack-sahara14:09
*** alazarev has joined #openstack-sahara14:32
*** IlyaE has joined #openstack-sahara15:00
*** _mattf is now known as mattf15:11
*** ErikB has joined #openstack-sahara15:13
*** alazarev has quit IRC15:18
*** Ch00k_ has joined #openstack-sahara15:27
*** Ch00k has quit IRC15:30
*** alazarev has joined #openstack-sahara16:21
*** alazarev has quit IRC16:35
SergeyLukjanovcrobertsrh, I've asked David to triage dashboard merging blueprint, thank you16:41
crobertsrhgreat!16:42
SergeyLukjanovcrobertsrh, heh, it's already high prio for the next cycle :)16:42
SergeyLukjanovyay! we can block them16:43
crobertsrhwow, now the pressure is on!16:43
openstackgerritTrevor McKay proposed a change to openstack/sahara: Filter credentials in jobs returned from REST api  https://review.openstack.org/8286316:44
*** alazarev has joined #openstack-sahara16:48
mattfcrobertsrh, what are you going to do w/ your newfound power over horizon?16:58
crobertsrhI'm looking to add more obscure JavaScript to everything.17:00
crobertsrhOf course, I'm always looking to do that17:01
elmikolol17:01
mattflol17:02
SergeyLukjanovgreat intention!17:04
*** Ch00k_ has quit IRC17:07
openstackgerritTrevor McKay proposed a change to openstack/sahara: Filter 'fields' from JobExecutions returned from REST api  https://review.openstack.org/8288317:35
tmckaySergeyLukjanov, mattf, ^^, no mechanism currently in Sahara to really do anything but leave out job_configs completely on wrapped JobExecutions.  Acceptable?  Possible alternative is to add a Resource type for job_configs, then add a mechanism for filtering callbacks so that specific configs can be screened out while leaving the rest.  Sounds like overkill to me.17:37
mattfsounds like bending over backward to open a paper bag17:39
tmckayNot sure why you would need job_configs reported in a job17:41
tmckayAt least for Oozie, you can find all the info you want from the Oozie console anyway :)17:42
tmckaywhich is maybe another problem17:42
dmitrymetmkay: we can add a _custom_filter() function to resource which we can call in _to_dict()17:42
dmitrymewe can then override it in JobExecution to filter only sensitive configs17:43
dmitrymes/resource/Resource/17:43
dmitrymeI meant the class17:43
tmckaydmitryme, yes, wasn't sure if we wanted to invent filtering features at this point ... I see that as a feature.17:43
tmckayAnd we're frozen ;-)17:44
dmitrymetmkay: if you mean feature freeze, then I think it does not count here: I would not call a feature something which is not user-facing17:45
tmckaydmitryme, okay, feel free to review and comment the above 82883.  I'll wait for feedback before doing anything else17:46
dmitrymetmkay: ok, sure17:47
tmckaydmitryme, I think of "feature" as anything that could destabilize the code17:47
tmckayalways a judgement call on where to draw the line with bug fixes17:47
dmitrymetmckay: probably you are right17:48
dmitrymethat Resource class is a nasty thing, so probably it is better not to touch it until we release Icehouse17:49
*** crobertsrh has quit IRC17:50
tmckaydmitryme, :)  and as mattf pointed out we need an overall security review, I think.  How we store credentials, does it matter that credentials are visible in the Oozie console for swift access, is there a way we can get around that (maybe encrypt values with a keypair or something)17:53
dmitrymetmckay: agree, that would be a good topic for design summit17:54
tmckayGood idea. I think Sergey sent an email about topics ...17:55
SergeyLukjanovhttp://summit.openstack.org17:56
SergeyLukjanovfor proposing topics for summit17:56
SergeyLukjanovsahara topic :)17:56
* mattf is waiting for the email from SergeyLukjanov that says "ok folks, deadline is tomorrow"17:56
mattfSergeyLukjanov, how many slots do we have?17:56
SergeyLukjanovmattf, design summit layout is under discussion now17:57
SergeyLukjanovmattf, heh, I'm waiting for such email from myself too :)17:57
mattflol17:57
SergeyLukjanovmattf, we'll have more slots than in HKG17:57
SergeyLukjanovI think that the exact number will be known in a few days17:58
mattfall your slot are belong to us?17:58
SergeyLukjanovwhat do you mean?17:58
mattfwow, bowie was young on the young americans album17:59
* mattf googles17:59
mattfoh man, it's an old meme17:59
mattfhttp://en.wikipedia.org/wiki/All_your_base_are_belong_to_us18:00
* mattf needs to update his material18:00
* SergeyLukjanov reading18:00
elmikowell played mattf18:00
* tmckay chuckles18:01
mattfi'll take your pity chuckle18:01
SergeyLukjanovre slots - I think 6-718:02
SergeyLukjanovcurrently, 7 in draft layout18:02
tmckayooo, alazarev put up the error reporting topic, +++118:02
tmckayI was just ranting about that yesterday in another chat18:02
alazarevanother big topic is workflow management18:03
alazarevnow the only thing you can do with hanged (or error) cluster is to delete it18:04
alazarevthis is not something users expect18:04
tmckayalazarev, could be the same idea, I was thinking of "What now?" with EDP.  For instance, I think we need at least raw Oozie workflows if users are going to submit through Sahara.  Otherwise, to do something complicated, I think they will go straight to the cluster command line on a node18:04
tmckayoh, okay, different topic18:04
tmckaybrb18:04
alazarev+1 on oozie workflow templates18:05
mattfi'm more of a get-better-insight than go-more-general, they often conflict18:06
mattfwell, at least for edp, which is to streamline/simplify the user experience18:06
mattfimho, the general tools are good for experts, but our audience is non-experts18:07
*** Ch00k has joined #openstack-sahara18:07
mattfwe could also simplify the template creation process. right now all the validation information happens at the end of the process. it could happen at the beginning18:08
mattf"make master node" -> "make worker node" -> how many workers do you want -> done ?18:09
mattfi bet that covers 95% of the template creations18:09
mattfno exposure to processes, just high level roles18:10
mattfexperts say "nah, forget this, i'll work w/ processes and make ha etc etc"18:10
mattfa user shouldn't have to wonder if they need to add a mapreduce client to all nodes18:10
alazarevmattf: now we have mixed approach and this leads to user confusion. cluster template is "full template for cluster" in UI and "partially filled cluster info" for backend18:10
mattfit's like we've exposed the implementation to the user. we can keep it around for the expert, but should have a simpler workflow for everyone else (most of the users)18:11
alazarevwe should either allow user to overwrite values in templates during cluster creation (more complex way) or add validation to templates and simplify the whole process (your suggestion)18:13
mattfthe fewer decisions we ask the user to make the better18:14
mattfan example: "make master node" -> "make worker node" -> how many workers do you want -> done ?18:14
toskysimplified workflow in the UI with a potential for separate "advanced options" if the user really want to tune (a small button :)18:14
mattfwhy do we even ask if htey want to make a master or a worker...18:14
alazarevprobably it is possible to keep both approaches18:14
mattfwhy not ask "how much memory and disk do you want?"18:15
alazarevmattf: I like the idea, wizard with one screen that creates the whole cluster18:16
mattfeach plugin knows it's default config for master & worker. we can start by evenly splitting across instance sizes, and optimize sizes in the future.18:16
mattfalso "how much memory and disk" shouldn't be an open ended question, that's cognitive effort on the user's part18:17
mattfwe can get the user's quota and present them w/ sizes: small, medium, large18:17
mattftrue, your medium != my medium, but what's that matter?18:18
alazarevmattf: quota often doesn't correlate with reality18:19
*** Ch00k has quit IRC18:19
mattfthat's a different problem tho, right? quota does constrain what the user can do.18:19
alazarevmattf: but we could ask flavor and required characteristics, that's all sahara need to create cluster18:19
mattfi'm suggesting we guess flavor based on available quota and desired size of the cluster/job18:20
mattfmguess == evenly divide18:21
mattfmaybe we can do better than that in the future, like making master > worker if # worker over a threshhold18:21
mattfor at least different shape for master & workers18:21
alazarevmattf: it's implementation details and could be discussed, I like the idea in general: one screen with few questions = running cluster18:22
mattfwe'll get that spark plugin (or similar) sometime and if you're running a spark cluster the shape of disk would be different than for mapreduce18:22
*** Ch00k has joined #openstack-sahara18:25
tmckaymattf, alazarev, so maybe this is one big topic after all, workflow for cluster and job creation, and maybe some subtopics like how do we expose the full power of things we've wrapped (like Oozie)18:35
*** alazarev has quit IRC18:35
tmckayI haven't been to one of these before, is there a scope limit on a topic?18:35
SergeyLukjanov++ for super simple flows for non-expert users18:36
tmckayWhat is the session duration?18:36
SergeyLukjanovtmckay, topics are 40 min long18:36
aignatovtmckay: 40-50 mins, but we can discuss it after and before session as well :)18:36
* mattf expects SergeyLukjanov is going to stop putting him on his reviews soon18:37
tmckaycan a topic run over multiple sessions, or is it always 1 to 1?18:37
*** alazarev has joined #openstack-sahara18:37
aignatovI think it can18:37
aignatovfew possible topics from me - security in Hadoop & OpenStack18:39
SergeyLukjanovmattf, :)18:39
aignatovand pluggable mechanism of EDP ;)18:40
aignatovbecause I think in the future EDP can't be dependent only on Oozie18:40
mattfaignatov, couldn't we teach oozie about spark?18:41
aignatovactually of spark plugin will be landed I don't know how edp will work on it :)18:41
mattfit won't. having a spark plugin is not really the right arch imho.18:41
mattfit's an ok stopgap, but ultimately spark is another process, like mapreduce, that runs on a hadoop cluster18:42
mattfit should be something that a distro plugin provides/deploys18:42
aignatovmattf: yes, so some changes are needed in EDP to support new data processing flows in non-hadoop plugins18:44
aignatovnon-pure-hadoop plugins :)18:44
mattfassuming we actually get the spark plugin in, we couldn't really claim we support spark until it's exposed through edp, imho18:45
*** alazarev has quit IRC18:45
mattfdid you have something else in mind when oyu mentioned oozie might not be our only interface into a cluster?18:45
tmckaymattf, aignatov, alazarev, SergeyLukjanov, http://summit.openstack.org/cfp/details/143, tried to capture the earlier discussion18:46
aignatovmattf: I think we could claim about plugin support if we can deploy its processes :)18:46
tmckaylet me know if you think I should edit the description18:46
tmckayoh my, all one line18:46
aignatovtmckay: thx18:47
SergeyLukjanovI think that we'll need to have some additional meetings after the summit to discuss topics for summit and prepare base for them18:47
SergeyLukjanovafter the release*18:47
aignatovafter the summit?18:47
aignatovok18:48
aignatovyes18:48
tmckayk, that looks a little better18:48
aignatovbut we can brainstorm here, in irc :)18:48
aignatovas for security, the some initial idea that we should think not only for hiding credentials but some tenant isolations because now anyone who know public url of some ooze deployed can have access to it :)18:49
tmckayyes18:50
SergeyLukjanovaignatov, sure, right now for example :)18:50
SergeyLukjanovaignatov, yeah, that's an issue too18:51
aignatovsome who has its own ooze client can run job on another's Oozie xD18:51
*** tosky has quit IRC18:55
*** crobertsrh has joined #openstack-sahara18:56
aignatovone more topic: "do we really need 'use_neutron' option? :)"18:57
mattfaignatov, nah, i'll put a patch up for that before we cut I18:59
* mattf kids at SergeyLukjanov18:59
SergeyLukjanovaignatov, nope, we could just auto discover it in catalog18:59
SergeyLukjanovmattf, heh19:00
mattfaignatov, we probably want a use_nova_networking19:00
aignatovmattf: I think the same as SergeyLukjanov said, we can auto discover networking19:01
mattfthat sounds cool, kinda hurts my head a bit tho19:02
aignatovone more topic, actually old theme: "Supporting new data sources and edp over it - Ceph, HBase, Cassandra, GlusterFS"19:04
mattfoldie by goodie19:05
mattferr but goodie19:05
aignatovI don't understand these expressions :)19:06
aignatovis it kinda one more meme?19:06
dmitrymeI think mattf means that we already talked about it19:06
dmitrymeright?19:06
mattfyou should use some russian idioms19:06
* mattf will google them and learn19:07
mattfdmitryme, mostly. it may be an old topic but it's a good topic19:07
aignatovdmitryme, mattf,  got it, yes, we talked about it right after 0.2 version released :)19:08
SergeyLukjanovit'll be quite weird if we'll start writing them on russian :)19:08
dmitrymemattf, regarding 'google them and learn', you can't even imaging how often we use that approach :-)19:08
aignatovI don't want write these idioms because most of them will contain "*******" :)19:09
mattflol19:09
dmitrymeaignatov: not true19:10
aignatovdmitryme: I'm kidding19:10
mattfaignatov, nice19:11
aignatovdmitryme: right, during irc conversation I use google 1 time per 10-20 lines19:11
aignatovavg19:11
*** ErikB has quit IRC19:12
SergeyLukjanovI'm using three finder click for dictionary/wiki19:15
*** alazarev has joined #openstack-sahara19:16
mattfaignatov, SergeyLukjanov tells me that you might have the hong kong demo pig script. can i have it?19:17
mattfi'm demo'ing sahara at devnation (red hat summit), and haven't had time to come up w/ my own19:17
SergeyLukjanovmattf, you should torture aignatov for it19:17
mattfi'd like to use yours as backup19:17
*** openstackgerrit has quit IRC19:18
mattfhmm, not sure if torture is the right word19:18
aignatovmattf: sure19:18
*** openstackgerrit has joined #openstack-sahara19:18
tmckaylol19:18
tmckayI don't often torture my colleagues, but when I do ...19:19
mattflol19:19
SergeyLukjanovmattf, it was a joke, not so bad as I think, but looks like nope19:19
tmckaySergeyLukjanov, no, it was quite funny19:19
*** ErikB2 has joined #openstack-sahara19:20
* mattf just missed it19:20
aignatovmattf: http://paste.openstack.org/show/74285/ ^^19:22
aignatovbtw, mattf, tmckay SergeyLukjanov we need to create new edp example for summit's demo19:23
aignatovmore impressive or/and funny as it was before :)19:25
SergeyLukjanovyup, something that could be visualized19:25
aignatovSergeyLukjanov: exactly19:25
mattfi agree19:26
mattfmy talk is on 16 apr19:26
mattfso we need that new demo soon!19:26
mattfs/we/i/19:26
aignatovso everyone are welcome for ideas19:26
aignatovso I can start implementing this asap in Pig, Jar, Java action, Streaming MapReduce or Hive, tmckay, ok, you know these things :)19:28
tmckayaignatov, a little bit19:29
tmckayaignatov, my Pig and Hive is pretty thin19:29
mattfaignatov, i was thinking an interactive spark demo would be slick, but...that's tricky atm19:29
aignatovtmckay: the same here :)19:29
aignatovmattf: yes, because we don't have spark in sahara19:30
tmckayI have an HDP big data book set from a training course at the office, there are some examples in there of predictor algorithms.  You know, people who bought this item also bought this other one.  Or you might like this movie, since you rented that one19:31
*** mattf is now known as _mattf19:32
tmckayI think those were all map reduce jobs19:33
tmckayaignatov, does mirantis have a big data training arm too?  I wonder if we could get some stuff from the HWX or mirantis training people.  I'm no data scientist :)19:36
tmckayjust like I wasn't a chemist or a physicist working on NMRs and CT scanners19:36
aignatovtmckay: no, there are no bigdata courses at Mirantis. It is totally OpenStack oriented atm,  so we are rest "Big data scientists"19:38
tmckayah, okay.  Well, maybe our HWX friends can help.19:39
tmckayjust wondering if there is something that already exists that we can just turn into a Sahara job19:39
aignatovhm, good idea, HW runs its own Hadoop summit, so I guess there are tons of great demos :)19:40
tmckayand then maybe do something cool with the output to render it19:40
aignatovso we can "torture" them xD19:40
tmckaylol19:40
tmckayThe new open source way19:40
tmckayOpen it .. .or else19:40
SergeyLukjanovI like this idea19:45
tmckaythe torture? ;-)19:46
elmikolol19:48
aignatovlet's rename sahara to...19:49
aignatovtorture19:49
tmckayllol, now that would get a lot of users19:49
tmckayTortureStack19:49
*** IlyaE has quit IRC19:49
aignatovahah, lol19:49
tmckay"Running a job never felt so bad"19:49
aignatovtmckay: haha, stop making me laughing19:51
tmckayaignatov, yeah, I think we've all gone a bit crazy.  Probably the renaming...19:51
ErikB2For demos - I am trying to think of something visually pleasing...19:53
tmckayErikB2, in the HWX hadoop training class, we did movie selection predictions19:54
elmikois tmckay ready for another renaming so soon?19:54
ErikB2Hadoop is not the most exciting thing when it comes to glitz per se. How about showing how to run something like the HiBench benchmark on a Sahara provisioned cluster19:54
tmckayelmiko, no, once is enough.  Next time I say we do global search and replace and cross our fingers19:55
elmikoHA!19:55
elmikocan we do that on a friday at like 4:45pm?19:55
aignatovErikB2: I guess that we will no have such resources to show benchmarking in the live demo19:55
ErikB2tmckay, I am not familiar with this, but this is likely something we could pull together (or out of the training class perhaps)19:56
tmckayErikB2, hmm, it might have been in the 'R' part of the data science portion... I'll have to look in the book19:57
ErikB2What do we want to demo/show - that we have a functioning hadoop cluster that we can do stuff on? It should definitely be Hadoop 2 based demo.19:57
ErikB2tmckay, ok. If you have the name of a lab or otherwise I can chase down. I have not had the luxury of taking our training. ;-)19:58
tmckayhmm, actually there's another shadowman guy who might have something... I'll try to drag him in here19:58
aignatovIt should be like calculating some useful or funny things or analysing text and then visualise it somehow19:59
tmckayjvyas, I think he's in here sometimes19:59
tmckayErikB2, ack, I'll take a look through the book this evening or tomorrow morning20:00
ErikB2I will try to come back with some concrete ideas for demos tomorrow as well.20:00
aignatovI think we don't needed overload openstack users with any difficult calculations demo or benchmarking, because OS is not so close to hadoop, I'm afraid that typical OS users will not or will not want deeply understand such things20:01
SergeyLukjanovErikB2, thanks for helping20:02
SergeyLukjanovaignatov, yup, some EDP job + nice visualization will be great20:02
aignatovErikB2: yes, that's would be great!20:02
ErikB2I don't want to demo EDP... :-)20:03
SergeyLukjanovErikB2, why not?20:03
aignatovErikB2: I will, I just need an example which will be loved by all in our summit talk20:04
ErikB2just joshing, although I do find EDP somewhat prickly on very easy to use. I know that we will discuss in ATL.20:07
*** IlyaE has joined #openstack-sahara20:07
ErikB2on=and not20:07
openstackgerritDmitry Mescheryakov proposed a change to openstack/sahara: Validate data sources reference different resources  https://review.openstack.org/8291020:16
*** dmitryme has quit IRC20:16
*** dmitryme has joined #openstack-sahara20:16
aignatovregardless edp,we just need a good mapreduce example for demo on summit :) because pi job and my last demo are not in the trend ;)20:17
*** alazarev has quit IRC20:20
*** dmitryme has quit IRC20:21
*** eanxgeek is now known as eanxgeek|log20:23
*** alazarev has joined #openstack-sahara20:37
*** ErikB2 has quit IRC20:46
elmikocrobertsrh: if i am using neutron do i need to specify AUTO_ASSIGNMENT_ENABLED in my local_settings?20:48
crobertsrhelmiko:  I have never used neutron, so I can't say for sure20:49
elmikok20:49
elmikoi'm guessing that i don't, but who knows :)20:49
*** dmitryme has joined #openstack-sahara20:51
crobertsrhLooks like it defaults to true if you don't set it20:51
crobertsrhI really should try out neutron at some point20:52
crobertsrhLet me know what you find20:54
elmikoi'm getting very close to having trunk sahara+dashboard+horizon running on the rdo icehouse stack20:55
elmikojust working out a few last kinks20:55
crobertsrhNice!20:55
elmikoand i'll have a doc to share when i get it working20:55
crobertsrhEven better20:55
elmikoi've got the dashboard into horizon, now i'm getting some flack about the /sahara endpoint not connecting, but i think i might have an issue with the ip address or something20:56
elmikoyay, working :)20:57
elmikonow to start pushing images20:57
*** IlyaE has quit IRC21:01
*** ErikB2 has joined #openstack-sahara21:03
openstackgerritAlexander Ignatov proposed a change to openstack/sahara: Add fixed and floating IPs discovery via neutron  https://review.openstack.org/8291921:06
*** crobertsrh has quit IRC21:10
elmikotmckay: ping21:19
elmikowhy doesn't sahara-image-elements put diskimage-create.sh into the path during `python setup.py install` ?21:32
*** dmitryme has quit IRC21:34
openstackgerritAndrew Lazarev proposed a change to openstack/sahara: [IDH] Fixed cluster scale down  https://review.openstack.org/7887621:34
*** witlessb has quit IRC21:35
*** Ch00k has quit IRC21:36
*** IlyaE has joined #openstack-sahara21:43
*** ErikB2 has quit IRC22:01
*** ErikB2 has joined #openstack-sahara22:08
*** tmckay has left #openstack-sahara22:12
*** alazarev has quit IRC22:16
*** alazarev has joined #openstack-sahara22:18
*** alazarev has quit IRC22:18
*** alazarev has joined #openstack-sahara22:20
*** alazarev has quit IRC22:22
*** IlyaE has quit IRC22:24
*** ErikB2 has quit IRC22:38

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!