18:06:44 #startmeeting sahara 18:06:45 Meeting started Thu Apr 17 18:06:44 2014 UTC and is due to finish in 60 minutes. The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:06:46 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:06:48 The meeting name has been set to 'sahara' 18:07:03 sahara folks, wake up 18:07:08 o/ 18:07:36 Hello 18:07:51 aignatov, jspeidel, mattf, tmckay 18:07:53 alazarev 18:08:09 hello 18:08:15 SergeyLukjanov, hi 18:08:19 hey 18:09:28 ok, we have some kind of quorum 18:09:37 let's start 18:09:45 #link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda#Agenda_for_April.2C_17 18:09:51 #topic News / updates 18:10:18 folks, please 18:10:26 I'll add info re release in next topic 18:10:31 I've been working on the dashboard merge into horizon. My first pass did it as a separate dashboard (Admin, Project, Sahara). 18:10:34 but it's almost here :) 18:10:41 dmitryme noted that it might not be the right way to go. I tend to agree, so I'm reworking the patch sets to have Sahara (Data Processing) live under "Project". 18:10:49 I am well into figuring that out, but when I asked a bit in the horizon channel, it sparked a bit of debate. 18:10:53 working on fixing HDP image bugs, debugging a problem that myself and elmiko ran into with diskimage-builder 18:11:12 Current plan is for the debate to be carried out on the horizon mailing list and in their weekly meeting. 18:11:21 crobertsrh, awesome 18:11:37 crobertsrh, ping me if you'll need some support on pushing it 18:11:44 we’ve finished POC for the customer with sahara on multi-region environment 18:12:01 I will include you on my email to the horizon list along with dmitryme and nikitakonovalov. 18:12:23 multi-region support is on review now: https://review.openstack.org/#/c/79795/ 18:12:31 nice 18:12:38 I was hoping to have it done by now, but that is definitely not the case. 18:13:06 crobertsrh, how is the review activity from the horizon team? 18:13:32 SergeyLukjanov: non-existant really so far 18:13:52 But dmitryme convinced me to abandon my initial approach earlier today, so it's probably for the best 18:13:54 o/ 18:14:07 almost forgot 18:14:28 crobertsrh, ok, I hope the review activity will be better after release sensation :) 18:14:36 aignatov, hey, any news? 18:14:44 tmckay, morning 18:14:48 I'm sure it will be great 18:14:49 hi 18:14:51 tmckay, any news? 18:15:12 SergeyLukjanov: nothing special, fixed ine bug in novanetwirk setup with savanna 18:15:34 I worked on the bigpetstore demo, got that to run on hadoop 2 from sahara, and I extended the cli integration test to support neutron, refactored a bit. 18:15:50 and starting writing sloccount mr job for demo 18:15:59 tmckay: hey, great progress! 18:16:10 and not so good on me :( 18:16:10 oh, and vanilla2 for cli integration test, too 18:16:46 tmckay, cool 18:17:03 ah, also I worked on heat stuff 18:17:20 I finally started playing with the integration tests, and I'm trying to understand if the failure I see is because of something wrong in my setup or not 18:17:20 updated Sahara resource in heat implementation 18:17:28 tmckay, probably you should split cli tests patch to several parts - to make it easier to review, is it possible? 18:17:39 tell me, does anyone know what it means when any http requests to sahara fail with "Authentication required", but the web UI works? Even when "admin" credentials are used from the command line? 18:17:45 here it is: 18:17:48 #link https://review.openstack.org/#/c/72336 18:17:57 SergeyLukjanov, yes, I thought of that, too. It is getting big. 18:18:04 I think I probably can 18:18:11 tosky, you can torture ylobankov about integration tests 18:18:23 * SergeyLukjanov like word "torture" 18:18:28 lol, I noticed that 18:18:41 ylobankov: run away from pirates!! 18:18:51 http://cloud-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img 18:18:56 oops 18:19:06 wrong chat? 18:19:10 trusty released today ;) 18:19:14 wrong terminal tab 18:19:36 folks, any other news/updates?? 18:20:04 oh, I noticed we still don't have a "Hive" job in the integration tests 18:20:08 last time I looked 18:20:23 I think maybe that would be a good thing to add to sahara 18:20:30 Anybody have a hive example? 18:20:56 tmckay: about authorization failed - I saw that only in case of expired token 18:21:00 I'm afraid that it's not working in some cases / plugins 18:21:10 ah, okay 18:21:12 don't actually remember details 18:21:46 okay, let's move on 18:21:56 #topic Icehouse release status 18:22:02 #info OpenStack Icehouse released today, stable/icehouse branches created 18:22:11 tmckay: yeah, we should look at Hive part and fix it in juno somehov 18:22:12 as I remember, hive doen’t work properly with swift in sahara 18:22:23 #info All Sahara repos tagged 18:22:43 I'll create stable/icehouse branches for repos after the meeting and send an announcement 18:22:55 #link https://wiki.openstack.org/wiki/Sahara/ReleaseNotes/Icehouse 18:23:04 release notes for icehouse ^^ 18:23:55 so, I'm expecting to announce I release of Sahara in ~40 mins after the meeting 18:24:27 #topic Action items from the last meeting 18:24:32 #link http://eavesdrop.openstack.org/meetings/sahara/2014/sahara.2014-04-10-18.05.html 18:24:37 #info no action items 18:24:44 #topic Design summit 18:24:58 folks, please, propose topic you'd like to discuss on summit 18:25:03 til monday 18:25:28 April 20 is the soft deadline for design summit sessions proposals 18:25:39 #info April 20 is the soft deadline for design summit sessions proposals 18:25:46 #link summit.openstack.org 18:26:17 I've proposed some missed topics today w/o description and planning to add it on weekend 18:26:39 please, comment on existing topics if you'd like to ensure that something will be discussed 18:27:00 How'll attend design summit in Atlanta? 18:27:03 small poll 18:27:14 * SergeyLukjanov attending 18:27:22 I will be there 18:28:01 looks like today is a sleepy day 18:28:09 tmckay? 18:28:20 He will be there 18:28:22 (I hope yes due to the joint talk) 18:28:28 elmiko will also be there 18:28:31 crobertsrh, and mattf, correct? 18:28:35 lol, yes, I will be there 18:28:40 yes, I believe mattf will be there too 18:28:41 tmckay, :) 18:29:10 crobertsrh, that's cool that you'll be on summit, we can share some thoughts with dashboard folks 18:29:23 Absolutely 18:29:26 aignatov and alazarev will be on summit too 18:29:28 I will be 18:29:51 and from HWX Erik and jspeidel 18:29:53 as I know 18:30:27 #info Sahara design summit slots are Thursday afternoon and Friday morning 18:31:23 so, folks, please, add topics 18:31:49 #topic Backward compat for Hadoop version 18:31:55 heh, the hot topic 18:32:08 so, let's share thoughts on it 18:32:21 alazarev was initially commented about it, so, alazarev, please 18:32:47 "kill hadoop 1"? 18:32:52 * tosky hides 18:33:00 it’s about https://review.openstack.org/#/c/88024/ 18:33:06 it's about 2.3.0 -> 2.4.0 18:33:30 oh, vanilla 18:33:34 tosky: no, this topic is about how to upgrade hadoop fromm 2.3.0 to higher version and keep working old clusters 18:33:41 we support some versions of hadoop in icehouse (both vanilla and hdp) 18:34:22 question: what do we do with sich versions in future? should we support them forever? should it be deprication period? 18:35:16 we can’t just remove 2.3.0 and start to support 2.4.0 only, because customers could have running clusters on 2.3.0 18:35:19 what is the upstream (apache) policy regarding support? 18:35:33 it sounds like we shouldn't replace plugin's version, but add new versions and declare deprecation period 18:35:38 alazarev: right now we provisioning/scaling logic can work with both hadoop versions 2.3.0 and 2.4.0 18:35:47 the same history with hdp versions 18:35:59 only restriction is hadoop version in rest call :) 18:36:21 hopefully we don’t have such problem with IDH anymore :) 18:36:38 I think it is more realistically to just keep support for older versions for this cycle 18:36:48 this also affects e.g. https://review.openstack.org/#/c/87753/ 18:37:01 but we definitely should look for ways to update clusters to newer version 18:37:02 we can’t just change version of oozie 18:37:10 do you mean keep 2.3 for Juno, add 2.4, remove 2.3 for K? 18:37:51 ok, but does hadoop provide support this? I mean, if you have a cluster running, do they support upgrades? 18:38:01 tosky: Ideally we should provide clusters update from 2.3 to 2.4 in K 18:38:09 also, I never tried an openstack upgrade: is it supposed to be online? 18:38:24 maybe we should implement live hadoop upgrade? killer feature in sahara :) 18:38:47 while the jobs are running ;-) 18:39:04 easier sulution: just don’t support upgrades, this will also eluminate problems with DB migrations :) 18:39:06 lol 18:39:22 I'd say it would be great to provide at least offline upgrade 18:39:49 we should at least stop replacing versions :) 18:39:51 this is a good topic for design session :) 18:40:07 alazarev already registered session for it 18:40:12 not sure if we find solution right now 18:40:14 ok 18:40:14 regarding upgrading OpenStack, it could be upgrade with some periods of unavailable functionality 18:40:17 see http://openstack-in-production.blogspot.ru/2014/02/our-cloud-in-havana.html 18:40:52 also this: http://openstack.redhat.com/Upgrading_RDO 18:41:21 we need volunteers to prepare an etherpad about upgrading Hadoop 18:41:25 dmitryme: “could” “theoretically” “be” 18:41:58 http://wiki.apache.org/hadoop/Hadoop_Upgrade 18:42:10 alazarev: I said 'ideally', I understand it is not easy to achieve 18:42:40 but tha page above is too old 18:43:11 mhh... still referenced by, for example, http://hadoop.apache.org/docs/r2.3.0/hadoop-project-dist/hadoop-hdfs/HdfsUserGuide.html#Upgrade_and_Rollback 18:43:37 sounds like we still need to have an etherpad with analysis of this docs :) 18:44:34 do we really want to support upgrades? I would vote on support two versions and force customers to create new hadoop cluster 18:44:54 alazarev, data migration will be needed at least 18:44:55 agree with alazarev 18:45:10 I'm basically agree with it 18:45:12 given the current status of affairs for both hadoop and openstack upgrades, I would say I agree with alazarev 18:45:25 SergeyLukjanov: data migration is out of sahara scope, it is from hadoop world 18:45:43 well, we should think how to support several minor versions of the same distro 18:45:47 at least until hadoop and/or openstack implement mechanism for live upgrade 18:45:57 alazarev, but in terms of sahara it's a way to migrate from deprecated to actual versioned cluster 18:46:44 we need to agree on something for now 18:46:58 any objections for stoping just replacing versions? 18:47:06 I vote on adding new version without removing old one 18:47:46 and perform changes like ‘upgrade oozie’ only in unreleased versions 18:47:48 hm, probably we can expand our db models with some flag like “old_hadoop_versions” and knowing this flag sahara could operate with existiong cluster with old version 18:48:47 in fact sacailing operation and deleting don’t have specific logic for the different minor hadoop versions 18:48:52 *scaling 18:49:14 scaling has specific logic 18:49:22 which? 18:50:16 10 mins left, so, let's move on 18:50:17 aignatov: at least list of hadoop configs 18:50:17 alazarev: but removing old deprecated versions for major OS releases? 18:50:34 tosky, it's a good idea 18:50:55 (where OS == OpenStack of course) 18:50:59 alazarev, could you aggregate thoughts on it, file blueprint and add details to it? 18:51:06 and attash it to the summit session 18:51:07 alazarev: hadoop configs changed very slowly in hadoop 18:51:20 tosky: yes, but only after anauncing deprication, so 2.3.0 we be removed only in K 18:51:30 alazarev: sure 18:51:53 alazarev: keeping an eye on upstream hadoop support policy, if any 18:52:09 alazarev, ? 18:52:26 SergeyLukjanov: sure 18:52:47 #action alazarev file blueprint re hadoop version upgrades, aggregate thoughts and details, link to the design summit session 18:52:49 thx 18:53:01 #topic IDH removal 18:53:19 any objections for removing IDH from the codebase? 18:53:19 nothing to discuss, just remove it 18:53:24 :) 18:53:33 This topic should be short one :) 18:53:34 agreed 18:53:37 for Juno, not IceHouse, right? 18:53:46 tosky, Icehouse already released 18:53:48 :) 18:53:51 IDH, we hardly knew ye 18:53:52 just to be sure :) 18:54:04 in fact in Icehouse it’ll not work anyway :( 18:54:10 sad but true 18:54:29 Intel droped all repos, customers will not be able to install IDH even in Icehouse 18:54:37 yup, that's sad 18:55:01 local mirror is needed, but there is no way to do it now 18:55:16 we can sell our local copy of IDH mirror :) 18:55:37 heh 18:55:47 #agreed remove IDH from codebase 18:55:49 alazarev: I give you money, just don’t sell it 18:56:09 #topic Open discussion 18:56:12 4 mins left 18:56:31 am, did I missed Roadmap cleanup 18:56:33 ? 18:56:57 roadmap? before summit? :) 18:57:42 no, I meant we need to update https://wiki.openstack.org/wiki/Sahara/Roadmap for Icehouse 18:57:44 we should cleanup it to be in line with release 18:57:52 dmitryme, could you please update it too 18:57:58 to align with release 18:58:05 Sergey: ok, I'll do it 18:58:13 #action dmitryme to align roadmap/Icehouse with release 18:58:16 thx 18:58:21 2 mins left 19:00:11 thank you all folks! 19:00:15 #endmeeting