Thursday, 2015-07-02

*** puranamr has quit IRC00:01
*** puranamr_ has quit IRC00:02
*** puranamr has joined #openstack-meeting-300:03
*** mickeys has quit IRC00:04
*** banix has joined #openstack-meeting-300:05
*** Swami has quit IRC00:10
*** sridhar_ram has joined #openstack-meeting-300:11
*** banix has quit IRC00:12
*** sridhar_ram1 has joined #openstack-meeting-300:17
*** sridhar_ram has quit IRC00:17
*** tsandall has quit IRC00:26
*** tsandall has joined #openstack-meeting-300:27
*** puranamr has quit IRC00:28
*** Rockyg has quit IRC00:29
*** SumitNaiksatam has quit IRC00:36
*** Aish has quit IRC00:39
*** pavel_bondar has quit IRC00:40
*** pavel_bondar has joined #openstack-meeting-300:41
*** tsandall has quit IRC00:44
*** tsandall has joined #openstack-meeting-300:45
*** Sukhdev has quit IRC00:45
*** stanzgy has joined #openstack-meeting-300:49
*** carl_baldwin has quit IRC00:53
*** tsandall has quit IRC00:55
*** SumitNaiksatam has joined #openstack-meeting-301:09
*** sridhar_ram1 has quit IRC01:12
*** dims_ has quit IRC01:19
*** stevemar has joined #openstack-meeting-301:21
*** stevemar has quit IRC01:24
*** sankarshan_away is now known as sankarshan01:25
*** banix has joined #openstack-meeting-301:25
*** armax has quit IRC01:26
*** Piet has quit IRC01:26
*** fallenpegasus has joined #openstack-meeting-301:28
*** Piet has joined #openstack-meeting-301:30
*** annp has joined #openstack-meeting-301:32
*** s3wong has quit IRC01:33
*** annp has quit IRC01:37
*** puranamr has joined #openstack-meeting-301:38
*** dims has joined #openstack-meeting-301:39
*** sigmavirus24 is now known as sigmavirus24_awa01:40
*** puranamr has quit IRC01:42
*** carl_baldwin has joined #openstack-meeting-301:42
*** wuhg has joined #openstack-meeting-301:52
*** baoli has joined #openstack-meeting-301:56
*** ivar-laz_ has joined #openstack-meeting-301:59
*** ivar-lazzaro has quit IRC02:02
*** ivar-laz_ has quit IRC02:03
*** nelsnelson has joined #openstack-meeting-302:08
*** baoli has quit IRC02:13
*** baoli has joined #openstack-meeting-302:13
*** zz_natorious is now known as natorious02:15
*** natorious is now known as zz_natorious02:16
*** jwang_ has joined #openstack-meeting-302:18
*** ducttape_ has quit IRC02:18
*** yamahata has quit IRC02:21
*** jwang__ has quit IRC02:21
*** sbalukoff has quit IRC02:22
*** armax has joined #openstack-meeting-302:29
*** jaypipes has quit IRC02:30
*** nelsnelson has quit IRC02:39
*** nelsnelson has joined #openstack-meeting-302:39
*** shwetaap has joined #openstack-meeting-302:40
*** yamamoto has joined #openstack-meeting-302:45
*** stevemar has joined #openstack-meeting-302:47
*** kebray has joined #openstack-meeting-302:48
*** Poornima has joined #openstack-meeting-302:57
*** badveli has quit IRC03:04
*** lazy_prince has quit IRC03:18
*** dims has quit IRC03:22
*** Aish has joined #openstack-meeting-303:24
*** Aish has left #openstack-meeting-303:24
*** coolsvap|away is now known as coolsvap03:45
*** galstrom_zzz is now known as galstrom03:49
*** galstrom is now known as galstrom_zzz03:56
*** baoli has quit IRC03:57
*** mrmartin has joined #openstack-meeting-303:58
*** galstrom_zzz is now known as galstrom04:13
*** hurgleburgler1 has joined #openstack-meeting-304:19
*** hurgleburgler has quit IRC04:19
*** DericHorn-HP has joined #openstack-meeting-304:19
*** woodster_ has quit IRC04:21
*** mrmartin has quit IRC04:21
*** DericHorn-HP has quit IRC04:23
*** sdake has joined #openstack-meeting-304:30
*** vgridnev has joined #openstack-meeting-304:33
*** galstrom is now known as galstrom_zzz04:33
*** shwetaap has quit IRC04:33
*** absubram has quit IRC04:35
*** lazy_prince has joined #openstack-meeting-304:48
*** nkrinner has joined #openstack-meeting-304:54
*** dobson has quit IRC04:55
*** yamamoto has quit IRC04:55
*** Poornima has quit IRC04:56
*** yamamoto has joined #openstack-meeting-304:57
*** SumitNaiksatam has quit IRC04:58
*** SumitNaiksatam has joined #openstack-meeting-304:58
*** amit213 has joined #openstack-meeting-305:00
*** amit213 has quit IRC05:00
*** amit213 has joined #openstack-meeting-305:00
*** dobson has joined #openstack-meeting-305:02
*** carl_baldwin has quit IRC05:12
*** Poornima has joined #openstack-meeting-305:14
*** DericHorn-HP has joined #openstack-meeting-305:18
*** yamamoto has quit IRC05:22
*** yamamoto has joined #openstack-meeting-305:27
*** nelsnelson has quit IRC05:31
*** yamamoto has quit IRC05:36
*** yamamoto has joined #openstack-meeting-305:37
*** coolsvap is now known as coolsvap|away05:37
*** coolsvap|away is now known as coolsvap05:38
*** yamamoto has quit IRC05:39
*** jtomasek has joined #openstack-meeting-305:40
*** stevemar has quit IRC05:42
*** yamamoto has joined #openstack-meeting-305:42
*** DericHorn-HP has quit IRC05:45
*** ivar-lazzaro has joined #openstack-meeting-305:47
*** egallen has joined #openstack-meeting-305:50
*** Longgeek has joined #openstack-meeting-305:52
*** irenab has quit IRC05:52
*** ivar-lazzaro has quit IRC05:53
*** ivar-lazzaro has joined #openstack-meeting-305:53
*** jtomasek has quit IRC05:54
*** ivar-lazzaro has quit IRC05:54
*** coolsvap is now known as coolsvap|away05:54
*** ivar-lazzaro has joined #openstack-meeting-305:54
*** ivar-lazzaro has quit IRC05:56
*** ivar-lazzaro has joined #openstack-meeting-305:57
*** egallen has quit IRC05:58
*** ivar-lazzaro has quit IRC05:59
*** hurgleburgler1 has quit IRC06:01
*** mrunge has joined #openstack-meeting-306:02
*** coolsvap|away is now known as coolsvap06:02
*** armax has quit IRC06:04
*** jtomasek has joined #openstack-meeting-306:05
*** kebray has quit IRC06:11
*** mohankumar has quit IRC06:13
*** coolsvap is now known as coolsvap|away06:16
*** banix has quit IRC06:18
*** irenab has joined #openstack-meeting-306:26
*** stevemar has joined #openstack-meeting-306:42
*** belmoreira has joined #openstack-meeting-306:44
*** radek_ has joined #openstack-meeting-306:45
*** stevemar has quit IRC06:46
*** ivar-lazzaro has joined #openstack-meeting-306:47
*** belmoreira has quit IRC06:47
*** ivar-lazzaro has quit IRC06:50
*** yuikotakada has joined #openstack-meeting-306:55
*** jtomasek has quit IRC06:58
*** belmoreira has joined #openstack-meeting-306:58
*** belmoreira has quit IRC06:58
*** belmoreira has joined #openstack-meeting-306:59
*** egallen has joined #openstack-meeting-307:03
*** egallen has quit IRC07:05
*** Gal has joined #openstack-meeting-307:06
*** jtomasek has joined #openstack-meeting-307:07
*** egallen has joined #openstack-meeting-307:07
*** fifieldt has quit IRC07:09
*** egallen_ has joined #openstack-meeting-307:12
*** egallen has quit IRC07:12
*** egallen_ is now known as egallen07:12
*** matrohon has joined #openstack-meeting-307:13
*** mpavlase has joined #openstack-meeting-307:15
*** mpavlase has quit IRC07:16
*** mpavlase has joined #openstack-meeting-307:16
*** egallen has quit IRC07:17
*** egallen has joined #openstack-meeting-307:18
*** coolsvap|away has quit IRC07:20
*** rharwood has quit IRC07:20
*** coolsvap|away has joined #openstack-meeting-307:23
*** rharwood has joined #openstack-meeting-307:23
*** egallen has quit IRC07:27
*** jtomasek has quit IRC07:30
*** jcoufal has joined #openstack-meeting-307:30
*** egallen has joined #openstack-meeting-307:31
*** vgridnev has quit IRC07:33
*** zz_ttrifonov is now known as ttrifonov07:35
*** jckasper has quit IRC07:36
*** jckasper has joined #openstack-meeting-307:49
*** stevemar has joined #openstack-meeting-307:49
*** marios has quit IRC07:53
*** marios has joined #openstack-meeting-307:53
*** stevemar has quit IRC07:53
*** jcoufal_ has joined #openstack-meeting-308:09
*** jcoufal_ has quit IRC08:09
*** dosaboy has quit IRC08:10
*** dosaboy has joined #openstack-meeting-308:11
*** yamamoto has quit IRC08:11
*** jckasper has quit IRC08:11
*** dosaboy has quit IRC08:12
*** yamamoto has joined #openstack-meeting-308:15
*** safchain has joined #openstack-meeting-308:17
*** matrohon has quit IRC08:18
*** matrohon has joined #openstack-meeting-308:18
*** dosaboy has joined #openstack-meeting-308:21
*** jckasper has joined #openstack-meeting-308:25
*** jckasper has quit IRC08:33
*** JeanBriceCombebi has joined #openstack-meeting-308:38
*** jckasper has joined #openstack-meeting-308:45
*** amotoki has quit IRC08:46
*** Longgeek has quit IRC08:52
*** Longgeek has joined #openstack-meeting-308:53
*** fallenpegasus has quit IRC09:06
*** dims has joined #openstack-meeting-309:24
*** bradjones has quit IRC09:33
*** jtomasek has joined #openstack-meeting-309:34
*** bradjones has joined #openstack-meeting-309:35
*** bradjones has quit IRC09:35
*** bradjones has joined #openstack-meeting-309:35
*** e0ne has joined #openstack-meeting-309:36
*** Gal has quit IRC09:37
*** stevemar has joined #openstack-meeting-309:38
*** stevemar has quit IRC09:42
*** e0ne is now known as e0ne_09:46
*** devvesa has joined #openstack-meeting-309:51
*** Gal has joined #openstack-meeting-310:01
*** killer_prince has joined #openstack-meeting-310:04
*** e0ne_ is now known as e0ne10:05
*** lazy_prince has quit IRC10:08
*** mickeys has joined #openstack-meeting-310:08
*** JeanBriceCombebi has quit IRC10:15
*** JeanBriceCombebi has joined #openstack-meeting-310:16
*** mickeys has quit IRC10:16
*** killer_prince has quit IRC10:25
*** lazy_prince has joined #openstack-meeting-310:26
*** rushiagr_away is now known as rushiagr10:42
*** lazy_prince has quit IRC10:42
*** egallen has quit IRC10:45
*** Poornima has quit IRC11:04
*** mwagner_lap has quit IRC11:13
*** yamamoto has quit IRC11:13
*** sahid has joined #openstack-meeting-311:18
*** pavel_bondar has quit IRC11:24
*** stevemar has joined #openstack-meeting-311:27
*** sahid has quit IRC11:27
*** stevemar has quit IRC11:30
*** JeanBriceCombebi has quit IRC11:32
*** sahid has joined #openstack-meeting-311:33
*** e0ne is now known as e0ne_11:34
*** e0ne_ is now known as e0ne11:36
*** JeanBriceCombebi has joined #openstack-meeting-311:38
*** yuikotakada has quit IRC11:45
*** mwagner_lap has joined #openstack-meeting-311:53
*** egallen has joined #openstack-meeting-311:58
*** zhenguo has quit IRC12:01
*** matrohon has quit IRC12:02
*** matrohon has joined #openstack-meeting-312:03
*** e0ne is now known as e0ne_12:06
*** e0ne_ is now known as e0ne12:11
*** julim has joined #openstack-meeting-312:22
*** JeanBriceCombebi has quit IRC12:23
*** JeanBriceCombebi has joined #openstack-meeting-312:26
*** julim has quit IRC12:27
*** jaypipes has joined #openstack-meeting-312:32
*** pavel_bondar has joined #openstack-meeting-312:33
*** matrohon has quit IRC12:35
*** matrohon has joined #openstack-meeting-312:35
*** yamamoto has joined #openstack-meeting-312:35
*** nkrinner has quit IRC12:38
*** devvesa has quit IRC12:39
*** Gal is now known as ^Gal^12:39
*** baoli has joined #openstack-meeting-312:40
*** egallen has quit IRC12:43
*** egallen has joined #openstack-meeting-312:44
*** egallen has quit IRC13:01
*** egallen has joined #openstack-meeting-313:01
*** neelashah has joined #openstack-meeting-313:05
*** matrohon has quit IRC13:06
*** ajmiller__ has joined #openstack-meeting-313:06
*** matrohon has joined #openstack-meeting-313:06
*** stevemar has joined #openstack-meeting-313:09
*** ajmiller_ has quit IRC13:10
*** vgridnev has joined #openstack-meeting-313:11
*** Networkn3rd has joined #openstack-meeting-313:15
*** julim has joined #openstack-meeting-313:15
*** zhenguo has joined #openstack-meeting-313:16
*** mrmartin has joined #openstack-meeting-313:23
*** peristeri has joined #openstack-meeting-313:27
*** amotoki has joined #openstack-meeting-313:28
*** mrunge has quit IRC13:29
*** e0ne is now known as e0ne_13:29
*** singlethink has joined #openstack-meeting-313:32
*** shwetaap has joined #openstack-meeting-313:35
*** fallenpegasus has joined #openstack-meeting-313:43
*** e0ne_ is now known as e0ne13:43
*** elmiko has joined #openstack-meeting-313:45
*** JeanBriceCombebi has quit IRC13:49
*** JeanBriceCombebi has joined #openstack-meeting-313:49
*** sankarshan is now known as sankarshan_13:51
*** sankarshan_ is now known as sm|CPU13:51
*** sm|CPU is now known as sankarshan13:51
*** venza has joined #openstack-meeting-313:52
*** fifieldt has joined #openstack-meeting-313:53
*** singleth_ has joined #openstack-meeting-313:54
*** AndreyPavlov has joined #openstack-meeting-313:56
*** irenab has quit IRC13:56
*** JeanBriceCombebi has quit IRC13:56
*** sigmavirus24_awa is now known as sigmavirus2413:56
*** JeanBriceCombebi has joined #openstack-meeting-313:56
*** esikachev has joined #openstack-meeting-313:57
*** pino|work has joined #openstack-meeting-313:57
*** fallenpegasus has quit IRC13:57
*** singlethink has quit IRC13:57
*** puranamr has joined #openstack-meeting-313:58
*** elmiko__ has joined #openstack-meeting-313:59
SergeyLukjanovhey sahara folks!13:59
*** tosky has joined #openstack-meeting-313:59
elmiko__hi13:59
esikachevhi!14:00
venzahello14:00
vgridnevo/14:00
AndreyPavlovhi14:00
toskyhi14:00
*** kchen has joined #openstack-meeting-314:00
elmiko__of course the vpn to my irc shell dies right before the meeting :/14:00
*** weiting has joined #openstack-meeting-314:00
*** hdd has joined #openstack-meeting-314:00
sreshetnyako/14:00
kcheno/14:00
NikitaKonovalovhi14:01
SergeyLukjanov#startmeeting sahara14:01
openstackMeeting started Thu Jul  2 14:01:24 2015 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SaharaAgenda14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: sahara)"14:01
openstackThe meeting name has been set to 'sahara'14:01
*** nikhil_k1away is now known as nikhil_k14:01
SergeyLukjanov#topic sahara@horizon status (crobertsrh, NikitaKonovalov)14:01
*** openstack changes topic to "sahara@horizon status (crobertsrh, NikitaKonovalov) (Meeting topic: sahara)"14:01
SergeyLukjanov#link https://etherpad.openstack.org/p/sahara-reviews-in-horizon14:02
NikitaKonovalovThere is finally a change created to move Sahara panels to contib14:02
NikitaKonovalov#link https://review.openstack.org/#/c/197363/14:02
elmiko__\o/14:02
*** sankarshan has quit IRC14:02
*** sankarshan has joined #openstack-meeting-314:02
NikitaKonovalovso once that one is merge, we'll need to rebases everythnig14:03
NikitaKonovalovactually it's better to start rebasing now14:03
*** banix has joined #openstack-meeting-314:03
SergeyLukjanovNikitaKonovalov, ++ for starting rebasing now14:04
NikitaKonovalovbecause the current changes wount be merged anyway14:04
SergeyLukjanovNikitaKonovalov, what's the progress of moving to contrib?14:04
vgridnevI have several patches added, one related for node process tab14:04
*** huichun has joined #openstack-meeting-314:04
vgridnevfor horizon I meant14:04
NikitaKonovalovSergeyLukjanov: the patch is on review, and guess what? no reviews so far14:04
SergeyLukjanov:(14:05
vgridnevand now it in merge conflict14:05
NikitaKonovalovI hope we'll get it merged fast14:05
SergeyLukjanovdavid-lyle, could we help somehow with a patch that is moving sahara to contrib?14:06
NikitaKonovalovvgridnev: it's now a good momnet to rebase your changes on top of the contrib change14:06
vgridnevNikitaKonovalov, ok14:06
NikitaKonovalovanyway I'll chack that that all our changes are rebased14:07
NikitaKonovalovcheck*14:07
*** mrmartin has quit IRC14:08
SergeyLukjanovNikitaKonovalov, ack14:08
SergeyLukjanovNikitaKonovalov, and please ensure that our etherpad contains all links to the CRs14:08
NikitaKonovalovno more new from me14:08
SergeyLukjanovok, thx14:08
NikitaKonovalovSergeyLukjanov: sure14:08
SergeyLukjanov#topic spark version status (elmiko)14:09
*** openstack changes topic to "spark version status (elmiko) (Meeting topic: sahara)"14:09
elmikohey14:09
SergeyLukjanovelmiko, hey ;)14:09
elmikogiven the recent changes proposed from venza, i wan't to talk about deprecetating 0.9.114:09
SergeyLukjanovshould we support older versions of spark?14:09
SergeyLukjanov#link https://review.openstack.org/#/c/195054 introduces 1.3 version of spark, but sahara plugin only lists 0.9.1 and 1.0.0 (https://review.openstack.org/#/c/196686 adds 1.3.1 to the sahara plugin -- venza), and we have no way to regenerate older versions14:09
elmikoand what our plans are for the future14:09
*** wxy has joined #openstack-meeting-314:09
elmikoi don't see much point in supporting more than 1 older version of spark14:09
SergeyLukjanovelmiko, agreed14:10
NikitaKonovalovelmiko: agree14:10
venzaactually versions 0.9.1 and 1.0.0 are no longer available from spark's website14:10
elmikoright, that too14:10
elmikoimo, we really need to get 1.4 support =)14:10
SergeyLukjanovwe could keep them as deprecated (only for ops on the already provisioned clusters)14:10
SergeyLukjanovand keep only latest version active14:11
elmikoSergeyLukjanov: +114:11
venzawe did not test 1.4 yet, but 1.3.1 works well, that's why my patch is for 1.3.114:11
venzaSergeyLukjanov: +114:12
SergeyLukjanovI hope to have fully working Spark support in HDP and CDH someday (with EDP and etc.) and then we'll be probably able to use them instead of separated plugin, what do you guys thinking about it?14:12
elmikoi'm talking more optimistically venza =)14:12
toskyvenza: do you think to push 1.4 for Liberty, and if yes, will it be 1.4 only or 1.4+1.3?14:12
*** sankarshan is now known as sankarshan_away14:12
elmikoi think we should still have a "vanilla" spark plugin at some point14:12
SergeyLukjanovanother rand idea - to merge vanilla hadoop and spark plugins14:12
venzayes, it is like the vanilla hadoop plugin14:12
SergeyLukjanovoh, spark based on CDH HDFS14:13
elmikoi've been experimenting with a bare fedora spark 1.4 image, and i could see value in having a separate, simple, spark plugin14:13
venzalately we are running compute only clusters without local hdfs14:13
elmikoimo, we should someday have "vanilla hadoop" and "vanilla spark", but maybe not as the same plugin14:13
*** puranamr has quit IRC14:14
venzatosky: I plan to work on 1.4 right after 1.3 gets merged14:14
venzatosky: probably is is again a simple patch14:14
venza*it14:15
*** wxy has left #openstack-meeting-314:15
elmikoyea14:15
*** sankarshan_away is now known as sankarshan14:16
elmikosounds like we are in agreement about deprecationg then14:16
SergeyLukjanovyup14:16
venzayes14:16
elmikowe'll probably have to talk in tokyo about the future of the spark plugin though?14:17
SergeyLukjanov#agreed keep only latest spark version active and deprecate older versions14:17
SergeyLukjanovthat's the summary I think ^^14:17
elmiko+114:17
venza+114:17
SergeyLukjanovgreat14:18
SergeyLukjanov#topic News / updates14:18
*** openstack changes topic to "News / updates (Meeting topic: sahara)"14:18
elmikokeystone session spec is finally up, #link https://review.openstack.org/#/c/197743/14:19
elmikoi have some poc code working locally with this14:19
NikitaKonovalovI've been working on NameNode HA support for HDP. And it is not working due to a strange Ambari behavior when starting NameNodes14:19
vgridnevMake some important back ports to stable/kilo branch in sahara, several bugs researching and also horizon, horizon and etc14:19
*** dims has quit IRC14:19
AndreyPavlovi've been working on shared across tenants and protected from updates/deletions resources14:19
toskyNikitaKonovalov: uh, for 2.2? We found an issue in 2.0.6, Oozie is not properly configured14:20
NikitaKonovalovAn Ambari bug is here https://issues.apache.org/jira/browse/AMBARI-12235 If anyone is interested14:20
NikitaKonovalovtosky: 2.214:20
SergeyLukjanovWe successfully moved to the in-tree Devstack plugin, so, it's now very easy to improve it's integration14:20
weitingWe are working on Sahara/Manila integration and I just cook one slide deck on google docs for your reference.14:20
weitinghttps://docs.google.com/presentation/d/1qv2L1AVJ2BuBfBX33bE2hBu4KROV4l5h5xVHG9S9Sp8/edit?usp=sharing14:20
toskyNikitaKonovalov: for reference, https://bugs.launchpad.net/sahara/+bug/147084114:20
openstackLaunchpad bug 1470841 in Sahara "NameNode HA for HDP2 does not set up Oozie correctly" [Undecided,New] - Assigned to Ethan Gafford (egafford)14:20
esikachevworking on cluster verification checks #links https://review.openstack.org/#/c/196713/14:20
NikitaKonovalovtosky: I'll keep that in mind, thanks14:20
weitingPlease take a look and let me know your comment.14:20
kchenI am working on NameNode HA support for CDH. hope can finish the codes soon.14:20
SergeyLukjanovweiting, thx!14:21
SergeyLukjanovkchen, cool!14:21
SergeyLukjanovkchen, are you going to impl HA for other services?14:21
toskyNikitaKonovalov: egafford is working on it (but I don't see him online), so you can coordinate with him14:21
kchen@Sergey, yes for Yarn.14:21
kchenOthers are not in current plan14:21
NikitaKonovalovkchen: do you have a change on review for NameNode HA?14:21
*** egafford has joined #openstack-meeting-314:21
kchen@Nikita no yet.14:22
kchenhope I can submit one patch soon.14:22
NikitaKonovalovkchen: ok, I was just curious to see how CDH does HA14:23
huichunegafford:  I have updated recurrence edp job spec14:23
kchenI have already submitted a spec and a patch to add a CM API for HDFS HA on CDH14:23
SergeyLukjanovAndreyPavlov, how is it going with a grenade code?14:23
SergeyLukjanovAndreyPavlov, have you tested it?14:24
egaffordhuichun: Cool; I'll take another look. More eyes on the recurrence spec would be handy, btw; it's important.14:24
NikitaKonovalovkchen: https://review.openstack.org/#/c/197551/ here is the change I have for HDP right now14:24
*** matrohon has quit IRC14:24
AndreyPavlovi've tested it as part of grenade14:24
kchenNikitaKonovalov: cool, I will check that.14:24
*** matrohon has joined #openstack-meeting-314:24
SergeyLukjanov#topic Open discussion14:25
*** openstack changes topic to "Open discussion (Meeting topic: sahara)"14:25
AndreyPavlovit worked fine, but haven't checked it after plugins implementation14:25
venzajust a question about version deprecation14:25
kchenNikitaKonovalov: https://review.openstack.org/#/c/196929/ this spec shows how to do HDFS HA for CDH14:25
venzait means the version is still listed, but no tests are run?14:26
venzahow is a user aware the version X is deprecated?14:26
kchenAll, one thing I am not clear, whether we have a plan to align all job/job_execution into job_template/job everywhere. codes, docs.14:26
kchenFor recently I was reading the documents, and found the names very confusing.14:26
SergeyLukjanovkchen, it could be fully done only with a v2 API14:27
vgridnevvenza, I suppose we can add some validation rules about deprecation of some plugins version14:27
NikitaKonovalovkchen: thanks I'll have a look14:27
SergeyLukjanovkchen, because we need to change an API endpoits and object names for it14:27
elmikokchen: yea, i have ides about that for v214:27
kchenSergeyLukjanov: ok. but Horizon already changed the names on UI, right?14:27
*** wxy_ has joined #openstack-meeting-314:27
toskyvenza: when vanilla 2.4 was deprecated, the version was listed but you couldn't create any new clusters14:27
venzatosky: ok14:27
toskychanging topic, I will propose a small spec to allow the scenario test runner to consume mako templates and convert the yaml files we have in etc/scenario to this format, so that sahara-ci won't need to do the replacement14:28
toskyI will need some feedback from degorenko, I guess14:28
elmikokchen, SergeyLukjanov, i should have a first draft of the v2 api spec up within the next 2 weeks. it has a roadmap for some of these changes (including renaming job templates/jobs)14:29
elmikoi have a proposed strategy for a number of changes we should implement over the remaining L and then M cycles14:29
kchentosky: so if I want to do scenario tests in my local machine, we do not need to do the replacement by hand, right?14:29
toskykchen: exactly!14:29
*** wxy_ has quit IRC14:29
toskykchen: that's the good side effect14:29
*** wxy_ has joined #openstack-meeting-314:30
kchentosky: sounds great :)14:30
*** wxy_ has quit IRC14:30
*** e0ne is now known as e0ne_14:30
*** wxy_ has joined #openstack-meeting-314:30
SergeyLukjanovtosky, could you probably write a spec for it?14:31
elmikohehe, that's exactly what we talked about last night!14:31
toskySergeyLukjanov: that's what I'm doing right now :)14:31
SergeyLukjanovgreat14:31
SergeyLukjanovyeah, I remember we were talking about it last night ;)14:32
SergeyLukjanovor day14:32
*** e0ne_ is now known as e0ne14:32
*** kebray has joined #openstack-meeting-314:33
elmikoi14:33
elmikoi14:33
elmikolol14:33
kchen?14:33
kchenso silent :)14:34
elmikoi'll plead once again, i could use reviews on https://review.openstack.org/#/c/197743/ and https://review.openstack.org/#/c/179393/ =)14:34
*** kebray has quit IRC14:34
elmikosorry, mistyped a few14:34
egaffordWhile we're on begging for reviews, it'd be great to finish off review on https://review.openstack.org/#/c/187809/ : there's more work to do on this change during the cycle in client/UI/integration tests, but it's currently pending this review.14:35
elmikothat should be our topic after open discussion, "review begging" ;)14:36
egaffordHeh.14:36
* elmiko shakes his cup14:37
*** MarkAtwood has joined #openstack-meeting-314:37
*** wxy has joined #openstack-meeting-314:37
*** JeanBriceCombebi has quit IRC14:37
*** dims has joined #openstack-meeting-314:38
*** galstrom_zzz is now known as galstrom14:40
*** regXboi has joined #openstack-meeting-314:40
SergeyLukjanovegafford, I'll take a look on it today again and it looks like I'll approve it :)14:40
*** wxy_ has quit IRC14:40
egaffordThanks SergeyLukjanov! I just want to make sure there's enough time to get all the bits in place in L.14:41
SergeyLukjanovegafford, that's important14:41
SergeyLukjanovfolks, propose corresponding changes to client asap to make us able to release client with at least few features per time ;)14:42
venzaSergeyLukjanov: about storing Spark images. There is 1.0.0 on mirantis web space linked in the documentation14:42
elmikogood question venza!14:43
*** JeanBriceCombebi has joined #openstack-meeting-314:43
venzaI have a 1.3.1 on google drive, but that is not good for documentation14:43
*** esp has left #openstack-meeting-314:43
*** sreshetnyak has quit IRC14:44
*** dims has quit IRC14:44
*** sreshetnyak has joined #openstack-meeting-314:44
*** matrohon has quit IRC14:45
SergeyLukjanovvenza, we could put it to the storage14:45
*** matrohon has joined #openstack-meeting-314:45
*** Ramanjaneya has quit IRC14:45
venzaSergeyLukjanov: you mean update the image on mirantis server?14:45
SergeyLukjanovI'm still thinking about how to safely publish images to tarballs.o.o14:45
*** nikhil_k is now known as nikhil_k1away14:45
*** nikhil_k1away is now known as nikhil_k14:46
SergeyLukjanovvenza, yeah14:46
*** nikhil_k is now known as nikhil_k1away14:46
*** banix has quit IRC14:46
*** nikhil_k1away is now known as nikhil_k14:46
venzaI will remove the link from the documentation for 1.0.0 since we are deprecating it, then we will see14:46
SergeyLukjanovthe main issue is that if we'll publish images after each change merged - nothing will be tested and it's not safe14:46
*** Vikram_ has joined #openstack-meeting-314:46
elmiko+114:47
elmikowhat's our option though, i think it's nice if we provide some images but we will always have the problem of validation.14:48
*** wxy has left #openstack-meeting-314:48
elmikoit doesn't seem friendly to ask all users to create images, but it almost seems like the best path.14:49
*** dims has joined #openstack-meeting-314:49
egaffordelmiko: That doesn't really fix the validation issue, though, so much as defer the problem away from the dev team toward support teams.14:49
tellesnobregai think that we want users to create their own images, we should make it easier, more straightforward14:50
elmikoright14:50
elmikoegafford: but otoh, who's doing all this validation work on the images, and how to keep up with newer versions in light of that?14:50
SergeyLukjanovelmiko, yeah14:50
egaffordtellesnobrega: Yeah, I have this dream of having an image generation service that's shared by Trove, Sahara, Octavia, etc.14:51
egaffordelmiko: I don't have a fabulous solution to that problem either, really, other than gating at major releases.14:51
tellesnobregaegafford, + 114:51
SergeyLukjanovright now, before publishing, we're asking esikachev to generate all images, test them and upload :)14:51
elmikoand we appreciate that esikachev is doing that =)14:52
egaffordelmiko, SergeyLukjanov: Backward (and even forward) compatibility will always be rough here without a vast matrix.14:52
elmikoegafford: agreed, my concern is that in the time it takes us to produce validated images, for spark let's say, we will want to be pushing a newer version. and will anyone even want the older versions?14:53
*** mpmsimo has joined #openstack-meeting-314:53
*** tidwellr has joined #openstack-meeting-314:53
elmikoassuming our images are for users who are trying out sahara, why isn't it fair to just announce "these are experimental images, for production usage you should use something else"14:54
SergeyLukjanovelmiko, good idea14:54
elmikoi mean, if someone is going into production with sahara they should have a partner, or know how to create/validate images, or something...14:54
SergeyLukjanovwe could probably publish all latest images14:54
elmikojust make sure to announce "experimental, use at your own risk" ;)14:55
SergeyLukjanovand document that it's just a experimental images14:55
egaffordelmiko: Well, this is a classic reliability vs. shiny tradeoff. Some folks will want the new shiny even at risk of pain, some will want things to just work immediately and will flee from Sahara if they don't.14:55
venza+1 for publishing with the disclaimer14:55
SergeyLukjanovmore then that, we could some day add some CI for this images14:55
SergeyLukjanovprobably periodic jobs14:55
tellesnobregaelmiko, i agree with that14:55
elmikoegafford: agreed, but how much assurance can we provide when we are talking about the depth of, essentially, free validation work?14:56
*** john-davidge has joined #openstack-meeting-314:56
*** carl_baldwin has joined #openstack-meeting-314:56
*** gsagie has joined #openstack-meeting-314:57
*** gsagie has left #openstack-meeting-314:57
SergeyLukjanovgood question :)14:57
*** wxy has joined #openstack-meeting-314:57
SergeyLukjanovbtw 3 mins left14:57
*** zz_natorious is now known as natorious14:57
*** bradjones has quit IRC14:57
*** yamahata has joined #openstack-meeting-314:58
egaffordelmiko: I think it's not at all unreasonable to assert that at major and point releases, we have a version of sahara-image-elements (which depends on a version of DIB) which we know to be able to create a functional image.14:58
*** wxy has quit IRC14:58
*** bradjones has joined #openstack-meeting-314:58
*** bradjones has quit IRC14:58
*** bradjones has joined #openstack-meeting-314:58
elmikoit makes sense to me if we have the juno release with supported validated images, and the kilo release with ..., but for master work it should be experimental images. imo14:59
tellesnobregahere at the university, we are starting to announce sahara so other researchers can use it, and we will probably need different images, having a way to generate them quickly would be nice, i mean, we dont want to have to have a setup just to build images, and we dont want to have to clone three projects to generates images everytime14:59
tellesnobregajust on the direction of DIY images14:59
*** neiljerram has joined #openstack-meeting-314:59
elmikotellesnobrega: but wouldnt it make more sense for your organization to provide a set of images that are blessed for all to ue?14:59
elmiko*use14:59
tellesnobregayes, of course15:00
etoews#startmeeting api wg15:00
openstacketoews: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.15:00
SergeyLukjanov#endmeeting15:00
tellesnobregaguess our time is up15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
egaffordelmiko, SergeyLukjanov: Frankly, I think that if we can't say that we have a stable release of sahara-image-elements for each major release, we really need to disown the image gen process entirely, and let something else grow to fill this gap.15:00
elmikooops15:00
openstackMeeting ended Thu Jul  2 15:00:16 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-07-02-14.01.html15:00
*** mlavalle has joined #openstack-meeting-315:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-07-02-14.01.txt15:00
egaffordHeh.15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2015/sahara.2015-07-02-14.01.log.html15:00
SergeyLukjanovthanks sahara folks15:00
carl_baldwinetoews: This is where we do the L3 meeting.15:00
*** tholtzen has joined #openstack-meeting-315:00
regXboicarl_baldwin: hi15:00
kchenbye all15:00
carl_baldwinregXboi: hi15:00
*** pc_m has joined #openstack-meeting-315:00
yamamotohi15:00
etoewsoops. sorry! off by 1 hour.15:00
elmikoetoews: it's in 1 hour ;)15:00
*** lazy_prince has joined #openstack-meeting-315:00
pavel_bondarcarl_baldwin: hi15:00
mlavallehi15:00
*** AndreyPavlov has left #openstack-meeting-315:00
carl_baldwinetoews: no worries, thanks.15:00
pc_mo/15:01
*** kchen has quit IRC15:01
*** weiting has quit IRC15:01
neiljerramhi15:01
john-davidgehi15:01
*** tosky has left #openstack-meeting-315:01
*** venza has left #openstack-meeting-315:01
carl_baldwinyamamoto: pavel_bondar mlavalle pc_m neiljerram john-davidge: hi15:01
carl_baldwinLet’s get started.15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Jul  2 15:01:55 2015 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic #topic Announcements15:02
*** openstack changes topic to "#topic Announcements (Meeting topic: neutron_l3)"15:02
*** absubram has joined #openstack-meeting-315:02
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:02
Vikram_hi15:02
carl_baldwinI don’t have anything to announce.  Does anyone have anything?15:02
carl_baldwinVikram_: hi15:02
carl_baldwin#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
carl_baldwinFirst is bug 1404743, it has been around for a while.15:04
openstackbug 1404743 in neutron "sporadic test failures due to VMs not getting a DHCP lease" [High,Confirmed] https://launchpad.net/bugs/140474315:04
carl_baldwinIt sounds like one of those bugs where it could have any number of causes.15:05
neiljerramIs any more detail known about it, e.g. is it to do with a previous dhcp_release failing?15:05
neiljerramcarl_baldwin: ah sorry, crossed lines :-)15:05
carl_baldwinneiljerram: No problems.15:06
*** dims has quit IRC15:06
carl_baldwinI think what we should do here is reassess the severity of the bug by looking through recent logstash.15:06
neiljerramI guess there are lots of situations like this, so a meta-question would be what instrumentation could be added to the DHCP agent, to help distinguish between possible causes.15:07
carl_baldwin#action carl_baldwin will reassess bug 140474315:07
openstackbug 1404743 in neutron "sporadic test failures due to VMs not getting a DHCP lease" [High,Confirmed] https://launchpad.net/bugs/140474315:07
*** Guest42148 has joined #openstack-meeting-315:07
carl_baldwinThe other bug is bug 146932215:08
openstackbug 1469322 in neutron "Associating a floatingip with a dual stack port requires the fixed-address to be specified" [High,Confirmed] https://launchpad.net/bugs/146932215:08
carl_baldwinThis one was filed as an rfe and discussed in the drivers meeting.  But, it looks like a regular bug to me.15:08
*** Guest42148 is now known as dims_15:09
regXboicarl_baldwin: I agree15:09
carl_baldwinIf anyone is interested in taking this on, let me know.15:09
*** kebray has joined #openstack-meeting-315:09
*** belmoreira has quit IRC15:10
*** asahlin_away is now known as asahlin15:10
*** kebray has quit IRC15:10
*** Piet has quit IRC15:10
carl_baldwin#topic Routing Network Segments15:10
*** openstack changes topic to "Routing Network Segments (Meeting topic: neutron_l3)"15:11
regXboicarl_baldwin: can we go back a second - I have a question15:11
carl_baldwin#undo15:11
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x8e73a50>15:11
regXboido we want to talk about https://bugs.launchpad.net/neutron/+bug/1323766 and how it relates to 1469322? (i.e. do we want the same resource working on both)15:11
openstackLaunchpad bug 1323766 in neutron "Incorrect Floating IP behavior in dual stack or ipv6 only network" [Medium,In progress] - Assigned to Bradley Jones (bradjones)15:11
*** ttrifonov is now known as zz_ttrifonov15:12
carl_baldwinregXboi: It is worth considering.  I had forgotten about 1469322 to be honest.15:13
regXboiI'm curious what progress is being made on 1323766 since they seem closely related15:13
*** vgridnev has quit IRC15:14
regXboianyway - now that that is in the log, we can move on15:14
john-davidgeregXboi: pinging brad now to see if he’s available to comment15:14
carl_baldwinregXboi: No progress has been made on 1323766 from what I can tell.15:14
regXboicarl_baldwin: that's how I read the bug, but wanted to confirm15:15
*** matrohon has quit IRC15:16
carl_baldwinLooks like the patch for 1469322 just stopped getting attention.15:16
*** matrohon has joined #openstack-meeting-315:16
*** puranamr has joined #openstack-meeting-315:17
carl_baldwin#action carl_baldwin will follow up and reconcile 1469322 and 132376615:17
carl_baldwin#topic Routing Network Segments15:17
*** openstack changes topic to "Routing Network Segments (Meeting topic: neutron_l3)"15:17
*** killer_prince has joined #openstack-meeting-315:18
carl_baldwinI think we made a lot of progress at the mid-cycle on this.  I have written it up as https://review.openstack.org/#/c/196812/15:18
*** DericHorn-HP has joined #openstack-meeting-315:18
regXboicarl_baldwin: I've got one outstanding question about AS, but it's not enough to not +1 it15:18
* regXboi shudders at the double negative15:18
*** lazy_prince has quit IRC15:19
carl_baldwinregXboi: I see it.  I will address the comment.15:19
neiljerramFWIW, I'm still interested in exploring my crazy pluggable IPAM idea, just in case it might fly...15:20
neiljerramBut that's no reason, I think, to hold up this spec as it is at the moment.15:21
regXboicarl_baldwin: thx - and as I said, it's a nit, so I've had +1 on it for a couple of PS now15:21
carl_baldwinneiljerram: johnbelamaric will be a very good person to help with that.15:21
neiljerramcarl_baldwin: Cool, I'll try to hook up with him15:21
carl_baldwinregXboi: Yes, and thank you for that.  Also, thank you for clarifying.15:21
pcarverI had one question that I added to the review but it may just be my misunderstanding of intent.15:22
pavel_bondarneiljerram: john is on vac now, I guess he will be available next week15:22
*** hurgleburgler has joined #openstack-meeting-315:22
carl_baldwinpcarver: I did not see it until just now when I refreshed the page.15:22
neiljerrampavel_bondar: Thanks.  Would you like to discuss my idea instead, then?  (After this meeting.)15:22
*** lazy_prince has joined #openstack-meeting-315:23
carl_baldwinneiljerram: pavel_bondar could also be a good person to help.15:23
pavel_bondarneiljerram: yes, let's try15:23
*** woodster_ has joined #openstack-meeting-315:23
*** pino|work has left #openstack-meeting-315:23
pcarverThere was some discussion at the summit regarding ODL and non-L2 networks. Is this spec on that same topic?15:24
carl_baldwinpcarver: I will address your comment after the meeting when I can.15:24
*** yamamoto has quit IRC15:24
*** egafford has left #openstack-meeting-315:24
neiljerrampavel_bondar: Thanks, I'll ping you in about 1 hour from now, if that will be convenient for you.15:24
carl_baldwinpcarver: I think this is a step in that direction.  I had a discussion with Ed about this one on one.  There will probably be more to it.15:24
*** jcoufal has quit IRC15:25
*** yamamoto has joined #openstack-meeting-315:25
pcarverOk. Just wanted to confirm. I talked with Ed one on one as well and learned a lot about what he was trying to say that I didn't get from the meeting.15:25
*** killer_prince has quit IRC15:25
carl_baldwinpcarver: Let’s talk about it later in the neutron room, I’m interested to know what you learned.15:26
pcarver10-415:26
*** puranamr has quit IRC15:26
carl_baldwinLet’s move on.  We’ve got a lot to cover.15:26
carl_baldwin#topic bgp-dynamic-routing15:26
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:26
tidwellrhi15:27
carl_baldwintidwellr: Vikram_: Anything to report here?  I know tidwellr has been working on the guts of this.15:27
regXboiare there links to look at?15:27
pavel_bondarneiljerram: let's better discuss it on monday in wide company(with john), since in an hour it will be 7:30 pm in my location, and long weekend starts today15:27
*** kebray has joined #openstack-meeting-315:27
Vikram_currently ryan is looking into it15:27
Vikram_i will start from next week15:27
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam#bgp-dynamic-routing15:27
regXboidoh15:28
carl_baldwin^ This may need some cleanup.  tidwellr could you look over the links there quickly today?15:28
tidwellryes, I can do that15:28
tidwellrI've got a devref review up https://review.openstack.org/#/c/19645215:28
*** mpmsimo has quit IRC15:28
tidwellrit's WIP, but I intend to start fleshing it out15:29
carl_baldwintidwellr: ack15:29
tidwellrit might be helpful for people to go to the devref first if they're interested15:29
*** pkarikh has quit IRC15:30
*** pkarikh has joined #openstack-meeting-315:30
tidwellrI have a bunch of code queued in my sandbox that I haven't put out for review15:30
carl_baldwintidwellr: Thanks!  It looks like a reasonably condensed document.15:30
neiljerrampavel_bondar: OK, thanks.15:30
*** ajmiller__ is now known as ajmiller15:30
tidwellrhoping to push reviews early next week15:31
carl_baldwintidwellr: Great, sounds like good progress.  I also happen to know you’re well on your way to creating the server-side queries to drive the announcements.15:31
carl_baldwinAnything else to discuss here?15:32
tidwellrnope, we just need to get moving on the dr_agent and RPC interface next week15:32
Vikram_will do that positively :)15:32
carl_baldwintidwellr: Vikram_: thanks15:33
carl_baldwin#topic neutron-ipam15:33
*** openstack changes topic to "neutron-ipam (Meeting topic: neutron_l3)"15:33
carl_baldwinpavel_bondar: I think we’re getting close.15:33
carl_baldwinpavel_bondar: Thanks for your patience with us reviewers.15:33
pavel_bondarcarl_baldwin: we are moving forward, and that is good15:34
pavel_bondarbig refactoring is now decomposed15:35
pavel_bondarinto small review like #link https://review.openstack.org/#/c/197950/15:35
*** doug-fish has quit IRC15:35
carl_baldwinpavel_bondar: What is the next review in line?15:35
pavel_bondarone I mentioned15:36
carl_baldwinpavel_bondar: ack15:36
pavel_bondarafter it goes #link https://review.openstack.org/#/c/153236/15:36
pavel_bondarI hope they are pretty small now and easy for review15:37
carl_baldwinpavel_bondar: actually, https://review.openstack.org/#/c/19709015:37
*** singleth_ has quit IRC15:37
carl_baldwin…. has to merge.  I’ll take care of it.15:37
pavel_bondarcarl_baldwin: it is in gate now15:37
carl_baldwinpavel_bondar: right, I thought it was hung up on something but just noticed it was approved this morning.15:38
carl_baldwinpavel_bondar: Anything else?15:38
pavel_bondarcarl_baldwin: but I see some failure there, so may require recheck15:38
carl_baldwinpavel_bondar: I’ll watch it.15:38
pavel_bondarcarl_baldwin: no, that is it15:38
pavel_bondarcarl_baldwin, thanks15:39
carl_baldwinpavel_bondar: thanks15:39
*** armax has joined #openstack-meeting-315:39
carl_baldwinI skipped an agenda item because I was reading the contents section of the L3 team page.15:39
carl_baldwin#topic Proposing Neutron instrumentation15:40
*** openstack changes topic to "Proposing Neutron instrumentation (Meeting topic: neutron_l3)"15:40
carl_baldwinregXboi: This is your item.  Sorry to have skipped it before.15:40
regXboicarl_baldwin: no worries - I figured it would be at the end15:40
regXboithe etherpad is live and I think the email explains it15:40
regXboi#link https://etherpad.openstack.org/p/neutron-instrumentation etherpad15:40
regXboiSam-I-Am has already dropped a few notes in - I have to ping gsagie as wll15:41
regXboi*well15:41
regXboiothers are welcome to chime in - I envision the output being an umbrella BP that won't totally land in liberty15:42
regXboibut hopefully we can get some small pieces of it in15:42
*** esikachev has left #openstack-meeting-315:42
regXboicarl_baldwin: that's all unless folks have questions and those can go on the etherpad or ML15:42
carl_baldwinregXboi: Good start.15:42
carl_baldwinregXboi: This sounds bigger than L3 a bit.15:43
regXboicarl_baldwin: it will likely grow beyond L3 as we go, but we'll start it here15:43
regXboicarl_baldwin: I've already sorta pinged mestery on the side about the potential for that growth15:43
carl_baldwinregXboi: ack, thanks15:44
carl_baldwin#topic DNS15:44
*** openstack changes topic to "DNS (Meeting topic: neutron_l3)"15:44
carl_baldwinmlavalle: hi15:44
mlavallecarl_baldwin: I will be pushing next review to https://review.openstack.org/#/c/88624/ later today. I am almost done15:44
mlavalleadding the third case: external ip on proverder network (no floating ip)15:45
mlavalleI also want to ask yamamoto to review https://review.openstack.org/#/c/90150/ again15:45
mlavallethat is the nova side15:45
yamamotosure15:46
mlavalleit is compatible now with its neutron counterpart, that is already merged15:46
mlavalleper your comment15:46
mlavalleand I will be pushing code for 88623 over the next few days15:46
mlavallethat's all so far15:47
carl_baldwinmlavalle: Sounds like the spec side is coming together.15:47
carl_baldwinmlavalle: How about the code side?15:47
mlavalleyep, 88624 is ready for merge15:48
*** JeanBriceCombebi has quit IRC15:48
mlavalleI will push code for 88623 over the next few days. Making progress15:48
*** stevemar has quit IRC15:48
mlavalleand as soon as I am done with 88624, I will start coding that one as well15:49
carl_baldwinmlavalle:  great!15:49
carl_baldwin#topic Address Scopes15:50
*** openstack changes topic to "Address Scopes (Meeting topic: neutron_l3)"15:50
carl_baldwinQuick update on this.  I think I have most of the L3 agent side worked out.  But, much of it is WIP in my sandbox.  I will work over the next week to clean it up in to nice patch to submit.15:50
carl_baldwinVikram_ has also done some great work on the api and db side.15:51
*** sbalukoff has joined #openstack-meeting-315:51
Vikram_Will complete by this week15:51
Vikram_and submit for review15:51
*** mwagner_lap has quit IRC15:51
*** stanzgy has quit IRC15:52
carl_baldwinVikram_: thanks.15:52
carl_baldwin#topic IPv615:53
*** openstack changes topic to "IPv6 (Meeting topic: neutron_l3)"15:53
carl_baldwinAnything here?15:53
*** mzawadzki_mirant has joined #openstack-meeting-315:54
*** adityav has joined #openstack-meeting-315:54
*** Piet has joined #openstack-meeting-315:54
carl_baldwinhaleyb: Are there any patches up for the issues that we’ve discovered recently?15:55
*** stevelle has joined #openstack-meeting-315:56
carl_baldwinjohn-davidge: Also, what needs to happen with prefix delegation?15:56
carl_baldwinjohn-davidge: Looks like a rebase is needed.  I’ll watch for that and then review.15:57
*** cdent has joined #openstack-meeting-315:58
bradjonescarl_baldwin: sorry wasn't around for comment earlier I was working on 1323766 a while back but the patch got abandoned because of testing issues15:58
bradjonescarl_baldwin: shall I reactivate it, as I solved a lot of the issues around dual stack and can sort the tests out pretty quickly15:58
carl_baldwinbradjones: hi.  Any plans to move forward with it?15:58
*** mickeys has joined #openstack-meeting-315:59
*** baoli has quit IRC15:59
bradjonescarl_baldwin: yeah I can sort those tests out pretty quick so as long as I'm not treading on anyones toes i'll get that done15:59
carl_baldwinbradjones: You are welcome to reactivate it for bug 132376615:59
openstackbug 1323766 in neutron "Incorrect Floating IP behavior in dual stack or ipv6 only network" [Medium,In progress] https://launchpad.net/bugs/1323766 - Assigned to Bradley Jones (bradjones)15:59
carl_baldwinbradjones: Thanks.15:59
bradjonescarl_baldwin: no problem15:59
*** kozhukalov_ has joined #openstack-meeting-316:00
carl_baldwinAnd, we’re out of time.  Thanks everyone.  There are lots of great things happening.16:00
carl_baldwin#endmeeting16:00
neiljerrambye all16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu Jul  2 16:00:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-07-02-15.01.html16:00
*** pc_m has left #openstack-meeting-316:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-07-02-15.01.txt16:00
regXboibye everybody16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2015/neutron_l3.2015-07-02-15.01.log.html16:00
*** regXboi has left #openstack-meeting-316:00
yamamotobye16:00
etoews#startmeeting api wg16:00
openstackMeeting started Thu Jul  2 16:00:37 2015 UTC and is due to finish in 60 minutes.  The chair is etoews. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
etoewshi!16:00
*** neiljerram has left #openstack-meeting-316:00
*** baoli has joined #openstack-meeting-316:00
Vikram_bye16:00
*** Vikram_ has quit IRC16:00
*** ryansb has joined #openstack-meeting-316:01
*** jtomasek has quit IRC16:01
cdento/16:01
* etoews still updating agenda16:02
sigmavirus24o/16:02
miguelgrinberghello16:02
stevelleo/16:02
sigmavirus24etoews: that's a pre-meeting agneda item16:02
sigmavirus24why didn't you do it then?16:02
sigmavirus24=P16:02
ryansbo/16:02
etoewsjit agenda16:02
elmikoo/16:02
ryansblol16:02
etoews#topic agenda16:02
*** openstack changes topic to "agenda (Meeting topic: api wg)"16:02
etoews#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:02
etoewsi didn't get to all of the reviews that could be frozen.16:03
etoews#topic previous meeting action items16:03
*** openstack changes topic to "previous meeting action items (Meeting topic: api wg)"16:03
etoews#link http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-06-25-00.01.html16:03
etoewselmiko to freeze and notify about https://review.openstack.org/#/c/18009416:04
*** absubram has left #openstack-meeting-316:04
etoewsthat happened right?16:04
elmikoyes16:04
etoews++16:04
etoewsetoews experiment with creating a guideline status mailing list update16:04
etoewsso i didn't get to any "experimenting" but i did give it some more thought16:05
ryansbone better, it's merged16:05
etoewsi think i'll just send out an email on a bi-weekly or monthly basis just describing what we're up to16:06
elmiko+116:06
cdentthat sounds about right etoews16:06
cdentpeople like the human touch16:06
*** matrohon has quit IRC16:06
elmikoso, we are saying no to an indie 'zine that gets published during summit? ;)16:07
etoewsi'm not not saying no16:07
elmikolol16:07
* elmiko puts away mimeograph machine16:07
ryansbthat's not right out, but I think email publishing costs are lower than indie 'zines16:07
elmikofair16:07
etoewsi was thinking about trying to put together a gerrit dashboard to include in the email but haven't had time to look into it16:08
etoews#link http://ghostcloud.net/openstack_gerrit_dashboards/16:08
etoews#link https://github.com/stackforge/gerrit-dash-creator/16:08
elmikothat sounds kinda cool16:09
ryansbgood idea, I did that for heat a while ago16:09
ryansband it seemed to be used by >0 people on the team16:09
etoewsit would be nice to "encode" as much of our merge process into the dashboard16:09
ryansbthough please shorten the URL before distributing the link16:09
etoewsya. some of the links it produces are pretty gnarly16:10
ryansbI think heat's dash is 2K16:10
ryansbthe URL...16:10
etoewsit basically looks like an sql injection attack16:10
*** singlethink has joined #openstack-meeting-316:11
etoewsanyway, no idea when i'd be able to get to that.16:11
*** hurgleburgler has left #openstack-meeting-316:11
elmikofwiw, it sounds really nice16:11
etoewsryansb: i might ping you about it if i run into any issues16:12
etoews#topic ongoing reviews of API impacting code/spec16:12
*** openstack changes topic to "ongoing reviews of API impacting code/spec (Meeting topic: api wg)"16:12
ryansbkk, here's what the heatdash looks like http://supb.ro/heatdash16:12
etoewsso this is the kind of thing i'd like to include in the newsletter16:13
*** stevemar has joined #openstack-meeting-316:13
etoewsa list of the ongoing reviews of API impacting code/spec16:13
*** sahid has quit IRC16:14
etoewsthe only one i'm currently aware of is the glance artifacts api spec16:14
*** stevemar has quit IRC16:14
etoewswhat else is out there that people are reviewing?16:14
*** tidwellr has left #openstack-meeting-316:14
*** amotoki_ has joined #openstack-meeting-316:14
elmikowe've had a minor one in sahara, but it wasn't large enough to pull in others16:15
elmikoalso, it touched on the old /task endpoint debate ;)16:15
etoewslink?16:15
etoewsi'm looking for anything within the past month btw16:15
etoewsdoesn't have to be currently under review16:16
elmikosec16:16
elmikooh, heh, he forgot to mark it as APIImpact...16:17
elmiko#link https://review.openstack.org/#/c/188011/16:17
*** amotoki has quit IRC16:17
elmikoand i forgot to remind him...16:17
etoewsthx16:17
etoewsanyone else?16:18
etoewsit would be nice to have at least one more example ;)16:18
*** lazy_prince has quit IRC16:19
ryansb*crickets*16:19
cdentwe all seem a bit tired today16:20
etoewsthere must be something in nova. /ping alex_xu16:20
*** tholtzen has left #openstack-meeting-316:20
etoewsoh well16:20
etoews#topic guidelines16:21
*** openstack changes topic to "guidelines (Meeting topic: api wg)"16:21
etoews#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:21
elmikoi could really use more eyeballs on #link https://review.openstack.org/#/c/183698/16:21
elmiko=)16:21
*** natorious is now known as zz_natorious16:21
etoewslet's have a look16:21
*** baoli has quit IRC16:23
etoews"In these cases though, the implementor should exercise caution to only return these codes in situations where an error cannot be handled by the server."16:23
miguelgrinbergI really don't have enough justification to -1, but I think text treats things as black or white, ignoring the frequently occurring gray zones16:23
etoewsdo you mean "...handled by the application code." ?16:24
cdentmiguelgrinberg: isn't that rather the point: the guidelines need to paint a black and white picture so that the grey zones are tiny16:24
etoewscdent: ++16:24
elmikoetoews: yea, that might be a better way to word it16:25
miguelgrinbergyeah well, I think the gray zones are there regardless of what the guidelines say16:25
*** baoli has joined #openstack-meeting-316:25
etoewsmiguelgrinberg: what gray zones did you have in mind in this case?16:25
elmikomiguelgrinberg: i added the second paragraph to help address the grey zones16:25
etoewswe are the beacon of light that leads developers out of gray zones16:25
miguelgrinbergwell, I think making a distinction between server and app is really not that interesting when you look at things from the client side16:25
miguelgrinbergfrom the client it's just a server, who cares if the 5xx codes are generated by the app or the server proper16:26
cdentwe are not writing guidelines for the client side miguelgrinberg, we're writing guidelines for people developing api services16:26
miguelgrinbergcatching exceptions and replacing them with a 500 is a good example of this16:26
etoewsbut our audience is primarily the openstack contributors developing those servers16:26
cdent(sorry, I got to dash away for about 5 minutes, brb)16:26
ryansbto be fair, those same folks also write clients16:27
miguelgrinbergWhat I mean is that I consider the app part of the server, because all that matters is how the client uses these responses16:27
etoewsright. but 5xx says that things are screwed up beyond the app code ability to deal with them.16:29
elmikoi think it does make a difference on the server side when you think about 500/501 vs 502/503/504/505 though16:29
etoewsif i'm writing a client, i know that 5xx probably isn't recoverable in the near term16:29
etoewsso giving guidance to openstack contributors on it is valuable imo16:30
miguelgrinbergetoews: right, that's the scope of the 500x, saying that they come from the server and not the app does not really help much16:30
elmikoimo, these 5xx guidelines are more oriented at server side development16:31
cdentthe implication miguelgrinberg is that application code should not raise MyFiveHundredException('whoops')16:31
miguelgrinbergyou can say that "normally these errors are generated by the WSGI layer" or something to that effect, but it isn't black and white16:31
cdentonly the server should explicitly do that kind of thing16:31
miguelgrinbergbut there is one clear case we all agree on where a 500 is appropriate (exceptions that are unhandled)16:31
miguelgrinbergso that breaks your rule16:31
*** singleth_ has joined #openstack-meeting-316:31
elmikothats also why i said *should not* instead of *must not*16:32
elmikoand then added the example of when you might generate them16:32
ryansbyeah, but unhandled exceptions are (to an extent) implicit, since you needn't go out of your way to *not* handle them16:33
miguelgrinbergwell, but I could see a case where application code may end up all confused and throw a 500 to get out of a mess. Why not?16:34
miguelgrinbergThat's what the 500 is about16:34
elmikook, so the main point of this guideline was to add something for developers creating server-side apps. does it seem appropriate for that type of guidance?16:34
miguelgrinbergit does not need to be just for unhandled exceptions16:34
elmikoagreed miguelgrinberg, that's why i added the example of when you might raise a 50016:35
*** mattgriffin has joined #openstack-meeting-316:35
elmikoi just wanted to signal that "hey, you might need to do this and that's acceptable"16:35
etoewsi think it's appropriate. it strongly discourages dev from throwing a 5xx.16:35
*** singlethink has quit IRC16:35
cdentyou raise a 500 when you catch an unhandled exception, but your app has unhandled exceptions _regularly_ it is broken and should be handling those exceptions more defensively16:35
elmikoright, unless you have a good reason16:35
cdentif it can defend against them, then it can also turn them into 4xx16:36
elmikocdent: agreed16:36
miguelgrinbergcdent: not always16:36
miguelgrinbergI disagree with the idea of the 400 being a catch-all for app errors for example16:36
cdentYou'll need to convince me miguelgrinberg because you just saying "not always" isn't really getting anywhere16:36
*** Swami has joined #openstack-meeting-316:37
etoews"throwing a 500 to get out of a mess" concerns me. 500 is not a get out of jail free card.16:37
miguelgrinberg5xx are for server errors and 4xx are for user errors, you have to return the ones that makes sense, who generates what does not matter16:37
*** fallenpegasus has joined #openstack-meeting-316:37
etoewsto me the flow would be like this16:38
miguelgrinbergetoews: I think it is. If there is a bug in the code, and that takes you to a place you shouldn't be, I think 500 makes sense16:38
cdentsure miguelgrinberg: the point I'm trying to make is that server errors should be minimized, by being defensive, and if you can be defensive you can almost always define the error as a 4xx16:38
cdentso if you _cannot defend_ then a 500 makes sense16:38
cdentbut that should be vanishingly rare (in the ideal case)16:39
cdentand the guidelines should be representing the idealized aspirational case16:39
etoewsthe code has a bug and does handle it, it throws a 500 but this is a **temporary** situation.16:39
etoewsthe code gets fixed, deployed, and that 500 goes away.16:39
miguelgrinbergtemporary until you upgrade16:39
etoews++16:39
miguelgrinbergthat's still the intended use for a 50016:40
etoewsand that's fine16:40
etoewsi just prefer to strongly discourage using 500 as an out16:40
etoewsdevs **will** abuse it16:40
cdentetoews++16:41
*** egallen has quit IRC16:41
etoewsit's natural that 500s happen from time to time because bugs but let's not encourage their use16:41
elmikoetoews: +116:41
*** ivar-lazzaro has joined #openstack-meeting-316:41
*** ivar-lazzaro has quit IRC16:41
*** ivar-lazzaro has joined #openstack-meeting-316:42
elmikoi'm gonna make the change etoews suggested, but then could we continue the argument on the review?16:42
cdentelmiko++16:42
miguelgrinbergyep16:42
etoewselmiko: good point.16:42
elmiko(i'm slightly confused about how to improve the language in the guideline)16:42
elmikothanks everybody!16:42
stevelledo we need a recommendation that says "fix your bugs?" :)16:43
miguelgrinbergI prefer "do not write bugs in your app"16:43
* cdent sighs16:43
elmikolol16:43
elmikostevelle: that should be the only guideline ;)16:43
etoewsyep. just add that guideline and our work here is done.16:44
stevellegreat, we adjourn for lemonade then?16:44
etoewsa spot of tea16:44
ryansbnow that you finished all the guidelines, sure16:44
etoews#topic freezing16:45
*** openstack changes topic to "freezing (Meeting topic: api wg)"16:45
etoewslots of guidelines ready for freeze16:45
etoewsthe list on the agenda isn't even complete.16:45
elmiko\o/16:45
etoewsi've been adding CPL reviewers with this script. https://review.openstack.org/#/c/193753/1/tools/add-reviewers.py16:46
*** galstrom is now known as galstrom_zzz16:46
etoewsSalvatore Orlando had a question about doing this with a gerrit group instead16:47
*** SumitNaiksatam has quit IRC16:47
etoewsiirc i think someone explored that16:47
etoewsbut i may not recall correctly16:47
etoewsdoes that ring any bells for anyone?16:47
cdenthow easy is it to manage those groups16:47
etoewsi think you need gerrit admin so not easy at all16:48
ryansbprobably harder than updating a json file16:48
etoewsmy thoughts too16:48
cdentthus my question16:48
etoewsalright. i think i'll just go forward with the script then.16:49
*** SumitNaiksatam has joined #openstack-meeting-316:49
ryansb+116:49
etoewselmiko: anything you want to discuss on re-review?16:49
*** mpavlase has quit IRC16:50
elmikonot specifically, just that we need to be dilligent about getting those back out the door =)16:50
etoews++16:50
elmikothey have been sitting for awhile after being reviewed by the larger openstack group16:50
etoews#topic APIImpact16:50
*** openstack changes topic to "APIImpact (Meeting topic: api wg)"16:50
etoews#link https://review.openstack.org/#/q/status:open+AND+(message:ApiImpact+OR+message:APIImpact),n,z16:50
etoewswhat's going on here? #link https://review.openstack.org/#/c/147738/16:52
cdentthat's a rather interesting sample url16:53
ryansbThere's #link https://review.openstack.org/#/c/188364/7 that's about adding an API for describing supported heat functions16:53
* cdent needs to eke out more time for this aspect of the work16:53
*** egallen has joined #openstack-meeting-316:53
etoewscdent: looks nothing like we have in http://specs.openstack.org/openstack/api-wg/guidelines/pagination_filter_sort.html#filtering16:53
*** ivar-lazzaro has quit IRC16:54
cdentindeed16:54
*** banix has joined #openstack-meeting-316:54
*** mestery has quit IRC16:55
elmikoits an interesting use though, how would we recommend specifying something like the glance metadata as filter options?16:55
*** kfox1111 has joined #openstack-meeting-316:55
ryansb4 minute warning16:56
cdentI'm not sure if we want to use ceilometer as an exemplar but the way it tends to refer to metadata keys is metdata.<some key>16:56
cdentand things of that ilk16:56
cdentso using '.' as a descent indicator16:56
elmikoah, so in this case, /volumes/details?glance_metadata.image_name=xxx ?16:57
cdentyeah, but then you've got problems with things named image.name16:57
elmikoright16:57
cdentso it just moves the worms around16:57
elmikointeresting question though16:57
etoewswell comment on the review if you have time/energy.17:00
*** mfedosin has quit IRC17:00
etoews#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Thu Jul  2 17:00:40 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-07-02-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-07-02-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2015/api_wg.2015-07-02-16.00.log.html17:00
etoewsthanks all!17:00
ryansbThanks!17:00
docaedo#startmeeting app-catalog17:01
openstackMeeting started Thu Jul  2 17:01:05 2015 UTC and is due to finish in 60 minutes.  The chair is docaedo. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
elmikothanks etoews17:01
*** openstack changes topic to " (Meeting topic: app-catalog)"17:01
openstackThe meeting name has been set to 'app_catalog'17:01
docaedo#topic rollcall17:01
*** openstack changes topic to "rollcall (Meeting topic: app-catalog)"17:01
*** cdent has left #openstack-meeting-317:01
*** mickeys has quit IRC17:01
docaedoWho do we have here today? Might be a quicker meeting :)17:01
sgordon>.>17:01
*** stevelle has left #openstack-meeting-317:01
kfox1111o/17:02
*** mickeys has joined #openstack-meeting-317:02
docaedook, well .. here we go!17:02
docaedo#topic Single YAML file switch status update (docaedo)17:02
*** openstack changes topic to "Single YAML file switch status update (docaedo) (Meeting topic: app-catalog)"17:02
docaedoI've been taking a little time off so haven't been able to focus on this much but I think I should be able to sort it out and get at least a WIP checked in today.17:02
docaedoMy plan is to just add a new field "asset_type", and adjust the schema to have all the fields and only require the ones that are common across current assets.17:03
*** beagles is now known as beagles_brb17:03
docaedoWe can easily adjust from there, but will appreciate feedback or thoughts on how to approach this if you have any.17:03
*** elmiko has left #openstack-meeting-317:03
docaedoThe intention here is to make it easier to support new/unknown asset types. Once this is merged then we can work on a new layout for the site that can show new asset types as they are added to the yaml17:04
kfox1111+1.17:04
docaedoI added the work items I think we need to do this here: https://blueprints.launchpad.net/app-catalog/+spec/expand-asset-types17:04
kfox1111it would be nice to copy some of the new attributes from glance too. like license.17:04
docaedowould appreciate any addition steps or considerations17:04
*** s3wong has joined #openstack-meeting-317:05
docaedokfox1111: sure17:05
kfox1111the work items looks good.17:05
*** singlethink has joined #openstack-meeting-317:05
docaedoThanks :)  Anything else on this topic? Pretty straightforward stuff I guess...17:06
*** carl_baldwin has quit IRC17:06
docaedo#topic Horizon panel status update (kfox1111)17:07
*** openstack changes topic to "Horizon panel status update (kfox1111) (Meeting topic: app-catalog)"17:07
kfox1111haven't gotten a chance to do anything else since last week.17:07
*** banix has quit IRC17:07
docaedono prob - would it be worth starting a ML thread to get input from anyone else on the topic?17:08
*** mattgriffin has quit IRC17:08
*** sankarshan is now known as sankarshan_away17:08
*** singleth_ has quit IRC17:08
kfox1111possibly? some folks last meeting said they were going to play around with it and maybe extend it for glance/murano. Maybe we wait a bit and see what falls out from that.17:09
*** mattgriffin has joined #openstack-meeting-317:09
kfox1111one topic related to the ui that may need discussing...17:09
docaedosounds good to me (waiting a bit to see if there's anything coming from others)17:09
kfox1111the app catalog is somewhat disjoint from any cloud release.17:09
*** puranamr has joined #openstack-meeting-317:10
docaedowhat's the UI topic?17:10
kfox1111since it is continuously updated, while the cloud itself is probably older then the current release.17:10
docaedo"it" in this case being the app catalog?17:10
kfox1111so we could have two options. 1, we release plugins for given releases and have to maintain backwards compatability.17:11
kfox1111yes.17:11
kfox1111or b, the horizon code includes javascript/templates/etc directly from apps.catalog.org allowing it to be upgraded outside of a cloud's upgrade cycle.17:11
*** e0ne has quit IRC17:11
docaedoI think most will lean towards option 1 - I know people get jumpy about pulling in even JS externally17:12
kfox1111I'm kind of afraid with as much changes that will happen as quickly as they will happen once we start adding advanced features like faceting, or changing the yaml to json and do one template,17:12
kfox1111that the option 1 will break frequently or we have to depricate frequently. :/17:12
kfox1111the other option is somewhere in between. we release a plugin frequenty for all the major cloud versions we support, and like google does,17:13
kfox1111unless the plugins the most recent, it says "notify yoru cloud admin to upgrade"17:13
kfox1111and make it very simple to upgrade.17:13
kfox1111like, seperate the javascript/template from the rest of the plugin, and make it simple to drop in the new files.17:14
docaedoThe way I see it, what we'll get together at this stage will be very much PoC for Horizon. Too late to even land a spec for L release, but possibly have something ready for M17:14
kfox1111the nice thing about plugins is they don't have to land in horizon. they can be seperate.17:14
docaedoThat idea (upgradable plugin) sounds nice, but are there any other horizon components that work that way?17:14
kfox1111I think it will be too much work to target before L, but L should be supportable.17:15
*** stevemar has joined #openstack-meeting-317:15
kfox1111no. but there are no horizon components that are global in nature either.17:15
kfox1111all the rest target the local cloud.17:15
docaedoyeah - this is new territory as far as I can see. I would say plan for plugin, not worry too much about compatability or upgrating ATM, and expect to work closely with Horizon team to solve this17:16
kfox1111if we don't do the upgradable plugin thing, then we have to define our data + api's very carefully since we will have to support them for years.17:16
docaedo+1 for defining the data and APIs carefully17:16
kfox1111I think it will be very hard to do that without a lot more experience though. :/17:16
docaedoYeah - guess this is not exactly easy but should be fun at any rate17:17
kfox1111we're in the v1 age, and what openstack project thinks their v1 apis are still good ideas? :/17:17
kfox1111agreed.17:17
kfox1111if we go down that route, we should maybe make a work item for coming up with a v1 api then.17:17
kfox1111I'm kind of afraid that the api for v1 with just flat files vs llike a v2 with elasticsearch woudl be so vastly different, maintaining v1 after v2 comes along will be next to impossible. :/17:18
docaedoSuggest we focus just on showing how it could work for now, as a horizon plugin with the assumption that the data supplied by JSON won't change much. Then any work integrating glance as a backend will have to be closely tied to the horizon plugin17:18
kfox1111yeah. was planning on doing that anway. just wanted to spark the conversation. cause its something we need to think about for the longer term.17:19
*** stevemar has quit IRC17:19
docaedoagreed - think that conversation will need some input from glance and horizon folk (and we have neither here today as far as I can tell)17:19
docaedospeaking of that...17:20
docaedoativelkov: able to make it today?17:20
*** shwetaap1 has joined #openstack-meeting-317:20
docaedook before we move on - I think we're on the same page re: short term work with horizon, right? I can help get more people engaged on this topic over the next few days too.17:21
docaedo(well, more like, next week :)17:21
kfox1111yup.17:21
*** fitoduarte has joined #openstack-meeting-317:21
kfox1111just setting expectations at this point.17:22
docaedoyep, thank you for that17:22
kfox1111when we make the json available, it will break in the near future when we decide what to do with it.17:22
docaedoyep - though we can include a version in the json itself (clunky but would work), and make the plugin "smart" about what to expect when it pulls in the JSON17:23
kfox1111yes, just worred long term, if we get too many entries, that will just break entirely.17:24
*** shwetaap has quit IRC17:24
docaedovery true and good thing to keep in mind...17:24
kfox1111we will have to put a search api in front and depricate the single file.17:24
docaedodefinitely, but I imagine that will come from glance artifact repository right? If we're going to store stuff there, might as well make use of the features and as I understand it, searching the glance repo is part of the package17:25
kfox1111yeah. if the POC pans out, the glance api becomes the app catalog api.17:26
docaedo+117:26
docaedook moving on I think?17:26
kfox1111yup.17:26
docaedogoing to push this to next week and hope ativelkov can join "Backing catalog with glance POS status update (ativelkov)"17:27
kfox1111k.17:27
docaedo#topic Stale URL checker (gosha)17:27
*** openstack changes topic to "Stale URL checker (gosha) (Meeting topic: app-catalog)"17:27
docaedoThink I'll remind one more time via email on this one, and if there's no response we'll have someone else (me probably) take it on.17:28
docaedoSeems like a relatively easy thing to do, and there's already examples in the system-config repo17:29
docaedoSo next topic (and maybe it'll be very short?)17:29
docaedo#topic Heat template env (kfox1111)17:29
*** openstack changes topic to "Heat template env (kfox1111) (Meeting topic: app-catalog)"17:29
*** SumitNaiksatam has quit IRC17:30
kfox1111was talking with the heat folks, and they believe the environment is somewhat part of the template to be provided by the app developer.17:30
kfox1111so we probably should provide an environment_url in addition to the template_url as an option.17:30
kfox1111And modify the horizon plugin to support that too.17:30
docaedowould environment_url be different than the horizon URL? what would it contain?17:31
docaedo(i.e. meant to say "this template only works in rackspace", or "this template only works in HP public cloud"17:32
kfox1111long term, the env_url will contain all the options for making it specific to various clouds, and the heat engine will present the appropriate ui to the user to customize.17:33
kfox1111so the env would have both nova-network and neutron support and the heat ui would provide the choice, for example.17:34
docaedointeresting - I thought that was sort of handled by requirements already, but that expects the user to make sense of them and know what's offered by their provider...17:34
kfox1111longer term, I'm pushing for them to make that more automagic in some cases. but baby steps.17:34
kfox1111yeah.17:34
docaedoyep - well I agree should be some magic there, in theory a template should "just work" :)17:35
kfox1111heat now has some cloud introspection capabilities itself.17:35
kfox1111yeah. so we talked, and the plan is to do it in heat, rather then try and do a bunch of logic in the app catalog ui.17:35
docaedo+10 for that, app catalog should never try to resolve cross-cloud compatability issues IMO17:36
kfox1111so we just provide the env file and template file to the heat ui, and they do the rest.17:36
docaedothat approach makes sense to me17:36
kfox1111I think we're going to still need to do some amount of that, just from the stand point of, if a template's known never to work on an older cloud for example, why bother the user with the option at all?17:37
kfox1111same with glance images. don't present hyperv images if the cloud doesn't have hyperv support at all.17:37
kfox1111a much easier filtering though.17:37
docaedoI would argue that it's on the user to figure that out - yes, through a filter17:38
*** mzawadzki_mirant has quit IRC17:38
docaedoi.e. uncheck hyper-v images, uncheck vmware images, etc.17:38
docaedoso app catalog should not try to discover what a user can use (i.e. do not try to detect if murano is installed somehow)17:38
kfox1111google does it with their store. if the phone isn't new enough for the apk, it just doesn't even show it to them.17:38
kfox1111its a better user experience.17:39
kfox1111it probably shouldn't detect it, but it might be something the operator is allowed to configure.17:39
docaedoI see the UX advantage there for sure, but what a can of worms that becomes the further down the stack you try to walk17:39
docaedo+1 on allowing operator to limit what is shown in horizon UI17:40
*** beagles_brb is now known as beagles17:40
*** absubram has joined #openstack-meeting-317:40
kfox1111k.17:41
*** zz_natorious is now known as natorious17:41
*** carl_baldwin has joined #openstack-meeting-317:41
docaedoready for our last big exciting topic?17:41
*** natorious is now known as zz_natorious17:42
docaedo#topic Open discussion17:42
*** openstack changes topic to "Open discussion (Meeting topic: app-catalog)"17:42
docaedosgordon: did you have anything you wanted to cover?17:42
*** galstrom_zzz is now known as galstrom17:43
docaedokfox1111: anything from your side?17:43
kfox1111nothing else at the moment.17:44
docaedoOK looks like we get 15 minutes back :)17:44
kfox1111awesome. :)17:44
docaedoThanks - looking forward to continuing the conversation on #openstack-app-catalog17:44
kfox1111have a great weekend. :)17:45
docaedoyou too!17:45
docaedo#endmeeting17:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:45
openstackMeeting ended Thu Jul  2 17:45:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-07-02-17.01.html17:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-07-02-17.01.txt17:45
openstackLog:            http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-07-02-17.01.log.html17:45
*** Yi has joined #openstack-meeting-317:45
*** kfox1111 has left #openstack-meeting-317:45
*** mwagner_lap has joined #openstack-meeting-317:47
*** yamamoto has quit IRC17:49
*** carl_baldwin has quit IRC17:49
*** nbouthors has joined #openstack-meeting-317:49
*** carl_baldwin has joined #openstack-meeting-317:51
*** carl_baldwin has quit IRC17:51
*** carl_baldwin has joined #openstack-meeting-317:52
*** mpavlase has joined #openstack-meeting-317:54
*** absubram has quit IRC17:55
*** banix has joined #openstack-meeting-318:07
*** amotoki_ has quit IRC18:09
*** kebray has quit IRC18:11
*** puranamr has quit IRC18:12
*** puranamr has joined #openstack-meeting-318:13
*** absubram has joined #openstack-meeting-318:15
*** Yi has quit IRC18:25
*** rushiagr is now known as rushiagr_away18:26
*** banix has quit IRC18:29
*** neelashah has quit IRC18:31
*** stevemar has joined #openstack-meeting-318:31
*** neelashah has joined #openstack-meeting-318:32
*** puranamr_ has joined #openstack-meeting-318:33
*** zhenguo has quit IRC18:33
*** ryansb has left #openstack-meeting-318:33
*** wuhg has quit IRC18:34
*** stevemar has quit IRC18:34
*** puranamr has quit IRC18:37
*** yamahata has quit IRC18:38
*** mickeys has quit IRC18:39
*** shwetaap1 has quit IRC18:43
*** Longgeek has quit IRC18:43
*** Longgeek has joined #openstack-meeting-318:43
*** e0ne has joined #openstack-meeting-318:46
*** julim has quit IRC18:47
*** stevemar has joined #openstack-meeting-318:48
*** Sukhdev has joined #openstack-meeting-318:48
*** yamamoto has joined #openstack-meeting-318:49
*** shwetaap has joined #openstack-meeting-318:50
*** kebray has joined #openstack-meeting-318:52
*** huichun has quit IRC18:53
*** kebray has quit IRC18:53
*** kebray has joined #openstack-meeting-318:54
*** yamamoto has quit IRC18:54
*** Longgeek has quit IRC18:54
*** SumitNaiksatam has joined #openstack-meeting-318:58
*** sdake_ has joined #openstack-meeting-318:58
*** sdake has quit IRC19:00
*** egallen has quit IRC19:01
*** sdake has joined #openstack-meeting-319:01
*** absubram has quit IRC19:01
*** Longgeek has joined #openstack-meeting-319:02
*** jtomasek has joined #openstack-meeting-319:02
*** sdake_ has quit IRC19:04
*** stevemar has quit IRC19:05
*** safchain has quit IRC19:08
*** mrmartin has joined #openstack-meeting-319:09
*** beagles is now known as beagles_biab19:09
*** Longgeek has quit IRC19:14
mattgriffinmegm_, ping19:17
*** john-davidge has quit IRC19:17
*** hdd has quit IRC19:23
*** puranamr_ has quit IRC19:25
*** kozhukalov_ has quit IRC19:27
*** puranamr has joined #openstack-meeting-319:32
*** kebray has quit IRC19:33
*** Yi has joined #openstack-meeting-319:37
*** Yi_ has joined #openstack-meeting-319:38
*** Yi has quit IRC19:42
*** jtomasek has quit IRC19:44
*** yamahata has joined #openstack-meeting-319:48
*** DericHorn-HP has quit IRC19:53
*** e0ne has quit IRC19:55
megm_Anyone here to discuss he HA Guide?20:02
*** egallen has joined #openstack-meeting-320:02
megm_Hi, egallen.  Are you here for the HA Guide meeting?20:03
egallenNo20:03
megm_Ah, too bad.  But have a nice day.20:03
*** stevemar has joined #openstack-meeting-320:05
megm_Hi, stevemar.  Are you here for the HA Guide meeting?20:06
*** stevemar has quit IRC20:09
*** Longgeek has joined #openstack-meeting-320:14
*** e0ne has joined #openstack-meeting-320:15
*** jrist has quit IRC20:20
*** Yi_ has quit IRC20:22
*** baoli has quit IRC20:23
*** singleth_ has joined #openstack-meeting-320:25
*** singlethink has quit IRC20:29
*** puranamr has quit IRC20:31
*** beagles_biab is now known as beagles20:35
*** reed has quit IRC20:37
*** reed_ is now known as reed20:37
*** reed has quit IRC20:38
*** reed has joined #openstack-meeting-320:38
*** reed_ has joined #openstack-meeting-320:38
*** puranamr has joined #openstack-meeting-320:38
*** mattgriffin has quit IRC20:43
*** mickeys has joined #openstack-meeting-320:43
*** Yi has joined #openstack-meeting-320:44
*** mattgriffin has joined #openstack-meeting-320:44
*** Sukhdev has quit IRC20:48
*** Sukhdev has joined #openstack-meeting-320:56
*** DericHorn-HP has joined #openstack-meeting-320:56
*** mickeys has quit IRC21:00
*** mickeys has joined #openstack-meeting-321:00
*** stevemar has joined #openstack-meeting-321:07
*** Rockyg has joined #openstack-meeting-321:08
*** DericHorn-HP has quit IRC21:08
*** stevemar has quit IRC21:09
*** neelashah has quit IRC21:10
*** Longgeek has quit IRC21:20
*** e0ne has quit IRC21:20
*** carl_baldwin has quit IRC21:25
*** carl_baldwin has joined #openstack-meeting-321:29
*** Rockyg has quit IRC21:31
*** DericHorn-HP has joined #openstack-meeting-321:33
*** jrist has joined #openstack-meeting-321:38
*** egallen has quit IRC21:38
*** egallen has joined #openstack-meeting-321:39
*** sambetts has quit IRC21:39
*** DericHorn-HP has quit IRC21:40
*** kebray has joined #openstack-meeting-321:41
*** kebray has quit IRC21:42
*** sambetts has joined #openstack-meeting-321:42
*** kebray has joined #openstack-meeting-321:46
*** egallen has quit IRC21:47
*** puranamr has quit IRC21:47
*** puranamr has joined #openstack-meeting-321:50
*** Piet has quit IRC21:53
*** egallen has joined #openstack-meeting-321:53
*** mattgriffin has quit IRC22:02
*** mickeys has quit IRC22:03
*** mickeys has joined #openstack-meeting-322:04
*** kebray has quit IRC22:06
*** devanand_ has joined #openstack-meeting-322:06
*** mrmartin has quit IRC22:08
*** sridhar_ram has joined #openstack-meeting-322:08
*** singlethink has joined #openstack-meeting-322:09
*** singleth_ has quit IRC22:12
*** vnod has joined #openstack-meeting-322:14
*** puranamr_ has joined #openstack-meeting-322:16
*** Longgeek has joined #openstack-meeting-322:17
*** puranamr has quit IRC22:19
*** puranamr has joined #openstack-meeting-322:21
*** sdake has quit IRC22:22
*** sdake has joined #openstack-meeting-322:22
*** kebray has joined #openstack-meeting-322:22
*** DericHorn-HP has joined #openstack-meeting-322:24
*** puranamr_ has quit IRC22:24
*** Longgeek has quit IRC22:25
*** Yi has quit IRC22:27
*** puranamr has quit IRC22:28
*** puranamr has joined #openstack-meeting-322:28
*** sambetts has quit IRC22:29
*** sambetts has joined #openstack-meeting-322:29
*** puranamr_ has joined #openstack-meeting-322:30
*** puranamr has quit IRC22:33
*** peristeri has quit IRC22:33
*** puranamr_ has quit IRC22:35
*** puranamr has joined #openstack-meeting-322:35
*** briancurtin has quit IRC22:36
*** shwetaap has quit IRC22:37
*** DericHorn-HP has quit IRC22:37
*** puranamr_ has joined #openstack-meeting-322:38
*** puranamr has quit IRC22:39
*** briancurtin has joined #openstack-meeting-322:39
*** puranamr has joined #openstack-meeting-322:40
*** galstrom is now known as galstrom_zzz22:40
*** egallen has quit IRC22:40
*** amit213 has quit IRC22:42
*** puranamr_ has quit IRC22:42
*** sdake has quit IRC22:43
*** elmiko__ has quit IRC22:43
*** sdake has joined #openstack-meeting-322:44
*** sdake has quit IRC22:46
*** puranamr has quit IRC22:48
*** puranamr has joined #openstack-meeting-322:48
*** sdake has joined #openstack-meeting-322:50
*** sdake has quit IRC22:51
*** Sukhdev has quit IRC22:56
*** singlethink has quit IRC22:56
*** puranamr_ has joined #openstack-meeting-322:59
*** sridhar_ram has quit IRC23:00
*** rharwood has quit IRC23:01
*** ajo has quit IRC23:02
*** egallen has joined #openstack-meeting-323:02
*** puranamr has quit IRC23:03
*** rharwood has joined #openstack-meeting-323:04
*** puranam__ has joined #openstack-meeting-323:04
*** ajo has joined #openstack-meeting-323:05
*** puranamr_ has quit IRC23:07
*** puranam__ has quit IRC23:09
*** puranamr has joined #openstack-meeting-323:10
*** puranamr has quit IRC23:11
*** puranamr has joined #openstack-meeting-323:14
*** puranamr has quit IRC23:14
*** puranamr has joined #openstack-meeting-323:15
*** kebray has quit IRC23:15
*** puranamr_ has joined #openstack-meeting-323:16
*** radek_ has quit IRC23:17
*** puranam__ has joined #openstack-meeting-323:18
*** puranamr_ has quit IRC23:18
*** puranamr has quit IRC23:19
*** yamamoto has joined #openstack-meeting-323:24
*** Sukhdev has joined #openstack-meeting-323:27
*** mpavlase has quit IRC23:28
*** alexpilotti has joined #openstack-meeting-323:32
*** sdake has joined #openstack-meeting-323:37
*** alexpilotti has quit IRC23:38
*** carl_baldwin has quit IRC23:40
*** alexpilotti has joined #openstack-meeting-323:44
*** Swami_ has joined #openstack-meeting-323:46
*** alexpilotti has quit IRC23:46
*** yamamoto has quit IRC23:47
*** zhenguo has joined #openstack-meeting-323:48
*** Swami has quit IRC23:49
*** egallen has quit IRC23:49
*** hdd has joined #openstack-meeting-323:54
*** Swami_ has quit IRC23:57
*** hdd has quit IRC23:57
*** hdd has joined #openstack-meeting-323:58

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