Wednesday, 2015-02-04

*** yamamoto has joined #openstack-meeting-300:00
*** yamamoto has quit IRC00:01
*** yamamoto has joined #openstack-meeting-300:02
*** banix has joined #openstack-meeting-300:03
*** sigmavirus24 is now known as sigmavirus24_awa00:07
*** etoews has quit IRC00:07
*** markvoelker has quit IRC00:07
*** alexpilotti has quit IRC00:10
*** thomasem has quit IRC00:10
*** VW has joined #openstack-meeting-300:11
*** VW has quit IRC00:11
*** marun has quit IRC00:11
*** VW has joined #openstack-meeting-300:12
*** igordcard has joined #openstack-meeting-300:16
*** Sukhdev has quit IRC00:16
*** igordcard has quit IRC00:17
*** yamamoto has quit IRC00:17
*** banix has quit IRC00:18
*** s3wong has quit IRC00:18
*** s3wong has joined #openstack-meeting-300:18
*** s3wong has quit IRC00:20
*** carl_baldwin has quit IRC00:33
*** etoews has joined #openstack-meeting-300:33
*** etoews has quit IRC00:39
*** xuhanp has quit IRC00:40
*** stevelle has joined #openstack-meeting-300:48
*** banix has joined #openstack-meeting-300:49
*** markvoelker has joined #openstack-meeting-300:52
*** yamamoto has joined #openstack-meeting-300:53
*** yamamoto_ has joined #openstack-meeting-300:55
*** david-lyle is now known as david-lyle_afk00:57
*** yamamoto has quit IRC00:57
*** wojdev has quit IRC00:59
*** markvoelker has quit IRC01:00
*** marun has joined #openstack-meeting-301:09
*** VW has quit IRC01:09
*** VW has joined #openstack-meeting-301:09
*** marun has quit IRC01:13
*** jpomero has quit IRC01:18
*** markvoelker has joined #openstack-meeting-301:19
*** etoews has joined #openstack-meeting-301:21
*** kitho has quit IRC01:27
*** Piet has quit IRC01:33
*** stanzgy has joined #openstack-meeting-301:37
*** jmanko has joined #openstack-meeting-301:38
*** etoews has quit IRC01:38
*** jmankov has quit IRC01:42
*** jmanko has quit IRC01:42
*** VW has quit IRC01:42
*** jmanko has joined #openstack-meeting-301:42
*** VW has joined #openstack-meeting-301:43
*** VW has quit IRC01:44
*** banix has quit IRC01:46
*** nelsnelson has quit IRC01:49
*** nelsnelson has joined #openstack-meeting-301:51
*** yamamoto_ has quit IRC02:01
*** yamamoto_ has joined #openstack-meeting-302:06
*** bpokorny has quit IRC02:06
*** aleksandr_null has quit IRC02:06
*** etoews has joined #openstack-meeting-302:11
*** aleksandr_null has joined #openstack-meeting-302:11
*** Haomeng has left #openstack-meeting-302:11
*** aleksandr_null has quit IRC02:13
*** VW has joined #openstack-meeting-302:18
*** aleksandr_null has joined #openstack-meeting-302:18
*** alexsyip has quit IRC02:23
*** sigmavirus24_awa is now known as sigmavirus2402:26
*** jckasper has joined #openstack-meeting-302:26
*** sigmavirus24 is now known as sigmavirus24_awa02:27
*** banix has joined #openstack-meeting-302:29
*** salv-orlando has quit IRC02:29
*** etoews has quit IRC02:36
*** VW has quit IRC02:42
*** VW has joined #openstack-meeting-302:43
*** shamail has joined #openstack-meeting-302:47
*** shamail has left #openstack-meeting-302:47
*** tellesnobrega_ has joined #openstack-meeting-303:03
*** eghobo has quit IRC03:04
*** SridharRamaswamy has quit IRC03:20
*** etoews has joined #openstack-meeting-303:33
*** mattgriffin has quit IRC03:35
*** mattgriffin has joined #openstack-meeting-303:40
*** etoews has quit IRC03:40
*** jmankov has joined #openstack-meeting-303:41
*** jmank has joined #openstack-meeting-303:42
*** jmanko has quit IRC03:44
*** jmankov has quit IRC03:45
*** banix has quit IRC03:56
*** sarob has joined #openstack-meeting-304:19
*** Sukhdev has joined #openstack-meeting-304:22
*** julim has quit IRC04:27
*** etoews has joined #openstack-meeting-304:36
*** etoews has quit IRC04:40
*** eghobo has joined #openstack-meeting-304:59
*** david-lyle_afk has quit IRC05:11
*** david-lyle_afk has joined #openstack-meeting-305:11
*** ivar-laz_ has joined #openstack-meeting-305:24
*** qwebirc78548 has joined #openstack-meeting-305:25
*** bradjones has quit IRC05:27
*** qwebirc28104 has joined #openstack-meeting-305:27
*** ivar-lazzaro has quit IRC05:27
*** yamamot__ has joined #openstack-meeting-305:27
*** qwebirc28104 has left #openstack-meeting-305:28
*** ivar-laz_ has quit IRC05:28
*** bradjones has joined #openstack-meeting-305:31
*** yamamoto_ has quit IRC05:31
*** qwebirc78548 has quit IRC05:34
*** etoews has joined #openstack-meeting-305:37
*** sarob has quit IRC05:40
*** mtreinish has quit IRC05:40
*** etoews has quit IRC05:44
*** eghobo has quit IRC05:44
*** ivar-lazzaro has joined #openstack-meeting-305:49
*** killer_prince is now known as lazy_prince05:49
*** mtreinish has joined #openstack-meeting-305:56
*** coolsvap_ is now known as coolsvap05:57
*** terrylhowe has quit IRC05:59
*** markvoelker has quit IRC06:08
*** wojdev has joined #openstack-meeting-306:13
*** enykeev has joined #openstack-meeting-306:17
*** mrmartin has joined #openstack-meeting-306:17
*** ivar-laz_ has joined #openstack-meeting-306:21
*** Sukhdev has quit IRC06:22
*** ivar-lazzaro has quit IRC06:24
*** wojdev has quit IRC06:26
*** tellesnobrega_ has quit IRC06:32
*** tellesnobrega__ has joined #openstack-meeting-306:32
*** markvoelker has joined #openstack-meeting-306:39
*** etoews has joined #openstack-meeting-306:41
*** markvoelker has quit IRC06:43
*** etoews has quit IRC06:45
*** mrda is now known as mrda-away06:47
*** wojdev has joined #openstack-meeting-306:59
*** VW has quit IRC07:00
*** VW has joined #openstack-meeting-307:01
*** ivar-laz_ has quit IRC07:03
*** ivar-lazzaro has joined #openstack-meeting-307:04
*** mrunge has joined #openstack-meeting-307:05
*** wojdev has quit IRC07:09
*** [1]evgenyf has quit IRC07:11
*** obondarev has joined #openstack-meeting-307:11
*** mattgriffin has quit IRC07:14
*** VW has quit IRC07:15
*** VW has joined #openstack-meeting-307:16
*** ivar-laz_ has joined #openstack-meeting-307:16
*** ivar-lazzaro has quit IRC07:19
*** ivar-laz_ has quit IRC07:19
*** VW has quit IRC07:23
*** [1]evgenyf has joined #openstack-meeting-307:23
*** VW has joined #openstack-meeting-307:23
*** VW has quit IRC07:29
*** VW has joined #openstack-meeting-307:29
*** egallen has joined #openstack-meeting-307:36
*** belmoreira has joined #openstack-meeting-307:36
*** egallen has quit IRC07:37
*** VW has quit IRC07:37
*** VW has joined #openstack-meeting-307:38
*** markvoelker has joined #openstack-meeting-307:39
*** markvoelker has quit IRC07:44
*** VW has quit IRC07:46
*** VW has joined #openstack-meeting-307:47
*** VW has quit IRC07:49
*** VW has joined #openstack-meeting-307:50
*** yamamot__ has quit IRC07:52
*** VW has quit IRC07:52
*** VW has joined #openstack-meeting-307:53
*** jcoufal has joined #openstack-meeting-307:54
*** scheuran has joined #openstack-meeting-307:57
*** VW has quit IRC07:58
*** VW has joined #openstack-meeting-307:59
*** VW has quit IRC07:59
*** VW has joined #openstack-meeting-308:00
*** armax has quit IRC08:03
*** egallen has joined #openstack-meeting-308:10
*** VW has quit IRC08:11
*** VW has joined #openstack-meeting-308:12
*** sahid has joined #openstack-meeting-308:12
*** sergef has joined #openstack-meeting-308:17
*** VW has quit IRC08:18
*** VW has joined #openstack-meeting-308:19
*** yamamoto_ has joined #openstack-meeting-308:19
*** egallen has quit IRC08:21
*** devvesa has joined #openstack-meeting-308:22
*** yamamoto_ has quit IRC08:24
*** yamamoto_ has joined #openstack-meeting-308:26
*** VW has quit IRC08:27
*** VW has joined #openstack-meeting-308:27
*** sergef has quit IRC08:27
*** VW has quit IRC08:32
*** mrmartin has quit IRC08:33
*** kozhukalov has joined #openstack-meeting-308:37
*** mrmartin has joined #openstack-meeting-308:37
*** iovadia has joined #openstack-meeting-308:39
*** markvoelker has joined #openstack-meeting-308:40
*** yamamoto_ has quit IRC08:41
*** etoews has joined #openstack-meeting-308:42
*** iovadia has quit IRC08:44
*** markvoelker has quit IRC08:45
*** zz_ttrifonov is now known as ttrifonov08:46
*** etoews has quit IRC08:47
*** MaxV has joined #openstack-meeting-308:49
*** stanzgy has quit IRC08:52
*** matrohon has joined #openstack-meeting-308:54
*** stanzgy has joined #openstack-meeting-308:54
*** JeanBriceCombebi has joined #openstack-meeting-308:56
*** iovadia has joined #openstack-meeting-308:58
*** sergef has joined #openstack-meeting-309:08
*** safchain has joined #openstack-meeting-309:19
*** belmoreira has quit IRC09:21
*** belmoreira has joined #openstack-meeting-309:22
*** igordcard has joined #openstack-meeting-309:27
*** bauzas has quit IRC09:29
*** jckasper has quit IRC09:30
*** bauzas has joined #openstack-meeting-309:30
*** zz_johnthetubagu is now known as johnthetubaguy09:33
*** salv-orlando has joined #openstack-meeting-309:37
*** ttrifonov is now known as zz_ttrifonov09:39
*** zz_ttrifonov is now known as ttrifonov09:40
*** markvoelker has joined #openstack-meeting-309:41
*** ttrifonov is now known as zz_ttrifonov09:42
*** zz_ttrifonov is now known as ttrifonov09:43
*** igordcard has quit IRC09:45
*** markvoelker has quit IRC09:47
*** ttrifonov is now known as zz_ttrifonov09:48
*** igordcard has joined #openstack-meeting-309:49
*** zz_ttrifonov is now known as ttrifonov09:49
*** jcoufal_ has joined #openstack-meeting-309:52
*** jcoufal has quit IRC09:53
*** igordcard has quit IRC09:54
*** ttrifonov is now known as zz_ttrifonov09:55
*** zz_ttrifonov is now known as ttrifonov10:00
*** ttrifonov is now known as zz_ttrifonov10:01
*** zz_ttrifonov is now known as ttrifonov10:02
*** scheuran has quit IRC10:04
*** ttrifonov is now known as zz_ttrifonov10:08
*** zz_ttrifonov is now known as ttrifonov10:09
*** JeanBriceCombebi has quit IRC10:09
*** JeanBriceCombebi has joined #openstack-meeting-310:10
*** ttrifonov is now known as zz_ttrifonov10:12
*** jtomasek has joined #openstack-meeting-310:12
*** JeanBriceCombebi has quit IRC10:14
*** zz_ttrifonov is now known as ttrifonov10:16
*** ttrifonov is now known as zz_ttrifonov10:18
*** scheuran has joined #openstack-meeting-310:18
*** zz_ttrifonov is now known as ttrifonov10:21
*** igordcard has joined #openstack-meeting-310:39
*** devvesa has quit IRC10:41
*** markvoelker has joined #openstack-meeting-310:43
*** alexpilotti has joined #openstack-meeting-310:47
*** stanzgy has quit IRC10:47
*** markvoelker has quit IRC10:48
*** belmoreira has quit IRC10:48
*** devvesa has joined #openstack-meeting-310:51
*** igordcard has quit IRC10:54
*** Longgeek has joined #openstack-meeting-310:55
*** jpich has joined #openstack-meeting-310:56
*** VW has joined #openstack-meeting-310:58
*** Godfath3r has joined #openstack-meeting-310:59
*** VW has quit IRC11:03
*** Godfath3r has quit IRC11:07
*** akrivoka has joined #openstack-meeting-311:28
*** Longgeek has quit IRC11:33
*** scheuran has quit IRC11:34
*** tellesnobrega__ has quit IRC11:43
*** markvoelker has joined #openstack-meeting-311:44
*** mattfarina has joined #openstack-meeting-311:44
*** neillc_afk has joined #openstack-meeting-311:46
*** neillc_afk is now known as neillc11:47
*** scheuran has joined #openstack-meeting-311:49
*** markvoelker has quit IRC11:49
*** igordcard has joined #openstack-meeting-311:50
*** KanagarajM has joined #openstack-meeting-311:50
*** rbertram has joined #openstack-meeting-311:52
*** r1chardj0n3s has joined #openstack-meeting-311:54
rbertramMorning r1chardj0n3s11:59
r1chardj0n3shey rbertram11:59
r1chardj0n3sright, just gonna go pour a whiskey so it's ready for the meeting :)11:59
rbertramLol11:59
r1chardj0n3sright, I'm ready :)12:01
david-lyle_afk#startmeeting Horizon12:01
openstackMeeting started Wed Feb  4 12:01:02 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle_afk. Information about MeetBot at http://wiki.debian.org/MeetBot.12:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:01
*** openstack changes topic to " (Meeting topic: Horizon)"12:01
openstackThe meeting name has been set to 'horizon'12:01
david-lyle_afkHello everyone12:01
r1chardj0n3shihi david-lyle_afk12:01
mattfarinaHello12:01
akrivokahi everyone12:01
*** david-lyle_afk is now known as david-lyle12:01
rbertramHey12:01
mrungehey o/12:01
* david-lyle slightly less afk now12:01
r1chardj0n3s"slightly" :)12:01
david-lylethe beauty of 5am12:02
r1chardj0n3s:/12:02
r1chardj0n3soh, radomir isn't here12:02
r1chardj0n3soh well, he misses out!12:02
david-lylefirst for the bookkeeping12:03
david-lylek-2 closes on Feb 5, I would like to have it wrapped and tagged latter today US time12:04
david-lylehttps://launchpad.net/horizon/+milestone/kilo-212:04
david-lyleI trimmed the list down substantially for bps12:04
david-lylethere are 3 more that have a chance of landing12:04
david-lylethe rest got bumped to k-312:05
david-lylewhich is now excessively large12:05
david-lyleand contains all the big ticket items for Juno12:05
david-lyleI'm not sure I even have a general angularization bp12:06
r1chardj0n3sdavid-lyle: that was originally covered by the identity table rework bp12:06
r1chardj0n3sdavid-lyle: and the launch instance bp12:06
david-lylethat's what I was about to ask12:07
r1chardj0n3sthe scope has creeped since then :/12:07
david-lyleabout the identity12:07
david-lyler1chardj0n3s: sure12:07
r1chardj0n3sunfortunately, that's still thai's baby even though I help out around the edges12:07
david-lyleI think we're getting close to start landing a lot of the backend part of that12:08
david-lylebut we can talk about that in a bit12:08
r1chardj0n3sit is certainly starting to land, yes12:08
david-lyleso other than k-2 closing and needing a few more core reviews12:08
david-lyleother general items are...12:08
david-lyleWe spent a bit of the cross-project meeting yesterday discussing the big-tent and horizon12:09
david-lyleas I mentioned in the last meeting, we need to come up with a plan12:09
david-lylewe were leaning toward a pure plugin model at the last Horizon meeting12:10
david-lyleI think that will have to suffice for some items, the concern that remains is consistent UX12:10
*** mwang2_ has joined #openstack-meeting-312:10
* david-lyle is cheating slightly by calling Horizon consistent12:10
mattfarinai've not looked but, would that plugin model work for JS?12:10
*** bradjones has quit IRC12:11
david-lylemattfarina: yes, it's designed to12:11
david-lyleyou can add angular modules now12:11
david-lylethere was some concern that some trove and sahara patches have been languishing12:12
david-lylewhich was the reason for the conversation12:12
david-lylejust mentioning to everyone, because it's not just on my mind moving forward12:12
mrungeoh, there are more patches like that, e.g some neutron and all router dashboard patches12:13
david-lylemrunge: indeed12:13
mrungedavid-lyle, the main issue here is, we don't have the expertise in those areas12:13
david-lylethat was also brought up12:13
*** alexpilotti has quit IRC12:13
mrungemoving areas back to the projects would be a good option12:14
*** bradjones has joined #openstack-meeting-312:14
david-lylebut you lose UX consistency and potentially overall quality12:14
david-lyleit needs to be discussed more12:14
david-lylethe router dash is a special case12:14
*** rdopiera has joined #openstack-meeting-312:15
david-lyleit's a third party dash that slipped in12:15
mrungeyes12:15
david-lyleI don't think it belongs12:15
david-lyleI'm ok with bug fixes to it because it's there, but don't want to add new features12:15
mrungedavid-lyle, but wouldn't then the plugin model fit for this?12:16
david-lylemrunge: aboslutely for a third party12:16
KanagarajMdavid-lyle: For admin-> system info panel, I have submitted one horizon blue print for  a new feature implemented in heat in k-2 https://blueprints.launchpad.net/horizon/+spec/heat-engine-status-report-horizon. could you consider for k-3?12:16
mrungeI could assume, e.g. a company working on storage might want to see additional features supported?12:16
david-lylewe may even want to spin it out ourselves12:16
*** ilyashakhat_ has joined #openstack-meeting-312:17
mrungeI assumed that ;-)12:17
david-lylemrunge: yes, if it goes beyond the cinder API, it should be external12:17
mrungewhat about 'rings' in horizon?12:17
mrungecore horizon and plugins?12:17
*** kevinbenton_ has joined #openstack-meeting-312:17
david-lylemrunge: where do the plugins live12:18
david-lylethat's the remaining question12:18
mrungewhereas I wouldn't necessarily make a technical distinction between plugins and core12:18
david-lyleI see 3 rings12:18
mrunge... and which ones?12:19
david-lylecore, openstack big tent projects, and 3rd party12:19
david-lylethe two ends are easy12:19
david-lylemiddle one's home needs to be determined12:19
mrungeopenstack - stackforge - closed source proprietary shit ?12:20
*** mwang2 has quit IRC12:20
*** mwagner_lap has quit IRC12:20
*** kevinbenton has quit IRC12:20
*** ilyashakhat has quit IRC12:20
david-lylethe thing is stackforge will become openstack12:21
david-lylefor more things12:21
david-lylepossibly a lot more things12:21
mrungesigh. get's worse and worse to put it all together12:22
david-lylemrunge: I agree, but a UI that looks like 20 different teams slapped it together is not a great answer either12:22
mrungeI totally agree with you12:23
rdopierathat's why we need to make it easier to make and extend the views12:23
rdopieraI had that proposal for layouts that got shot down by angular...12:23
*** TravT has joined #openstack-meeting-312:23
mattfarinardopiera i like the "extend the views" part of that12:23
rdopieramattfarina: we are struggling with that in tuskar-ui (aka tripleo-ui)12:24
rdopierait's possible currently, but a lot of boilerplate and unnecessary work12:24
*** terrylhowe has joined #openstack-meeting-312:25
rdopieraand you may get conflicts between plugins easily12:25
david-lylerdopiera: extend the views how, extend instances view or horizon views in general?12:25
rdopieradavid-lyle: right now we have classes for the views that are like table view, or tab view, etc.12:25
mattfarinardopiera i was thinking of looking into this post kilo. other systems have solved the conflit issue well enough12:26
rdopieradavid-lyle: I would like to replace those with "layout" views with slots -- things like tables, tabs, menus, graphs -- would go into those slots12:26
rdopieradavid-lyle: so each view would basically have a list of objects that go into those slots, and would be responsible for rendering their html in the right spot on the page12:27
rdopieradavid-lyle: this way you can easily replace one slot with another, or add another slot to a view12:27
*** mwagner_lap has joined #openstack-meeting-312:27
rdopierathere would be different layout views -- simple, two-column, with tabs, etc.12:28
david-lylerdopiera: I remember the proposal now12:29
rdopieraa lot like the gui toolkits12:29
david-lyleit's still valid even if it's done in angular12:29
* david-lyle just shuddered thinking of python generated angular12:30
r1chardj0n3sjust don't do it12:31
r1chardj0n3s:P12:31
david-lyler1chardj0n3s: scared myself12:31
TravTwhat about some angular generated pythong?12:31
rdopierawell, the contents of those slots may as well be angular stuff12:31
rdopierait doesn't matter12:31
david-lylerdopiera: yes12:31
rdopierait's just for the plugins to be able to easily swap them out12:32
david-lyleor django at this point12:32
rdopierait will also make it easier to rewrite stuff to angular12:32
rdopierabecause you can do it in smaller steps12:32
r1chardj0n3snot that "slots" in angular might just be *directives* which can be extended or overridden12:33
r1chardj0n3ser, "note" not "not"12:33
david-lyleI find it surprising that django doesn't already have these types of views12:33
david-lylewill research more after12:34
david-lyleI'll start a mailing list thread about horizon and the big tent12:34
david-lylewe can discuss there12:34
david-lylewe have an agenda to get to :)12:35
neillcrdopiera: do you have a link to your proposal?12:35
r1chardj0n3sdavid-lyle: please include a small intro in that email :)12:35
david-lyler1chardj0n3s: will do12:35
r1chardj0n3scheers!12:36
rdopieraneillc: I'm not sure, it was a year ago12:36
*** david-lyle is now known as david-lyle_afk12:36
rdopieraneillc: it was written up in the etherpads for the Atlanta summit...12:36
*** baoli_ has joined #openstack-meeting-312:36
david-lyle_afk#topic Switching to bower from xstatic12:36
*** openstack changes topic to "Switching to bower from xstatic (Meeting topic: Horizon)"12:36
*** david-lyle_afk is now known as david-lyle12:36
neillcok thanks12:36
r1chardj0n3sok this is the topic I added :)12:37
* david-lyle pass r1chardj0n3s the mic12:37
r1chardj0n3sthanks!12:37
r1chardj0n3sSo rdopiera asked me if I could go ahead and implement https://blueprints.launchpad.net/horizon/+spec/static-file-bower12:37
r1chardj0n3ssince objections are withering away at this point12:37
r1chardj0n3sa couple of people popped up saying that lack of node.js support on their platforms is a problem12:38
r1chardj0n3sso ... I wrote a python implementation of the subset of bower that we need12:38
mattfarinar1chardj0n3s did anyone figure out the plan for mirrors of the code (in addition to the bower registry) for testing and build environments?12:38
david-lylenothing more python won't fix12:38
r1chardj0n3smattfarina: I'm totally getting to that :)12:38
r1chardj0n3sIt's not finished, but the remaining work is not a huge task and neillc's going to finish it off12:38
r1chardj0n3sI think this is the least-resistance path to getting bower into the project12:39
r1chardj0n3sIt won't handle dependencies, requiring us to explicitly list all components with pinned versions. I believe this is desirable for Horizon anyway.12:39
r1chardj0n3sOnce we've got that integrated into Horizon, we will look at providing a simple caching proxy that can be used by #infra to remove Internet connectivity issues.12:39
r1chardj0n3s (hai mattfarina ;)12:39
rdopierathat's awesome12:39
david-lyleso a bower freeze12:39
*** baoli_ has quit IRC12:40
r1chardj0n3syep12:40
r1chardj0n3sbower (the node.js implementation) has no capacity for mirrors/proxies and probably never will because it's *hideously* complex12:40
*** baoli has joined #openstack-meeting-312:40
r1chardj0n3sbower.py on the other hand is a simple implementation and we can easily add a caching proxy mode12:40
david-lylesounds reasonable12:41
mrungethis is *awesome*12:41
david-lylethis will solve a lot of headaches12:41
r1chardj0n3sFYI the current implementation is https://github.com/r1chardj0n3s/laughing-robot12:41
r1chardj0n3s(I love github's always-appropriate random project names ;)12:41
david-lyleand neillc thanks for taking one for the team :D12:41
neillcheh12:42
r1chardj0n3syes!12:42
david-lyleso next week then?...12:42
r1chardj0n3sso, if everyone's cool with that as an approach, we (well, neillc) will forge ahead!12:42
david-lyle+112:43
rbertramr1chardj0n3s: when is it ready for us to use?12:43
r1chardj0n3sneillc totally said he'd have it done by Friday12:43
TravTr1chardj0n3s: I love it.12:43
r1chardj0n3s:)12:43
mattfarina+112:43
r1chardj0n3s[he might not have said that thing]12:43
neillcthat's not quite how *I* remember that conversation going...12:43
r1chardj0n3soh sure12:43
david-lylethanks r1chardj0n3s12:44
david-lylegreat news12:44
*** david-lyle is now known as david-lyle_afk12:44
david-lyle_afk#topic Open Discussion12:45
r1chardj0n3srbertram: more realistically, patches will start hitting (for new requirements and the integration of the tool) in the next week or two12:45
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"12:45
*** david-lyle_afk is now known as david-lyle12:45
*** markvoelker has joined #openstack-meeting-312:45
rbertramr1chardj0n3s: cool12:45
david-lyleAfter that high note, I'd like to bring it down a bit and remind people that k-3 closes on March 19, just 6 weeks away12:46
david-lyleWe have a lot of high priority items left to get in12:46
* rbertram is taking x static items off his todo list12:46
david-lyleso we're really going to have to push to land some of the big changes12:47
r1chardj0n3salso, folks, please think about how bower.py might assist the creation of system packages from bower packages12:47
david-lyleassuming they're ready12:47
mattfarinathe system packages are build on xstatic ones. so, we'll still need to maintain the ones we already do12:48
mattfarinaunless the build process changes12:48
mattfarinaany thought to how to do that?12:49
*** KanagarajM has quit IRC12:49
*** markvoelker has quit IRC12:49
mrungeI see separate packages as a profit here12:50
mrungesince we won't interphere with already released versions12:50
mattfarinaon an unrelated note, has anyone looked at the angular reusable wizard... https://review.openstack.org/#/c/13741712:51
r1chardj0n3sdavid-lyle: at the moment https://review.openstack.org/#/c/150636/ is kinda the blocker patch for the angular work12:51
r1chardj0n3smattfarina: shen only just added the demo, and it's 11:51pm so I was going to look at it tomorrow :)12:52
david-lyler1chardj0n3s: that's my top review priority other than k-212:52
david-lylenot much left for k-212:52
r1chardj0n3sdavid-lyle: it's certainly my priority patch12:52
TravTYes, that reusable wizard is the next thing ready for reviews.12:53
david-lyler1chardj0n3s: I will look today12:53
TravTwe've got a number of other reusable widgets that should be ready within the next week12:53
r1chardj0n3sI've already gone over the code of the wizard, but haven't had a chance to see it in action, which is why the demo is great to have now12:53
TravTr1chardj0n3s: how close is the keystone api?12:54
r1chardj0n3sTravT: shen raised an issue about unit tests, which I've had to respond vaguely to12:54
TravTi didn't get to rebase the glance api on it today and round it out, but will later today.12:54
r1chardj0n3sI'm pretty sure I covered off your params issue12:54
TravTyes, i saw that12:55
TravTthanks12:55
TravTit looks like it should work12:55
r1chardj0n3snp :)12:55
david-lyler1chardj0n3s: in all fairness he commented vaguely to begin with12:55
mattfarinar1chardj0n3s which tests? The Jasmine ones?12:55
r1chardj0n3smattfarina: yep12:56
mattfarinar1chardj0n3s he has another review up to address Jasmine12:56
r1chardj0n3sBTW if anyone has any objections to me adding support for using karma as the jasmin test runner, please speak now12:56
r1chardj0n3s:)12:56
r1chardj0n3smattfarina: that was a jasmine configuration issue though - which I had to fix in my patch anyway (so rebase, yay!)12:56
* rdopiera has no objections12:56
r1chardj0n3s(current jasmine configuration is ... obscure ;)12:57
r1chardj0n3sI think someone mentioned jpich's phrase "tribal knowledge" IIRC12:58
TravTwe've got a lot of cross dependencies going on with this work that is going to be pretty painful if we don't merge and iterate12:58
david-lyletribe of 2 maybe12:58
* david-lyle not in that tribe12:58
r1chardj0n3sdavid-lyle: indeed12:58
r1chardj0n3sTravT: yes, merging ASAP :)12:58
r1chardj0n3sI'm getting good at rebasing and cherry-picking. These aren't life goals I originally had ;)12:59
mattfarinaha12:59
TravTi love your latest branch name12:59
TravTmerge-hell12:59
david-lylecores, please review the angular patches, the best part is r1chardj0n3s top patch isn't even angular12:59
david-lylefor the most part12:59
r1chardj0n3sI completely forgot that those are exposed ;)12:59
*** xuhanp has joined #openstack-meeting-313:00
*** NobodyCam has quit IRC13:00
david-lyleforgot about the 200 lines13:00
david-lylenot all angular13:00
mrunger1chardj0n3s, you could have picked worse names ;)13:00
TravThttps://review.openstack.org/#/c/150636/1613:00
r1chardj0n3smrunge: I will be *very* careful in the future choosing my names ;)13:00
TravTyou can always do the git review -t <topic> if you want to give a diff name13:00
*** BadCub has quit IRC13:01
r1chardj0n3soh, you should *not* have told me about that ;)13:01
TravTbut I don't mind the funny names13:01
r1chardj0n3swhee!13:01
david-lyletime's up. Thanks everyone and have a great week. 6 weeks until k-313:01
david-lyle#endmeeting13:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:01
openstackMeeting ended Wed Feb  4 13:01:50 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-02-04-12.01.html13:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-02-04-12.01.txt13:01
TravTrhx13:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-02-04-12.01.log.html13:01
*** rbertram has left #openstack-meeting-313:01
TravTthx13:01
r1chardj0n3sthanks all!13:02
neillcthanks all13:02
*** neillc has left #openstack-meeting-313:02
*** TravT has left #openstack-meeting-313:06
*** BadCub has joined #openstack-meeting-313:07
*** NobodyCam has joined #openstack-meeting-313:07
*** r1chardj0n3s is now known as r1chardj0n3s_afk13:07
*** Networkn3rd has quit IRC13:08
*** rdopiera has quit IRC13:10
*** bknudson has joined #openstack-meeting-313:11
*** TravT has joined #openstack-meeting-313:11
*** TravT has left #openstack-meeting-313:11
*** markvoelker has joined #openstack-meeting-313:20
*** nelsnelson has quit IRC13:22
*** rcarrillocruz has left #openstack-meeting-313:23
*** nelsnelson has joined #openstack-meeting-313:23
*** JeanBriceCombebi has joined #openstack-meeting-313:26
*** mrmartin has quit IRC13:36
*** mrunge has quit IRC13:47
*** thomasem has joined #openstack-meeting-313:54
*** wojdev has joined #openstack-meeting-313:55
*** jpich has left #openstack-meeting-313:55
*** etoews has joined #openstack-meeting-313:56
*** jckasper has joined #openstack-meeting-314:01
*** yamamoto has joined #openstack-meeting-314:02
*** etoews has quit IRC14:03
*** thomasem has quit IRC14:03
*** thomasem has joined #openstack-meeting-314:04
*** thomasem has quit IRC14:05
*** thomasem has joined #openstack-meeting-314:05
*** belmoreira has joined #openstack-meeting-314:11
*** reed has joined #openstack-meeting-314:14
*** cbader has joined #openstack-meeting-314:15
*** jckasper has quit IRC14:18
*** jckasper has joined #openstack-meeting-314:19
*** julim has joined #openstack-meeting-314:19
*** julim has quit IRC14:21
*** VW_ has joined #openstack-meeting-314:24
*** julim has joined #openstack-meeting-314:24
*** mrmartin has joined #openstack-meeting-314:25
*** Longgeek has joined #openstack-meeting-314:33
*** Longgeek has quit IRC14:35
*** lblanchard has joined #openstack-meeting-314:35
*** peristeri has joined #openstack-meeting-314:38
*** baoli has quit IRC14:41
*** nelsnelson has quit IRC14:42
*** baoli has joined #openstack-meeting-314:43
*** etoews has joined #openstack-meeting-314:51
*** mattgriffin has joined #openstack-meeting-314:59
*** sigmavirus24_awa is now known as sigmavirus2415:00
*** marun has joined #openstack-meeting-315:04
*** thangp has joined #openstack-meeting-315:04
*** marun has quit IRC15:08
*** peristeri has quit IRC15:08
*** jcoufal has joined #openstack-meeting-315:09
*** zz_jgrimm is now known as jgrimm15:09
*** peristeri has joined #openstack-meeting-315:10
*** baoli has quit IRC15:11
*** jcoufal_ has quit IRC15:12
*** baoli has joined #openstack-meeting-315:12
*** wojdev_ has joined #openstack-meeting-315:13
*** wojdev has quit IRC15:13
*** wojdev_ is now known as wojdev15:13
*** julim has quit IRC15:15
*** julim has joined #openstack-meeting-315:18
*** nelsnelson has joined #openstack-meeting-315:18
*** amotoki has joined #openstack-meeting-315:20
*** peristeri has quit IRC15:23
*** rcleere_ is now known as rcleere_away15:24
*** Networkn3rd has joined #openstack-meeting-315:25
*** rcleere_away is now known as rcleere_15:25
*** mattfarina has quit IRC15:27
*** yamahata has joined #openstack-meeting-315:28
*** Sukhdev has joined #openstack-meeting-315:30
*** VW_ has quit IRC15:33
*** terrylhowe has left #openstack-meeting-315:33
*** wojdev has quit IRC15:34
*** ChuckC has joined #openstack-meeting-315:40
*** ChuckC_ has quit IRC15:41
*** nelsnels_ has joined #openstack-meeting-315:46
*** nelsnelson has quit IRC15:46
*** matrohon has quit IRC15:50
*** pc_m has joined #openstack-meeting-315:56
*** pc_m has left #openstack-meeting-315:59
*** VW_ has joined #openstack-meeting-316:00
*** sarob has joined #openstack-meeting-316:00
*** erikmwilson has joined #openstack-meeting-316:02
*** wojdev has joined #openstack-meeting-316:09
*** xuhanp has quit IRC16:09
*** mattfarina has joined #openstack-meeting-316:12
*** wojdev has quit IRC16:12
*** JeanBriceCombebi has quit IRC16:13
*** igordcard has quit IRC16:13
*** bpokorny has joined #openstack-meeting-316:13
*** ChuckC_ has joined #openstack-meeting-316:14
*** carl_baldwin has joined #openstack-meeting-316:16
*** JeanBriceCombebi has joined #openstack-meeting-316:16
*** armax has joined #openstack-meeting-316:16
*** ChuckC has quit IRC16:17
*** nelsnels_ has quit IRC16:17
*** Networkn3rd has quit IRC16:19
*** Networkn3rd has joined #openstack-meeting-316:19
*** nelsnelson has joined #openstack-meeting-316:23
*** coolsvap is now known as coolsvap_16:28
*** marun has joined #openstack-meeting-316:30
*** SridharRamaswamy has joined #openstack-meeting-316:30
*** SridharRamaswam1 has joined #openstack-meeting-316:33
*** SridharRamaswamy has quit IRC16:34
*** banix_ has joined #openstack-meeting-316:43
*** belmoreira has quit IRC16:52
*** gholler has joined #openstack-meeting-316:57
*** annegent_ has joined #openstack-meeting-316:58
*** lazy_prince is now known as killer_prince17:00
*** banix_ has quit IRC17:01
*** kozhukalov has quit IRC17:03
*** s3wong has joined #openstack-meeting-317:04
*** MaxV has quit IRC17:06
*** [1]evgenyf has quit IRC17:06
*** absubram has joined #openstack-meeting-317:07
*** absubram has left #openstack-meeting-317:07
*** scheuran has quit IRC17:07
*** vishwanathj has joined #openstack-meeting-317:15
*** safchain has quit IRC17:19
*** matrohon has joined #openstack-meeting-317:20
*** jcoufal has quit IRC17:26
*** sahid has quit IRC17:29
*** JeanBriceCombebi has quit IRC17:30
*** iovadia has quit IRC17:30
*** Piet has joined #openstack-meeting-317:30
*** Sukhdev has quit IRC17:30
*** jtomasek has quit IRC17:33
*** devvesa has quit IRC17:34
*** SridharRamaswam1 has quit IRC17:38
*** SridharRamaswamy has joined #openstack-meeting-317:38
*** banix has joined #openstack-meeting-317:39
*** yamamoto has quit IRC17:39
*** ttrifonov is now known as zz_ttrifonov17:39
*** s3wong has quit IRC17:40
*** stevelle has left #openstack-meeting-317:41
*** etoews has quit IRC17:47
*** alexsyip has joined #openstack-meeting-317:50
*** eghobo has joined #openstack-meeting-317:51
*** annegent_ has quit IRC17:53
*** killer_prince is now known as lazy_prince17:55
*** coolsvap_ is now known as coolsvap17:57
*** VW_ has quit IRC17:59
*** SumitNaiksatam has joined #openstack-meeting-318:01
SumitNaiksatamvishwanathj: hi18:01
*** lazy_prince is now known as killer_prince18:02
*** akrivoka has left #openstack-meeting-318:09
*** Salman has joined #openstack-meeting-318:11
*** erikmwilson has quit IRC18:11
*** yamahata has quit IRC18:14
*** SridharRamaswam1 has joined #openstack-meeting-318:19
*** SridharRamaswamy has quit IRC18:19
*** coolsvap is now known as coolsvap_18:20
*** rkukura has joined #openstack-meeting-318:23
vishwanathjSumitNaiksatam, Hi18:24
*** SridarK has joined #openstack-meeting-318:29
*** pc_m has joined #openstack-meeting-318:30
*** badveli has joined #openstack-meeting-318:30
SumitNaiksatamSridarK: pc_m: hi18:30
pc_mhi18:30
SumitNaiksatambadveli: hi18:30
SumitNaiksatamlets get started18:30
badvelihello sumit18:30
SumitNaiksatam#startmeeting Networking FWaaS18:30
openstackMeeting started Wed Feb  4 18:30:44 2015 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:30
*** openstack changes topic to " (Meeting topic: Networking FWaaS)"18:30
vishwanathjSridarK, pc_m, badveli, hi18:30
openstackThe meeting name has been set to 'networking_fwaas'18:30
badvelihello viswantah18:30
pc_mvishwanathj: hi18:31
SumitNaiksatam#info metting agenda https://wiki.openstack.org/wiki/Meetings/FWaaS#Agenda_for_Next_Meeting18:31
SumitNaiksatam#info Kilo-2 is Feb 5th18:31
SumitNaiksatamthat is tomorrow18:31
SridarKhi all18:31
SumitNaiksatamany other pieces of information worth sharing?18:31
*** amotoki has quit IRC18:32
SumitNaiksatam#topic Bugs18:32
*** openstack changes topic to "Bugs (Meeting topic: Networking FWaaS)"18:32
SridarKSumitNaiksatam: nothing new that needs attention18:33
SumitNaiksatamSridarK: yeah, my observation as well18:33
SumitNaiksatamthere were a few issues which cropped up during the week18:33
SumitNaiksatamthankfully folks jumped in and patches are passing the gate18:34
SumitNaiksatam* jumped in with a fix18:34
SridarKSumitNaiksatam: :-)18:34
SumitNaiksatam:-)18:34
SumitNaiksatambadveli: anything to report on the bugs assigned to you?18:34
badvelisumit looked like some other modules implemented the connection track18:35
badvelii saw some review18:35
SumitNaiksatamgood, can you post the review?18:35
SumitNaiksatamreview link18:35
badvelitrying to check now, i saw it when i was checking all the open reviews18:36
badvelii will send the link to the team18:36
*** yamahata has joined #openstack-meeting-318:37
SumitNaiksatambadveli: thanks18:37
SumitNaiksatam#topic Docs18:37
*** openstack changes topic to "Docs (Meeting topic: Networking FWaaS)"18:37
SumitNaiksatamit seems that there are some doc bugs for the freescale fwaas plugin18:38
SumitNaiksatamother than that i dont see anything new18:38
SumitNaiksatamSridarK: did you notice anything?18:38
SridarKSumitNaiksatam: nothing else18:38
SumitNaiksatamSridarK: okay good18:38
SridarKSumitNaiksatam: i will check with swami if there is anything pending on the dvr changes - i think it is done18:39
SumitNaiksatamSridarK: thanks18:39
SridarKSumitNaiksatam: np at all18:39
SumitNaiksatamso just FYI for everyone - the freescale patch author added the DocImpact flag to his review18:40
SumitNaiksatamthat generated a bug like this:18:40
SumitNaiksatam#link https://bugs.launchpad.net/openstack-manuals/+bug/141723718:40
SumitNaiksatamand that can be followed up witha documentation patch18:40
SridarKSumitNaiksatam: thanks - good to know this18:41
SumitNaiksatamyeah, since we have quite a few vendor patches in review18:41
*** Salman has quit IRC18:41
SumitNaiksatamand i would imagine that might need to be documented18:42
SumitNaiksatamalthough things keep changing with regards to the vendor documentation18:42
SumitNaiksatamand i am not sure that exactly what is the latest on that (in terms of incorporating vendor docs in the main docs)18:42
SumitNaiksatambut just keep an eye on this18:42
SumitNaiksatamokay moving one18:42
SumitNaiksatam*on18:43
SumitNaiksatam#topic Firewall Insertion18:43
*** openstack changes topic to "Firewall Insertion (Meeting topic: Networking FWaaS)"18:43
SumitNaiksatamSridarK: thanks for the WIP patch18:43
*** sarob has quit IRC18:43
SridarKBasic skeleton18:43
SridarK#link https://review.openstack.org/#/c/134896/18:43
SridarKsorry18:43
SridarKwrong link18:44
SridarK#link https://review.openstack.org/15269718:44
SumitNaiksatami suspect that this is now target for kilo-318:44
SridarKSumitNaiksatam: yes we should be good18:44
SridarKbasic extension and db changes18:44
SumitNaiksatamso we will have to really push to ge this in at the front end of k-318:44
SridarKSumitNaiksatam: yes for sure18:45
SridarKTrying to keep a separation between the extension & db code for existing fwaas and the insertion work now.18:45
SumitNaiksatamsince we might need to refactor the vendor plugins/drivers18:45
SridarKTrying to keep that in mind for sure and see how we can minimize impact18:45
SumitNaiksatami guess the good thing is that the firewall extension have moved to the neutron-fwaas repo18:45
SumitNaiksatamSridarK: thanks18:45
SridarKyes that was good18:45
SumitNaiksatamso we dont have to do the multi-repo acrobatics18:46
SridarKSumitNaiksatam: surely is a blessing18:46
badveli Sumit i did not really follow this18:46
badvelicould you please explain18:46
SumitNaiksatamgiven that I think we should go full steam ahead and try to get this wrapped up18:46
SridarKyes18:46
SumitNaiksatambadveli: sorry, which part?18:46
SridarKbadveli: few mins pls18:46
SumitNaiksatamSridarK: go ahead18:47
SridarKone thought is that keeping the new extension and db as a separate entity will enable other plugins to pick up the the basic FW resource, policies, rules etc and if needed adopt the router insertion extension. If they need a different insertion strategy they can still use the fwaas extension (and db) and use a different extension / db implementation for their own insertion model. IMHO, keeping this separation will enabl18:47
SumitNaiksatamanyone have a chance to look at SridarK’s patch?18:47
vishwanathjnope18:48
SridarKalso this can help minimize impacts to other plugins18:48
SridarKSumitNaiksatam: i think this will keep things clean in terms of the insertion have some separation18:49
SridarKAnyways just trying to get some rationale out there - we can always discuss more offline or in the review18:49
SumitNaiksatamSridarK: by keeping the extension and db separate, you mean using attribute extension (instead of, say, adding the router attribute to the firewall resource)?18:49
SridarKSumitNaiksatam: yes18:50
SridarKSumitNaiksatam: and also the db for these parts as  a separate table18:50
SridarKSumitNaiksatam: i want to avoid polluting the existing firewall db code as much as possible18:50
SumitNaiksatamSridarK: the db can still be a separate table (and I think it will need to be regardless of how you decided to extend the resource definition)18:51
SridarKSumitNaiksatam: the plugin will include the existing fwaas extension and this new rtrinsertion extension18:51
SumitNaiksatamSridarK: since its a 1:n relationship18:51
SridarKSumitNaiksatam: we will keep the logic in the plugin18:51
SridarKSumitNaiksatam: yes u are correct18:51
SridarKSumitNaiksatam: i want other plugins to inherit from the existing firewall db class18:52
SridarKSumitNaiksatam: irrespective of the insertion strategy18:52
SumitNaiksatamSridarK: i think the choice will be between adding the “router_ids” as an optional attribute to the firewall resource, or using the attribute extension18:52
SridarKSumitNaiksatam: yes the latter18:52
SumitNaiksatamSridarK: sorry i forget, but did we state an explicit design decision in our spec?18:53
SridarKso it is not in the firewall resource as such18:53
SumitNaiksatamif we did then, we are just executing on that design18:53
SridarKSumitNaiksatam: i think i did state both as possible options18:53
*** annegent_ has joined #openstack-meeting-318:54
*** jckasper has quit IRC18:54
SumitNaiksatamSridarK: ah ok18:54
SumitNaiksatamother folks in the team please chime in18:54
SridarKSumitNaiksatam: sorry my inability to communicate very effectively on irc :-)18:54
SridarKSumitNaiksatam: if a plugin does not want the router insertion and just the fwaas extension for the fw resource - want it make it easy for them to do that18:55
SumitNaiksatamSridarK: i think you are very articulate, certainly more than me! :-)18:55
SridarKSumitNaiksatam: :-)18:56
SumitNaiksatamSridarK: i very much agree with that intent18:56
vishwanathjI might need to revisit the spec again to be an effective contributor18:56
SumitNaiksatamvishwanathj: sure, please do :-)18:56
SridarKSumitNaiksatam: perhaps i can also follow up with a email to the fwaas folks18:56
SumitNaiksatamSridarK: sure18:56
SridarKvishwanathj: no worries -18:56
SridarKthats all from me18:56
SridarKbadveli: sorry - did not want to lose my train of thought18:57
badveli no problem18:57
badvelias things are changing i am a bit not sure which way we are going18:57
SumitNaiksatambadveli: thanks for waiting18:58
SridarKbadveli: i think if u look at the email from SumitNaiksatam on patch from Doug u should get a good idea18:58
SumitNaiksatambadveli: can you be more specific on what “things” and which “way” you are referring to?18:58
SumitNaiksatambadveli: apologies upfront if i might have confused you18:58
*** annegent_ has quit IRC18:59
badveli about the extension part18:59
badvelino problem since this is chaning18:59
*** annegent_ has joined #openstack-meeting-319:00
badvelimy question is if i need to get the patch for service objects should i follow it/ should i wait for sridark patch19:00
SridarKbadveli: no u are not dependent on my patch19:00
SumitNaiksatamright, they are not related, at least to the extent i know19:01
badvelithanks sridar, sumit. So now we can move the extension part to the fwaas repo, correct?19:01
SumitNaiksatambadveli: its already moved19:02
SumitNaiksatamthat was my email informing the team that it had moved19:02
SumitNaiksatamthe existing fwaas extension definition19:03
SumitNaiksatambadveli: i am still pretty fuzzy on how you are planning to implement your extension19:03
badvelithanks sumit, so i can start working my patch19:03
SumitNaiksatambadveli: if its not fwaas-specific, then the extension definition should not be in the neutron-fwaas repo19:04
SumitNaiksatamthe extensions we are discussing here are not fwaas-specific19:04
*** enykeev has quit IRC19:04
SumitNaiksatamsorry i meant - they *are* fwaas specific19:04
badvelimy problem would be if did not have the extension over fwaas, it would be tough to implement the reference impl19:05
SridarKSumitNaiksatam: i guess badveli will need to push a patch to neutron for the extensions19:06
SumitNaiksatambadveli: okay19:06
*** sarob has joined #openstack-meeting-319:06
*** enykeev has joined #openstack-meeting-319:06
badveliyes sridar, sumit. looks like i need to push the a patch for neutron19:06
SumitNaiksatamSridarK: yeah, i meant to say, it depends on what is stated in the approved blueprint19:06
badvelias the reviewers wanted it to be generic19:06
badveli but would it make the reference implementation19:07
badvelithe fwaas usage not so easy?19:07
SumitNaiksatambadveli: my thinking was that we had discussed these issues at design time (while proposing the spec)19:08
SumitNaiksatambadveli: perhaps good idea to check with Yi19:08
SridarKbadveli: i think it should be ok - u can still implement the reference in fwaas - u will just need to manage 2 patches19:08
*** ivar-lazzaro has joined #openstack-meeting-319:09
badvelithanks sumit, sridark, yes we have discussed in getting two patches19:09
badveliultimately we want to get the code in19:10
*** VW_ has joined #openstack-meeting-319:10
*** etoews has joined #openstack-meeting-319:10
SumitNaiksatambadveli: yeah19:11
*** ivar-lazzaro has quit IRC19:11
SumitNaiksatamokay anyone have any questions for badveli on this?19:11
badvelithanks sumit, as long as  we are in agree19:11
*** ivar-lazzaro has joined #openstack-meeting-319:12
SridarKI am good19:12
SumitNaiksatambadveli: thanks for the update19:12
badvelithanks sumit19:12
SumitNaiksatam#topic Service Objects19:12
*** openstack changes topic to "Service Objects (Meeting topic: Networking FWaaS)"19:12
SumitNaiksatamservice objects was a separate agenda item, but we munged it with the earlier topic19:13
SumitNaiksatamjust added the topic for anyone going through the logs19:13
badvelithanks sumit, let me start working on the patches19:13
SumitNaiksatambadveli: great19:13
SumitNaiksatam#topic FWaaS L3 agent refactoring/restructuring19:13
*** openstack changes topic to "FWaaS L3 agent refactoring/restructuring (Meeting topic: Networking FWaaS)"19:13
SumitNaiksatampc_m: hi19:13
pc_mSumitNaiksatam: hi19:13
SumitNaiksatamanything to discuss today on this?19:14
pc_mnothing on this front.19:14
SumitNaiksatampc_m: ah okay19:14
pc_mSumitNaiksatam: Waiting for FW insertion to complete first.19:14
SumitNaiksatampc_m: and again, many thanks for your continued patience19:14
pc_mSumitNaiksatam: np. I've got enough other balls to juggle.19:14
pc_m:)19:14
SumitNaiksatampc_m: _;_19:14
SumitNaiksatam:-)19:14
SumitNaiksatam#topic FWaaS gate jobs19:15
*** openstack changes topic to "FWaaS gate jobs (Meeting topic: Networking FWaaS)"19:15
SumitNaiksatampc_m: since you are around19:15
SumitNaiksatampc_m: you had taken an AI for yourself to send us some pointers19:15
SumitNaiksatam;-)19:15
pc_mSumitNaiksatam: Yes... here you go... https://wiki.openstack.org/wiki/Neutron/FunctionalGateSetup19:15
SumitNaiksatamah sweet!19:16
pc_mSumitNaiksatam: Please let me know if you have any issues in following the steps (feel free to make corrections).19:16
SumitNaiksatampc_m: this is great info for everyone19:16
pc_mFor VPN, I have a commit out for review to make the check queue non-voting.19:16
SumitNaiksatampc_m: can you share the link to that review?19:16
pc_mOnce approved, and we use it for a bit, I'll do the last piece to make it voting.19:17
SridarKpc_m: this is great19:17
pc_m#link https://review.openstack.org/#/c/152602/19:17
SumitNaiksatampc_m: thanks19:17
SumitNaiksatami think the timing is good to this since the extension definition has moved19:17
pc_mIn the instructions, I put all the VPN review #s so you can see the actual diffs for VPN through the steps/19:17
pc_mI'm going to send this out on the ML today.19:18
SumitNaiksatampc_m: sweet!19:18
SumitNaiksatami will go through it19:18
SridarKSumitNaiksatam: Nikolay was working on the FWaaS Scenario tests - i have asked him if will be able to continue thru this and if so we can get some these tests in19:19
*** devlaps has joined #openstack-meeting-319:20
pc_mSumitNaiksatam: You'll likely want to get the experimental queue going, and the gate hooks, and then people can do commits with functional tests.19:20
SumitNaiksatampc_m: definitely19:20
SumitNaiksatamSridarK: that is awesome19:20
SumitNaiksatamSridarK: can you add me to the conversations as well?19:20
SridarKSumitNaiksatam: yes will do19:20
SumitNaiksatamSridarK: thanks19:21
pc_mFor VPN, we had people hold off on committing functional test modules, until we got that in place.19:21
SumitNaiksatampc_m: that sounds logical19:21
SumitNaiksatampc_m: again thanks a bunch for documenting this19:21
pc_mOtherwise, you get functional modules upstreamed, and then when the tests are working, there are failures to deal with.19:22
pc_mnp19:22
SumitNaiksatamlots of people have done this in the past, you took the trouble of documenting it so others can use19:22
vishwanathj+119:22
SumitNaiksatamin true spirit of community work!19:22
pc_mthanks.19:22
SridarKpc_m: this is like a book for "defense against the dark arts" :-)19:22
pc_m:)19:23
SumitNaiksatamSridarK: lol19:23
SumitNaiksatamdidnt i say you were very articulate! ;-P19:23
SridarKthere is some deep magic in those parts19:23
SridarK:-)19:23
SumitNaiksatamwe have only few mins left and need to cover vendor drivers19:23
SumitNaiksatam#topic Vendor Plugins/drivers19:23
*** openstack changes topic to "Vendor Plugins/drivers (Meeting topic: Networking FWaaS)"19:23
SumitNaiksatamthe freescale plugin was merged, yay!19:23
vishwanathj+119:23
SridarKyes finally19:23
SridarKkudos to trinath for his persistence19:24
SumitNaiksatamkudos to the author for his pereseverance19:24
SridarK:-)19:24
SumitNaiksatamvishwanathj: on to your patch19:24
SumitNaiksatamthe last i checked it had comments from SridarK19:24
*** devlaps has quit IRC19:24
SumitNaiksatamare those addressed?19:24
vishwanathjI have addressed comments from SridarK and pc_m19:24
SridarKvishwanathj: yes thanks19:25
pc_m+119:25
SridarKvishwanathj: i think we are good19:25
SumitNaiksatamoh, trinath put a -119:25
vishwanathjTrinath also commented early this morning, he is asking to upload README that has link to WIKI page and CI contacts....is that a hard requirement19:25
SumitNaiksatamhmmm19:25
SumitNaiksatamvishwanathj: no19:25
SumitNaiksatamvishwanathj: but do it19:26
SridarKvishwanathj: yes he got pulled for that19:26
SumitNaiksatamvishwanathj: i mean your call19:26
SumitNaiksatamits not a hard requirement19:26
SridarKvishwanathj: so good to do it i think19:26
vishwanathjI dont have a WIKI page yet, what are the CI contact requirements...completely new to this19:26
SumitNaiksatamvishwanathj: let us know when you do, and we can hopefully proceed quickly from there19:26
SumitNaiksatamvishwanathj: wiki page is a 2 min job, so should not be an issue19:27
SumitNaiksatamvishwanathj: you can update the wiki page independently19:27
vishwanathjSumitNaiksatam, pc_m, SridarK, will let you guys know once I upload a new patch set to get your votes19:27
vishwanathjok19:27
pc_mroger19:27
SridarKvishwanathj: u put ur email id or better yet some other colleague in ur company who will get spammed if ur CI job goes down19:27
SridarK:-)19:27
vishwanathj:)19:27
SumitNaiksatamfor the CI contact requirements i believe you would already have a brocade contact, no?19:27
SumitNaiksatamvishwanathj: see this - #link https://review.openstack.org/#/c/152229/19:28
SumitNaiksatamfyi19:28
vishwanathjI will check with natarajk, he was the contact earlier, maybe will keep as the contact :)19:28
SridarK:-)19:28
SumitNaiksatamcheck if that file has a brocade contact that can deal with your fwaas plugin19:28
vishwanathjSumitNaiksatam, thanks for the link, ok19:29
SumitNaiksatamthere are two other vendor drivers:19:29
vishwanathjSridarK, pc_m, SumitNaiksatam, appreciate your earlier reviews19:29
SridarKSumitNaiksatam: yes first patch is up19:29
SumitNaiksatammcafee: #link https://review.openstack.org/15209319:29
SumitNaiksatamcisco: #link https://review.openstack.org/15228219:29
SridarKneed to refactor for vendor repo and there will be one more on agent/driver19:30
vishwanathjSumitNaiksatam, can brocade fwaas still make Kilo-2 by tomorrow19:30
SumitNaiksatamvishwanathj: my earlier wish - “we can hopefully proceed quickly from there”19:30
vishwanathjok19:30
yamahataregarding to mcafee, we're respining the patch and working on CI system.19:30
SumitNaiksatamyamahata: great, thanks for joining, are you the point of contact for this?19:31
yamahataYes.19:31
vishwanathjyamahata, hi19:31
yamahatavishwanathj: hi.19:31
SumitNaiksatamyamahata: i see a differenent author on the patch19:31
SumitNaiksatamokay anyway19:31
yamahataYalei is also contact, but he's located in China.19:31
yamahataIt's midnight now in China.19:31
SumitNaiksatamyamahata: and you are now in the bay area?19:32
yamahataSumitNaiksatam: Yeah at last.19:32
SumitNaiksatamok good! :-)19:32
SumitNaiksatamoh, we are two mins over19:32
SumitNaiksatam#topic Open Discussion19:32
*** openstack changes topic to "Open Discussion (Meeting topic: Networking FWaaS)"19:32
SridarKi have updated the FWaaS wiki with links to most of the patches19:32
SumitNaiksatamanything that we missed?19:32
SridarK#link https://wiki.openstack.org/wiki/Neutron/FWaaS/KiloPlan19:32
SumitNaiksatamSridarK: cool!19:32
SridarKpls check if i have messed up someone's patch id etc19:33
SumitNaiksatamSridarK: you will need to maintain it now :-)19:33
SridarKyamahata: i will add intel as well19:33
SridarKSumitNaiksatam: :-)19:33
SridarKno worries19:33
SumitNaiksatamand please note, that every feature has all the associated componentst that need to be completed19:33
SumitNaiksatamlike docs, tempest tests, CLI, horizon, etc19:34
SumitNaiksatamas captured in the table on the wiki19:34
*** johnthetubaguy is now known as zz_johnthetubagu19:34
SumitNaiksatamand, we as a team, need to plan to cover all those aspects19:34
SumitNaiksatamanything else anyone wants to add?19:34
vishwanathj+119:34
SumitNaiksatamnot just this, but in general?19:34
vishwanathjagreed19:34
SridarKSumitNaiksatam: i am good19:35
SumitNaiksatamvishwanathj: thanks for posting the sequence diagrams19:35
vishwanathjwill add more as I go along19:35
SumitNaiksatamvishwanathj: that is a great community contribution!19:35
SumitNaiksatamfrom a fwaas perspective19:35
SridarK+119:35
SumitNaiksatamokay thanks all for joining, sorry for going over19:35
SumitNaiksatambye!19:35
vishwanathjit was a win win situation19:35
SridarKbye all thanks19:35
badvelibye19:35
vishwanathjbye19:36
pc_mbye!19:36
SumitNaiksatam#endmeeeting19:36
*** pc_m has left #openstack-meeting-319:36
SumitNaiksatamvishwanathj: absolutely, glad you see it that way19:36
yamahatabye19:36
vishwanathjthanks19:36
*** vishwanathj has quit IRC19:37
*** jckasper has joined #openstack-meeting-319:42
*** carl_baldwin has quit IRC19:49
*** carl_baldwin has joined #openstack-meeting-319:52
*** peristeri has joined #openstack-meeting-319:53
*** lintan__ has quit IRC19:55
*** annegent_ has quit IRC19:58
*** VW_ has quit IRC19:59
*** VW_ has joined #openstack-meeting-320:02
*** annegent_ has joined #openstack-meeting-320:04
*** sarob has quit IRC20:13
*** sarob has joined #openstack-meeting-320:16
*** gholler has quit IRC20:22
*** r1chardj0n3s_afk is now known as r1chardj0n3s20:22
*** r1chardj0n3s has left #openstack-meeting-320:23
*** vishwanathj has joined #openstack-meeting-320:24
*** mattfarina has quit IRC20:24
*** carl_baldwin has quit IRC20:25
*** sarob has quit IRC20:31
*** penick has joined #openstack-meeting-320:35
*** mrda-away is now known as mrda20:39
*** baoli has quit IRC20:42
*** rkukura has left #openstack-meeting-320:45
*** matrohon has quit IRC20:48
*** nelsnelson has quit IRC20:51
*** etoews has quit IRC21:01
*** lblanchard has quit IRC21:03
*** etoews has joined #openstack-meeting-321:03
*** annegent_ has quit IRC21:10
*** etoews has quit IRC21:13
*** mattgriffin has quit IRC21:13
*** mrmartin has quit IRC21:15
*** ChuckC_ is now known as ChuckC21:16
*** mrmartin has joined #openstack-meeting-321:17
*** mattgriffin has joined #openstack-meeting-321:18
*** mrmartin has quit IRC21:22
*** Networkn3rd has quit IRC21:25
*** sarob has joined #openstack-meeting-321:32
*** Piet has quit IRC21:33
*** SridarK has quit IRC21:33
*** baoli has joined #openstack-meeting-321:38
*** sergef has quit IRC21:43
*** julim has quit IRC21:45
*** belmoreira has joined #openstack-meeting-321:48
*** carl_baldwin has joined #openstack-meeting-321:52
*** sarob has quit IRC21:54
*** thangp has quit IRC21:57
*** bradjones has quit IRC21:57
*** carl_baldwin has quit IRC21:59
alaski#startmeeting nova_cells22:00
openstackalaski: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.22:00
dansmithfail22:00
alaskiSumitNaiksatam: can you #endmeeting please?22:00
alaskiwell, I guess we go off the record then22:01
alaskiAnyone here for the cells meeting?22:01
belmoreirahi22:01
*** bradjones has joined #openstack-meeting-322:01
dansmitho/22:02
alaskismall crowd today, but that's alright22:02
alaskitopic: Test failure22:02
*** melwitt has joined #openstack-meeting-322:02
alaskiThere have been some intermittent test failures in the tempest job22:03
alaskiI spent some time trying to repro locally, but I'm not seeing them22:03
melwittdid we start the meetbot22:03
alaskimelwitt: the last meeting didn't end properly :(22:03
dansmith#endmeeting22:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:03
openstackMeeting ended Wed Feb  4 22:03:44 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-02-04-18.30.html22:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-02-04-18.30.txt22:03
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-02-04-18.30.log.html22:03
dansmithIIRC, after 60 minutes, anyone can endmeeting it22:03
*** annegent_ has joined #openstack-meeting-322:04
melwittoh cool22:04
alaskioh, good to know22:04
alaski#startmeeting nova_cells22:04
openstackMeeting started Wed Feb  4 22:04:13 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. Information about MeetBot at http://wiki.debian.org/MeetBot.22:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:04
*** openstack changes topic to " (Meeting topic: nova_cells)"22:04
openstackThe meeting name has been set to 'nova_cells'22:04
alaski#topic Test failurs22:04
*** openstack changes topic to "Test failurs (Meeting topic: nova_cells)"22:04
alaskiargh22:04
*** s3wong has joined #openstack-meeting-322:04
dansmithuse #undo22:04
alaski#undo22:04
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x33399d0>22:04
dansmith(if you want)22:04
alaskisweet22:05
beaglesI thought it was pretty appropriate22:05
alaski#topic Test failures22:05
*** annegent_ has quit IRC22:05
*** openstack changes topic to "Test failures (Meeting topic: nova_cells)"22:05
beagles"failurs"22:05
melwittheh22:05
belmoreirahehe22:05
alaski:)22:05
alaskilast week bauzas exluded the last test we expect to fail on the check-tempest-dsvm-cells job22:06
alaskiso in theory it should be passing, but isn't22:06
alaskithe most common failure I've seen is an ec2 run idempotent job22:06
alaskiwhich I can't get to fail locally22:06
alaskihttp://logs.openstack.org/04/153004/3/check/check-tempest-dsvm-cells/dc1ee1f/console.html has an example22:07
alaskiany eyes on that are appreciated so we can get the job voting at some point22:07
melwittI'm also (still) running tests locally. since the instance object flavor field merged failures have changed a bit and I'm investigating22:08
alaskimelwitt: great22:08
alaskiany help on testing is much appreciated22:09
alaski#topic WIP22:09
*** openstack changes topic to "WIP (Meeting topic: nova_cells)"22:09
alaskihttps://review.openstack.org/#/c/150381/22:09
alaskiThere's a patch up for a quick PoC of multiple db support22:10
belmoreiraunfortunately Dheeraj is not here to comment22:10
alaskithat's alright22:10
belmoreirahe continues to look how to allow DB api to connect to different DBs22:11
alaskidansmith added some good comments to the review22:11
belmoreirayes, just saw it. Thanks22:11
alaskihe also mentioned passing info through the context for picking a db, which I think is a good idea22:11
*** etoews has joined #openstack-meeting-322:12
dansmithyeah, think that's how it's going to have to work,22:12
dansmithelse we'll need some major refactoring of db api22:12
alaskiagreed22:13
belmoreiraok22:13
alaskiwe can get into more specifics as work progresses, but that seems like the right mechanism to try22:13
alaskion my end I've been busy with other things that are wrapping up now, so I'm going to be coding furiously on this now22:14
alaskiso there should be some more code to look at soon22:14
alaski(it's also why this agenda is light)22:15
alaskiany other work to be called out?22:15
dansmithalaski: the flavor stuff merged, so I should try fixing the libvirt driver now, right?22:15
*** kevinbenton_ is now known as kevinbenton22:15
alaskidansmith: yes, that would be excellent22:15
dansmithalaski: and, does that mean that the flavor stuff didn't break cells?22:16
alaskiI think that ties into what melwitt has been investigating22:16
dansmithbecause that would be ... shocking22:16
dansmithah, melwitt you wanna do that?22:16
alaskidansmith: it appears that it didn't22:16
dansmithalaski: shocking22:16
alaskidansmith: heh, we had faith in you22:16
dansmithglad someone did :)22:16
alaskibut yes, the libvirt driver should be looked at in light of the flavors work22:17
belmoreiradansmith: can you point me to the flavor stuff?22:17
alaskiit's likely that a previous workaround can now be removed22:17
melwittalaski, dansmith: yes, it didn't make it worse from what I see so far, there's something different wrong now which I'm working out22:18
dansmithbelmoreira: https://review.openstack.org/#/c/135700/22:18
belmoreiradansmith: thanks22:18
dansmithmelwitt: boy, you really know how to compliment someone eh?22:18
dansmith:P22:18
*** Sukhdev has joined #openstack-meeting-322:18
alaskidoes someone want an action item to look at things?22:19
alaskimelwitt: I'm guessing you'll continue digging in?22:19
melwittdansmith: lol. not what I meant, sorry. from my understanding, the flavor stuff should have made 60 failures disappear but it didn't, the failures are now different. I've *almost* got a handle on what it is that I hope to confirm later today, then I will be asking you for help :P22:20
dansmithmelwitt: oh, really? I didn't expect it to fix any of those22:20
melwittdansmith: it should have because the problem was that cell couldn't access the flavor that existed only at the top. with flavor staying with the instance, it should have had all the info it needed to succeed22:21
alaskiit should mean that flavors don't need to exist in the cells db now22:21
dansmithmelwitt: ah, but only if the code that is looking up the flavor is using the per-instance interface22:21
dansmithmelwitt: so I think probably some more work is needed to convert those22:21
melwittI also figured out why the flavor not found problem got fixed and then returned. it got fixed the first time by garyk passing flavor obj down to driver22:21
dansmithmelwitt: so maybe tomorrow we can sync up on some of those failures and take a look at what changes might be easy?22:22
melwittbut then it broke again when I added a get flavor call to fill in extra_specs that he asked for22:22
alaskimelwitt: ahh22:22
melwittflavor get fails if you're in the non-top cell.22:22
dansmiththis should fix that22:23
dansmithbut we have to change the code to use the flavor on the instance instead of looking it up22:23
alaskiyeah, the work from garyk shouldn't be necessary any longer22:23
dansmithnor the extra_specs thing22:23
alaskiright22:23
alaskithere are some lookups in ironic that can be removed as well22:23
dansmithcool22:23
alaskiit sounds like melwitt has this in hand, with some possible assistance from dansmith22:24
melwitts/possible/probable :)22:25
dansmithcool22:25
dansmithhah22:25
alaskiso we'll move on22:25
dansmithI can offer probable assistance22:25
alaskimelwitt: keep him busy22:25
alaski#topic open discussion22:25
*** openstack changes topic to "open discussion (Meeting topic: nova_cells)"22:25
melwitt:)22:25
alaskiThere's still an open question of networking22:26
alaskiI spoke with anteaya at the nova midcycle and she should be getting me in touch with someone from neutron22:26
dansmithmeaning whether we support n-net, or how we organize cells and neutron?22:26
alaskithe latter22:26
dansmithso,22:26
dansmithif we associate a neutron endpoint per cell,22:26
belmoreiraalaski: that is great22:26
dansmiththen they can be the same or one per cell, or one per few cells right?22:27
*** tellesnobrega_ has joined #openstack-meeting-322:27
dansmithif we're switching db/mq per cell, no reason we can't also switch the neutron being used22:27
alaskidansmith: right.  but that assumes no longer using a global neutron22:27
dansmithand then in the migration code, we can initially just fail if the target node isn't the same neutron endpoint as us22:27
alaskior that it partitions similarly22:27
dansmithalaski: ah, I guess that might break some of our API stuff that expect a single pool of network resources22:28
alaskiright, so we need some discussion on where best to address that22:28
alaskiwe work around it at rackspace, but I need to reach out and see what limitations that causes22:29
*** tonyb has joined #openstack-meeting-322:29
dansmithyeah22:29
belmoreirathis is the inital spec for nova net to neutron migration: https://review.openstack.org/#/c/147723/122:30
* tonyb is massively late. Did I get volenteered for anything?22:30
dansmithtonyb: yeah, you're figuring out networking22:30
alaskiideally it would be nice if neutron partitioned along cell lines so we could do the multiple endpoint thing that you suggested dansmith22:30
tonybdansmith: awesome.  I can do that.22:30
alaskitonyb: yep, please report back in a week with the solution22:30
dansmithalaski: yeah, even if multiple partitions share a neutron22:30
belmoreiraalaski: in fact I was thinking in the other way arround... having a central neutron22:31
dansmiththat is likely going to require cells-like support in neutron I think,22:31
dansmithwhich is something we could wait a long time for22:31
tonybI22:32
tonybI'll talk to gus on the neutron side.  It's something we should consider as part of the migration planning that's going on.22:33
belmoreiraalaski: seems interesting... but I think that should be a long term goal...22:33
*** bpokorny has quit IRC22:33
alaskilong term it might make sense.  I'd like to get a sense of how the neutron group sees things22:33
alaskiI have the feeling that we're going to influence how neutron is deployed to work with cells22:34
alaskibut primarily I think we need to get everyone talking22:35
tonybalaski, dansmith (and others) do you have time after the nova meeting tomorrow to talk to some neutron folk? (if I can arrange it)22:35
alaskiwhich meeting time is it tomorrow?22:36
dansmiththat's the morning one22:36
dansmithand yeah, I prolly could22:36
*** s3wong has quit IRC22:36
alaskiyeah, I'll be around then22:36
tonybokay I'll see what I can do.22:36
alaskitonyb: thanks22:36
alaskiany other topics for discussion?22:37
dansmithmove to get back to work :)22:37
alaskisounds good to me22:37
alaski#endmeeting22:38
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:38
openstackMeeting ended Wed Feb  4 22:38:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:38
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-02-04-22.04.html22:38
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-02-04-22.04.txt22:38
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-02-04-22.04.log.html22:38
alaskithanks everyone!22:38
tonybDid you guys talk about testing befoer I arrived?22:38
alaskitonyb: we talked about the tempest job22:38
tonybalaski: okay I'll read the minutes.22:39
tonybif I have questions can I poke you?22:39
tonybor is it stupid late for you?22:39
alaskitonyb: sure, I'm around for about 20 more minutes22:39
tonybalaski: cool.22:39
*** nelsnelson has joined #openstack-meeting-322:57
*** jaypipes has quit IRC23:00
*** mattgriffin has quit IRC23:02
*** elmiko has joined #openstack-meeting-323:03
*** penick has quit IRC23:13
*** penick has joined #openstack-meeting-323:17
*** belmoreira has quit IRC23:20
*** banix has quit IRC23:20
*** rcleere_ is now known as rcleere_away23:21
*** reed has quit IRC23:24
*** peristeri has quit IRC23:31
*** baoli has quit IRC23:39
*** stevelle has joined #openstack-meeting-323:52
*** annegent_ has joined #openstack-meeting-323:55
*** markvoelker has quit IRC23:56
*** ryansb has joined #openstack-meeting-323:56

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