Wednesday, 2015-09-16

*** shwetaap has joined #openstack-meeting-300:00
*** kzaitsev_mb has joined #openstack-meeting-300:00
*** shwetaap1 has quit IRC00:03
*** fitoduarte has quit IRC00:08
*** yamamoto has quit IRC00:09
*** Swami has quit IRC00:11
*** kzaitsev_mb has quit IRC00:13
*** SumitNaiksatam has quit IRC00:15
*** jwang_ has joined #openstack-meeting-300:16
*** armax_ has joined #openstack-meeting-300:17
*** devlaps has quit IRC00:18
*** dims_ has quit IRC00:20
*** bapalm_ has joined #openstack-meeting-300:20
*** jwang has quit IRC00:21
*** alanmeadows has quit IRC00:21
*** armax has quit IRC00:21
*** bapalm has quit IRC00:21
*** alanmeadows_ has joined #openstack-meeting-300:21
*** alanmeadows_ has quit IRC00:21
*** alanmeadows_ has joined #openstack-meeting-300:21
*** galstrom_zzz has quit IRC00:21
*** armax_ is now known as armax00:21
*** alanmeadows_ is now known as alanmeadows00:21
*** galstrom_zzz has joined #openstack-meeting-300:22
*** FallenPegasus has quit IRC00:22
*** yamahata has quit IRC00:24
*** bradjones has quit IRC00:25
*** betherly_ has joined #openstack-meeting-300:28
*** xgerman_ has joined #openstack-meeting-300:28
*** persia_ has joined #openstack-meeting-300:29
*** lexholden has joined #openstack-meeting-300:32
*** gabriel-1 has joined #openstack-meeting-300:33
*** JoshNang_ has joined #openstack-meeting-300:34
*** rex_lee_ has joined #openstack-meeting-300:34
*** madhu_ak has quit IRC00:34
*** sweston_ has joined #openstack-meeting-300:35
*** alanmeadows has quit IRC00:35
*** davidmichaelkarr has quit IRC00:35
*** jaypipes has quit IRC00:35
*** JoshNang has quit IRC00:35
*** fnordahl has quit IRC00:35
*** gabriel-bezerra has quit IRC00:35
*** persia has quit IRC00:36
*** sweston has quit IRC00:36
*** xgerman has quit IRC00:36
*** mikal has quit IRC00:36
*** rex_lee has quit IRC00:36
*** betherly has quit IRC00:36
*** betherly_ is now known as betherly00:36
*** JoshNang_ is now known as JoshNang00:36
*** mikal has joined #openstack-meeting-300:36
*** sweston_ is now known as sweston00:37
*** xgerman_ is now known as xgerman00:37
*** lexholden has quit IRC00:37
*** jaypipes has joined #openstack-meeting-300:39
*** shwetaap has quit IRC00:40
*** cloudtrainme has joined #openstack-meeting-300:40
*** davidmichaelkarr has joined #openstack-meeting-300:41
*** banix has joined #openstack-meeting-300:41
*** fnordahl has joined #openstack-meeting-300:42
*** alanmeadows has joined #openstack-meeting-300:42
*** alanmeadows has quit IRC00:42
*** alanmeadows has joined #openstack-meeting-300:42
*** mwagner_lap has joined #openstack-meeting-300:42
*** jckasper has joined #openstack-meeting-300:45
*** salv-orl_ has joined #openstack-meeting-300:53
*** Yingxin1 has quit IRC00:54
*** Yingxin has joined #openstack-meeting-300:54
*** yamamoto has joined #openstack-meeting-300:55
*** salv-orlando has quit IRC00:56
*** salv-orl_ has quit IRC00:57
*** hoangcx has joined #openstack-meeting-300:58
*** DericHorn-HP has joined #openstack-meeting-301:00
*** Yingxin1 has joined #openstack-meeting-301:00
*** Yingxin has quit IRC01:01
*** FallenPegasus has joined #openstack-meeting-301:01
*** banix has quit IRC01:01
*** dims_ has joined #openstack-meeting-301:05
*** yamahata has joined #openstack-meeting-301:08
*** baojg has joined #openstack-meeting-301:15
*** FallenPegasus has quit IRC01:17
*** lazy_prince has joined #openstack-meeting-301:18
*** stevemar has joined #openstack-meeting-301:19
*** stanzgy has joined #openstack-meeting-301:19
*** stanzgy__ has joined #openstack-meeting-301:19
*** baojg has quit IRC01:20
*** geoffarnold is now known as geoffarnoldX01:20
*** shwetaap has joined #openstack-meeting-301:22
*** killer_prince has joined #openstack-meeting-301:27
*** davidmichaelkarr has quit IRC01:27
*** geoffarnoldX is now known as geoffarnold01:28
*** stevemar has quit IRC01:29
*** banix has joined #openstack-meeting-301:29
*** stevemar has joined #openstack-meeting-301:30
*** lazy_prince has quit IRC01:30
*** lazy_prince has joined #openstack-meeting-301:30
*** killer_prince has quit IRC01:31
*** Yingxin has joined #openstack-meeting-301:33
*** dims_ has quit IRC01:34
*** Yingxin1 has quit IRC01:35
*** baoli has joined #openstack-meeting-301:36
*** FallenPegasus has joined #openstack-meeting-301:37
*** baojg has joined #openstack-meeting-301:38
*** sigmavirus24 is now known as sigmavirus24_awa01:43
*** ivar-laz_ has joined #openstack-meeting-301:43
*** ivar-lazzaro has quit IRC01:46
*** sballe has quit IRC01:46
*** ivar-laz_ has quit IRC01:47
*** zhenguo has joined #openstack-meeting-301:50
*** s3wong has quit IRC02:06
*** VW_ has joined #openstack-meeting-302:11
*** armax has quit IRC02:13
*** davidmichaelkarr has joined #openstack-meeting-302:16
*** DericHorn-HP has quit IRC02:17
*** puranamr has joined #openstack-meeting-302:17
*** stevemar_ has joined #openstack-meeting-302:20
*** doug-fish has joined #openstack-meeting-302:26
*** zhenguo has quit IRC02:28
*** baojg has quit IRC02:28
*** alanmeadows has quit IRC02:28
*** stevemar has quit IRC02:28
*** fnordahl has quit IRC02:28
*** baojg has joined #openstack-meeting-302:29
*** geoffarnold is now known as geoffarnoldX02:30
*** zhenguo has joined #openstack-meeting-302:33
*** alanmeadows has joined #openstack-meeting-302:33
*** lazy_prince has quit IRC02:34
*** fnordahl has joined #openstack-meeting-302:34
*** lazy_prince has joined #openstack-meeting-302:34
*** bharathm has joined #openstack-meeting-302:42
*** shwetaap has quit IRC02:43
*** FallenPegasus has quit IRC02:44
*** bharathm has quit IRC02:47
*** banix has quit IRC02:48
*** ivar-lazzaro has joined #openstack-meeting-302:49
*** geoffarnoldX is now known as geoffarnold02:49
*** geoffarnold is now known as geoffarnoldX02:50
*** puranamr has quit IRC02:50
*** shwetaap has joined #openstack-meeting-302:50
*** lazy_prince has quit IRC02:51
*** mickeyspiegel has quit IRC02:54
*** rbak has quit IRC02:59
*** banix has joined #openstack-meeting-302:59
*** rbak has joined #openstack-meeting-302:59
*** DericHorn-HP has joined #openstack-meeting-303:01
*** doug-fish has quit IRC03:07
*** baojg has quit IRC03:07
*** puranamr has joined #openstack-meeting-303:11
*** DericHorn-HP has quit IRC03:12
*** ivar-lazzaro has quit IRC03:14
*** ivar-lazzaro has joined #openstack-meeting-303:14
*** puranamr has quit IRC03:15
*** DericHorn-HP has joined #openstack-meeting-303:15
*** fifieldt has joined #openstack-meeting-303:18
*** ivar-lazzaro has quit IRC03:18
*** VW_ has quit IRC03:22
*** baojg has joined #openstack-meeting-303:22
*** VW_ has joined #openstack-meeting-303:22
*** ivar-lazzaro has joined #openstack-meeting-303:22
*** fitoduarte has joined #openstack-meeting-303:23
*** armax has joined #openstack-meeting-303:23
*** VW_ has quit IRC03:26
*** SumitNaiksatam has joined #openstack-meeting-303:31
*** puranamr has joined #openstack-meeting-303:34
*** tfukushima has joined #openstack-meeting-303:36
*** banix has quit IRC03:37
*** rbak has quit IRC03:41
*** david-lyle has joined #openstack-meeting-303:41
*** rbak has joined #openstack-meeting-303:42
*** ivar-laz_ has joined #openstack-meeting-303:51
*** ivar-laz_ has quit IRC03:51
*** puranamr has quit IRC03:51
*** ivar-laz_ has joined #openstack-meeting-303:52
*** ivar-lazzaro has quit IRC03:54
*** iben has joined #openstack-meeting-303:55
*** amotoki has joined #openstack-meeting-303:56
*** ivar-laz_ has quit IRC03:56
*** DericHorn-HP has quit IRC03:59
*** carl_baldwin has joined #openstack-meeting-303:59
*** Guest79093 has quit IRC04:02
*** Brian has joined #openstack-meeting-304:03
*** Brian is now known as Guest3475604:04
*** ativelkov has quit IRC04:07
*** pkarikh has quit IRC04:08
*** pkarikh has joined #openstack-meeting-304:08
*** ativelkov has joined #openstack-meeting-304:09
*** Guest34756 has quit IRC04:09
*** baoli has quit IRC04:10
*** shwetaap has quit IRC04:11
*** geoffarnoldX is now known as geoffarnold04:14
*** tfukushima has quit IRC04:21
*** DericHorn-HP has joined #openstack-meeting-304:26
*** coolsvap has joined #openstack-meeting-304:28
*** irenab has quit IRC04:30
*** sdake has joined #openstack-meeting-304:33
*** baojg has quit IRC04:33
*** sdake_ has joined #openstack-meeting-304:34
*** kebray has joined #openstack-meeting-304:37
*** stevemar_ has quit IRC04:38
*** sdake has quit IRC04:38
*** kebray has quit IRC04:39
*** baojg has joined #openstack-meeting-304:40
*** DericHorn-HP has quit IRC04:40
*** kebray has joined #openstack-meeting-304:41
*** david-lyle has quit IRC04:42
*** david-lyle has joined #openstack-meeting-304:45
*** fitoduarte has quit IRC04:48
*** carl_baldwin has quit IRC04:49
*** geoffarnold is now known as geoffarnoldX04:54
*** fitoduarte has joined #openstack-meeting-304:55
*** sdake_ has quit IRC04:56
*** mrmartin has joined #openstack-meeting-304:56
*** Brian has joined #openstack-meeting-304:58
*** Brian is now known as Guest2308704:58
*** amit213 has quit IRC04:59
*** sdake has joined #openstack-meeting-304:59
*** amit213 has joined #openstack-meeting-304:59
*** zz_ttrifonov is now known as ttrifonov05:06
*** adduarte has joined #openstack-meeting-305:09
*** sdake_ has joined #openstack-meeting-305:10
*** fitoduarte has quit IRC05:12
*** sdake has quit IRC05:14
*** ttrifonov is now known as zz_ttrifonov05:15
*** tfukushima has joined #openstack-meeting-305:21
*** lazy_prince has joined #openstack-meeting-305:24
*** irenab has joined #openstack-meeting-305:25
*** tfukushima has quit IRC05:26
*** peristeri has joined #openstack-meeting-305:28
*** baojg has quit IRC05:28
*** Sukhdev_ has joined #openstack-meeting-305:33
*** sbalukoff has quit IRC05:38
*** sbalukoff has joined #openstack-meeting-305:40
*** baoli has joined #openstack-meeting-305:41
*** lsmola has joined #openstack-meeting-305:42
*** vgridnev has joined #openstack-meeting-305:45
*** baoli has quit IRC05:46
*** tfukushima has joined #openstack-meeting-305:52
*** tfukushima has quit IRC05:53
*** tfukushima has joined #openstack-meeting-305:53
*** stendulker has joined #openstack-meeting-305:57
*** numans has joined #openstack-meeting-306:15
*** mrunge has joined #openstack-meeting-306:17
*** sankarshan_away has quit IRC06:17
*** sankarshan_away has joined #openstack-meeting-306:19
*** zz_ttrifonov is now known as ttrifonov06:21
*** markvoelker has quit IRC06:25
*** qwebirc93053 has joined #openstack-meeting-306:32
*** bharathm has joined #openstack-meeting-306:34
*** qwebirc93053 has left #openstack-meeting-306:34
*** e0ne has joined #openstack-meeting-306:37
*** stevemar has joined #openstack-meeting-306:38
*** e0ne has quit IRC06:39
*** stevemar has quit IRC06:42
*** sankarshan_away is now known as sankarshan06:42
*** btully has quit IRC06:46
*** vgridnev has quit IRC06:57
*** marios has joined #openstack-meeting-307:01
*** marios has quit IRC07:01
*** marios has joined #openstack-meeting-307:01
*** ihrachys has joined #openstack-meeting-307:03
*** mrunge has quit IRC07:06
*** vgridnev has joined #openstack-meeting-307:11
*** SumitNaiksatam has quit IRC07:11
*** SumitNaiksatam has joined #openstack-meeting-307:12
*** armax has quit IRC07:12
*** ihrachys has quit IRC07:14
*** yamahata has quit IRC07:14
*** matrohon has joined #openstack-meeting-307:16
*** fnordahl has quit IRC07:19
*** marios has quit IRC07:19
*** Guest23087 has quit IRC07:19
*** ativelkov has quit IRC07:19
*** zhenguo has quit IRC07:19
*** alanmeadows has quit IRC07:19
*** hoangcx has quit IRC07:23
*** kebray has quit IRC07:23
*** marios has joined #openstack-meeting-307:24
*** Guest23087 has joined #openstack-meeting-307:24
*** ativelkov has joined #openstack-meeting-307:24
*** zhenguo has joined #openstack-meeting-307:24
*** alanmeadows has joined #openstack-meeting-307:24
*** mrunge has joined #openstack-meeting-307:25
*** fnordahl has joined #openstack-meeting-307:25
*** markvoelker has joined #openstack-meeting-307:26
*** Sukhdev_ has quit IRC07:30
*** markvoelker has quit IRC07:30
*** evgenyf has joined #openstack-meeting-307:31
*** [1]evgenyf has joined #openstack-meeting-307:35
*** evgenyf has quit IRC07:38
*** [1]evgenyf is now known as evgenyf07:38
*** sankarshan is now known as sankarshan_away07:50
*** iben has quit IRC07:58
*** vgridnev has quit IRC07:58
*** JeanBriceCombebi has joined #openstack-meeting-307:59
*** ihrachys has joined #openstack-meeting-308:00
*** safchain has joined #openstack-meeting-308:02
*** e0ne has joined #openstack-meeting-308:03
*** egallen has joined #openstack-meeting-308:09
*** mickeys has joined #openstack-meeting-308:10
*** bryan_att has quit IRC08:10
*** sdake has joined #openstack-meeting-308:11
*** hoangcx has joined #openstack-meeting-308:11
*** sdake_ has quit IRC08:12
*** mickeys has quit IRC08:17
*** e0ne has quit IRC08:24
*** kzaitsev_mb has joined #openstack-meeting-308:31
*** JeanBriceCombebi has quit IRC08:34
*** alexpilotti has joined #openstack-meeting-308:35
*** JeanBriceCombebi has joined #openstack-meeting-308:38
*** e0ne has joined #openstack-meeting-308:46
*** mru- has joined #openstack-meeting-308:47
*** sankarshan_away is now known as sankarshan08:48
*** kbyrne has joined #openstack-meeting-308:53
*** mru- is now known as mrunge_08:58
*** JeanBriceCombebi has quit IRC08:58
*** mrunge_ has quit IRC09:01
*** mrunge_ has joined #openstack-meeting-309:01
*** bmotz__ is now known as bmotz09:02
*** kumar has joined #openstack-meeting-309:05
*** hoangcx has quit IRC09:18
*** yamamoto has quit IRC09:26
*** markvoelker has joined #openstack-meeting-309:26
*** B_Smith has quit IRC09:30
*** sdake has quit IRC09:30
*** kzaitsev_mb has quit IRC09:30
*** markvoelker has quit IRC09:31
*** killer_prince has joined #openstack-meeting-309:33
*** dims_ has joined #openstack-meeting-309:35
*** lazy_prince has quit IRC09:36
*** B_Smith has joined #openstack-meeting-309:37
*** mrunge_ has quit IRC09:38
*** mru_ has joined #openstack-meeting-309:39
*** vgridnev has joined #openstack-meeting-309:39
*** stevemar has joined #openstack-meeting-309:40
*** mru_ has quit IRC09:42
*** mrunge_ has joined #openstack-meeting-309:42
*** stevemar has quit IRC09:44
*** mrunge_ has quit IRC09:44
*** mrunge has quit IRC09:48
*** mrunge_ has joined #openstack-meeting-309:48
*** baojg has joined #openstack-meeting-309:48
*** mrunge_ has quit IRC09:49
*** mrunge_ has joined #openstack-meeting-309:49
*** bharathm has quit IRC09:50
*** sankarshan is now known as sankarshan_away09:51
*** JeanBriceCombebi has joined #openstack-meeting-309:54
*** mrunge_ is now known as mrunge09:55
*** jkraj has joined #openstack-meeting-310:19
*** yamamoto has joined #openstack-meeting-310:26
*** baojg has quit IRC10:30
*** baojg has joined #openstack-meeting-310:31
*** yamamoto has quit IRC10:32
*** JeanBriceCombebi has quit IRC10:32
*** baojg has quit IRC10:35
*** mwagner_lap has quit IRC10:36
*** kzaitsev_mb has joined #openstack-meeting-310:43
*** Guest23087 has quit IRC10:48
*** Brian has joined #openstack-meeting-310:48
*** Brian is now known as Guest3577010:48
*** stanzgy__ has quit IRC10:48
*** stanzgy has quit IRC10:49
*** e0ne has quit IRC10:56
*** b3nt_pin has quit IRC11:01
*** beagles has joined #openstack-meeting-311:02
*** beagles is now known as Guest8682511:02
*** yamamoto has joined #openstack-meeting-311:03
*** yamamoto has quit IRC11:03
*** irenab has quit IRC11:05
*** tsufiev has joined #openstack-meeting-311:06
*** lazy_prince has joined #openstack-meeting-311:13
*** e0ne has joined #openstack-meeting-311:13
*** killer_prince has quit IRC11:16
*** doug-fish has joined #openstack-meeting-311:17
*** pchriste has joined #openstack-meeting-311:19
*** Guest35770 has quit IRC11:19
*** Guest86825 has quit IRC11:23
*** banix has joined #openstack-meeting-311:23
*** beagles__ has joined #openstack-meeting-311:24
*** banix has quit IRC11:27
*** mrmartin has quit IRC11:27
*** markvoelker has joined #openstack-meeting-311:27
*** julim has joined #openstack-meeting-311:28
*** vgridnev has quit IRC11:30
*** markvoelker has quit IRC11:32
*** beagles__ has quit IRC11:33
*** DericHorn-HP has joined #openstack-meeting-311:34
*** vgridnev has joined #openstack-meeting-311:37
*** doug-fish has quit IRC11:41
*** doug-fish has joined #openstack-meeting-311:42
*** lexholden has joined #openstack-meeting-311:43
*** Brian has joined #openstack-meeting-311:44
*** Brian is now known as Guest5264811:44
*** irenab has joined #openstack-meeting-311:45
*** doug-fish has quit IRC11:46
*** doug-fish has joined #openstack-meeting-311:46
*** yuikotakada has quit IRC11:47
*** mrmartin has joined #openstack-meeting-311:49
*** stendulker has quit IRC11:49
*** akrivoka has joined #openstack-meeting-311:51
*** masco_ has joined #openstack-meeting-311:56
*** baoli has joined #openstack-meeting-311:57
*** baoli has quit IRC11:57
*** baoli has joined #openstack-meeting-311:58
*** baoli_ has joined #openstack-meeting-311:59
david-lyle#startmeeting Horizon12:00
openstackMeeting started Wed Sep 16 12:00:34 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: Horizon)"12:00
openstackThe meeting name has been set to 'horizon'12:00
david-lyleanyone around to talk horizon12:01
david-lyle?12:01
doug-fishgood morning12:01
tsufievo/12:01
mrungeo/ good morning12:01
*** cbits has left #openstack-meeting-312:01
*** robcresswell has joined #openstack-meeting-312:02
david-lyleLet's talk Liberty RC-112:02
*** JeanBriceCombebi has joined #openstack-meeting-312:02
david-lyle#topic RC-112:02
*** openstack changes topic to "RC-1 (Meeting topic: Horizon)"12:02
*** baoli has quit IRC12:03
david-lyleTalking to rel-mgmt, it seems we should have the FFEs landed by the end of the week12:03
david-lyleand try to have an RC by the end of next week12:03
david-lyleso that means code for the FFEs need to land quickly and the focus should move to bugs12:04
*** evgenyf has quit IRC12:04
*** yamamoto has joined #openstack-meeting-312:04
david-lyleI need to start paring down the FFE list and bug list to be more tracking of what needs to be in vs what would be nice12:04
david-lyleif fact, I think it would be nice to look at some of the bugs here to make a more informed decision on removing from RC-112:05
robcresswellI've been having a go at that. I think its closer to 25, down from 40+, bug wise. Curvature is ready, shelving is in, and I'm still going over databases bp.12:05
*** jckasper has quit IRC12:05
david-lyle#link https://launchpad.net/horizon/+milestone/liberty-rc112:06
david-lylerobcresswell: ok, thanks12:06
*** rdopiera has joined #openstack-meeting-312:07
david-lylefor FFEs I think images won't make it, the other reasonably should12:07
*** r1chardj0n3s has joined #openstack-meeting-312:07
david-lylenow looking at bugs12:07
r1chardj0n3so/12:07
*** evgenyf has joined #openstack-meeting-312:09
*** yamamoto has quit IRC12:09
robcresswellThere's a few angular related ones which could be bumped from rc1 for sure.12:10
david-lylerobcresswell: ok, sorry reading XSS one12:10
david-lylewill finish comments later12:11
mrungedavid-lyle, masco tried to reproduce the first one xss, but failed12:11
*** ducttape_ has joined #openstack-meeting-312:11
masco_yes12:11
david-lyleyeah that needs further investigation12:12
masco_i tried with the options what the reporter said12:12
david-lyleif it's there, is been there forever12:12
*** markvoelker has joined #openstack-meeting-312:12
*** mrunge_ has joined #openstack-meeting-312:13
masco_he is hesitating to share the file to reproduce the issue :(12:13
david-lyleok, I'll leave it in RC-1 for now, but not sure I will block on it12:13
mrungenevertheless, while looking at container code, there's much room for improvement12:14
tsufiev(Like throwing it away completely)12:14
tsufiev:)12:14
david-lylemrunge: no doubt12:14
mrungehey, it's not sahara code12:14
mrungeI mean sahara dashboard12:15
david-lyleI've suggested containers as a work area to many people, no bites12:15
*** mwagner_lap has joined #openstack-meeting-312:16
mrungeabout: https://bugs.launchpad.net/bugs/149417112:16
openstackLaunchpad bug 1494171 in OpenStack Dashboard (Horizon) "Javascript error: Module 'horizon.auth' is not available!" [High,Confirmed]12:16
mrungeI'fe had another report about this12:16
mrungekfox111 was able to reproduce it12:16
*** beagles has joined #openstack-meeting-312:16
robcresswellYeah, from kfox right? He was asking about it12:16
david-lylesince the second XSS is an indirect vector, I'm moving to next12:17
robcresswellIt was in another package I thought mrunge12:17
mrungerobcresswell, we now have 2 packages reporting the same issue with missing horizon.auth12:17
mrungeone debian, one is mine12:18
ducttape_I have seen the issue too, this collect static stuff etc needs a test case12:18
ducttape_something to automatically flag it12:18
mrungeducttape_, collectstatic was executed12:18
ducttape_I have no doubt, but something to test we have all the js in the correct order and locations12:19
mrungeand the environment was rebuilt before creating the package12:19
mrungebut I agree12:19
mrungewould be great to test js in order etc.12:19
* robcresswell points at tsufiev12:19
ducttape_when I saw it, I was missing some js libraries that were supposed to be autocollected etc.   this is the result of having autocollection, in my experience12:20
tsufievrobcresswell: huh?12:20
robcresswelltsufiev: They were asking for tests :p12:20
ducttape_tsufiev - Rob is signing you up to test all the things ;)12:20
mrungeawesome, thank you robcresswell12:21
tsufievrobcresswell: the issue being discussed would have been caught by i9n tests for sure12:21
mrungeis that due to autocollection feature?12:21
*** beagles has quit IRC12:21
mrungeif yes, can we revert that *feature*?12:21
*** mrunge_ has quit IRC12:22
ducttape_i think it's quite core to having stuff work, as you are seeing right now12:22
tsufievrobcresswell: I think it' s'more likely some unit-tests12:22
ducttape_the other option is having a static html list of js includes12:22
david-lylethe problem with disabling autodiscovery is then we have to specify all js files in plugin, or content loaded as a plugin, which is all12:23
robcresswellWith angular that list would be colossal12:23
ducttape_its a few hundred lines, if I recall12:23
*** lexholden has quit IRC12:23
mrungeyes, and it will be loaded, even if you're not using features12:24
robcresswellducttape_: For a couple of panels...12:24
robcresswellI think one thing this does highlight is a big disconnect between developers and packagers that we need to fix.12:24
ducttape_I think we still need to dig into this, the bug may or may not be autodiscovery12:24
robcresswellducttape_: agreed12:25
mrungeright12:25
david-lyleyes12:25
robcresswellIt would be good to get more info or docs etc on what packagers need us to be aware of12:25
robcresswellpain points etc12:25
mrungerobcresswell, still on my todo list12:25
ducttape_I agree, this is also a side effect of xstatic.... which haunts me when I think about it12:25
tsufievrobcresswell: on the second thought, I don't know whether auto discovery is enabled in i9n tests12:26
mrungeuhm, not sure if this is an issue of xstatic12:26
tsufievMight be not12:26
ducttape_right, let's get it understood first12:26
*** jaypipes has quit IRC12:26
*** jaypipes_ has joined #openstack-meeting-312:26
mrungeI'm seeing myself hacking a something together about packaging12:26
r1chardj0n3sit sounds like we've wandered into xstatic ;)12:26
*** JeanBriceCombebi has quit IRC12:26
robcresswellmrunge: Sure, I know you're busy, wasn't supposed to be calling you out on it :)12:26
r1chardj0n3sand probably shouldn't have12:27
mrungemost probably to be done during the flight to tokyo12:27
ducttape_r1chardj0n3s - we are wandering away.  don't go near there!12:27
david-lyleyes, autodiscovery and xstatic are not related12:27
david-lyleother than the word static12:27
r1chardj0n3sI have a cleanup for xstatic in the works, just getting distracted by doa/tempest/devstack :/12:27
mrunger1chardj0n3s, doa could keep you busy for a longer time12:28
david-lyleany bugs targeting RC-1 <= medium will be removed from the list12:28
david-lylethe d-o-a issue is important because it blocks another release12:28
r1chardj0n3snooo, I just want my simple fix to the model in and a bunch of stuff in horizon is fixed by it and I can move on with my life please pretty please? :)12:28
david-lylewhich we have a minor FFE in around WebSSO and the login fix patch12:29
robcresswellr1chardj0n3s: Which patch?12:29
r1chardj0n3srobcresswell: https://review.openstack.org/#/c/222478/12:29
r1chardj0n3sit ran smack into a devstack change that sdague checked in last week that broke a few gates :/12:30
david-lyleand the webSSO is +A'd but got caught in the gate12:30
david-lyleI'll push to see if we can get that reverted for now12:30
*** nikhil_k has quit IRC12:31
robcresswellr1chardj0n3s: Ah, doa :p12:31
r1chardj0n3srobcresswell: yes, hi :)12:31
* robcresswell pretends he never saw it12:31
r1chardj0n3slol, nice try!12:31
mrungelet's merge doa into horizon12:31
r1chardj0n3sthis meeting is recorded, you know :)12:31
mrungeand then deprecate it12:32
robcresswelldangit12:32
tsufievmrunge: seems reasonable to me as well12:32
robcresswellCan we *please* merge curvature :)12:32
mrunge(the first part, tsufiev)12:32
david-lylerobcresswell: still trying to find time to code review it12:33
doug-fishon curvature - I've missed many of the demos at-scale. Is it working well now?12:33
ducttape_it is, seems pretty ready to go12:33
*** dclain has joined #openstack-meeting-312:33
david-lyledoug-fish: yes has been the consensus12:33
doug-fishcool12:33
tsufievrobcresswell: I'm afraid if we start reading curvature code there will be another couple of weeks to polish it12:34
david-lylethere was a red-herring the past couple of days, but...12:34
robcresswellI'm reluctant to approve it again, because I'm starting to look like I'm forcing it through. IMO its been pretty feature ready for the past 2/3 patchsets, but we keep adding little tweaks to it.12:34
ducttape_if we don't read the code, thats a pretty scary thing too12:34
robcresswellOne would hope code review involves looking at the code...12:35
ducttape_exactly12:35
doug-fishyou mean _all_ of the code?12:35
doug-fish*kidding*12:35
david-lyleok12:35
tsufievducttape_: nope, I meant some tiny refactoring a that I already did while angularizing it12:35
david-lyleso bugs and FFEs are the priority12:35
david-lyletimeline again, FFEs by the end of the week, or moved to M12:36
doug-fishsorry - before we move on - does curvature have/need FFE?12:36
david-lyleand RC hopefully next week12:36
robcresswelldoug-fish: It has FFE12:36
david-lyledoug-fish: has12:36
doug-fishok thx12:36
david-lyle#topic summit planning12:37
*** openstack changes topic to "summit planning (Meeting topic: Horizon)"12:37
*** dclain has quit IRC12:37
david-lyleit's the time where we set up session planning, in the past we've done that on etherpad12:37
david-lylethat's a bit messy12:37
david-lylebut manageable12:38
david-lyleanother option is google forms12:38
*** e0ne has quit IRC12:38
david-lylebut access is no global to that12:38
*** davidsha_ has joined #openstack-meeting-312:38
david-lyleany preferences?12:38
r1chardj0n3sI propose we lock ourselves in a room and don't come out until we have a solid plan for domain-scoped tokens and federation and get past the endless bickering...12:38
ducttape_-112:39
ducttape_there is no hope12:39
r1chardj0n3sof course, we'll all starve12:39
ducttape_I'd go with etherpad12:39
robcresswelletherpad has worked, stick with that I suppose. Bit messy, but seems to function okay.12:39
r1chardj0n3setherpad is fine :)12:39
mrungeas long as we have beer, or shiraz r1chardj0n3s ...12:39
r1chardj0n3scurrently sipping whiskey ;)12:39
tsufiev+1 for etherpad & beer12:40
mrungelet's do an etherpad and try to keep total lines low12:40
david-lyledomain scoped token will go in early post Liberty in d-o-a12:40
ducttape_or a really small font :P12:40
robcresswellHaha I still have this amazing memory of r1chardj0n3s and sqchen having this deep technical discussion, turning me to and saying "did you get all that down?" and I just looked up from my keyboard and groaned.12:40
r1chardj0n3s:D12:40
robcresswellLess hangover on Friday for me this time.12:40
david-lyleok, I will set up an etherpad and post to the mailing list12:40
robcresswellSounds good12:41
mrungethank you david-lyle12:41
david-lyle#action david-lyle create etherpad for session planning email to dev list12:41
amotoki+1 for etherpad. it is important to ensure we  put your name when you put an idea to etherpad12:41
mrunge+1 amotoki12:41
mrungegood suggestion12:41
*** iben has joined #openstack-meeting-312:41
*** ducttape_ has quit IRC12:41
david-lyle#topic PTL elections12:42
*** openstack changes topic to "PTL elections (Meeting topic: Horizon)"12:42
david-lyleSo the nomination season is open. This is the last day to submit your self-nominations. Voting if necessary will be held the next week, IIRC12:43
tsufievdavid-lyle: do we have a choice :)?12:43
david-lyletsufiev: always12:43
mrungevoting will begin tomorrow12:43
david-lylethanks mrunge12:44
david-lyletsufiev: I encourage anyone who thinks they want or can improve on the job being done, or just wanting a change to run12:44
* tsufiev steps back just in case12:45
*** kornicameister has joined #openstack-meeting-312:45
*** pauloewerton has joined #openstack-meeting-312:45
david-lyle#topic Choosing a final replacement name for an 'AVAILABLE_REGIONS' setting12:46
*** openstack changes topic to "Choosing a final replacement name for an 'AVAILABLE_REGIONS' setting (Meeting topic: Horizon)"12:46
*** etoews has quit IRC12:46
david-lyleno author but I'm looking at tsufiev :)12:46
*** wendar has quit IRC12:47
tsufievSo lhcheng suggested to drop AVAILABLE_ prefix because it's excessive12:47
*** wendar has joined #openstack-meeting-312:47
*** dims_ has quit IRC12:47
mrungeshouldn't REGIONS be renamed to something else?12:47
tsufievMeaning that the new setting name is AVAILABLE_REGIONS -> KEYSTONE_ENDPOINTS12:47
*** sbalukoff has quit IRC12:48
mrungeyes!12:48
r1chardj0n3syes, I think I already +1'ed that :)12:48
*** etoews has joined #openstack-meeting-312:48
mrungemake sense to me,12:48
masco_+112:48
*** persia_ has quit IRC12:48
david-lyleok, are we resolved on changing, I propose and indefinite deprecation cycle to accommodate existing installations12:48
mrungedo you have a review handy?12:48
r1chardj0n3sseems fair12:48
doug-fishI think that's fine for the setting -- but is that how we'd label the field in the UI?12:48
mrungeyesm david-lyle12:48
*** sarob has quit IRC12:48
mrungeuhm, do we have it at all in UI?12:49
david-lylemrunge: yes12:49
david-lyletwo places12:49
*** lbragstad has quit IRC12:49
tsufievmrunge: https://review.openstack.org/#/c/222129/12:49
david-lyleone in d-o-a and one optional header in Horizon12:49
*** kornicameister has quit IRC12:49
mrungeI thought we present it, yes, but without a name on it12:49
david-lyleah, trying to remember user visible string12:50
*** DericHorn-HP has quit IRC12:50
*** yamamoto has joined #openstack-meeting-312:50
*** sbalukoff has joined #openstack-meeting-312:50
*** persia has joined #openstack-meeting-312:50
david-lyleRegion12:50
*** bharathm has joined #openstack-meeting-312:51
david-lyle:)12:51
david-lylesuggestions on that change?12:51
tsufievdoug-fish: doesn't federation bp aim to somehow hide keystone ENDPOINTS in user facing UI?12:51
david-lyleCloud?12:51
*** lbragstad has joined #openstack-meeting-312:51
doug-fishtsufiev: maybe ... federated keystones wouldn't have to be explicitly chosen, their regions would just be available12:52
mrungesounds cloudy, but I can not think of a better term12:52
david-lyleI'm good with the new setting name, for the record12:52
david-lyleit's the most accurate, but I'll look for further input12:52
tsufievdoug-fish: so I think we should have consistent UI for both federated and non-federated setups12:52
masco_we can get list of name and give it for voting12:53
doug-fishtsufiev: I'm not sure that will be possible: non-federated setups expose the keystone endpoints before login; federated setups discover the keystone endpoints after login12:53
*** JeanBriceCombebi has joined #openstack-meeting-312:54
*** sarob has joined #openstack-meeting-312:54
doug-fishtsufiev: I suppose some kind of hybrid of this would be possible, but that kind of makes my head hurt.12:54
david-lyleI think that's a discussion for a different time :)12:54
doug-fishagreed.12:54
tsufievdoug-fish: do we mean the same thing here by keystone endpoint?12:55
tsufievdavid-lyle: okay12:55
*** bharathm has quit IRC12:55
david-lyleperhaps Tokyo?12:55
doug-fishindeed12:55
david-lyle#topic Open Discussion12:55
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"12:55
tsufievHave you seen my recent mail about cinder quotas?12:56
*** bryan_att has joined #openstack-meeting-312:56
david-lyletsufiev: I read through it, basically we have a bogus policy choice12:56
david-lyledid cinder implement limits instead?12:57
amotokiinfo: this mail: http://lists.openstack.org/pipermail/openstack-dev/2015-September/074351.html12:57
david-lyleor are we just forcing worse UX on users?12:57
tsufievamotoki: thanks!12:57
*** dims_ has joined #openstack-meeting-312:58
tsufievdavid-lyle: no insight about cinder :(12:58
*** JeanBriceCombebi has quit IRC12:58
robcresswellDid nobody from Cinder reply?12:58
tsufievrobcresswell: not yet12:58
david-lyletsufiev: I don't believe they did, just recalling the nova fun12:59
*** JeanBriceCombebi has joined #openstack-meeting-313:00
amotokiat least we should use a same policy for quota-show among nova, cinder, neutron and other projects.13:00
david-lyleI'll work on some input/feedback from cinder13:01
david-lylewe are out of time13:01
*** jckasper has joined #openstack-meeting-313:01
david-lyleThanks everyone and please focus your reviews on the remaining FFEs and bugs for RC-113:01
david-lyle#endmeeting13:01
robcresswello/13:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:01
openstackMeeting ended Wed Sep 16 13:01:54 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-09-16-12.00.html13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-09-16-12.00.txt13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-09-16-12.00.log.html13:02
masco_bye all13:02
*** shwetaap has joined #openstack-meeting-313:02
r1chardj0n3so/13:02
*** r1chardj0n3s has left #openstack-meeting-313:02
*** pauloewerton has left #openstack-meeting-313:02
*** masco_ has left #openstack-meeting-313:02
*** tsufiev has left #openstack-meeting-313:02
mrungebye13:02
*** DericHorn-HP has joined #openstack-meeting-313:05
*** sarob has quit IRC13:07
*** e0ne has joined #openstack-meeting-313:09
*** jkraj has quit IRC13:10
*** robcresswell has left #openstack-meeting-313:11
*** beagles has joined #openstack-meeting-313:15
*** sarob has joined #openstack-meeting-313:16
*** neelashah has joined #openstack-meeting-313:17
*** shwetaap1 has joined #openstack-meeting-313:19
*** krtaylor has quit IRC13:20
*** shwetaap has quit IRC13:22
*** lblanchard has joined #openstack-meeting-313:25
*** VW_ has joined #openstack-meeting-313:25
*** jmckind has joined #openstack-meeting-313:31
*** salv-orlando has joined #openstack-meeting-313:31
*** VW_ has quit IRC13:32
*** VW_ has joined #openstack-meeting-313:32
*** numans has quit IRC13:35
*** VW_ has quit IRC13:37
*** amotoki has quit IRC13:42
*** zhenguo has quit IRC13:43
*** peristeri has quit IRC13:45
*** DericHorn-HP has quit IRC13:45
*** sigmavirus24_awa is now known as sigmavirus2413:47
*** sigmavirus24 is now known as sigmavirus24_awa13:48
*** ndipanov has joined #openstack-meeting-313:50
*** rbak has quit IRC13:51
*** yamahata has joined #openstack-meeting-313:55
*** tellesnobrega is now known as tellesnobrega_af13:57
ihrachyshey qos folks :)13:58
*** nate_gone is now known as njohnston13:58
ajohi ndipanov , johnthetubaguy , ihrachys , irenab14:00
ajowaiting a couple of minutes to be all in sync14:01
ajoping irenab , she told me se could join late.14:01
*** vladikr has joined #openstack-meeting-314:01
ajohi vladikr  :-)14:01
*** moshele has joined #openstack-meeting-314:01
*** Irenab_ has joined #openstack-meeting-314:01
njohnstono/14:01
moshelehi14:02
ajohi moshele , irenab_ , hi njohnston  :)14:02
ndipanovo/14:02
ihrachys\o/14:02
ajo:)14:02
ajook14:02
ajo#startmeeting neutron_qos14:02
openstackMeeting started Wed Sep 16 14:02:23 2015 UTC and is due to finish in 60 minutes.  The chair is ajo. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
Irenab_Hi14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:02
openstackThe meeting name has been set to 'neutron_qos'14:02
ajoThanks everybody for joining, specially thanks to the nova folks for joining us: ndipanov , vladikr and johnthetubaguy14:02
johnthetubaguyhi all14:03
ajoWe need to make some progress in a couple of topics regarding nova-neutron integration for QoS14:03
ajo#topic nova-neutron integration : flavours?, or how do we do it14:03
*** openstack changes topic to "nova-neutron integration : flavours?, or how do we do it (Meeting topic: neutron_qos)"14:03
*** VW_ has joined #openstack-meeting-314:04
ajoFirst one, we need some way to make sure we can have some sort of association from the type of instance tenant picks to the QoS level he gets,14:04
ajoor something equivalent, I know johnthetubaguy commented something about vif flavours? (could be?) but I'm unaware of what did you mean with that14:04
*** stendulker has joined #openstack-meeting-314:04
ajois that something gestating on the nova side?14:04
ihrachyswe may need it for stuff outside qos btw, like jumbo14:05
johnthetubaguyno, I was thinking on the neutron side14:05
johnthetubaguyreally, I am thinking about volumes14:05
johnthetubaguywith volumes you have your SSD vs spinning disk volumes14:05
johnthetubaguyand they have have different QoS setup14:05
johnthetubaguyand you pick what happens by selecting a volume type owned by cinder14:05
johnthetubaguyI have always liked the idea of something similar in Neutron14:06
ajojohnthetubaguy, ack, may be we could setup something like port flavors speciying the level of Qos + the type of nic, for example, and nova could reference that from it's own flavors in a key?14:06
johnthetubaguyideally no14:06
ajoQoS policies are quite like flavors, but, dont' specify the type of nic, for example14:06
johnthetubaguyusers are meant to create ports, then pass them into nova14:06
johnthetubaguywhen they create the port, they need to set QoS14:06
*** Irenab_ has quit IRC14:06
ajojohnthetubaguy, doesn't nova create the ports now?14:06
ajoI mean, you can specify a port id, but you can specify the network14:07
johnthetubaguyajo: in the happy case, it does not14:07
johnthetubaguywe have some code we want to deprecate that can create ports for you, mostly for backwards compatiblitiy14:07
johnthetubaguynow thats an extreme view of the world14:07
ajojohnthetubaguy, unless we enforce nova not to be able to do that, it's out of our control a bit, or nova may need to receive the "flavor" of port it will create14:07
ajonet-id=xxxx,port-flavor=xxxx (or qos-policy=xxxxx)14:07
johnthetubaguybut in theory, we build for that world, then add any sugar that you need to make that true14:07
ihrachysjohnthetubaguy: so basically you suggest to have no integration, and allow users to assign QoS policies to ports prior to passing them to nova, basically smth that we already have14:08
johnthetubaguyNova would just use a default port flavor, I would assume14:08
johnthetubaguyihrachys: so if that works already today, thats interesting14:08
*** rbak has joined #openstack-meeting-314:08
ajoihrachys, in that case, we miss a way in QoS to enforce default policies to ports per tenant (via Role based access control, I guess)14:08
ajowe need that anyway14:08
ajojohnthetubaguy, or have one per tenant,14:09
ihrachysajo: it can be similar to default sec groups14:09
ajook, at worst, we could just pass the policy id / or flavor, along with the net-id to nova, if that works...14:09
*** JeanBriceCombebi has quit IRC14:09
ajoor we don't , encouraging the people to create the port first14:09
johnthetubaguywell ideally neutron knows about the default volume type, and just deals with it when we don't specify one14:09
ihrachysajo: I actually think that preparing port for nova is the ideal situation, but some people complain about complexity behind neutron flow14:09
ajojohnthetubaguy, ok, I guess that makes sense,14:10
johnthetubaguybut if you want something other than the default, yeah, I would prefere them to create things up front really14:10
ndipanovand when you do need to specify? you need to create a port first?14:10
ihrachysnot sure adding required explicit port allocation step will help14:10
ajondipanov, yes, that's what johnthetubaguy means14:10
*** JeanBriceCombebi has joined #openstack-meeting-314:10
ajoand I agree with ihrachys, we grow complexity of the user, but...14:10
ajoonly if they want to move to a non-default policy14:10
ihrachysthat said, I believe all complexity concerns should be hidden on client layer, not API14:11
*** sigmavirus24_awa is now known as sigmavirus2414:11
johnthetubaguyso if you want to do security groups, today, you create your ports upfront, else crazy things happen, as I understand it14:11
ihrachysand if we can live with decoupled nova and neutron, then I am good to stay lazy14:11
johnthetubaguyso I don't see any change here with qos14:11
ajodecoupling is better14:11
johnthetubaguyso my thing is more, we assume decoupled14:11
ihrachysthen why do you suggest integration in the first place? :)14:11
ajomay be we need a third project to provide "flavors" ;)14:12
ajosince an instance is comprised by volume, net, compute, etc...14:12
moshelemaybe it should be part of the openstack client project14:12
ajo;)14:12
* ajo adds more complexity ;D14:12
johnthetubaguyajo: so thats how glance started, but lets not go there14:12
*** julim has quit IRC14:12
ajojohnthetubaguy, I'm partly joking, but worried about usability14:12
johnthetubaguyso the idea, originally was that heat would know about ports and servers, and help tie those together, its not really turned out that way14:13
ajojohnthetubaguy, may be it's, as ihar said, something to be left to the client (horizon, cmdline..)14:13
johnthetubaguyso here is the thing...14:13
johnthetubaguymy view is that we should make it work with creating ports up front14:13
ihrachysyeah, heat did not prove itself successful :(14:13
johnthetubaguyif we need something else, then maybe, but that comes second14:13
johnthetubaguyihrachys: not sure, I think its doing some good stuff, just not really that14:13
ihrachysjohnthetubaguy: with ports prepared, it works now14:14
ajojohnthetubaguy, that has to be assumed, it's on our agenda for M14:14
*** gsagie has joined #openstack-meeting-314:14
ihrachysjohnthetubaguy: re heat - more about expectations of universal adoption14:14
ajojohnthetubaguy, but we're looking for the plan forward in coordination with nova. Will that work for users, do they need something more?14:14
johnthetubaguyihrachys: but it sounds like its two granular, and there are no flavors, quotas and policy?14:14
johnthetubaguyihrachys: ah, thats fair14:15
ihrachysjohnthetubaguy: there are qos policies that are attachable to ports14:15
johnthetubaguyihrachys: OK, so maybe we are there then14:15
johnthetubaguyso what happens by default if I don't set any QoS policy?14:15
ihrachysjohnthetubaguy: if you mean neutron should have a global flavor that would be superset of qos policies and something else, then yes, it's not there14:15
johnthetubaguyits just open?14:15
ajojohnthetubaguy, we're only missing: when you create a port, what's the default policy for a given tenant14:15
ihrachysjohnthetubaguy: if no policy is set, no policy is applied14:15
ajoor.. a flavor if we make a superset containing more details about ports14:16
ajo(vnic type, qos policy, etc..)14:16
ihrachysjohnthetubaguy: there is no modifiable default policy14:16
johnthetubaguyright, well, surely it might be per network? in the provider network case?14:16
johnthetubaguyI think we should consider how default policies work when you create your ports before starting your VM, basically14:16
ihrachyswe can attach policies to networks already14:16
ihrachysand ports inherit it14:16
ajotrue14:17
johnthetubaguyihrachys: cool, so maybe what we need is a default policy that gets attached to user created networks?14:17
ihrachysI will also side note that neutron still does not have modifiable sec groups14:17
johnthetubaguyalthough that sounds a little useless14:17
*** tellesnobrega_af is now known as tellesnobrega14:17
*** lazy_prince has quit IRC14:17
ihrachysso here, we are consistent in not supporting it :)14:17
ajook14:17
ajohere we have two points of view14:17
ajo1) all left to port creation and neutron control14:17
ajo   and so controlled by the client (in regards of flavor relations if user wants that)14:18
ajo2) the port flavor/qos_policy key to flavors, so nova can tell neutron14:18
johnthetubaguybut for 1) you do have nice controlled defaults, which should just work when nova creates the ports right?14:18
johnthetubaguyso here is the problem...14:18
johnthetubaguyyou pick flavor 714:18
johnthetubaguyit says QoS policy A14:19
johnthetubaguybut you pass in your own port with QoS policy B14:19
johnthetubaguynow what does that mean?14:19
*** cloudtrainme has quit IRC14:19
johnthetubaguyleaving this all in Nova really side steps that issue14:19
johnthetubaguyoops14:19
ihrachysthat's an interesting note14:19
johnthetubaguyleaving this all in Neutron side steps that14:19
ajoyes,14:20
ajothat's a fair point, I was just thinking of that14:20
ajoeven if nova changed the QoS, user could move it to a different one if he wanted / had access to it14:20
ajoso may be, quotas, enforcement and defaults should be left to neutron,14:20
ajoand make horizon aware of it14:21
*** akrivoka has left #openstack-meeting-314:21
ajowith some mechanism to be able to specify access & default policies for tenant network / port creation14:21
*** Irenab_ has joined #openstack-meeting-314:21
ajodoes that sound reasonable?14:21
ajoI know irenab_ was rising the this topic of flavours initially, so irenab_ irenab , you may want to read the log later and ping us via mail if you see any concern14:22
*** DericHorn-HP has joined #openstack-meeting-314:22
ihrachysyes, it seems to me no integration is actually needed14:22
Irenab_Sure, will follow up later14:22
ajo+1 johnthetubaguy , thanks for discussing this with us, the feedback has been very valuable14:23
ajoso, let's move on14:23
ajo#topic nova-neutron integration: bandwidth guarantees, and overcommitments...14:23
*** openstack changes topic to "nova-neutron integration: bandwidth guarantees, and overcommitments... (Meeting topic: neutron_qos)"14:23
ajovladikr, ndipanov ^14:23
ajohow do we handle that?14:23
ndipanovwell14:23
ajowe can set a policy that says "guarantee 1Gbps on this port"14:24
ndipanovit's tricky really14:24
*** gsagie has left #openstack-meeting-314:24
ajobut if it's plugged to the wrong compute node, or the wrong PF, it won't work14:24
ajondipanov: nothing is easy lately :)14:24
ndipanovso we are only assuming this when using physical ports (VFs)14:24
vladikrPFs14:25
ajondipanov: our goal is to do it also for virtio ports14:25
vladikrah14:25
*** jruano has joined #openstack-meeting-314:25
ajobut I understand that'd require neutron coordination14:25
ndipanovajo I thought so14:25
Irenab_Are you talking about sriov only?14:25
ajoas neutron knows what's the upstream port/route/tunnel for a network14:25
ajoIrenab_: we may solve both, may be not both at the same time, as requisites and interactions could be different14:25
ndipanovok so the way nova scheduling currently works is the compute host publishes it's data about available resources14:26
*** DericHorn-HP has quit IRC14:26
*** nikhil has joined #openstack-meeting-314:26
ndipanovso available bandwith would have to be published as well14:26
ajondipanov, aha14:26
ajondipanov, and also, be known internally on nova-compute for the PF/VFs relationship14:26
Irenab_So nova will do bw bookkeeping?14:26
ndipanovjohnthetubaguy, similar things keep popping up with cinder (like proximity to volumes etc)14:26
ajomay be you have 20G total in the compute, but 10G is to one PF, 10G is to other PF14:26
ndipanovdo you remember anything about that?14:26
*** B_Smith has quit IRC14:27
ndipanovajo, right but that's a problem of structuring the data14:27
ajondipanov, right, that's just internal to nova-compute14:27
ndipanovwhat I am getting at is that we have no way of letting nova-compute know any of this in the first place right now14:27
*** sdake_ has joined #openstack-meeting-314:27
ajondipanov, what do you mean?, letting it know the available BW ?14:28
johnthetubaguyso what ndipanov, I see it as something our scheduler refactoring efforts are heading towards14:28
ndipanovyeah14:28
*** btully has joined #openstack-meeting-314:28
johnthetubaguyoops, s/what ndipanov/what ndipanov said/14:28
ndipanovjohnthetubaguy, well yes :) eventually14:28
ajook, so we may need to provide something to nova compute to discover the available bandwidth on the PFs, it's a matter of inspecting the link, or... otherwise get it given in config14:29
*** alexpilotti has quit IRC14:29
johnthetubaguyajo: once we add network segments, and I particularly interested in IP address availability, for example, but thats an asside14:29
ajoI suspect for virtio's it's going to be harder14:29
ndipanovajo, but doesn't that get complicated with qos?14:29
ajosince neutron may need to publish that info back to nova somehow14:29
ndipanovajo, currently there is no such an interface at all14:30
ajondipanov, I know14:30
ajondipanov, yes, then we put qos in place, and...14:30
johnthetubaguyyeah, XenAPI has some basic BW reporting stuff, but I wouldn't say its a great pattern to copy for libvirt14:30
ndipanovthere are several ways to think about it14:30
ajondipanov, nova may need to be aware of what the policy says14:30
ajondipanov, or neutron needs to publish the policy to nova in a way nova understands14:30
johnthetubaguythat is more usage focused, rather than scheduling14:30
ajoor just the constrains out of the policy...14:30
*** DericHorn-HP has joined #openstack-meeting-314:30
ndipanovjohnthetubaguy, but it affects it no?14:30
*** tellesnobrega is now known as tellesnobrega_af14:30
johnthetubaguyndipanov: not the way we have things setup at least14:31
*** tellesnobrega_af is now known as tellesnobrega14:31
ndipanovajo, so in an ideal world - (global?) scheduler runs a neutron plugin that neutron agents publish data to, and none of this code lives in nova14:31
ndipanovwe are far away from that world atm14:31
ajondipanov, ok, that sounds like a good ideal14:32
johnthetubaguyndipanov: +1 to both of those comments14:32
*** DericHorn-HP has quit IRC14:32
ajondipanov, so neutron publishes a plugin, via stevedore or whatever... and the scheduler just takes it, and uses it14:32
johnthetubaguyI always like to keep one eye to the future and one to the present, so its worth keeping that all in mind14:32
*** tellesnobrega is now known as tellesnobrega_af14:32
ndipanovyes that would be ideal14:32
ndipanovbut that is blocked by a lot of work that needs to be done to split out the scheduler14:33
ajomay be, it's better to tackle the SR-IOV thing first14:33
ajoas it's the simplest case14:33
ajo"simplest"14:33
ndipanovyes - sr-iov is simpler because it is already handled by nova-compute14:33
*** dclain has joined #openstack-meeting-314:33
ajondipanov, you may only need to be aware of what "min bandwidth constraint" do we have on a certain port14:33
ndipanovas in - the least amount of bandwith we can provide but we may be able to do more?14:34
ajondipanov, isn't sbauza working on those scheduler improvements? or was he?14:34
ndipanovajo, he is but they are not easy with the current constraints nova has14:34
ndipanovand they are not easy in general14:34
ajondipanov: let me re-read your phrase14:35
*** nikhil has quit IRC14:35
ajondipanov: correct14:35
*** nikhil has joined #openstack-meeting-314:35
ndipanovso yeah that would be possible in some fashion for sriov ports but only for them without the scheduler work14:35
ajosaid that, neutron may need to somehow know that other ports on the same PF are min: restricted, and cap a max: on the unrestricted ports <- moshele14:35
ajoIrenab_ ^14:36
ndipanovthere is one more way to do it14:36
ndipanovand johnthetubaguy may disagree14:36
ajondipanov: which one?14:36
* ajo listens :)14:36
ndipanovwe had a notion of an extensible resource tracker, where you would be able to add your own resource plugins to nova14:36
Irenab_ In general i think neutron should be responsible for bookkeeping14:37
*** julim has joined #openstack-meeting-314:37
ajoIrenab_: yes, that's why I like the point of a neutron plugin inside the nova scheduler :)14:37
ndipanovthe idea was interesting but the implementation was lacking because the general code has very loose apis14:37
ndipanovbut there is some work now to make those APIs stable and ... well useful14:37
*** david-lyle has quit IRC14:37
Irenab_+1 on this ajo14:37
ajondipanov, can you link to those APIs?14:37
johnthetubaguyndipanov: I guess the summary of my position is: we need to make progress in the short term, if we agree the longer term plan, I am fine with a bit of compromise in the short term14:37
*** dclain_ has joined #openstack-meeting-314:38
ajojohnthetubaguy: +114:38
ndipanovwell this is a compromise because we'd wait for jaypipes_ 's work14:38
* ndipanov looks for the patches14:38
*** tellesnobrega_af is now known as tellesnobrega14:38
ajothanks ndipanov14:38
ndipanovhttps://review.openstack.org/#/c/12899214:39
ndipanovso this is the first patch14:39
*** rhochmuth has joined #openstack-meeting-314:39
ndipanovthis is still not ideal because nova has to own a lot of code that is basically a neutron implementation detail14:39
ndipanovbut at least it will have a well defined boundary within nova14:39
ajo#link https://review.openstack.org/#/c/12899214:40
ndipanov(I think)14:40
ndipanovjohnthetubaguy, ^14:40
ndipanov?14:40
ndipanovdoes that sound not entirely false to you?14:40
*** dclain has quit IRC14:40
ajoOk, I have 772 LOCs to read :)14:41
Irenab_Same here 😊14:41
ajoor at least ~300 not counting tests :)14:41
ndipanovajo read the related BP instead maybe14:41
* johnthetubaguy looks14:41
ajoyeah, ndipanov , that's a better idea in fact14:42
ajo#link https://blueprints.launchpad.net/nova/+spec/resource-objects14:42
Irenab_Ajo: what about overcommitment ?14:43
ajoIrenab_, that's what we were talking about, preventing it14:43
*** lexholden has joined #openstack-meeting-314:43
johnthetubaguyndipanov: yeah, thats stuff is close now, seems worth following that14:43
ndipanovajo, so that would give you the place to do it in nova that nova folks won't hate14:43
Irenab_I wonder if it always desired to be precented or should ve some provider policy14:44
ndipanovajo, but than we would want to have a unified view for both virt and phys ports14:44
ajondipanov, yes,14:44
ajothat's the longer term plan14:44
ajoirenab_ not sure I follow14:45
ajondipanov: for virt ports, neutron needs to feed data14:45
*** geoffarnoldX is now known as geoffarnold14:45
Irenab_VM can be created and paused, other can be active14:45
ajondipanov, another extra option (on the compute low level side), could be letting neutron decide the exact pci address/based on PF capabilities14:45
ajoand there's where the new os-libvif thing could come in14:46
* ajo looks for the link johnthetubaguy provided him this morning14:46
ajo#link http://lists.openstack.org/pipermail/openstack-dev/2015-June/067783.html14:46
johnthetubaguymaybe, I see the vif lib first making it easier to add support for driver XYZ vif14:47
*** fabiog has joined #openstack-meeting-314:47
ajondipanov, is it possible/reasonable to have some kind of rfe/spec for M in regards of the basic min-bandwidth guarantees/not overcommitment in nova?14:48
ajojohnthetubaguy ^  ?14:49
ajotalking of SR-IOV only14:49
ajonot asking for commitments, just trying to understand where do we stand14:50
ndipanovajo, yes - I actually proposed a session for SR-IOV14:50
*** pasquier-s has joined #openstack-meeting-314:50
ajoah, true, that could be in the same session14:50
ndipanovfor the summit14:50
ndipanovwell maybe - this touches on several more things like scheduling14:50
ajoyeah,14:50
ajomay be needs a separate one, yikes, too bad I can't go this year :/14:51
ajondipanov: I proposed a cross project session for neutron14:51
ndipanovand I am not too keen on sriov bandwith being a different thing than other bandwidth but such is life14:51
ajoregarding this14:51
ndipanovajo, ok cool that makes sense14:51
ajolet me find the link14:52
ajo#link https://etherpad.openstack.org/p/neutron-mitaka-designsummit14:52
ajo4.14:53
Irenab_ndipanov: i agree, it should be general approach to handle different vif types14:53
*** witek has joined #openstack-meeting-314:53
ajoI just removed the "port defaults per tenant / RBAC" part from the etherpad14:54
ajomakes no sense after our discussion and the other proposed solution14:54
ndipanovyeah so it may make sense to be part of the vif lib14:54
ajoIrenab_: ping me back if you believe the agreement we made misses something important when you read the minutes14:54
ndipanovand then nova compute would just call it's reporting method when reporting it's own resources14:55
Irenab_Ajo: will do14:55
*** mroderus has joined #openstack-meeting-314:55
ndipanovbut that seems like it can get arbitrarily complicated ...14:55
ajondipanov, yep14:55
ndipanovanyway - let's conclude - did you get some info to go on ajo ?14:55
ajondipanov, we either add realtime interactions, or reporting so the other side can act quickly14:56
ajondipanov: lots of information to digest14:56
ndipanovok ping me or johnthetubaguy on -nova if something is unclear I guess14:56
ajondipanov, let us digest, and then let's organize more meetings14:56
ndipanovyay meetings!14:56
ajondipanov ':D let's minimize them14:57
*** adduarte has quit IRC14:57
ajondipanov: if we had powerpoints this would be solved already.. (in the powerpoint)14:57
ndipanovI love powerpoints14:57
ajos/powerpoint/presentations/g14:57
Irenab_We can collaborate on etherpad14:57
ndipanov0 bugs reported to date14:57
ajondipanov: lol14:57
ajoIrenab_, what was the etherpad link you proposed initially?14:58
*** dims_ has quit IRC14:58
ajoand let's close the meeting, 2 minutes to go14:58
ajoI guess we can update that etherpad with the conclussions...14:58
*** stevemar has joined #openstack-meeting-314:58
*** carl_baldwin has joined #openstack-meeting-314:58
*** dims_ has joined #openstack-meeting-314:58
*** kebray has joined #openstack-meeting-314:58
Irenab_Will send you once get tocomputer14:58
ajook :)14:59
ajothanks everybody for joining14:59
Irenab_Impossible from phone ....14:59
ajoand providing feedback on the topic14:59
ajo#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Sep 16 14:59:19 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-09-16-14.02.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-09-16-14.02.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-09-16-14.02.log.html14:59
*** tomasztrebski has joined #openstack-meeting-314:59
*** vladikr has left #openstack-meeting-314:59
*** moshele has left #openstack-meeting-314:59
ajoo/14:59
*** smialy has joined #openstack-meeting-315:00
Irenab_ajo: will ping you in 20 mins or so with link to etherpad15:00
rhochmuth#startmeeting monasca15:00
openstackMeeting started Wed Sep 16 15:00:13 2015 UTC and is due to finish in 60 minutes.  The chair is rhochmuth. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: monasca)"15:00
openstackThe meeting name has been set to 'monasca'15:00
rhochmuthroll call15:00
rhochmutho/15:00
mroderuso/15:00
witekhi15:00
fabiogo/15:00
*** ddieterly has joined #openstack-meeting-315:00
rbako/15:01
ddieterlyo/15:01
rhochmuthHere is the agenda that is listed:15:01
rhochmuthAgenda for Wednesday September 16, 2015 (15:00 UTC)15:01
rhochmuth1.Update on Logging Plans15:01
rhochmuth2.Devstack15:01
rhochmuth1.to merge/enable monasca client in Rally we need to have monasca devstack plugin first15:01
rhochmuth3.Grafana update15:01
rhochmuth4.Tempest tests update15:01
*** qwebirc73939 has joined #openstack-meeting-315:01
*** tsv has joined #openstack-meeting-315:01
rhochmuthplease add items to the etherpad at, https://etherpad.openstack.org/p/monasca-team-meeting-agenda15:01
rhochmuth#topic logging15:02
*** openstack changes topic to "logging (Meeting topic: monasca)"15:02
ddieterlyis it just us 3 here today?15:02
rhochmuththere are more15:02
bmotzah, I'm here too15:02
bmotzo/15:02
tomasztrebskihello guys :)15:02
tsv\0/15:02
ddieterlyhi15:02
ddieterlyhands up if you're going to participate in the meeting, please15:02
rhochmutho/15:02
mroderustomasztrebski: could you give a brief update on your Python port of the logging API?15:02
fabiogo.15:03
fabiogI think we have a quorum,15:03
rhochmuthwe do15:03
rhochmuthtomas, the floor is yours15:03
ddieterlygreat15:03
rhochmuthi <3 irc15:03
tomasztrebskibrief update ? hmm...well its on private github, so if anyone would like to take a peek, be my guest and as for the status15:04
*** qwebirc73939 has quit IRC15:04
mroderuscan you post the link?15:04
*** Irenab_ has quit IRC15:04
witekhere it is: https://github.com/kornicameister/monasca-log-api15:04
tomasztrebskilogic is pretty much ready, including kafka publisher, resource to receive logs, some service like stuff to validate requests and so on15:04
tomasztrebskiwhat I dont have is some unit tests (one major for kafka publisher), tox and general polishing15:05
rhochmuthso, this is the python code15:05
rhochmuth?15:05
tomasztrebskiyes, it is python code15:05
tomasztrebskisimilar to monasca-api you make15:05
*** jesseo has joined #openstack-meeting-315:05
tomasztrebskias far as it goes for structure15:05
rhochmuththere is also the monasca-log-api in stackforge at, https://github.com/stackforge/monasca-log-api15:06
rhochmuthwhich is all have at the moment15:06
tomasztrebskiyes, but it is java only15:06
rhochmuthis it possible to add the python to the java repo?15:06
rhochmuththen everything will be under gerrit review15:07
witek#https://github.com/kornicameister/monasca-log-api is a for of stackforge/monasca-log-api15:07
tomasztrebskiI believe it is, https://github.com/stackforge/monasca-api/tree/master/monasca_api, you have something like it in monasca-api15:07
*** banix has joined #openstack-meeting-315:07
*** fabiog has quit IRC15:07
tsvTom, what is the pre-requisite for running the python logging-api ? is it standalone ?15:07
rhochmuthcorrect, the monasca-api has both the java and python code15:07
*** rockyg has joined #openstack-meeting-315:07
*** fabiog has joined #openstack-meeting-315:08
tomasztrebskiso the same thing we have in monasca-log-api, however it is my own fork15:08
rhochmuthis it fully functional?15:08
*** jckasper has quit IRC15:08
*** mickeys has joined #openstack-meeting-315:08
tomasztrebskinothing particular I guess, but I don't know what it would behave on server, I didn't have a chance to check that out15:08
tomasztrebskipretty much, I am still working on some polishing and tests, but I managed to run it locally and post some data into the resource15:09
rhochmuthcool, so it would be really good to get that merged back in the monasca-log-api repo so it is under gerrit review15:10
tsv+115:10
tomasztrebskias for what @tsv asked for, I can only say for dev mode so the only requirement you'd have is to create virtenv install requirements and run server.py15:10
rhochmuththis is an area that gets some scrutiny with the TC15:10
rhochmuthwe had our tempest tests in a separate repo, not merged in with the main tempest repo, and had some feedback to merge that in15:10
tsvsounds good Tom, that sounds straight forward15:10
rhochmuthso, i'm working on getting our tempest tests merged in15:11
rhochmuthtoo15:11
tomasztrebski+115:11
rhochmuthnot to change the subject, just offering additional reasons why this could be important15:11
mroderusok, so shall we merge before you want to have a look at it?15:12
rhochmuthso, we'll start taking a closer look at your work tomasz, in parallel with a merge15:12
*** rockyg has left #openstack-meeting-315:12
mroderusok, makes sense15:12
rhochmuthwe'll look at things that are outside of gerritt too15:12
ddieterlyrhochmuth: shouldn't all new dev be done in the stackforge repos?15:13
rhochmuthyes, that is the case.15:13
*** Memke has joined #openstack-meeting-315:13
tomasztrebskimeaning to say, gerrit will be skipped for monasca-log-api and any repo under stackforge ? am i getting it right ?15:14
*** Memke is now known as macio-fu15:14
rhochmuthgerrit should already be on the monasca-log-api in stackforge15:14
witekno, we have to add it to stackforge/monasca-log-api15:14
witekyes, it is15:14
tsvand review it before it merges ?15:14
ddieterlytsv: well, of course ;-)15:15
tsv:)15:15
rhochmuthok, so i think we have a plan15:15
rhochmuthwill start to merge15:15
*** kebray has quit IRC15:15
rhochmuthto the monasca-log-api15:15
rhochmuthalso, others to start review the code, testing, ...15:15
rhochmuthsound good?15:16
ddieterlyyea, i think we need to start enforcing more testing at this point15:16
*** jckasper has joined #openstack-meeting-315:16
mroderustomasztrebski: are you ok with that?15:16
rhochmuthddieterly: yes, i'm going to give an update on tempest, but there are also unit tests too15:16
tomasztrebskibasically yes, I just lost point about where python code should reside, should it be pushed to gerrit or left on github ?15:17
witek#action tomasztrebski pushes initial draft of python monasca-log-api implementation to gerrit next week15:17
ddieterlyyes, gerrit15:18
tomasztrebskiI like that :)15:18
rhochmuth:-)15:18
rhochmuthok, next topic15:18
rhochmuth#topic devstack15:19
*** openstack changes topic to "devstack (Meeting topic: monasca)"15:19
ddieterlyok, i'm setting up devstack on a vm right now15:19
ddieterlylearning to spell 'devstack' basically15:19
rbakSo we are working on getting monasca into devstack?15:19
rhochmuthwho added the devstack topic15:19
rbakThat was me15:19
fabiogddieterly: that is a good exercise :-)15:19
ddieterlyi did this 1 year aga for the ceilometer interface, but forgot everything15:19
ddieterlyrbak: yea15:20
rhochmuthrbak: awesome!!!15:20
rhochmuthdo you need any help15:20
rbakSorry, that was meant to be a question, not a statement.15:20
ddieterlyrbak: yea, 'we' are working on getting monasca into devstack15:21
rhochmuthohhh, a question in the form of a sentence15:21
rbakOur QA team was trying to get Monasca into Rally, but was blocked by Monasca not being in devstack15:21
*** ajmiller has joined #openstack-meeting-315:21
rhochmuthyes, we are starting to do that15:21
*** fabiog_ has joined #openstack-meeting-315:21
rhochmuththere are a lot of dependencies on devstack15:21
rbakAlright, I think that's all we really needed to hear.  I'll pass along that it's work in progress.15:22
rhochmuthso, ddieterly will be starting on this, and i'll be helping too15:22
*** kebray has joined #openstack-meeting-315:22
ddieterlywe will be doing the python api and perister15:22
rhochmuthhopefully, we'll know a little more for next weeks meeting15:22
*** ildikov has joined #openstack-meeting-315:22
ddieterlynot sure if that helps twc at this point15:22
rbakWe were just wondering where that was15:23
rbakI know it's come up before15:23
fabiog_ddieterly: do you want to send patches to the ceilosca installation for testing?15:23
*** jaypipes_ is now known as jaypipes15:23
ddieterlyi don't know at this point15:23
fabiog_ddieterly: it could be a easy environment for validating that devstack with your changes works15:23
ddieterlynot sure what that entails15:23
tomasztrebskibtw, if I may interrupt, do you have any guidelines for python code or should it follow openstack guidelines only without any mods ?15:24
*** fabiog has quit IRC15:24
*** jesseo has quit IRC15:24
*** tsv has quit IRC15:24
rhochmuthtomasztrebski: we follow the openstack guidelines15:24
ddieterlytomasztrebski: openstack pep 8 standards15:24
*** yamamoto has quit IRC15:24
rhochmuthtomasztrebski: correct15:24
ddieterlyno funny business ;-)15:24
rhochmuthfabiog: as soon as we have monasca integrated in devstack, we'll look into adding ceilosca too15:25
rhochmuthwill probably need help15:25
ddieterly@fabiog_ i'll look into it15:25
rhochmuthright now we're just getting up to speed on devstack and tempest15:25
rhochmuthas soon as that is in reasonable shape we'll look at ceilosca too15:26
rhochmuthok, next topic?15:26
*** nkrinner is now known as nkrinner_afk15:26
*** Sukhdev_ has joined #openstack-meeting-315:26
rhochmuth#topic grafana15:27
*** openstack changes topic to "grafana (Meeting topic: monasca)"15:27
rbakI just wanted to bring this up again since it barely made it in the last meeting15:27
rhochmuthok15:27
rbakI've started work on a monasca plugin for the latest grafana.15:27
rhochmuthgreat!15:27
rhochmuthhow is it looking?15:28
fabiog_+115:28
rbakIt's not quite ready to share, but should be by next week I would think15:28
rhochmuthawesome15:28
rbakAnd with all the repo talk I should ask where we want to put this.15:28
rhochmuthi would like to see this merged in with the grafana repo15:28
rbakSo are we alright with a private repo until that time?15:29
rhochmuthi think this is fine to have outside in a separate repo, just like we have the current repo15:29
rbakAlright, I'll plan on that15:29
rhochmuthwell, i think it woudl still be public, just not in gerrit review under openstack, since this is really another project15:29
rbakThat's what I meant.15:30
rhochmuthi would start with a public fork of the grafana repo, then hopefully we can merge back to the Grafana project15:30
*** lazy_prince has joined #openstack-meeting-315:30
fabiog_rhochmuth: I think in the future we should start engaging with the Grafana community and see if they allow us to be officially supported15:30
rhochmuthyes, that was the plan all along15:30
rbakAlso, in case anyone missed it, the gnocchi project is also trying to merge their own plugin15:30
rbakinto grafana15:30
mroderusrbak: if it's only a plugin, why do we have to merge it?15:31
rhochmuthcorrect, i saw a post on that in openstack operators this week15:31
*** vgridnev has quit IRC15:31
rhochmuthi think wherever all the grafana plugins are stored these days, is where we should merge our code too15:31
rhochmuthin grafana 1.X, this was in the grafana project15:32
rbakmroderus: It's a datasource.  Grafana isn't really easily plugable as far as I know15:32
rhochmuthrbak: is it the similar to 1.X?15:32
mroderusok, I understand15:32
rhochmuthall the data sources are in the Grafana repo15:32
rhochmuth?15:32
*** rbrndt has joined #openstack-meeting-315:33
rbakIn the respect that the datasources are in the grafana project, yes15:33
rbakThere's a lot of other changes though15:33
*** JeanBriceCombebi has quit IRC15:33
rhochmuthok, so i think we are ok doing the development outside of gerrit in this case, as this is another openstack project15:33
*** kumar has quit IRC15:33
rhochmuthas grafana is not an openstack project15:33
rhochmuthso the proper landing spot is the grafana repo15:34
rbakAlright, I'll have it somewhere public and share it next week hopefully.15:34
rbakAnd we can try to get it merged as we move forward15:34
fabiog_rbak: is based on 2.1.x?15:34
rbakyes15:34
rhochmuthi know the founder of raintank which is where grafana is developed by15:34
*** david-ly_ has joined #openstack-meeting-315:35
rhochmuthso, if we need help in adding to grafana then let me know and we can get a discussion arranged15:35
rbaksounds good15:35
*** bharathm has joined #openstack-meeting-315:35
rhochmuthok, i think we are ready for next topic15:36
rhochmuth#tempest15:36
rhochmuth#topic tempest15:36
*** openstack changes topic to "tempest (Meeting topic: monasca)"15:36
rhochmuththis should be quick15:36
rhochmuthi started on getting the tempest tests15:36
rhochmutha tester did the original development a while ago15:37
rhochmuthbut we never merged to openstack/tempest15:37
rhochmuthso i'm getting that work going15:37
rhochmuthi'm hoping this will get completed in a couple of weeks15:37
rhochmuthor less15:38
rhochmuthif anyone wants to help, please let me know15:38
tomasztrebskiI think some tempests might me done by us as well, regarding monasca log api as far as I know15:38
rhochmuththat woud be great15:38
smialywe based on yours https://github.com/hpcloud-mon/tempest adds some simple tests15:38
tomasztrebskiok, @smialy is here so he can share the info about that with you15:39
*** armax has joined #openstack-meeting-315:39
smialywe (mean: fujitsu) prepare some simple test for testing our changes15:39
smialyhttps://github.com/FujitsuEnablingSoftwareTechnologyGmbH/tempest15:39
rhochmuthand those are for the log api?15:40
rhochmuthso, i'll try and get this first set through, and then we can start to get the log tests integrated too15:41
smialyyes - we put some message in monasca-log-api and search it in elasticsearch15:41
rhochmutheverything in tempest works via the api15:41
*** david-ly_ is now known as david-lyle15:41
rhochmuthso, if you are going around the api, i'm not sure that tempest would work with that15:41
tomasztrebskibut tempests for log-api are using log-api as far as I know, isn't that right @smialy?15:42
smialywe use elasticsearch api :)15:42
smialyyes15:43
mroderusI think currently the API has only PUSH methods15:43
mroderusI mean POST, sorry15:43
smialyPOST*15:43
smialy:)15:43
*** Piet has joined #openstack-meeting-315:43
smialyfor this moment only single log with json format15:43
rhochmuthso, i think the initial log tests would just focus on POST, if that is all we have15:44
*** Sukhdev_ has quit IRC15:44
rhochmutheventually, we'll be able to query via API too15:44
rhochmuthand then can add additioanl tests15:44
mroderuseventually, yes15:44
*** Swami has joined #openstack-meeting-315:44
smialylog-api dont have endopont to search15:44
*** nikhil_ has joined #openstack-meeting-315:44
*** nikhil_ is now known as Guest6328215:45
rhochmuthok, are there more topics?15:45
ddieterlyis brad k in the room?15:45
rhochmuthIs there a performance update from TWC and the problem queries?15:45
ddieterlyright15:45
rhochmuthbmotz: how are you doing15:46
rhochmuthyou seem to be finding misc bugs in the python api15:46
*** Guest63282 is now known as nikhil_k15:46
rhochmuthbut, nothing too bad yet15:46
*** Sukhdev has joined #openstack-meeting-315:47
witekthere are a couple of pending pull requests from us on https://github.com/hpcloud-mon15:47
rhochmuthwitek: ok, will take a look15:47
witekcould anyone take a look, please15:47
ddieterlywhich repo exactly?15:47
tomasztrebskimonasca-keystone is the one I contributed to, but there are couple others15:48
tomasztrebskijust cant recall which one :(15:48
rhochmuthansible-monasa-keystone?15:48
rhochmuthso, is this all for ansible related changes?15:48
witekddieterly: I send you a list15:49
witekrhochmuth: mainly15:49
ddieterly@tomasztrebski ping the core guys to push them along every now and then if you are not getting things looked at15:49
tomasztrebskiyes ansible-monasca-keystone15:49
tomasztrebskisorry to ask, but could you give some names :)15:49
* ddieterly roland15:49
rhochmuthwitek: ok, we'll take a look15:49
rhochmuthddieterly is core too15:50
*** krtaylor has joined #openstack-meeting-315:51
rhochmuthok, unless anyone has more topics, updates or questions, we might be ending early15:51
tomasztrebskiwhile we on merges part, in monasca-log-api I made some changes that should be done in monasca-common (if we stick to 1:1 port to python, cause they are now in monasca-common)15:52
*** JeanBriceCombebi has joined #openstack-meeting-315:52
*** nikhil_k has quit IRC15:52
ddieterlythat's ok15:52
tomasztrebskito be precise I am refering to this https://github.com/kornicameister/monasca-log-api/blob/master/monasca_log_api/common/services.py15:52
tomasztrebskiin java that is available here -> https://github.com/stackforge/monasca-common/tree/master/java/monasca-common-model/src/main/java/monasca/common/model15:53
ddieterlyrhochmuth: how about avro?15:53
ddieterlywe still thinking about doing something with that?15:54
rhochmuthwhat is the services.py for?15:54
*** devlaps has joined #openstack-meeting-315:54
ddieterlyrhochmuth: ?15:55
tomasztrebski@rhochmuth, in monasca-common [java] there are classes: ComputeServiceInfo, VolumeServiceInfo and ObjectStoreServiceInfo...I know there is monasca-common in python now, but it does not have those classes yet, so my question is should it this code be moved there or left i monasca-log-api for now15:55
tomasztrebskiservices.py defines those classes15:55
rhochmuthtomasztrebsk: i'll review off-line15:56
rhochmuthin general, the code in monasca-common for the java and python is not 1:115:56
rhochmuthso, i'll need to get back to you on this15:57
tomasztrebskiok, just leave me comment somewhere @ github or where you think is the best place to put it15:57
rhochmuthok15:57
tomasztrebskithx15:57
tomasztrebskithat's all I wanted to say15:57
tomasztrebski:)15:57
rhochmuthi think that is all we have time for today15:58
witekthank you Roland15:58
tomasztrebskiyep, thx...it was good chat :)15:59
rhochmuth#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Wed Sep 16 16:00:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-09-16-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-09-16-15.00.txt16:01
fabiog_rhochmuth: please end the meeting16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/monasca/2015/monasca.2015-09-16-15.00.log.html16:01
*** evgenyf has quit IRC16:01
*** smialy has quit IRC16:01
*** DericHorn-HP has joined #openstack-meeting-316:01
*** mroderus has quit IRC16:03
*** fabiog_ has quit IRC16:04
*** sballe has joined #openstack-meeting-316:06
*** marios has quit IRC16:09
*** marios has joined #openstack-meeting-316:10
*** safchain has quit IRC16:11
*** tomasztrebski has quit IRC16:14
*** JeanBriceCombebi has quit IRC16:18
*** rbrndt has left #openstack-meeting-316:20
*** sdake_ is now known as sdake16:23
*** matrohon has quit IRC16:24
*** yamamoto has joined #openstack-meeting-316:25
*** pchriste has left #openstack-meeting-316:28
*** B_Smith has joined #openstack-meeting-316:29
*** watanabe_isao has joined #openstack-meeting-316:29
*** yamamoto has quit IRC16:29
*** beagles is now known as beagles-brb16:30
*** ttrifonov is now known as zz_ttrifonov16:33
*** watanabe_isao has quit IRC16:33
*** lazy_prince has quit IRC16:35
*** jruano has quit IRC16:36
*** B_Smith has quit IRC16:36
*** davidsha_ has quit IRC16:39
*** vgridnev has joined #openstack-meeting-316:41
*** DericHorn-HP has quit IRC16:45
*** bharathm has quit IRC16:46
*** bharathm has joined #openstack-meeting-316:46
*** dclain_ has quit IRC16:47
*** tfukushima has quit IRC16:47
*** neelashah has quit IRC16:48
*** s3wong has joined #openstack-meeting-316:50
*** kzaitsev_mb has quit IRC16:53
*** fitoduarte has joined #openstack-meeting-316:54
*** B_Smith has joined #openstack-meeting-316:56
*** yamahata has quit IRC17:00
*** VW_ has quit IRC17:00
*** sbalukoff has quit IRC17:00
*** beagles-brb is now known as beagles17:01
*** VW_ has joined #openstack-meeting-317:01
*** Sukhdev has quit IRC17:01
*** kebray has quit IRC17:03
*** neelashah has joined #openstack-meeting-317:04
*** iben has quit IRC17:05
*** VW_ has quit IRC17:05
*** kebray has joined #openstack-meeting-317:05
*** iben has joined #openstack-meeting-317:08
*** cloudtrainme has joined #openstack-meeting-317:10
*** lsmola has quit IRC17:13
*** yamamoto has joined #openstack-meeting-317:13
*** egallen has quit IRC17:15
*** fitoduarte has quit IRC17:17
*** madhu_ak has joined #openstack-meeting-317:18
*** bmotz has quit IRC17:18
*** e0ne has quit IRC17:19
*** stendulker has quit IRC17:21
*** jckasper has quit IRC17:22
*** stendulker has joined #openstack-meeting-317:22
*** stendulker_ has joined #openstack-meeting-317:24
*** stendulker has quit IRC17:24
*** fitoduarte has joined #openstack-meeting-317:24
*** SumitNaiksatam has quit IRC17:27
*** yamahata has joined #openstack-meeting-317:28
*** geoffarnold has quit IRC17:29
*** geoffarnold has joined #openstack-meeting-317:31
*** stendulker_ has quit IRC17:33
*** lexholden has quit IRC17:34
*** VW_ has joined #openstack-meeting-317:35
*** ddieterly has quit IRC17:42
*** ihrachys has quit IRC17:46
*** tfukushima has joined #openstack-meeting-317:48
*** ivar-lazzaro has joined #openstack-meeting-317:50
*** tfukushima has quit IRC17:52
*** ivar-lazzaro has quit IRC17:53
*** beagles has quit IRC17:53
*** ivar-lazzaro has joined #openstack-meeting-317:54
*** sdake_ has joined #openstack-meeting-317:54
*** ivar-laz_ has joined #openstack-meeting-317:55
*** sdake has quit IRC17:58
*** ivar-lazzaro has quit IRC17:59
*** e0ne has joined #openstack-meeting-317:59
*** DericHorn-HP has joined #openstack-meeting-317:59
*** geoffarn_ has joined #openstack-meeting-318:04
*** geoffarnold has quit IRC18:07
*** sbalukoff has joined #openstack-meeting-318:09
*** pballand has joined #openstack-meeting-318:11
*** iben has quit IRC18:16
*** e0ne has quit IRC18:18
*** tfukushima has joined #openstack-meeting-318:18
*** e0ne has joined #openstack-meeting-318:20
*** Sukhdev_ has joined #openstack-meeting-318:22
*** numans has joined #openstack-meeting-318:22
*** tfukushima has quit IRC18:23
*** mickeys has quit IRC18:23
*** iben has joined #openstack-meeting-318:26
*** carl_baldwin has quit IRC18:27
*** david-lyle has quit IRC18:30
*** iben has quit IRC18:34
*** vgridnev has quit IRC18:38
*** ivar-laz_ has quit IRC18:38
*** jckasper has joined #openstack-meeting-318:38
*** ivar-lazzaro has joined #openstack-meeting-318:39
*** matrohon has joined #openstack-meeting-318:49
*** jruano has joined #openstack-meeting-318:50
*** mrmartin has quit IRC18:53
*** bharathm has quit IRC19:00
*** vgridnev has joined #openstack-meeting-319:02
*** cloudtrainme has quit IRC19:02
*** macio-fu has quit IRC19:02
*** bpokorny has joined #openstack-meeting-319:02
*** cloudtrainme has joined #openstack-meeting-319:04
*** robcresswell has joined #openstack-meeting-319:05
*** cloudtrainme has quit IRC19:08
*** cloudtrainme has joined #openstack-meeting-319:08
*** cloudtrainme has quit IRC19:10
*** ihrachys has joined #openstack-meeting-319:16
*** DericHorn-HP has quit IRC19:19
*** dclain has joined #openstack-meeting-319:20
*** mrmartin has joined #openstack-meeting-319:20
*** dclain_ has joined #openstack-meeting-319:21
*** FallenPegasus has joined #openstack-meeting-319:22
*** dclain has quit IRC19:24
*** rdopiera has quit IRC19:31
*** iben has joined #openstack-meeting-319:31
*** tqtran has joined #openstack-meeting-319:33
*** e0ne has quit IRC19:35
*** kzaitsev_mb has joined #openstack-meeting-319:37
*** ihrachys has quit IRC19:38
*** iben has quit IRC19:39
*** ihrachys has joined #openstack-meeting-319:39
*** cloudtrainme has joined #openstack-meeting-319:39
*** mrmartin has quit IRC19:42
*** FallenPe_ has joined #openstack-meeting-319:42
*** bharathm has joined #openstack-meeting-319:44
*** FallenPegasus has quit IRC19:45
*** sdake has joined #openstack-meeting-319:49
*** bharathm has quit IRC19:49
*** crobertsrh has joined #openstack-meeting-319:52
*** sdake_ has quit IRC19:52
*** Rockyg has joined #openstack-meeting-319:55
*** FallenPe_ has quit IRC19:56
*** ihrachys has quit IRC19:57
*** tsufiev has joined #openstack-meeting-319:57
*** ducttape_ has joined #openstack-meeting-319:58
*** jwy has joined #openstack-meeting-320:00
robcresswell#startmeeting horizondrivers20:00
openstackMeeting started Wed Sep 16 20:00:19 2015 UTC and is due to finish in 60 minutes.  The chair is robcresswell. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"20:00
openstackThe meeting name has been set to 'horizondrivers'20:00
robcresswellAnyone about for the meeting?20:00
mrungeo/20:00
*** lhcheng has joined #openstack-meeting-320:00
bpokornyo/20:01
jwyhi20:01
ducttape_o/20:01
lhchengo/20:01
robcresswellDavid is away atm, so have stolen chair. bpokorny, just a few announcements to make then will pass on to you.20:01
*** TravT has joined #openstack-meeting-320:01
bpokornySounds good20:01
robcresswell#link https://wiki.openstack.org/wiki/Meetings/HorizonDrivers20:01
robcresswellAgenda, not much on it20:02
tsufievO/20:02
robcresswellFirst thing is: The etherpad is up for Mitaka Summit Session Topics20:02
*** openstackstatus has quit IRC20:02
robcresswell#link https://etherpad.openstack.org/p/horizon-mitaka-summit20:02
*** mestery has quit IRC20:02
robcresswellNote the bits at the top too, so we don't end up with a huge mess.20:03
robcresswellSecond notice is: rel mgmt wants us to aim for RC1 at the end of this week I believe.20:03
*** mestery has joined #openstack-meeting-320:03
robcresswell#link https://launchpad.net/horizon/+milestone/liberty-rc120:03
*** openstackstatus has joined #openstack-meeting-320:03
*** ChanServ sets mode: +v openstackstatus20:03
robcresswellCores really need to be picking up bugs. We have 3/4 bps and <20 bugs, so get on with it :p20:04
*** sambetts has quit IRC20:05
*** mickeys has joined #openstack-meeting-320:05
mrungeah yes, david mentioned earlier, bugs <= medium prio might not make it into rc120:05
*** carl_baldwin has joined #openstack-meeting-320:05
robcresswellYes, I've been removing a few already.20:05
robcresswellThe translations appear to be fixed again now.20:06
*** sigmavirus24 is now known as sigmavirus24_awa20:06
mrunge\o/20:06
mrungebut selenium is broken again?20:06
robcresswellBut we still have several High bugs that really need reviews. A lot are not too complex.20:06
robcresswellYes, it broke late last week again I think20:06
mrungedarn20:07
robcresswellIntegration is still up though I *think*. tsufiev may have more to say on the matter.20:07
*** bharathm has joined #openstack-meeting-320:07
*** Aish has joined #openstack-meeting-320:07
tsufievrobcresswell: no news = good news20:07
robcresswellExcellent.20:07
*** sigmavirus24_awa is now known as sigmavirus2420:08
robcresswellThat's all from me. Expect pings about bugs/bps, sorry if I get annoying.20:08
robcresswellbpokorny, your turn :)20:08
bpokornyThanks!20:08
mrungerobcresswell, you're doing fine :)20:08
*** stevemar has quit IRC20:08
mrungekeep pinging!20:08
bpokornyJust wanted to publicize this one for the M release:  https://blueprints.launchpad.net/horizon/+spec/nova-server-groups20:09
bpokornyAbility to manage server groups via Horizon.20:09
*** stevemar has joined #openstack-meeting-320:09
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/nova-server-groups20:09
lhchengbpokorny: is that different as service groups?20:09
tsufievmrunge: iirc selenium fix is blocked by DOA issue20:09
bpokornyI put a review out already for setting the server groups.20:09
bpokornylhcheng:  I think so...  I'll have to look into what service groups are.20:10
mrungetsufiev, by which doa issue?20:10
*** sambetts has joined #openstack-meeting-320:10
bpokornyBut server groups are managed on the cli with the "nova server-group-XXXX"  commands.20:10
tsufievmrunge: the one Richard was trying to fix with lhcheng, but then it appeared that we need to rename DOA ). Sorry, I'm from tablet, difficult to paste links20:11
*** stevemar has quit IRC20:11
robcresswellBP looks solid IMO.20:11
mrungetsufiev, ok, thanks. I'll look that up or ask you tomorrow20:12
*** clu_ has joined #openstack-meeting-320:12
lhchengbpokorny: we're using the term service group in-house, sounds like the same actually :) it allows a user to set a scheduler hint20:12
robcresswellHas code, and is supported elsewhere.20:12
lhchengbpokorny: that's going to be useful for us, thanks20:12
robcresswellSO we aren't waiting on service updates :D20:12
bpokornylhcheng: Yep, that's what's needed.20:12
ducttape_nova service list  (etc) is usually the service status.   more confusion20:12
*** lexholden has joined #openstack-meeting-320:12
bpokornyScheduler hints20:12
*** Sukhdev_ has quit IRC20:13
bpokornySo as a next step, I'll ping David later about approval for the bp for the M release.20:13
bpokornyAnd that's all I had on that one :)20:14
robcresswellWe can just vote now20:14
robcresswellThere should be several cores here20:14
lhchengbpokorny: cool20:14
lhcheng+ for me20:14
*** FallenPegasus has joined #openstack-meeting-320:14
bpokornyAh, sounds good.20:14
tqtran+ for me as well20:14
robcresswellYeah I think it looks good. Approved. We dont have an M tag yet, so will mark for 'next'20:14
TravTbpokorny: is this just adding hints?20:14
bpokornyThe first part is being able to boot a VM with hints.20:15
bpokornyBut as a next step, we'll also probably want the ability to create/edit/delete server groups.20:15
ducttape_bpokorny - there are some scheduler hints available to admins - like place the vm on a specific host20:16
ducttape_we'd need to check the auth reqmts on some of those options, perhaps ?20:16
lhchengducttape_: aggregates + flavor metadata (I think)20:16
TravTthis type of information you can get from the metadata catalog in glance.20:17
TravTyou can create metadata items and then set their visibility20:18
lhchengthe hints available to user should be configurable, depending how the deployer wants their scheduler to work20:18
TravTand then only show to users based on their ability to see them20:18
*** beagles has joined #openstack-meeting-320:18
TravTthat is what glance metadata catalog gives you20:18
ducttape_bpokorny - your life is getting complex ^  ;)20:18
TravTwe already use it in horizon.20:19
bpokornyducttape_:  Heh - always how it goes :)20:19
ducttape_but it seems like this is interesting work / supported by most all20:19
*** tfukushima has joined #openstack-meeting-320:19
TravTit isn't too hard...20:19
TravTthere is an api for it.20:19
bpokornyAs far as I've seen, there's not a way to specify server groups currently via Horizon.20:20
ducttape_boot from vol TravT, just to throw a monkey wrench at you20:20
mrungebpokorny, yes, that's right20:20
*** Piet has quit IRC20:20
ducttape_right now you'd have to use live migration to simulate something close to that20:21
*** iben has joined #openstack-meeting-320:23
*** tfukushima has quit IRC20:24
robcresswellHas the dust settled?20:24
*** matrohon has quit IRC20:25
bpokornyI think so?  :)20:25
robcresswellIf there are still people around, I'd like to discuss the remaining RC1 BPs and see if people have time to review them.20:25
robcresswell#info Nova Server Groups blueprint approved20:26
robcresswelllhcheng: Were you still intending to look over https://blueprints.launchpad.net/horizon/+spec/database-clustering-support ?20:26
robcresswellI know I have it on my list. It's a big bp, so would be good to get 2 core reviews if possible.20:27
lhchengugh, I just did a first pass on the code. have to look at it again20:27
*** iben has quit IRC20:28
lhchengrobcresswell: yeah, its a big chunk of  code20:28
lhchengwill try to look at it tomorrow20:28
robcresswelllhcheng: Yup. Thanks. I will do the same.20:28
robcresswellThere is also a sahara bp20:29
robcresswell#link https://blueprints.launchpad.net/horizon/+spec/unified-job-interface-map-ui20:29
robcresswellIt's had a number of reviews from Horizon folk too in the last patch set.20:29
robcresswellI don't suppose anyone will volunteer to review?20:30
robcresswelltqtran, clu_ *hint hint*20:30
tsufievrobcresswell: I'm still against embedding html into js, but an author didn't respond20:31
mrungethen it's easy: -120:32
mrungeI can do that tsufiev :P20:32
robcresswelltsufiev: I had a discussion with them on IRC. IMO with Sahara, since it is likely to move out soon, it isn't really a blocker.20:32
robcresswellAs long as it's not insanity, I'm inclinced to be lenient with it.20:32
robcresswellBut I'm not sure what davids stance is on that20:32
tsufievHeh. Then I don't see much sense in reviewing it at all20:32
tsufievIf it doesn't beak horizon, it's fine20:33
mrungeWe have to keep that code alive for quite a time20:33
robcresswellWell, difference between "where does a one-time-usage-template live" and "this code is totally insane"20:33
mrungecough20:33
robcresswellAs I understood, they are planning on moving it out in M, and contrib/ was the first stage to that.20:33
robcresswellBut not sure on absolute plans.20:33
*** macio-fu has joined #openstack-meeting-320:34
tsufievrobcresswell: insanity creeps in with small steps ;)20:34
mrungeI mean, embedding js in html is not the worst thing in sahara dashboard20:34
robcresswelltsufiev: Haha. If you feel strongly, -1 the patch set.20:35
robcresswellI'll look at it after the databases code.20:35
tsufievmrunge: js inside html is okay, reverse is not IMO20:35
mrungeouch :x20:35
tsufievOkay, i'll say my word and -1 it20:35
robcresswellSure thing20:37
*** ndipanov has quit IRC20:37
robcresswellRight I think that is all on the agenda. Does anyone else have any other blueprints or points they'd like to raise (or argue about?)20:37
TravTyeah20:37
*** macio-fu has quit IRC20:37
TravTre: angularizing the tables.20:38
TravTi think there are a couple bug fixes we should still do on master with what is there.20:38
TravTbut otherwise:20:38
TravThttps://openstack.nimeyo.com/58582/openstack-dev-horizon-patterns-for-angular-panels20:38
robcresswellYep, I've yet to reply to this20:39
*** iben has joined #openstack-meeting-320:39
robcresswellTravT: Which bugs? Tag them for rc1 please20:39
*** ajmiller has quit IRC20:39
robcresswellTravT: They may not make it, but still be good to get visibility.20:40
*** ajmiller has joined #openstack-meeting-320:40
TravThere's one.20:40
mrungeyes, robcresswell +120:40
TravThttps://review.openstack.org/#/c/217295/20:40
TravTit is under the larger bp20:40
tsufievrobcresswell: btw, if an rc1 bug has 2 not tagged dependency bugs/commits, should I tag them as well?20:40
mrungeTravT, is that a bug or a feature?20:41
robcresswelltsufiev: Wow, what a question. I would say yes, tag them, but don't expect them to get in or not.20:41
mrungesince we're that late, I'd try to fix bugs and not to introduce new features20:42
*** puranamr has joined #openstack-meeting-320:42
TravTprobably could change to a bug and fix the usage of '-' in numerous other spots in angular horizon.20:42
tsufievrobcresswell: it's about https://review.openstack.org/#/c/215196/20:42
mrungesounds more like it's fixing a bug?20:42
TravTit is a bug20:43
robcresswellTravT: Probably better to tag as a bug, rather than feature work20:43
robcresswelltsufiev: looking...20:43
robcresswelltsufiev: Yep, tag all as RC1, we'll see where we get to20:44
tsufievrobcresswell: okay20:44
TravTyeah, i could do that... could then track down other places we need to replace '-' with using the filter.20:44
*** mwagner_lap has quit IRC20:44
robcresswelltsufiev: As I said, I'm being pretty sharp about the bug list, so it may be removed again shortly, but best to draw attention to it first so its an educated decision.20:45
mrungeuhm, bugs still can be fixed after rc1 release20:47
*** puranamr has quit IRC20:47
mrungebut they will need backports from mitaka to liberty branch then20:47
robcresswellHa, yeah ofc20:47
mrungejust as a reminder20:47
mrungethat's not that easy for features20:47
robcresswellWe may also have an RC2 depending. I just meant they may get removed from rc1 etc.20:47
TravTi'm working on a searchlight panel which has uncovered some bugs in magic search.  I might submit them up too.  kfox1111 also experienced one of them on his app catalog plugin20:47
mrungethere are quite a few bugs currently20:48
robcresswellThe remaining BPs should get in IMO, if people will review. I've +2'd Curvature, merged shelving, looking into dbs/ sahara20:48
robcresswellmrunge: Indeed, but it is shrinking. I've got it down to about half of Monday, obsoleted a few, reviewed/ merged a lot :p20:49
mrungerobcresswell, pain points are still in20:49
robcresswellmrunge: pain points?20:49
mrungeuhm xss20:50
mrungethe re-login bug20:50
mrungeetc. just walk through the list of high prio bugs in horizon20:50
mrungenot to mention doa bugs20:50
mrungewhich currently fall out of the view, because it's a different project20:51
robcresswellYep. I believe the re-login bug had a fix out20:51
mrungenope20:51
mrungethere's a proposal20:51
mrungebut it's not merged20:51
robcresswellAh, my mistake20:51
mrungeand tsufiev said, it breaks project switching20:52
robcresswell:(20:52
tsufievmrunge: did I?20:52
mrungetsufiev, I believe so20:52
robcresswellWell, we've got a busy couple of days ahead then :)20:54
mrungeyes!20:54
tsufievOkay, let's first fix DOA job that's failing, and then re-login bug and see what's next...20:54
robcresswellYes. Please focus reviews on those bugs targeted for RC1, and mention any others that may be blockers.20:55
robcresswellCurvature needs another core review, me and lhcheng will target dbs, and then sahara I'll look at afterwards, see if I can drag someone else in too.20:56
robcresswellThat covers the FFEs I think, unless angular images is looking ready to go live.20:56
TravTrobcresswell: there is good progress on them, but I don't think they'll be ready.20:58
robcresswellTravT: h'okay. I'm glad development was kept open though.20:58
TravTyeah, we've really made some improvements in the last few weeks and found some additional ways to reduce code redundancy20:59
robcresswellGood stuff. I'm looking forward to settling on patterns so I can update my networks panel and push it.20:59
robcresswellAnyway, thats the hour21:00
robcresswellThanks everyone!21:00
mrungethanks robcresswell21:00
robcresswell#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
tsufievThanks and bye!21:00
openstackMeeting ended Wed Sep 16 21:00:32 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-09-16-20.00.html21:00
*** jwy has left #openstack-meeting-321:00
bpokornyThanks all!21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-09-16-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-09-16-20.00.log.html21:00
*** Piet has joined #openstack-meeting-321:00
TravTthanks robcresswell21:00
*** tsufiev has left #openstack-meeting-321:01
*** robcresswell has left #openstack-meeting-321:03
*** crobertsrh is now known as _crobertsrh21:07
*** lexholden has quit IRC21:10
*** lblanchard has quit IRC21:11
*** vgridnev has quit IRC21:13
*** yamahata has quit IRC21:14
*** puranamr has joined #openstack-meeting-321:16
*** ducttape_ has left #openstack-meeting-321:18
*** mickeys has quit IRC21:21
*** mickeys has joined #openstack-meeting-321:21
*** Aish_ has joined #openstack-meeting-321:23
*** Aish_ has quit IRC21:24
*** Rockyg has quit IRC21:25
*** Aish has quit IRC21:25
*** jmckind has quit IRC21:26
*** Sukhdev has joined #openstack-meeting-321:27
*** puranamr has quit IRC21:28
*** tqtran has left #openstack-meeting-321:31
*** julim has quit IRC21:35
*** krtaylor has quit IRC21:46
*** rhochmuth has quit IRC21:50
*** beagles has quit IRC21:54
*** david-lyle has joined #openstack-meeting-321:56
*** neelashah has quit IRC22:02
*** kebray has quit IRC22:04
*** carl_baldwin has quit IRC22:09
*** stevemar has joined #openstack-meeting-322:10
*** stevemar has quit IRC22:13
*** tfukushima has joined #openstack-meeting-322:20
*** VW__ has joined #openstack-meeting-322:21
*** VW_ has quit IRC22:24
*** tfukushima has quit IRC22:25
*** VW__ has quit IRC22:25
*** Sukhdev has quit IRC22:28
*** david-lyle has quit IRC22:29
*** jruano has quit IRC22:31
*** krtaylor has joined #openstack-meeting-322:32
*** kebray has joined #openstack-meeting-322:35
*** mwagner_lap has joined #openstack-meeting-322:37
*** rbak has quit IRC22:42
*** cloudtrainme has quit IRC22:45
*** dims_ has quit IRC22:48
*** banix has quit IRC22:48
*** Sukhdev_ has joined #openstack-meeting-322:51
*** kebray has quit IRC22:54
*** dclain_ has quit IRC22:59
*** markvoelker has quit IRC23:05
*** Sukhdev_ has quit IRC23:15
*** jruano has joined #openstack-meeting-323:27
*** dims_ has joined #openstack-meeting-323:32
*** baoli_ has quit IRC23:37
*** yamamoto has quit IRC23:39
*** hoangcx has joined #openstack-meeting-323:47
*** salv-orlando has quit IRC23:48
*** Swami has quit IRC23:50
*** yamahata has joined #openstack-meeting-323:51
*** Sukhdev has joined #openstack-meeting-323:52
*** badveli has joined #openstack-meeting-323:52
*** shwetaap1 has quit IRC23:55
elmikoanyone around for api-wg meeting?23:59

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