Tuesday, 2014-11-18

*** Guest60909 has quit IRC00:03
*** safchain has quit IRC00:09
*** chuckC_ has quit IRC00:10
*** david-lyle is now known as david-lyle_afk00:13
*** ChuckC has joined #openstack-meeting-300:13
*** pballand has quit IRC00:17
*** pballand has joined #openstack-meeting-300:21
*** ChuckC has quit IRC00:25
*** SridharRamaswam1 has quit IRC00:29
*** bpokorny has joined #openstack-meeting-300:30
*** Ark has joined #openstack-meeting-300:33
*** Ark is now known as Guest2571900:34
*** hurgleburgler has quit IRC00:36
*** SridharRamaswamy has joined #openstack-meeting-300:37
*** emagana has joined #openstack-meeting-300:41
*** SridharRamaswamy has quit IRC00:42
*** ChuckC has joined #openstack-meeting-300:43
*** chuckC_ has joined #openstack-meeting-300:45
*** bradjones has quit IRC00:48
*** ChuckC has quit IRC00:48
*** ChuckC has joined #openstack-meeting-300:49
*** bradjones has joined #openstack-meeting-300:49
*** carl_baldwin has quit IRC00:51
*** dboik_ has joined #openstack-meeting-300:58
*** SridharRamaswamy has joined #openstack-meeting-301:02
*** yamahata has joined #openstack-meeting-301:06
*** yamahata has quit IRC01:07
*** yamahata has joined #openstack-meeting-301:07
*** pballand has quit IRC01:09
*** pballand has joined #openstack-meeting-301:10
*** jaypipes has quit IRC01:11
*** jacalcat has quit IRC01:14
*** salv-orlando has quit IRC01:14
*** hinnant has quit IRC01:15
*** wuhg has joined #openstack-meeting-301:18
*** MaxV has quit IRC01:18
*** salv-orlando has joined #openstack-meeting-301:19
*** banix has quit IRC01:19
*** emagana has quit IRC01:24
*** vkmc has joined #openstack-meeting-301:26
*** asahlin has quit IRC01:27
*** asahlin has joined #openstack-meeting-301:28
*** SridharRamaswamy has quit IRC01:29
*** jacalcat has joined #openstack-meeting-301:31
*** jacalcat has left #openstack-meeting-301:31
*** banix has joined #openstack-meeting-301:41
*** banix has quit IRC01:42
*** MarkAtwood has quit IRC01:42
*** sigmavirus24 is now known as sigmavirus24_awa01:48
*** pballand has quit IRC01:48
*** lhcheng_ has quit IRC01:50
*** banix has joined #openstack-meeting-301:53
*** banix has quit IRC01:54
*** garyduan has quit IRC01:54
*** garyduan has joined #openstack-meeting-301:55
*** julim has joined #openstack-meeting-301:56
*** jacalcat has joined #openstack-meeting-301:59
*** jacalcat has left #openstack-meeting-302:00
*** mwang2 has quit IRC02:03
*** bpokorny has quit IRC02:15
*** banix has joined #openstack-meeting-302:17
*** SridharRamaswamy has joined #openstack-meeting-302:24
*** sigmavirus24_awa is now known as sigmavirus2402:29
*** jacalcat has joined #openstack-meeting-302:32
*** SridharRamaswamy has quit IRC02:37
*** jacalcat has left #openstack-meeting-302:37
*** vkmc has quit IRC02:38
*** Viswanath has joined #openstack-meeting-302:38
*** sankarshan is now known as sankarshan_away02:40
*** Viswanath has quit IRC02:41
*** armax has quit IRC02:43
*** banix has quit IRC02:45
*** etoews has joined #openstack-meeting-302:48
*** s3wong has quit IRC02:51
*** armax has joined #openstack-meeting-302:56
*** chuckC_ has quit IRC02:59
*** chuckC_ has joined #openstack-meeting-303:00
*** sigmavirus24 is now known as sigmavirus24_awa03:02
*** armax has quit IRC03:07
*** sergef has joined #openstack-meeting-303:09
*** SumitNaiksatam has quit IRC03:14
*** SumitNaiksatam has joined #openstack-meeting-303:14
*** banix has joined #openstack-meeting-303:17
*** ivar-laz_ has joined #openstack-meeting-303:21
*** ivar-laz_ has quit IRC03:22
*** ivar-laz_ has joined #openstack-meeting-303:22
*** ivar-laz_ has quit IRC03:22
*** ivar-laz_ has joined #openstack-meeting-303:23
*** ivar-lazzaro has quit IRC03:23
*** ivar-laz_ has quit IRC03:23
*** ivar-lazzaro has joined #openstack-meeting-303:25
*** naohirot has quit IRC03:27
*** pballand has joined #openstack-meeting-303:32
*** armax has joined #openstack-meeting-303:33
*** pballand has quit IRC03:35
*** sankarshan_away is now known as sankarshan03:36
*** jacalcat1 has joined #openstack-meeting-303:37
*** chuckC_ has quit IRC03:39
*** jacalcat1 has left #openstack-meeting-303:40
*** jaypipes has joined #openstack-meeting-303:42
*** etoews has quit IRC03:50
*** etoews has joined #openstack-meeting-303:50
*** armax has quit IRC03:58
*** naohirot has joined #openstack-meeting-304:02
*** armax has joined #openstack-meeting-304:03
*** ivar-laz_ has joined #openstack-meeting-304:13
*** ivar-laz_ has quit IRC04:13
*** ivar-laz_ has joined #openstack-meeting-304:13
*** ivar-lazzaro has quit IRC04:16
*** ivar-laz_ has quit IRC04:17
*** banix has quit IRC04:18
*** dboik_ has quit IRC04:29
*** etoews has quit IRC04:38
*** armax has quit IRC04:40
*** etoews has joined #openstack-meeting-304:42
*** otherwiseguy has quit IRC04:55
*** otherwiseguy has joined #openstack-meeting-304:58
*** banix has joined #openstack-meeting-305:02
*** s3wong has joined #openstack-meeting-305:16
*** etoews has quit IRC05:17
*** s3wong has quit IRC05:21
*** SridharRamaswamy has joined #openstack-meeting-305:21
*** SumitNaiksatam has quit IRC05:24
*** SumitNaiksatam has joined #openstack-meeting-305:26
*** banix has quit IRC05:43
*** otherwiseguy has quit IRC05:57
*** Guest25719 has quit IRC06:01
*** SridharRamaswamy has quit IRC06:06
*** Longgeek has joined #openstack-meeting-306:34
*** sunrenjie has quit IRC06:34
*** Ark has joined #openstack-meeting-306:36
*** Ark is now known as Guest9927506:36
*** sunrenjie has joined #openstack-meeting-306:36
*** sunrenjie has quit IRC06:40
*** sunrenjie has joined #openstack-meeting-306:41
*** mrunge has joined #openstack-meeting-306:53
*** sankarshan is now known as sankarshan_away06:57
*** k4n0 has joined #openstack-meeting-306:57
*** Guest99275 has quit IRC06:58
*** sergef has quit IRC07:11
*** iovadia has joined #openstack-meeting-307:31
*** amotoki has joined #openstack-meeting-307:32
*** Longgeek has quit IRC07:53
*** Longgeek has joined #openstack-meeting-307:53
*** sunrenjie has quit IRC07:54
*** sunrenjie has joined #openstack-meeting-307:54
*** yamamoto_ has joined #openstack-meeting-307:56
*** jtomasek has joined #openstack-meeting-307:56
*** Longgeek_ has joined #openstack-meeting-307:57
*** Longgeek has quit IRC08:00
*** matrohon has joined #openstack-meeting-308:06
*** Ark has joined #openstack-meeting-308:09
*** Longgeek_ has quit IRC08:09
*** Ark is now known as Guest4604308:09
*** Longgeek has joined #openstack-meeting-308:10
*** mrmartin has quit IRC08:12
*** Guest46043 has quit IRC08:13
*** mrmartin has joined #openstack-meeting-308:13
*** Longgeek_ has joined #openstack-meeting-308:14
*** VineetMenon has joined #openstack-meeting-308:15
*** Longgeek has quit IRC08:18
*** sunrenjie has quit IRC08:19
*** yamamoto_ has quit IRC08:25
*** jcoufal has joined #openstack-meeting-308:26
*** ameade has quit IRC08:26
*** sweston has quit IRC08:26
*** erw has quit IRC08:27
*** ameade_ has joined #openstack-meeting-308:27
*** sweston_ has joined #openstack-meeting-308:27
*** erw has joined #openstack-meeting-308:27
*** lhcheng has joined #openstack-meeting-308:31
*** sergef has joined #openstack-meeting-308:33
*** sergef has quit IRC08:33
*** sergef has joined #openstack-meeting-308:33
*** sergef has quit IRC08:36
*** MaxV has joined #openstack-meeting-308:36
*** sergef has joined #openstack-meeting-308:36
*** MaxV has quit IRC08:39
*** mrmartin has quit IRC08:40
*** sergef has quit IRC08:42
*** sergef has joined #openstack-meeting-308:43
*** iovadia has left #openstack-meeting-308:57
*** iovadia has joined #openstack-meeting-308:57
*** MaxV has joined #openstack-meeting-308:58
*** safchain has joined #openstack-meeting-308:59
*** sergef has quit IRC09:01
*** sergef has joined #openstack-meeting-309:02
*** sergef has quit IRC09:02
*** sergef has joined #openstack-meeting-309:04
*** reed has joined #openstack-meeting-309:09
*** jcoufal has quit IRC09:11
*** jcoufal has joined #openstack-meeting-309:13
*** zz_ttrifonov is now known as ttrifonov09:14
*** sergef has quit IRC09:14
*** jcoufal has quit IRC09:14
*** jcoufal has joined #openstack-meeting-309:14
*** yamamoto_ has joined #openstack-meeting-309:25
*** yamamoto_ has quit IRC09:30
*** sergef has joined #openstack-meeting-309:32
*** sergef has quit IRC09:37
*** etoews has joined #openstack-meeting-309:45
*** igordcard has joined #openstack-meeting-309:45
*** etoews has quit IRC09:50
*** sergef has joined #openstack-meeting-309:53
*** sergef has quit IRC09:53
*** matrohon has quit IRC09:55
*** matrohon has joined #openstack-meeting-310:06
*** sergef has joined #openstack-meeting-310:13
*** ilyashakhat has joined #openstack-meeting-310:16
*** matrohon has quit IRC10:22
*** naohirot has quit IRC10:27
*** matrohon has joined #openstack-meeting-310:34
*** yamamoto has joined #openstack-meeting-310:41
*** etoews has joined #openstack-meeting-310:46
*** etoews has quit IRC10:50
VineetMenon\help10:50
*** sergef has quit IRC10:57
*** yamamoto has quit IRC11:03
*** Longgeek_ has quit IRC11:04
*** mrmartin has joined #openstack-meeting-311:04
*** Longgeek has joined #openstack-meeting-311:05
*** vkmc has joined #openstack-meeting-311:28
*** gaitan_ has joined #openstack-meeting-311:34
*** gaitan has quit IRC11:37
*** bradjones_ has joined #openstack-meeting-311:38
*** bradjones has quit IRC11:39
*** bradjones_ is now known as bradjones11:39
*** bradjones has joined #openstack-meeting-311:39
*** etoews has joined #openstack-meeting-311:47
*** etoews has quit IRC11:51
*** igordcard has quit IRC11:52
*** yamamoto has joined #openstack-meeting-312:04
*** iovadia has quit IRC12:07
*** iovadia has joined #openstack-meeting-312:08
*** yamamoto has quit IRC12:09
*** baoli has quit IRC12:13
*** sergef has joined #openstack-meeting-312:14
*** sergef has quit IRC12:14
*** MaxV has quit IRC12:15
*** MaxV has joined #openstack-meeting-312:15
*** jtomasek has quit IRC12:41
*** jtomasek has joined #openstack-meeting-312:47
*** naohirot has joined #openstack-meeting-312:51
*** baoli has joined #openstack-meeting-312:57
*** igordcard has joined #openstack-meeting-312:59
*** k4n0 has quit IRC13:01
*** alexpilotti has quit IRC13:01
*** alexpilotti has joined #openstack-meeting-313:03
*** jacalcat has joined #openstack-meeting-313:06
*** dboik has joined #openstack-meeting-313:13
*** jacalcat has left #openstack-meeting-313:19
*** sergef has joined #openstack-meeting-313:34
*** dboik has quit IRC13:35
*** asahlin has quit IRC13:38
*** eliqiao has joined #openstack-meeting-313:39
*** eliqiao has quit IRC13:45
*** jacalcat has joined #openstack-meeting-313:45
*** evgenyf has joined #openstack-meeting-313:51
*** xuhanp has joined #openstack-meeting-313:51
*** carl_baldwin has joined #openstack-meeting-313:52
*** sergef has quit IRC13:57
*** banix has joined #openstack-meeting-313:58
*** mrunge has quit IRC14:01
*** yamamoto has joined #openstack-meeting-314:01
*** marun has joined #openstack-meeting-314:02
*** dboik has joined #openstack-meeting-314:02
*** regXboi has joined #openstack-meeting-314:02
*** regXboi has left #openstack-meeting-314:03
*** mattfarina has joined #openstack-meeting-314:04
*** sergef has joined #openstack-meeting-314:04
*** s3wong has joined #openstack-meeting-314:05
*** johnbelamaric has joined #openstack-meeting-314:07
*** jpomero has quit IRC14:07
*** seizadi has joined #openstack-meeting-314:10
*** markmcclain has joined #openstack-meeting-314:12
*** jgrimm is now known as zz_jgrimm14:12
*** amotoki_ has joined #openstack-meeting-314:13
*** asahlin has joined #openstack-meeting-314:16
*** sergef has quit IRC14:21
*** etoews has joined #openstack-meeting-314:24
*** akrivoka has joined #openstack-meeting-314:26
*** vishwanathj has joined #openstack-meeting-314:26
*** johnbelamaric has quit IRC14:29
*** mattfarina has quit IRC14:30
*** peristeri has joined #openstack-meeting-314:30
*** markus_z has joined #openstack-meeting-314:38
*** david-lyle_afk is now known as david-lyle14:43
*** hurgleburgler has joined #openstack-meeting-314:46
*** emagana has joined #openstack-meeting-314:46
*** sigmavirus24_awa is now known as sigmavirus2414:47
*** etoews_ has joined #openstack-meeting-314:52
*** etoews has quit IRC14:55
*** apmelton_ has joined #openstack-meeting-315:00
*** s3wong has quit IRC15:01
*** jpich has joined #openstack-meeting-315:04
*** armax has joined #openstack-meeting-315:04
*** seizadi has quit IRC15:05
*** SumitNaiksatam has quit IRC15:05
*** marun has quit IRC15:06
*** naohirot has quit IRC15:06
*** hinnant_ has joined #openstack-meeting-315:07
*** Sukhdev has joined #openstack-meeting-315:07
*** vishwanathj has quit IRC15:08
*** MaxV has quit IRC15:09
*** carl_baldwin has quit IRC15:11
*** sicarie has joined #openstack-meeting-315:11
*** ChuckC_ has joined #openstack-meeting-315:11
*** ChuckC has quit IRC15:11
*** banix has quit IRC15:13
*** MaxV has joined #openstack-meeting-315:15
*** apmelton_ has left #openstack-meeting-315:20
*** MaxV has quit IRC15:21
*** ChuckC_ has quit IRC15:21
*** MaxV has joined #openstack-meeting-315:21
*** sweston_ is now known as sweston15:23
*** nelsnelson has joined #openstack-meeting-315:26
*** tmazur has joined #openstack-meeting-315:28
*** zz_jgrimm is now known as jgrimm15:28
*** marun has joined #openstack-meeting-315:29
*** Sukhdev has quit IRC15:34
*** tsufiev has joined #openstack-meeting-315:38
*** xuhanp has quit IRC15:39
*** taravind has joined #openstack-meeting-315:44
*** taravind has quit IRC15:44
*** Sanjay has joined #openstack-meeting-315:44
*** otherwiseguy has joined #openstack-meeting-315:45
*** gholler has joined #openstack-meeting-315:45
*** crobertsrh has joined #openstack-meeting-315:49
*** markmcclain has quit IRC15:52
*** mrmartin has quit IRC15:54
*** johnbelamaric has joined #openstack-meeting-315:55
*** markus_z has left #openstack-meeting-315:56
*** rdopiera has joined #openstack-meeting-315:57
*** sergef has joined #openstack-meeting-315:58
*** sergef has quit IRC15:58
*** SumitNaiksatam has joined #openstack-meeting-315:58
*** vladikr has joined #openstack-meeting-315:58
*** sergef has joined #openstack-meeting-315:58
*** johnbelamaric has quit IRC16:00
*** baoli has quit IRC16:00
*** rbertram has joined #openstack-meeting-316:00
*** tzumainn has joined #openstack-meeting-316:00
*** dboik_ has joined #openstack-meeting-316:01
david-lyle#startmeeting Horizon16:01
openstackMeeting started Tue Nov 18 16:01:15 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: Horizon)"16:01
openstackThe meeting name has been set to 'horizon'16:01
*** doug-fish has joined #openstack-meeting-316:01
david-lyleHello everyone!16:01
rhagartyhello16:01
asahlinhi16:01
akrivokahello! o/16:01
doug-fishHi all16:01
wuhgHello all16:02
crobertsrhhello/16:02
*** absubram__ has joined #openstack-meeting-316:02
Sanjayhi16:02
*** gary-smith has joined #openstack-meeting-316:02
*** johnbelamaric has joined #openstack-meeting-316:02
rbertramhi16:02
gary-smithhi16:03
lhchenghello16:03
*** sambetts has joined #openstack-meeting-316:03
*** robcresswell has joined #openstack-meeting-316:03
*** john-davidge has joined #openstack-meeting-316:03
absubram__hi16:03
david-lyleAll right, not much on the agenda for today.16:03
robcresswello/16:03
*** matrohon has quit IRC16:04
rdopierahi16:04
david-lyleagenda can be found at: #link https://wiki.openstack.org/wiki/Meetings/Horizon16:04
*** dboik has quit IRC16:04
david-lyleI've started planning out the Kilo blueprints16:04
david-lyle#link https://launchpad.net/horizon/+milestone/kilo-1 reflects some of this16:05
*** yamahata has quit IRC16:05
david-lyleThere is a little cleanup to do on there16:05
*** jpomero has joined #openstack-meeting-316:05
david-lyleuntil we move to a specs repo, there will still be un-prioritized bps at the bottom as that is author's way of asking for inclusion16:06
david-lyleAdditionally, we have some other blueprints that need to be reviewed, as we discussed at the summit16:07
*** baoli has joined #openstack-meeting-316:07
david-lyleAnother observation from walking through the ~270 blueprints is people don't look for matching blueprints before crafting their own16:07
doug-fish270?!16:08
david-lyleI think there are at least 4 bps around pagination in general16:08
*** vladikr has left #openstack-meeting-316:08
david-lyledoug-fish: yeah 27016:08
david-lyledon't even look at the bug count16:08
doug-fishIt's not exactly clear to me which blueprints should still be reviewed.  Plus I'm a little bit lazy and might not study all 270.16:08
david-lylethat's for another week16:08
david-lyledoug-fish: well, I've created a list :)16:08
david-lyle#topic Review Blueprints for Approval in Kilo16:09
*** openstack changes topic to "Review Blueprints for Approval in Kilo (Meeting topic: Horizon)"16:09
doug-fishhooray!  a list!16:09
david-lyleon the meeting agenda I pasted roughly 12 bps that are written in the new format and should be considered for Kilo16:09
doug-fishoh that list.  :-)16:10
david-lyleI'm not sure walking through each in this meeting is the best use of time. But I would like to provide a little time for questions regarding any of those16:10
doug-fishtough to ask questions before we've reviewed.16:11
david-lylelet's give them a final yes/no next week16:11
david-lyleunderstood16:11
david-lyleThere are also no blueprints I've found for the angular work that was agreed to at the summit16:12
rhagartyand how does one suggest a blueprint for consideration?16:12
*** carl_baldwin has joined #openstack-meeting-316:12
david-lylerhagarty: use the new template https://blueprints.launchpad.net/horizon/+spec/template and set the milestone16:13
david-lyleto where in Kilo you think it would land16:13
*** lhcheng_ has joined #openstack-meeting-316:13
rhagartythought I did that... will check16:13
*** marun has quit IRC16:13
doug-fishI have a question kind of related to angular work.  I'm curious if we have any performance metrics for Horizon page load time.  I think one of our goals for using angular is to make Horizon load faster, but would be good if we had some way to measure that.16:14
david-lylerhagarty: I'll be honest, I haven't made it past k-1 yet16:14
*** MarkAtwood has joined #openstack-meeting-316:14
doug-fish(I have a fear in the back of my mind using angular is going to make our pages load slower)16:14
david-lylethat would be ironic16:15
*** peristeri has quit IRC16:15
doug-fishI've worked on single page apps before - that load time is tough and has to be managed.16:15
jpichI think it's expected to make interactions faster, e.g. realising quicker you didn't fill that form correctly16:15
david-lylebut worth categorizing16:15
jpichor maybe i'm misunderstanding16:15
doug-fishjpich - yeah that's true - the client side only interactions should be better16:16
david-lyledoug-fish: we still have to load the data16:16
rdopieradavid-lyle: I added the oslo-config and stevedore entrypoints blueprints to kilo, not sure if in the right way...16:16
*** bpokorny has joined #openstack-meeting-316:16
*** lhcheng has quit IRC16:16
david-lylethe idea is once the data is loaded, we won't keep reloading the data at every click16:16
david-lyleso the overall performance should increase16:16
doug-fishdavid-lyle: right, and if we aren't careful we are going to push out a data-less page, then go back and load data, so our load time would get slower by a full page load cycle.16:16
david-lylewe can't really speed up the other service APIs16:17
*** peristeri has joined #openstack-meeting-316:17
doug-fishunderstood.16:17
rdopieradoug-fish: but that would be only on the login page :)16:17
rdopieraon the other hand, we get async loading for free16:17
david-lylerdopiera: thanks16:17
rdopierawhich horizon currently doesn't have -- it does all the api calls serially16:17
doug-fishsure - calling in parallel should be a nice benefit16:18
doug-fishI'm just suggesting we think about how we measure it to make sure we are really getting the benefit we hope for.16:18
david-lyledoug-fish: it is a realistic concern16:19
rdopieradoug-fish: you want to have benchmarks for regressions on the gate?16:19
lhcheng_if we are doing things in parallel using angular, there is a possibility to hit an issue on api rate limiting. something to validate later.16:19
rdopieradoug-fish: that would be awesome :)16:19
wuhgdavid-lyle:should the integration test use the net bp template?16:20
doug-fishrdopiera:  ideally, I'd like to have those benchmarks.  I'm a bit concerned that we'll be measuring the peformance of the gate instead of the performance of Horiozn16:20
wuhgs/net/new16:20
david-lylewuhg: for new blueprints yes, I've approved all the integration test bps I could find16:20
lhcheng_we already saw this issue on usage page, call to ceilometer hits api rate limiting.16:20
david-lylethose are fairly straight-forward and I just want them done :)16:21
lhcheng_++ on doug-fish's proposal to do some benchmarking16:21
* david-lyle puts palm on face16:21
doug-fishlhcheng_:  I'm not familiar with api rate limiting.  Do you know where I can find out more?16:21
doug-fishnevermind.  google.16:22
lhcheng_doug-fish: lol16:24
david-lyleAround the blueprints for review and overlap in some cases, e.g., pagination, I'm going to pick the one that matches the agreed on path forward at the summit and point all other bp authors to that one16:24
david-lyleand mark the other ones superseeded16:24
*** peristeri has quit IRC16:26
*** SumitNaiksatam has quit IRC16:26
david-lylerhagarty: your bp in k-2 was trivial, just accepted it16:26
david-lyledid you have another?16:26
*** peristeri has joined #openstack-meeting-316:26
rhagartydavid-lyle, the manage/unamange volume was the one I was thinking of16:27
*** banix has joined #openstack-meeting-316:27
david-lylerhagarty: not on my radar yet, but I haven't made it through all 270 yet16:27
david-lylewish there was a way to delete some16:28
*** marun has joined #openstack-meeting-316:28
david-lyleI'll keep walking through them16:28
rhagartydavid-lyle, https://blueprints.launchpad.net/horizon/+spec/add-manage-unmanage-volume16:29
*** clu_ has joined #openstack-meeting-316:29
robcresswelldavid-lyle: Sounds like a good plan to cut down on repetition16:29
david-lyleany other concerns about blueprints for Kilo?16:29
asahlindavid-lyle:  Is there a cutoff date for submitting?16:30
*** bpokorny has quit IRC16:30
david-lyleasahlin: no, the list is fluid for the milestones until later in k-316:30
doug-fishhttps://wiki.openstack.org/wiki/Kilo_Release_Schedule16:30
david-lylebut it's nice to have them in plan before the last minute16:31
asahlindavid-lyle: understood, sooner the better16:31
doug-fishand that's not for a while16:31
*** peristeri has quit IRC16:31
david-lyleI'm going to try and minimize the core-reviewer overload as much as possible16:31
david-lylethat may mean leaving some perfectly good ideas out16:31
amotoki_do we obsolete old submitted blueprints? 270 is really too big number.16:31
david-lyleamotoki_: I'm open to suggestions16:31
david-lylesome are good ideas but need more details and an owner16:32
*** peristeri has joined #openstack-meeting-316:32
david-lyleI can mark the dormant ones obsolete and ask for a resubmit if they are still desired16:32
david-lylethere are bps from 2012 in there16:32
amotoki_it is a good idea to leaving a comment to follow our new bp requirement before obsoleting them.16:33
david-lyleI agree16:33
amotoki_if authors still have interests on working, they should update details.16:33
david-lyleamotoki_: ++16:33
david-lyleI'll continue the clean upd16:34
david-lyle#topic Open Discussion16:35
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:35
john-davidgeWe'd like to talk about upstreaming Curvature if there's interest in the community?16:35
*** pballand has joined #openstack-meeting-316:36
john-davidgeAnd if so, we need to agree a stregegy for doing so16:36
rdopierasorry, but what is curvature?16:36
gary-smithspine anomaly16:36
john-davidgehttps://www.openstack.org/summit/portland-2013/session-videos/presentation/interactive-visual-orchestration-with-curvature-and-donabe16:37
john-davidgeShorter video demo: http://youtu.be/oFTmHHCn2-g16:37
david-lylejohn-davidge: at the summit we saw image launch, what is does curvature control?16:37
asahlinwould curvature be a replacement (more advanced) for the network topology that's in horizon16:37
john-davidgeWe currently see it as a new/alternative dashboard view. It could replace the current network topology view but it also has more functionality than just that16:38
*** yamamoto has quit IRC16:39
*** iovadia has quit IRC16:39
david-lylethis seems like a heat template generator16:40
john-davidgedavid-lyle: The video demo should explain everything quite well, but curvature can be used to deploy/modify/destroy instances, networks, routers, volumes16:40
david-lyleyour doing orchestration outside of heat16:41
david-lyles/your/you're/16:41
david-lyleessentially16:41
john-davidgedavid-lyle: You raise a good point16:41
david-lyleI think that would be a great improvement for our heat UI16:42
amotoki_agree. it seems a kind of visual editing  of heat template or more.16:42
asahlinjohn-davidge:  I watched your demo, it does look pretty cool.   Everyone likes interactive UI's.16:42
rbertramI watched the vid, & wondered how curvature works at scale.16:42
rbertramI do agree it is cool.16:42
david-lyleAnd I could see parts of this in the network topology as well16:42
john-davidgerbertram: It handles up to arounf 2k instances quite well, after that browser performance becomes an issue16:43
rbertraminteresting.16:43
amotoki_it is a big topic how we can manage ~1k instances thru GUI :-)16:44
*** ChuckC_ has joined #openstack-meeting-316:44
*** ChuckC_ is now known as ChuckC16:44
rbertramso it's for admin as well as individual projects16:44
david-lylewhat's the graphing algorithm for 2k nodes, cone tree?16:44
john-davidgerbertram: We see it as being most useful to new users who aren't nessessarily familiar with SDN concepts, but can be used by anyone16:45
john-davidgerbertram: Great for at-a-glance viewing of tenant activity16:45
sambettsdavid-lyle: its of our own invention on top of D3 cross referencing the OpenStack data16:45
*** cbader has joined #openstack-meeting-316:45
rbertramjohn-davidge: the new user still has to learn what can connect to what, the meaning of colors, etc. Done user testing?16:46
sambettsdavid-lyle: we've not done anything special just making sure D3 knows where to put links16:46
david-lylesambetts: when you hit 2k nodes a meaningful layout becomes difficult16:46
john-davidgerbertram: limited user testing, yes. But community feedback is what we're currently seeking :)16:46
robcresswellYeah, people mentioned at the summit that it would be good to have different "personas" (sp?) I think the word was, for different levels of user.16:46
*** krykowski has joined #openstack-meeting-316:46
robcresswellWe wondered if Curvature would help with this goal16:46
sambettsdavid-lyle: agreed16:47
john-davidgedavid-lyle: absolutely, at scale it become less useful, but not as quickly as the current network topology16:47
doug-fishwhen you say "we are constantly getting information back from openstack" how is it interacting with the other services?16:47
amotoki_apart from 2k nodes :-) I agree it can be a good replacement of network topology and "network topology" is a kind of "overview" for users.16:47
david-lylejohn-davidge: very true16:47
david-lyleamotoki_: ++16:47
*** devlaps has joined #openstack-meeting-316:47
asahlinamotoki_: +116:47
asahlinIMO, that is where I picture it fitting in.16:48
rbertramjohn-davidge: still wondering about knowing what can connect to what, couldn't tell from video if it helps know that16:48
david-lyleI think that makes the most sense, but once we start building up the topology before pushing, I think that would best be in heat template generation16:49
john-davidgerbertram: Curvature will only allow the user to draw valid connections. Trying to draw an invalid link just doesn't do anything currently.16:49
sambettsdavid-lyle: thats fine for template generation, but can you live modify a deploied heat template?16:50
*** SumitNaiksatam has joined #openstack-meeting-316:50
david-lylesambetts: you can modify a template and restack16:50
rbertramjohn-davidge: OK. not a showstopper, but potential improvement for future to show which nodes are valid when user starts connecting.16:50
john-davidgedavid-lyle: I guess perhaps we're filling a gap between single actions and template generation. You don't nessesarily want to save each set of deploy/edit actions as a heat template everytime.16:50
sambettsis that a complete redeploy?16:50
john-davidgerebertram: Yes that's a good idea. Perhaps something along the lines of greying out invalid nodes when the root node is selected?16:51
david-lylebut I think this works in lieu of the network topology, but complete the actions as they are made, rather than delaying them16:51
amotoki_the recent development of network topology is not so active, and it would be really great if we have more active contributions :-)16:52
rbertramjohn-davidge: yeah - just thinking of novices16:52
amotoki_in addition, we can switch both panels.16:52
david-lyleI think the first blueprint should target updating/replacing network-topology16:52
david-lylewe can hash out the interaction details in the blueprint process16:53
doug-fishyeah good approach.  this is really cool and would be a great improvememt16:53
david-lylethen perhaps use that foundation for generating heat templates, if there is desire to do so by the developers16:53
robcresswelldavid-lyle: Sounds like a good start to us. We're really keen on getting community input on how it would be useful.16:54
robcresswellWe'll work on a blueprint16:54
rbertramHow easy is it to install as-is, so people can play with it hands-on?16:54
david-lylemight make a good landing page, once it's in16:54
john-davidgedavid-lyle: That sounds like a sensible place to start.16:54
*** pc_m has joined #openstack-meeting-316:54
david-lyleI always wanted a more visual landing page16:54
robcresswellrbertram: https://github.com/CiscoSystems/curvature16:54
sambettsrbertram: The README on that github should get you up and running ^^16:55
robcresswellIts straightforward, but currently uses Ruby16:55
david-lylenetwork topology just didn't quite get there16:55
john-davidgedavid-lyle ++16:55
amotoki_+116:55
*** Longgeek has quit IRC16:55
robcresswellOn the subject of network topology, is that why we still include jquery-ui?16:55
robcresswellI was wondering why we still have jquery-ui and bootstrap16:56
david-lyleI think there may be another reason, but it escapes me16:56
david-lylea date picker maybe16:56
rbertramyeah16:56
*** sarob has joined #openstack-meeting-316:56
john-davidgeGreat, well as long as there's interest that gives us something to work towards. Once there's some working code up for review we can talk more about where exactly it will all fit in.16:56
robcresswelldavid-lyle: Fair enough. I was wondering about getting rid of it. It seems an unnecessary requirement, doesnt it?16:57
rbertrambut I thought there were other things16:57
david-lylejohn-davidge: please write up a blueprint and target it to k-2 or k-316:57
robcresswelljohn-davidge: +116:57
john-davidgedavid-lyle: Will do!16:57
amotoki_BTW, there are two hot topics on the dev list: JS tooling (especially dependency management) and horizon/dashboard split.16:57
david-lylerobcresswell: well the calendar date picker would need a replacement16:57
amotoki_I would like to see who leads the work, and they are good candidates of next week topics.16:57
amotoki_(regarding splitting, mrunge is leading the work already)16:58
david-lyleamotoki_: indeed, I wanted the distro vs js developer debate to drift toward a mutually acceptable solution16:58
robcresswelldavid-lyle: Yes, understood. I just meant the library seems a bit much for a date picker.16:58
robcresswelldavid-lyle: I'll look into it.16:58
david-lylerobcresswell: oh, absolutely16:58
david-lyleno argument here16:59
david-lyleamotoki_: for the split, I think we need mrunge here to discuss16:59
rbertramrobcresswell: are you just asking why we have jquery-ui? or also why we have bootstrap?16:59
david-lylemaybe with the offset meeting times16:59
amotoki_david-lyle: no doubt on that.16:59
david-lylewhich is another thread17:00
robcresswellrbertram: Why we have both. I thought they achieved similar things.17:00
david-lyleplease fill out the doodle17:00
*** emagana has quit IRC17:00
david-lylealso on the mailing list17:00
david-lyletime's up, thanks everyone!17:00
david-lyle#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Nov 18 17:00:29 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-11-18-16.01.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-11-18-16.01.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-11-18-16.01.log.html17:00
pballandhello17:00
*** tzumainn has left #openstack-meeting-317:00
*** pc_m has left #openstack-meeting-317:00
*** robcresswell has left #openstack-meeting-317:00
*** emagana has joined #openstack-meeting-317:00
pballand#startmeeting CongressTeamMeeting17:00
openstackMeeting started Tue Nov 18 17:00:49 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:00
*** doug-fish has left #openstack-meeting-317:00
openstackThe meeting name has been set to 'congressteammeeting'17:00
*** vishwanathj has joined #openstack-meeting-317:00
*** clu_ has left #openstack-meeting-317:01
*** Sanjay has left #openstack-meeting-317:01
pballandthinrichs is out this week, so I will be running the meeting17:01
*** tmazur has quit IRC17:01
pballandanyone around?17:01
sarobMorn17:01
*** rdopiera has left #openstack-meeting-317:01
*** lhcheng_ has left #openstack-meeting-317:01
*** jwy has joined #openstack-meeting-317:01
*** jasonsb has joined #openstack-meeting-317:01
*** TravT has joined #openstack-meeting-317:02
pballandhi sarob17:02
*** jpich has left #openstack-meeting-317:02
pballandwelcome back17:02
sarobThx17:02
*** kudva has joined #openstack-meeting-317:02
*** sambetts has left #openstack-meeting-317:02
*** akrivoka has left #openstack-meeting-317:02
*** absubram__ has quit IRC17:02
banixhi17:02
*** TravT has left #openstack-meeting-317:02
pballandbanix: hi17:03
jasonsbhallo17:03
kudvahi17:03
pballandwelcome everyone17:03
pballandI’ll go ahead and kick things off with an update from the administrative side17:03
*** s3wong has joined #openstack-meeting-317:04
pballandat the summit, we discussed several blueprints and requested they be submitted by last friday17:04
*** bpokorny has joined #openstack-meeting-317:04
pballandthere has been quite a bit of activity here17:04
pballand#link https://blueprints.launchpad.net/congress17:04
*** emagana has quit IRC17:05
sarob24 by last night17:05
*** tqtran has joined #openstack-meeting-317:05
*** tqtran has left #openstack-meeting-317:05
pballandthinrichs couldn’t make it today, but he submitted numerous blueprints, and there are a lot of specs for review17:05
*** gary-smith has left #openstack-meeting-317:05
pballand#link https://review.openstack.org/#/q/status:open+congress-spec,n,z17:05
pballandif you comitted to add a blueprint and haven’t yet done so, please push it asap17:06
pballandlets get a quick status update from around the room17:06
*** MaxV has quit IRC17:06
*** jcoufal has quit IRC17:07
pballandwho wants to go first?17:07
pballandsarob: mind giving an update?17:08
*** jwy has quit IRC17:08
*** rbertram is now known as rbertram_afk17:08
sarobSure17:08
*** jwy has joined #openstack-meeting-317:08
sarobWe met with a lot of people over the summit17:09
sarobThe two follow up deep dives17:09
*** rayv has joined #openstack-meeting-317:09
sarobI am now following up with what commitments17:09
*** Steven___ has joined #openstack-meeting-317:10
sarobPeople and companies can make to the kilo release17:10
sarobOf congress17:10
sarobIf you haven't heard from me by mid week17:10
sarobPlease reach out17:11
sarobSo we have a gauge of how much work we can get17:11
sarobDone this release cycle17:11
sarobThat's it for me17:12
pballandok, thanks17:12
banixI did a few code reviews. was looking at the specs and I think the priority of blueprints need to be set so one can get a better idea about them17:12
pballandbanix: agreed - the push last week was to get the bluprints published, and now it will be on reviewing and prioritizing them17:13
pballandideally, we would have the blueprints before the summit, but we are a week or two behind17:13
*** krykowski has quit IRC17:13
sarobSeems like the summit design etherpad17:14
pballandI don’t that that is a bad thing at this level or project maturity, however17:14
sarobIs a good place to hash out17:14
sarobPriorities17:14
*** crobertsrh has quit IRC17:14
sarobSome of the bp are there but needs an update17:15
*** johnma has joined #openstack-meeting-317:15
pballandbanix: id the challenge that there are too many to look at/understand, or just you don’t know where your time would be best spent?17:15
*** johnma has left #openstack-meeting-317:15
banixthe latter; i think it wont be bad to have ptl ;) go through them and assign a priority to start with17:16
banixof course the priorities can change but having an initial priority will give an structure to what is there and identify major (and less major) areas to work on17:16
pballandbanix: agreed - I think its reasonable to have that by next week17:17
pballand(since thinrichs isn’t here to defend himself, I’ll go ahead and assign that to him ;) )17:17
*** baoli has quit IRC17:17
jasonsbbanix: i think this is also a function of how many people are working on them per sarob's point17:17
sarobBanix what's yours17:18
pballand#action PTL to prioritize blueprints by 11/25 meeting, pballand to assist17:18
kudvabanix: prioritizing will also depend on who will be working on coding those, and with expertise on them no?17:18
banixpballand: thanks. I am a bit out of the loop as I had to take several weeks off work for personal reasons and had to cancel my trip to the summit so others may have a better handle of what is what17:18
pballandbanix: do you have any blueprints to add, or any other updates?17:18
*** ndillon has joined #openstack-meeting-317:18
banixno that’s it for me for now17:19
*** Steven___ has quit IRC17:19
*** stevenld has joined #openstack-meeting-317:19
pballandbanix seems to have left17:20
banixpballand: no just responded17:20
pballandok, thanks banix17:20
pballandin case you missed it, all of the notes from the summit are in the etherpad: https://etherpad.openstack.org/p/par-kilo-congress-design-session17:21
*** alexsyip has joined #openstack-meeting-317:21
pballandjasonsb: mind giving an update next?17:21
jasonsbsure17:22
jasonsbi don't have too much.  working on getting something set up with security people to discuss congress17:22
jasonsbtry to have something this week17:22
jasonsbalso want to thank arosen for generous time last week to go through some QoS things17:23
jasonsbbesides that i had a question for the end: murano integration and the recent keystone policy post to the ML17:23
*** krykowski has joined #openstack-meeting-317:23
jasonsbare they solving different problems or same17:24
rayvHello my name is Ray Valdez and I am interested in contributing to congress  with respect to security.17:25
jasonsbthats it for me17:25
*** arosen has joined #openstack-meeting-317:25
pballandjasonsb, lets give kudva a chance for a status update, and then we can get in to that17:25
arosenwhoops sorry i'm late. Was thinking it was still at 10am still x.x17:25
pballandrayv: hello and welcomed17:25
pballandkudva: mind giving an update?17:26
pballandrayv: would you mind giving a quick intro after kudva?17:26
kudvaI started some work on ceilometer integration but a few weeks had to drop it.17:27
kudvaWill pick it up again and submit something by next week.17:27
kudvaalso, workign with a colleague in security to develop a blueprint17:28
rayvI am from IBM Research and work in the area of secure systems17:28
pballandkudva: great - there has been some work ongoing with the ceilometer plugin, and we met with the team in Paris17:28
pballandwhat specific features are you working on?17:29
kudvapballand: would llike to get an update on that17:29
*** amotoki_ has quit IRC17:29
kudvapballand: I was looking to see how alarms may be used to communicate between congress and ceilometer17:30
pballandI don’t know the specifics on the driver work - but there are three patches in code review17:30
kudvapballand: will look, thanks17:30
pballandfrom the team, the way we are polling aggregated stats is inefficient with the current implemenation, and alarms won’t help17:31
pballandceilometer is looking at improving the efficiency of aggregation in this release17:31
pballandother than that, I would recommend reaching out wo Pierre ettori and Madhu Mohan for details on their patches17:31
kudvapballand: okay, will do that.17:32
pballandarosen: do you have any updates to share?17:33
arosenpballand:  sure17:33
arosenOn my end the CI has been failing over the last day. Unfortunately, a change merged into devstack that broke anyone using precise as a slave. The devstack fix (https://review.openstack.org/#/c/135163/) is now in the process of merging so hopefully we should be up and running shortly.17:34
arosen I'm also working on refactoring the base datasource framework which should hopefully improve a number of things. Here's a WIP patch for that work: https://review.openstack.org/#/c/135099/17:34
arosenHere's the blueprint i have for the specs refactoring work: https://review.openstack.org/#/c/134420/17:35
*** dboik_ has quit IRC17:35
arosenthat's all from me unless anyone wants to talk about this.17:35
*** dboik has joined #openstack-meeting-317:35
pballandthanks arosen17:35
pballandrayv: what brings you to the congress project?17:36
rayvI am interest in security policy enforcement17:36
*** sarob has quit IRC17:37
*** dboik has quit IRC17:37
*** sarob has joined #openstack-meeting-317:37
pballandfantastic - do you have something in particular you are looking to contribute?17:37
rayvI have a simple blueprint that I would like to implement as starting point, isolating physical systems for tenants.17:39
*** jwy has quit IRC17:39
*** yamamoto has joined #openstack-meeting-317:39
*** jwy has joined #openstack-meeting-317:39
pballandrayv: I don’t recall seeing that - have you submitted it to launchpad and/or gerrit?17:40
rayvI haven't yet,  I will work with kudva to submit.17:40
pballandok, fantastic17:41
pballandhaving example use cases that others can follow is great for the project - I’m excited to see how it goes17:42
pballanddid I miss anyone with status updates?17:43
*** jwy has quit IRC17:43
alexsyipI have been working on a parent-key relation for datasource drivers.17:43
pballand(we still have jasonb’s question)17:43
alexsyipI have a change on gerrit that more or less works, but I need to work on it some more.17:43
*** jwy has joined #openstack-meeting-317:43
alexsyipAaron is using it for the glance driver work.17:44
alexsyipI’m also working on a blueprint/spec for a heat driver.17:44
alexsyipI should have something today for that.17:44
*** yamamoto has quit IRC17:44
*** baoli has joined #openstack-meeting-317:45
alexsyipThat’s all.17:45
pballandalexsyip: thanks17:45
*** safchain has quit IRC17:45
*** rbertram_afk is now known as rbertram17:45
jwyi'll give updates on the horizon items before i drop out of the room again (internet is being flaky)17:46
pballandok, I’m going to open the floor to jasonsb, and any other topics that people want to bring up17:46
*** otherwiseguy has quit IRC17:47
jwyfinishing up the spec/bp for creating policies in horizon17:47
jwyand rajdeep is still working on adding view of data source tables17:48
jwyjasonb: you had suggested bip.io in the kilo etherpad for creating policies - wondering if you had specific thoughts on that?17:49
jasonsbjwy: no specific thoughts.  i was going to attempt to put something together for a POC17:50
jasonsbjwy: alas, i got lazy last week17:50
jwyhaha ok17:50
jasonsbjwy: i will try to put together something for a demo17:50
jwycool17:51
pballandjasonsb: were you referring to this keyston emai: http://osdir.com/ml/openstack-dev/2014-11/msg01191.html ?17:52
jasonsbyes17:54
jasonsbthats the one17:54
pballandI know thinrichs was working on doing something similar in Congress - injest all the RBAC config files, and answer questions similar to those in the eimail17:54
pballand*email17:54
pballandto me, this seems like an appropriate problem for Congress - what do others think?17:55
jasonsblooked kind of like an invitation, but i didn't sit in on any of the keystone discussions17:56
jasonsbso i was just curious if anybody had more context17:56
*** cbader has quit IRC17:57
pballandthinrichs and I were too swamped to attend any keystone sessions , unfortunately17:57
*** cbader has joined #openstack-meeting-317:57
pballandit definitely seems like something we should engage with over the mailing list17:57
*** emagana has joined #openstack-meeting-317:59
pballandonly 2 more minutes - any last minute comments to squeeze in?17:59
alexsyipI agree.  Tim has already started working on something for this.  The last time the openstack list had a discussion about it, Tim was involved.18:00
alexsyipI’ll let him know there’s more activitiy on the keystone list.18:00
*** kudva has quit IRC18:00
pballandthanks alexsyip18:01
pballandthanks everyone for joining18:01
pballandhave a great week!18:01
jasonsbbye18:01
banixbye18:01
pballand#endmeeting18:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:01
openstackMeeting ended Tue Nov 18 18:01:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-11-18-17.00.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-11-18-17.00.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-11-18-17.00.log.html18:01
*** vishwanathj has quit IRC18:01
*** rayv has quit IRC18:02
*** tsufiev has left #openstack-meeting-318:04
*** ndillon has left #openstack-meeting-318:05
*** evgenyf has quit IRC18:06
*** ivar-lazzaro has joined #openstack-meeting-318:07
*** rajdeep has joined #openstack-meeting-318:08
*** jacalcat has left #openstack-meeting-318:09
*** jwy has left #openstack-meeting-318:09
*** dawood has joined #openstack-meeting-318:09
*** otherwiseguy has joined #openstack-meeting-318:11
*** dawood has quit IRC18:12
*** sergef has quit IRC18:15
*** SridharRamaswamy has joined #openstack-meeting-318:15
*** jasonsb has left #openstack-meeting-318:15
*** pballand has quit IRC18:15
*** rajdeep has quit IRC18:18
*** sergef has joined #openstack-meeting-318:21
*** dawood has joined #openstack-meeting-318:23
*** pballand has joined #openstack-meeting-318:24
*** nelsnelson has quit IRC18:26
*** nelsnelson has joined #openstack-meeting-318:27
*** LouisF has joined #openstack-meeting-318:30
*** sergef has quit IRC18:30
*** dawood has quit IRC18:30
*** bpokorny_ has joined #openstack-meeting-318:32
*** SridharRamaswamy has quit IRC18:33
*** dboik has joined #openstack-meeting-318:34
*** bpokorny has quit IRC18:35
*** ycombinator_ has joined #openstack-meeting-318:38
*** asahlin has quit IRC18:42
*** sergef has joined #openstack-meeting-318:43
*** bpokorny has joined #openstack-meeting-318:45
*** peristeri has quit IRC18:48
*** bpokorny_ has quit IRC18:48
*** sergef has quit IRC18:49
*** stevelle has joined #openstack-meeting-318:49
*** markmcclain has joined #openstack-meeting-318:51
*** markmcclain has quit IRC18:51
*** markmcclain has joined #openstack-meeting-318:52
*** peristeri has joined #openstack-meeting-318:52
*** SridharRamaswamy has joined #openstack-meeting-318:53
*** Radu_ has joined #openstack-meeting-318:55
*** terrylhowe has joined #openstack-meeting-318:56
*** dboik_ has joined #openstack-meeting-318:58
*** mwang2 has joined #openstack-meeting-318:58
*** briancurtin has joined #openstack-meeting-318:59
briancurtinhey all, python-openstacksdk getting started19:00
briancurtinBrian Curtin19:00
*** Radu_ has left #openstack-meeting-319:01
*** dboik has quit IRC19:01
terrylhoweTerry Howe, HP19:01
sigmavirus24Ian Cordasco, Rackspace19:01
stevelleSteve Lewis, Rackspace19:01
*** Ark has joined #openstack-meeting-319:01
sigmavirus24briancurtin: did you start the meeeting?19:01
*** emagana has quit IRC19:01
briancurtin#startmeeting python-openstacksdk19:02
openstackMeeting started Tue Nov 18 19:02:07 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
sigmavirus24s/et/t/19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:02
openstackThe meeting name has been set to 'python_openstacksdk'19:02
*** Ark is now known as Guest7783019:02
briancurtinnow i did!19:02
sigmavirus24:D19:02
*** jamielennox has joined #openstack-meeting-319:02
briancurtinanyways, if jamielennox or dtroyer come in, cool, but let's go19:03
briancurtina couple of these are quick19:03
jamielennoxo/19:03
*** emagana has joined #openstack-meeting-319:03
*** krykowski has quit IRC19:03
briancurtinif anyone has a few minutes to check out the switch from manual limit/marker to an iterator, that would be awesome: https://review.openstack.org/13410519:03
* dhellmann arrives late19:04
briancurtinwe also had sigmavirus24's entry_points review at https://review.openstack.org/131314 - however, our talk at the summit leans toward this not being something we should pursue, right?19:04
briancurtin#topic entry_points to load services - https://review.openstack.org/13131419:04
*** openstack changes topic to "entry_points to load services - https://review.openstack.org/131314 (Meeting topic: python-openstacksdk)"19:04
sigmavirus24briancurtin: that's what I thought, but there seem to be mixed opinions19:04
sigmavirus24I'm on the fence and given the somewhat conflicting opinions I've not abandoned it, yet19:05
*** krykowski has joined #openstack-meeting-319:05
terrylhoweI think jamielennox ’s points against entry points were good, but we still need to do something19:05
terrylhoweI was thinking there would be maybe a dict to pass UserPreference constructor that would override and/or add services19:06
sigmavirus24That said, I'm also liable to be very busy for the next couple weeks for personal reasons so if someone wants to commandeer that patchset, by all means, go ahead19:06
jamielennoxi see the need for them, i just think we need to make it clear that it's not part of our lib or we confuse users when services aren't present19:06
jamielennoxfor example anything in openstack.ext.* is fair game19:07
jamielennoxs/services/libraries19:07
dhellmannjamielennox: I'm not sure I understand, are there notes from that discussion? I hate to make you rehash it here19:08
terrylhoweI was thinking maybe create pref = user_preference.UserPreference({‘lbaas’: ‘hp.lbaas’})19:08
dhellmannthe comment on the patch says something about the initialization order of the preferences object and command line parsing, but I didn't think we were building a command line tool in the sdk19:08
terrylhowesomething like that if someone wanted to add a service19:08
dhellmannso the application developer would have to explicitly add the services?19:09
terrylhoweI guess so19:09
dhellmannyou can still do that with entry points, fwiw, using the NamedExtensionManager or EnabledExtensionManager19:09
jamielennoxdhellmann: that was a fairly informal discussion with just the few of us so probably not. My concern with allowing arbitratry entry points on the main client object is the UX of a user not having the designate library installed for example, or dealing with versions of those libraries19:09
dhellmannah, ok, sure -- we'd have to define an API for those plugins to adhere to in any case, so we could take those factors into account19:10
*** krykowski has quit IRC19:10
briancurtini dont think  you should have to enable services manually - we just have to figure something out between load up everything we have (which may not be in your service catalog), and nothing19:10
jamielennoxif we don't know if it's going to be installed, or we don't control the functions in it i'd prefer to just namespace it a little so it's obviously an addition to the library19:10
dhellmannthe alternative is to do some sort of thing where the caller tells us how to import a module, and that is just so ripe for errors that are hard to debug I hate to think of the usability issues19:11
jamielennoxbriancurtin: i agree19:11
jamielennoxdhellmann: yea, that's not a good approach19:11
*** Guest77830 has quit IRC19:12
*** crobertsrh has joined #openstack-meeting-319:12
*** ycombinator_ has quit IRC19:12
dhellmannhow do we decide when something moves between the special namespace and the default?19:12
terrylhoweso are you guys saying we could use entrypoints if the namespace is openstack.ext?19:12
jamielennoxas i said the best i've though of was a ext obj, which had not much more than a __getattr__ that hands off to a NamedExtensionManager from that value19:12
terrylhowethe only thing is we have to do this before we have a service catalog19:12
briancurtinah, yeah19:12
dhellmannthe actual plugin namespace is invisible to everyone except the developer, so I'm not sure that name makes a lot of difference. I assumed you meant that the sdk objects would treat extensions somehow differently from builtins19:12
dhellmannit seems like deciding which plugins to load is independent of the service catalog, isn't it?19:13
sigmavirus24jamielennox: so something like openstack.services.builtin vs openstack.services.ext?19:14
jamielennoxdhellmann: i would think so, you just get an exception if you don't have the entry in SC19:14
dhellmannjamielennox: or we could disable the plugin once we do have the service catalog19:14
dhellmannbut yeah, and exception is probably better since it's an opportunity to explain what's going wrong instead of just having a feature disappear19:14
terrylhowewell, the service catalog is used to create the Connection class, it just wouldn’t have the attribute19:15
jamielennoxsigmavirus24: i was more thinking with an object, c = openstack.Connection()   c.identity vs c.ext.dns19:15
briancurtinfail as early as we can, but no earlier19:15
*** ycombinator_ has joined #openstack-meeting-319:15
dhellmannjamielennox: how do we decide when c.ext.dns is "good enough" to become c.dns?19:15
jamielennoxdhellmann: i think it's a matter of explaining the failure, if the entry isn't in the catalog and you get a NoCatalogEntryExc as opposed to a AttributeException for it just not being there19:16
jamielennoxdhellmann: i was thinking when it moved into the tree19:16
*** igordcard has quit IRC19:16
*** LouisF has quit IRC19:16
jamielennoxdhellmann: at least initially the point was to have no external deps19:16
dhellmannjamielennox: changing the name of the thing when it moves into the tree is just going to break any apps that use it, though19:16
dhellmannwe don't need external dependencies to "mix" access to the plugins, do we? I think I don't understand the concerns, still.19:17
jamielennoxthere's a transition period anyway where you no longer have to install the external library, if the library was still available it would still work under c.ext19:18
dhellmannyeah, but then you have an opportunity for 2 versions of the same thing to be present as well19:18
jamielennoxmy concern is more for when the dns people add a bunch of functions we don't want to support in SDK, the project graduates and we are left supporting all those functions19:18
briancurtini would think of something like c.ext for where rackspace non-standard auth goes, instead of something like a designate lib19:19
*** baoli has quit IRC19:19
dhellmannjamielennox: why would we not support the full API?19:19
jamielennoxit's not the API that's the problem - you should see the amount of random crap that gets thrown in these client libraries19:20
dhellmannI guess you're anticipating an incubation period for a library that would be outside of the sdk tree, and then at some point that code moving into the main tree?19:20
dhellmannfor oslo that graduation step is a trigger for us to re-evaluate the API of the module and clean it up19:21
briancurtinall we should be concerned with, at least at the start, is supporting the REST API. conveniences on top of that, if that's what youre talking about, seem like the "even higher level"19:21
briancurtin(where 'even higher level' is that shade-like lib)19:21
dhellmannyeah, I would expect something like that to be built on top of this, rather than using this extension mechanism19:22
*** crobertsrh has left #openstack-meeting-319:22
sigmavirus24So I think I understand jamielennox's POV but I'm not sure I agree with it. If we don't want to immediately include code of incubated libraries then why not give openstack projects the ability to use the entry points without having to do c.ext19:22
dhellmannso maybe we just say "this is how you make a plugin to support your rest API" and then later we have other plugins for higher-level functions19:22
sigmavirus24I was thinking of c.ext much the same was as dhellmann so *shrug*19:22
jamielennoxanyway, it's just my opinion and not one i need to hold to firmly, i'm just concerned that given our goal is to make a nice API if we let everybody join with there own entrypoint we have no control over that and for those that are not intimitely familiar with the library and how entrypoints work we end up in a mess of what is supported and not19:23
terrylhoweWhat if the user had to manually say ‘allow plugins’ and we’d look at entry points19:23
*** wuhg has quit IRC19:23
*** otherwiseguy has quit IRC19:23
dhellmannthe plugins we're talking about are one per service, or one per version of a service, right?19:24
sigmavirus24terrylhowe: like c = Connection(load_plugins=True)?19:24
terrylhoweyes and yes19:24
terrylhoweone per service19:24
jamielennoxi was trying to visualize this from a coming to openstack and possibly to python what is intuitive19:24
dhellmannjamielennox: I can see your point, but I'm worried that segregating the plugins into 2 groups will make the SDK harder for an app developer to use19:25
jamielennoxplugins into 2 groups? was thinking purely what we maintain (which should be almost everything that is graduated) vs what we don't. What is internal isn't (at least currently) a plugin19:26
dhellmannjamielennox: ah, ok, I thought those would just go into a different namespace19:26
terrylhoweso, if load_plugins=True we don’t override existing services19:27
jamielennoxdhellmann: that's at least not currently the plan, we were talking entrypoints only for out of tree19:27
dhellmannok, that wasn't my impression from the patch just mentioned, sorry for the confusion19:27
jamielennoxi may be wong here19:28
dhellmannterrylhowe: "override existing services"?19:28
terrylhowewell, you couldn’t override out compute services19:28
dhellmannyeah, I don't think we ever want to allow that, do we?19:28
jamielennoxah, that patch loads everything via entrypoint - sorry19:29
dhellmannjamielennox: right, and I like the "pick one way and do it" approach19:29
jamielennoxas a preference i'd say lets not use entrypoints for things we can call directly in python, i don't see why we'd want to let anyone change those values19:30
*** jacalcat has joined #openstack-meeting-319:30
briancurtinagreed there19:31
dhellmannyeah, I guess the point is to say "here's how we load the services we know about" and then your code doesn't have 2 separate paths for setting things up19:31
*** SridharRamaswamy has quit IRC19:31
dhellmannif we don't want plugins because we think we'll end up with a lot of crap, let's just not use them at all to begin with19:31
*** emagana has quit IRC19:32
dhellmannI'd much rather see a well-thought-out sdk that works with a small number of services and tackle the extension issue in a later rev19:32
*** emagana has joined #openstack-meeting-319:32
jamielennoxdhellmann: ++19:32
jamielennoxpunt on extensions until someone really wants them19:33
briancurtinworks for me19:33
dhellmannand at that point we'd have some sense of our requirements to be able to do them more cleanly19:33
dhellmannI personally have less concern about the crap issue, since anything out of tree is going to have to be installed separately and someone else is going to maintain it, but I'm willing to wait and see19:34
*** emagana has quit IRC19:34
*** SridharRamaswamy has joined #openstack-meeting-319:34
*** emagana has joined #openstack-meeting-319:34
briancurtinsince we're a little over halfway through, moving on to get to a few other things19:34
briancurtin#topic make prop access return None by default instead of raise AttributeError - https://review.openstack.org/13463219:35
*** openstack changes topic to "make prop access return None by default instead of raise AttributeError - https://review.openstack.org/134632 (Meeting topic: python-openstacksdk)"19:35
briancurtinterrylhowe +2'ed that, but it could use looks from others19:35
dhellmanndo we want to return None or raise a more specific exception for that case?19:35
dhellmannI assume some properties can have None as a value?19:36
*** emagana has quit IRC19:36
stevelledhellmann: I was considering that case but haven't found any useful way yet19:36
briancurtinthat's one concern, but having it raise an attribute is kind of ugly to work with19:36
*** emagana has joined #openstack-meeting-319:36
terrylhoweIf someone cared, that ould ‘attr’ in resource19:36
dhellmannbriancurtin: I'm concerned this is going to hide errors caused by typos19:37
dhellmannvalues would always come back None instead of a NoSuchProperty error19:37
briancurtinthe current one definitely hides typos unless you're very specific about the try/except19:38
dhellmannthat try:except block in security_group.py should probably be inside the for loop instead of outside, but otherwise that doesn't look bad to me19:38
dhellmannyeah, we definitely need a different exception type19:38
dhellmannNoSuchPropertyError should subclass AttributeError probably19:39
jamielennoxso i understand that AttributeError is weird because we defined the attribute with prop, i think None is a bad default and we should make a new exception19:39
briancurtini just think if you want to check if an object has a header value set, you just access and either get back a value or not, like how you do dict.get(key, default) instead of try: dict[key] except KeyError19:39
jamielennoxbriancurtin: so add a default=None to the prop()19:40
jamielennox?19:40
briancurtini had done that a long time ago but either abandoned it or got rejected, but id like to revisit that, i think19:40
dhellmannthat might work19:40
terrylhowethis code would be accessed in the resource.prop case, so it is a little more typo proof19:40
jamielennoxi'd be happy with default= for that case19:41
briancurtinso perhaps two things: betteer exception, an optional default return value19:41
dhellmannso if I type "resource.porp" I'll get an AttributeError but if the person who set up "resource.prop" made a type I will get None?19:41
dhellmanns/type/typo19:41
dhellmannheh19:41
dhellmannif I understand correctly, then having a default for the property makes more sense now so I'm OK with returning None19:42
*** reed has quit IRC19:42
*** matrohon has joined #openstack-meeting-319:42
terrylhoweresource.porp wouldn’t hit this code, only resource.prop19:43
briancurtinare we actually ok setting None as *the* default return value, or just an user-enabled one19:45
briancurtinalthough, i think i would just want to set every single prop ever to be default=None, defeating the purpose of it being user-set (since we're the user in this case)19:45
stevelleis the value proposition of a default to really indicate the property by that name exists?19:46
stevelleotherwise we might be discussing another requirement for Resource19:46
dhellmannbriancurtin: I'm ok having None as the default default19:47
briancurtini think so. i'd like to be able to do "obj.read_ACL" and i either get the ACL back or something telling me it exists but isn't actually set, so None19:47
dhellmannstevelle: isn't the fact that the developer declared the property an assumption that the value will be there?19:47
jamielennoxyea, that could work, still expose default= on the prop but default default is None19:47
dhellmannjamielennox: ++19:48
briancurtinso i just have to shift https://review.openstack.org/#/c/134632/ around a bit then and we're good?19:48
jamielennoxif you want to get tricky later if isinstance(default, Exception): raise else return19:48
dhellmannbriancurtin: I think I'm happy with it as is, if you add the default handling in another patch19:49
briancurtincool19:49
dhellmannif there are no objections, I'll approve it now?19:49
stevellenone here19:50
dhellmannjamielennox?19:50
jamielennoxthat's fine19:50
dhellmannok, +2a19:50
briancurtin#topic jenkins/swift high level views19:51
*** openstack changes topic to "jenkins/swift high level views (Meeting topic: python-openstacksdk)"19:51
briancurtinterrylhowe: what's needed to proceed with the jenkins example and related code? anything?19:51
terrylhoweI have two features in my jenkins thing that need to be pulled out into their own patches19:51
terrylhoweswift could be rebased on master now19:52
briancurtinyeah i need to do that, but i also think im going to start breaking out into other reviews for later things so i dont smash too much in this supposed "first cut"19:52
briancurtinonce we have these couple of high-level interfaces in, how do we want to go about building them out? do we just go a few different ways, reconvene soon, and see what works? bulk up the examples, do some blog posts, and try to get people to bang on the interfaces to see what they like?19:55
*** matrohon has quit IRC19:55
terrylhoweI’d like to try a high level and thing POC with OSC19:56
terrylhowes/thing/thin19:56
terrylhoweit’d be nice to have the thin code in master even if we scrap it later on just for the POC19:57
briancurtini'll check out that review you have up for it19:57
terrylhowe2 minutes.  Unicode?19:58
briancurtinone last question with 2 minutes on the clock: in some of my toying with the high-level swift interface, i started wondering if we need to make a decision on unicode/bytes, or if we just pass through what we got and return what we received?19:58
briancurtinyep19:58
dhellmannit seems like the answer to that depends on the API we're calling, doesn't it?19:59
briancurtinit came up because i was trying to determine if you gave me a Container object or a container name, so then i was checking against six.text_type, then i wondered if that's right, or if we should just act as a "you gave me some Python object that is a name, we send that name"19:59
dhellmannwe can pass the container instance and its name to the same method and that's supposed to work?20:00
briancurtindhellmann: it does, but i guess i havent seen any details around saying "this property must be utf8" or somethig, but i havent dug super far20:00
briancurtindhellmann: i'm toying with something high-level, not set in stone yet20:01
dhellmannok20:01
* dhellmann has to run to the tc meeting and doesn't have a good answer for that one :-/20:01
briancurtindhellmann: it's kind of wonky for now, but i wanted to easily be able to create an object in a container, whether that container is a container.Container or "mycontainer"20:01
briancurtini guess we'll toy with it and see where it goes, don't need to be rigid up front, i think20:01
*** john-davidge has quit IRC20:02
briancurtinanyways, that's time, so...20:02
briancurtin#endmeeting20:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:02
dhellmannmaybe unicode(container.Container) should return its name and then you can use that?20:02
openstackMeeting ended Tue Nov 18 20:02:22 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-11-18-19.02.html20:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-11-18-19.02.txt20:02
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-11-18-19.02.log.html20:02
briancurtindhellmann: ah, maybe!20:02
*** Ark has joined #openstack-meeting-320:03
*** Ark is now known as Guest2255220:03
*** Sukhdev has joined #openstack-meeting-320:03
*** matrohon has joined #openstack-meeting-320:17
*** wendar_ is now known as wendar20:22
*** alexpilotti has quit IRC20:23
*** alexpilotti has joined #openstack-meeting-320:24
*** ycombinator_ has quit IRC20:24
*** matrohon has quit IRC20:25
*** alexpilotti has quit IRC20:25
*** sarob has quit IRC20:26
*** matrohon has joined #openstack-meeting-320:28
*** matrohon has quit IRC20:29
*** alexpilotti has joined #openstack-meeting-320:38
*** alexpilotti has quit IRC20:39
*** sarob has joined #openstack-meeting-320:39
*** alexpilotti has joined #openstack-meeting-320:40
*** alexpilotti has quit IRC20:41
*** mattfarina has joined #openstack-meeting-320:42
*** yamamoto has joined #openstack-meeting-320:42
*** alexpilotti has joined #openstack-meeting-320:42
*** hurgleburgler has quit IRC20:43
*** alexpilotti has quit IRC20:43
*** dboik_ has quit IRC20:44
*** pballand has quit IRC20:44
*** dboik has joined #openstack-meeting-320:44
*** alexpilotti has joined #openstack-meeting-320:45
*** alexpilotti has quit IRC20:46
*** alexpilotti has joined #openstack-meeting-320:47
*** yamamoto has quit IRC20:47
*** alexpilotti has quit IRC20:48
*** alexpilotti has joined #openstack-meeting-320:49
*** alexpilotti has quit IRC20:49
*** johnbelamaric has quit IRC20:50
*** johnbelamaric has joined #openstack-meeting-320:50
*** alexpilotti has joined #openstack-meeting-320:51
*** alexpilotti has quit IRC20:51
*** Guest22552 has quit IRC20:51
*** otherwiseguy has joined #openstack-meeting-320:53
*** alexpilotti has joined #openstack-meeting-320:53
*** alexpilotti has quit IRC20:54
*** jamielennox has left #openstack-meeting-320:55
*** alexpilotti has joined #openstack-meeting-320:55
*** devlaps has quit IRC20:55
*** alexpilotti has quit IRC20:56
*** jacalcat has left #openstack-meeting-320:57
*** alexpilotti has joined #openstack-meeting-320:57
*** alexpilotti has quit IRC20:59
*** otherwiseguy has quit IRC21:01
*** otherwiseguy has joined #openstack-meeting-321:03
*** SridharRamaswamy has quit IRC21:05
*** johnbelamaric has quit IRC21:06
*** johnbelamaric has joined #openstack-meeting-321:06
*** devlaps has joined #openstack-meeting-321:07
*** baoli has joined #openstack-meeting-321:08
*** baoli has quit IRC21:09
*** baoli has joined #openstack-meeting-321:10
*** SridharRamaswamy has joined #openstack-meeting-321:10
*** SumitNaiksatam has quit IRC21:11
*** mwagner_lap has quit IRC21:11
*** terrylhowe has left #openstack-meeting-321:18
*** sergef has joined #openstack-meeting-321:27
*** gholler has quit IRC21:28
*** bpokorny_ has joined #openstack-meeting-321:28
*** bpokorny has quit IRC21:31
*** sergef has quit IRC21:37
*** carl_baldwin has quit IRC21:42
*** pballand has joined #openstack-meeting-321:44
*** baoli has quit IRC21:45
*** baoli has joined #openstack-meeting-321:46
*** baoli has quit IRC21:48
*** baoli has joined #openstack-meeting-321:48
*** SumitNaiksatam has joined #openstack-meeting-321:50
*** baoli has quit IRC21:53
*** baoli has joined #openstack-meeting-321:54
*** carl_baldwin has joined #openstack-meeting-321:55
*** banix has quit IRC21:56
*** mattfarina has quit IRC21:58
*** SridharRamaswamy has quit IRC22:00
*** dboik has quit IRC22:00
*** dboik has joined #openstack-meeting-322:02
*** Sukhdev has quit IRC22:03
*** emagana has quit IRC22:05
*** jaypipes has quit IRC22:05
*** emagana has joined #openstack-meeting-322:06
*** emagana has quit IRC22:10
*** baoli has quit IRC22:22
*** otherwiseguy has quit IRC22:22
*** baoli has joined #openstack-meeting-322:22
*** jacalcat1 has joined #openstack-meeting-322:23
*** rbertram has quit IRC22:25
*** sarob has quit IRC22:29
*** jacalcat has joined #openstack-meeting-322:29
*** jacalcat has left #openstack-meeting-322:29
*** otherwiseguy has joined #openstack-meeting-322:31
*** jacalcat1 has quit IRC22:31
*** baoli has quit IRC22:32
*** peristeri has quit IRC22:32
*** baoli has joined #openstack-meeting-322:33
*** banix has joined #openstack-meeting-322:33
*** sarob has joined #openstack-meeting-322:33
*** SridharRamaswamy has joined #openstack-meeting-322:35
*** johnbelamaric has quit IRC22:37
*** cbader has quit IRC22:37
*** baoli has quit IRC22:38
*** emagana has joined #openstack-meeting-322:38
*** baoli has joined #openstack-meeting-322:39
*** johnbelamaric has joined #openstack-meeting-322:39
*** banix has quit IRC22:41
*** sarob has quit IRC22:41
*** johnbelamaric has quit IRC22:43
*** yamamoto has joined #openstack-meeting-322:44
*** sarob has joined #openstack-meeting-322:44
*** jpomero has quit IRC22:46
*** sarob has quit IRC22:48
*** carl_baldwin has quit IRC22:48
*** yamamoto has quit IRC22:49
*** emagana has quit IRC22:50
*** baoli has quit IRC22:50
*** emagana has joined #openstack-meeting-322:50
*** baoli has joined #openstack-meeting-322:51
*** emagana has quit IRC22:55
*** baoli has quit IRC22:57
*** baoli has joined #openstack-meeting-322:57
*** baoli has quit IRC23:00
*** baoli has joined #openstack-meeting-323:00
*** emagana has joined #openstack-meeting-323:03
*** marun has quit IRC23:03
*** jgrimm is now known as zz_jgrimm23:05
*** baoli has quit IRC23:05
*** baoli has joined #openstack-meeting-323:06
*** salv-orlando has quit IRC23:07
*** SridharRamaswamy has quit IRC23:07
*** etoews has joined #openstack-meeting-323:09
*** ChuckC has quit IRC23:11
*** etoews_ has quit IRC23:11
*** baoli has quit IRC23:14
*** baoli has joined #openstack-meeting-323:15
*** banix has joined #openstack-meeting-323:16
*** salv-orlando has joined #openstack-meeting-323:16
*** baoli has quit IRC23:21
*** baoli has joined #openstack-meeting-323:21
*** otherwiseguy has quit IRC23:22
*** salv-orlando has quit IRC23:22
*** jpomero has joined #openstack-meeting-323:23
*** salv-orlando has joined #openstack-meeting-323:25
*** mwang2 has quit IRC23:29
*** wuhg has joined #openstack-meeting-323:31
*** banix has quit IRC23:32
*** dboik_ has joined #openstack-meeting-323:36
*** ChuckC has joined #openstack-meeting-323:37
*** dboik_ has quit IRC23:37
*** SridharRamaswamy has joined #openstack-meeting-323:37
*** sarob has joined #openstack-meeting-323:37
*** dboik has quit IRC23:39
*** xuhanp has joined #openstack-meeting-323:40
*** sarob has quit IRC23:42
*** SridharRamaswamy has quit IRC23:42
*** sarob has joined #openstack-meeting-323:42
*** xuhanp has quit IRC23:43
*** markmcclain has quit IRC23:49
*** emagana has quit IRC23:54
*** emagana has joined #openstack-meeting-323:55
*** etoews has quit IRC23:55
*** amotoki_ has joined #openstack-meeting-323:56
*** SridharRamaswamy has joined #openstack-meeting-323:57
*** amotoki has quit IRC23:57
*** banix has joined #openstack-meeting-323:57
*** emagana has quit IRC23:59

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