Wednesday, 2015-08-12

*** VW_ has quit IRC00:01
*** VW_ has joined #openstack-meeting-300:01
*** david-lyle has quit IRC00:03
*** puranamr has quit IRC00:05
-openstackstatus- NOTICE: Zuul was restarted due to an error; events (such as approvals or new patchsets) since 23:01 UTC have been lost and affected changes will need to be rechecked00:05
*** VW_ has quit IRC00:05
*** bharath has quit IRC00:07
*** puranamr has joined #openstack-meeting-300:07
*** puranamr has quit IRC00:12
*** puranamr has joined #openstack-meeting-300:12
*** nelsnelson has quit IRC00:24
*** stevemar has joined #openstack-meeting-300:31
*** stevemar has quit IRC00:34
*** stevemar has joined #openstack-meeting-300:40
*** nelsnelson has joined #openstack-meeting-300:40
*** stevemar has quit IRC00:41
*** Aish has quit IRC00:49
*** lexholden has quit IRC00:49
*** woodster_ has quit IRC00:50
*** bharath has joined #openstack-meeting-300:51
*** puranamr has quit IRC00:52
*** david-lyle has joined #openstack-meeting-300:54
*** bharath has quit IRC00:56
*** baoli has joined #openstack-meeting-301:12
*** sridhar_ram has quit IRC01:12
*** Brian___ has joined #openstack-meeting-301:13
*** zhenguo has joined #openstack-meeting-301:16
*** puranamr has joined #openstack-meeting-301:20
*** tqtran_ has quit IRC01:24
*** tobe_ has joined #openstack-meeting-301:39
*** nelsnelson has quit IRC01:44
*** baoli has quit IRC01:49
*** bknudson has quit IRC01:51
*** neelashah has joined #openstack-meeting-301:57
*** Aish has joined #openstack-meeting-301:59
*** baoli has joined #openstack-meeting-302:04
*** Brian___ has quit IRC02:05
*** ajmiller has joined #openstack-meeting-302:06
*** nelsnelson has joined #openstack-meeting-302:06
*** neelashah has quit IRC02:07
*** stevemar has joined #openstack-meeting-302:09
*** yamamoto has joined #openstack-meeting-302:09
*** yamahata has quit IRC02:15
*** Brian_ has joined #openstack-meeting-302:20
*** nelsnelson has quit IRC02:20
*** yamamoto has quit IRC02:23
*** david-lyle has quit IRC02:33
*** nelsnelson has joined #openstack-meeting-302:38
*** nelsnelson has quit IRC02:42
*** shwetaap has joined #openstack-meeting-302:44
*** bharath has joined #openstack-meeting-302:44
*** wendar has quit IRC02:46
*** wendar has joined #openstack-meeting-302:46
*** puranamr has quit IRC02:48
*** bharath has quit IRC02:49
*** yamamoto has joined #openstack-meeting-303:03
*** banix has quit IRC03:08
*** tobe_ has quit IRC03:15
*** tobe_ has joined #openstack-meeting-303:16
*** baoli has quit IRC03:23
*** baoli has joined #openstack-meeting-303:28
*** david-lyle has joined #openstack-meeting-303:30
*** sdake_ has joined #openstack-meeting-303:35
*** sdake has quit IRC03:39
*** stevemar has quit IRC03:44
*** sdake_ is now known as sdake03:46
*** bharath_ has joined #openstack-meeting-303:51
*** baoli has quit IRC03:55
*** bharath_ has quit IRC03:56
*** stevemar has joined #openstack-meeting-304:00
*** Brian_ has quit IRC04:05
*** Poornima has joined #openstack-meeting-304:18
*** Sukhdev_ has joined #openstack-meeting-304:19
*** puranamr has joined #openstack-meeting-304:38
*** Aish has quit IRC04:42
*** shwetaap has quit IRC04:50
*** terrylhowe has quit IRC04:51
*** tobe_ has quit IRC04:53
*** tobe_ has joined #openstack-meeting-305:04
*** Brian_ has joined #openstack-meeting-305:05
*** Brian_ has quit IRC05:40
*** bharath has joined #openstack-meeting-305:40
*** Aish has joined #openstack-meeting-305:43
*** bharath has quit IRC05:45
*** Brian_ has joined #openstack-meeting-305:57
*** Sukhdev_ has quit IRC05:58
*** hareeshp has joined #openstack-meeting-306:07
*** Poornima has quit IRC06:09
*** puranamr has quit IRC06:09
*** mrmartin has joined #openstack-meeting-306:11
*** zhenguo has quit IRC06:13
*** Aish has quit IRC06:15
*** hareeshp has quit IRC06:19
*** e0ne has joined #openstack-meeting-306:22
*** Poornima has joined #openstack-meeting-306:29
*** mrunge has joined #openstack-meeting-306:33
*** sahid has joined #openstack-meeting-306:34
*** sdake_ has joined #openstack-meeting-306:36
*** stevemar has quit IRC06:36
*** stevemar has joined #openstack-meeting-306:36
*** e0ne has quit IRC06:39
*** sdake has quit IRC06:39
*** stevemar has quit IRC06:40
*** e0ne has joined #openstack-meeting-306:40
*** e0ne has quit IRC06:45
*** e0ne has joined #openstack-meeting-306:49
*** e0ne has quit IRC06:54
*** bharath has joined #openstack-meeting-307:02
*** devvesa has joined #openstack-meeting-307:03
*** ig0r_ has joined #openstack-meeting-307:14
*** yamamoto has quit IRC07:20
*** yamahata has joined #openstack-meeting-307:24
*** yuikotakada has joined #openstack-meeting-307:34
*** zhenguo has joined #openstack-meeting-307:36
*** stevemar has joined #openstack-meeting-307:37
*** ig0r__ has joined #openstack-meeting-307:38
*** stevemar has quit IRC07:40
*** ig0r_ has quit IRC07:41
*** tobe_ has quit IRC07:44
*** tobe_ has joined #openstack-meeting-307:50
*** yamamoto has joined #openstack-meeting-307:51
*** ajmiller has quit IRC07:56
*** tobe_ has quit IRC08:00
*** vgridnev has joined #openstack-meeting-308:00
*** sdake_ has quit IRC08:04
*** tobe_ has joined #openstack-meeting-308:05
*** yamahata has quit IRC08:08
*** ajmiller has joined #openstack-meeting-308:12
*** ig0r__ has quit IRC08:13
*** ig0r_ has joined #openstack-meeting-308:17
*** ig0r_ has quit IRC08:19
*** yamamoto has quit IRC08:31
*** yamamoto has joined #openstack-meeting-308:32
*** tfukushima has joined #openstack-meeting-308:34
*** stendulker has joined #openstack-meeting-308:35
*** pavel_bondar has joined #openstack-meeting-308:43
*** lexholden has joined #openstack-meeting-308:52
*** lexholden has quit IRC08:53
*** lexholden has joined #openstack-meeting-308:54
*** stevemar has joined #openstack-meeting-309:38
*** stevemar has quit IRC09:41
*** bharath has quit IRC09:47
*** bharath has joined #openstack-meeting-309:49
*** yamamoto has quit IRC09:50
*** yamamoto has joined #openstack-meeting-309:51
*** bharath has quit IRC09:53
*** pavel_bondar has quit IRC10:05
*** jcoufal has joined #openstack-meeting-310:05
*** ig0r_ has joined #openstack-meeting-310:10
*** jkraj has joined #openstack-meeting-310:19
*** lexholden has quit IRC10:28
*** jcoufal has quit IRC10:35
*** ig0r_ has quit IRC10:46
*** bharath has joined #openstack-meeting-310:49
*** bharath has quit IRC10:54
*** alexpilotti has joined #openstack-meeting-310:55
*** jcoufal has joined #openstack-meeting-311:00
*** jcoufal has quit IRC11:01
*** jcoufal has joined #openstack-meeting-311:01
*** jcoufal has quit IRC11:02
*** mwagner_lap has quit IRC11:02
*** jcoufal has joined #openstack-meeting-311:02
*** tobe_ has quit IRC11:03
*** zhenguo has quit IRC11:03
*** tobe_ has joined #openstack-meeting-311:04
*** yamamoto has quit IRC11:08
*** tobe_ has quit IRC11:09
*** yuikotakada has quit IRC11:10
*** Poornima has quit IRC11:13
*** jcoufal has quit IRC11:15
*** stendulker has quit IRC11:18
*** robcresswell has joined #openstack-meeting-311:18
*** Brian_ has quit IRC11:19
*** Poornima has joined #openstack-meeting-311:19
*** Brian_ has joined #openstack-meeting-311:23
*** lexholden has joined #openstack-meeting-311:24
*** baoli has joined #openstack-meeting-311:33
*** tobe_ has joined #openstack-meeting-311:33
*** baoli has quit IRC11:35
*** baoli has joined #openstack-meeting-311:35
*** julim has joined #openstack-meeting-311:38
*** stevemar has joined #openstack-meeting-311:39
*** tobe_ has quit IRC11:39
*** matrohon has joined #openstack-meeting-311:41
*** stevemar has quit IRC11:42
*** Brian_ has quit IRC11:58
*** masco has joined #openstack-meeting-311:59
david-lyle#startmeeting horizondrivers12:00
openstackMeeting started Wed Aug 12 12:00:54 2015 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.12:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.12:00
*** openstack changes topic to " (Meeting topic: horizondrivers)"12:00
openstackThe meeting name has been set to 'horizondrivers'12:00
david-lyleany horizon folks around?12:01
mrungeyes!12:01
mrungegood morning david-lyle !12:01
david-lylegood afternoon mrunge12:01
robcresswellAfternoon12:02
robcresswellSo.. 3 of us?12:03
david-lyleI don't see many others online right now, so yeah12:03
mrungemakes decisions easier ;-)12:03
mascogood morning all12:03
mrungedavid-lyle, have you had the time to look at blueprints?12:04
david-lyleSo as discussed in last weeks Horizon team meeting, we wanted to clean up the blueprint backlog in horizon and get back to the point where we can provide more immediate feedback on new blueprints proposed. And to clean out ones that are obsolete or don't make sense any more12:05
mrungeor did anyone found out, which blueprints need to be discussed?12:05
david-lylejust wanted to record that for other12:05
david-lyles12:05
david-lylemrunge: I am open to plans of attach12:05
mrungeyes, we have way too many bps to act on12:05
david-lyle*attack12:05
robcresswellYup. Now would be a good time if anyone has a blueprint they are active on, to mention it.12:05
mrungemasco, I know you were about to open a bp12:06
mrungedid you already do it actually?12:06
david-lyleunfortunately, we can't sort bps by date12:06
david-lylewhich would be nice12:06
mascohttps://blueprints.launchpad.net/horizon/+spec/replace-sorteddict-with-ordereddict12:07
*** tsufiev has joined #openstack-meeting-312:07
tsufievo/12:07
mrungetsufiev, o/12:07
mrungemasco, yes! That's something fitting into django-1.8 as well12:08
mascomrunge, it was created by my fellow developer https://blueprints.launchpad.net/horizon/+spec/service-chaining-support12:08
mrungekeeping it separate makes sense as well12:08
*** tellesnobrega_ has joined #openstack-meeting-312:08
* mrunge was talking about https://blueprints.launchpad.net/horizon/+spec/replace-sorteddict-with-ordereddict12:08
david-lyleI think the bp masco linked makes perfect sense and is non-controversial as python 2.7 is the minimum in OpenStack12:08
mrungeyes12:08
robcresswellYup. Also 1.9 is supposed to be supported by the M release, so this needs to be done.12:09
david-lyleI don't see a reason not to approve, anyone?12:09
mascoit doesn't need much work, but i need you guys approval to start12:09
mrungeno, makes sense12:09
*** yamamoto has joined #openstack-meeting-312:09
* robcresswell is getting confused by all the double negatives12:09
mrungeand about prio here?12:09
david-lyleI put medium12:09
mrungegreat12:10
mascothanks!12:10
robcresswellIt's a blocker for 1.9 support it seems, so med or high IMO.12:10
david-lylemasco are you thinking Liberty or M for that?12:10
mascoi can submit in Liberty12:10
mrungejust added that12:11
*** VW_ has joined #openstack-meeting-312:11
david-lyleok, one down :)12:11
david-lylethanks masco12:11
mascothanks all12:11
mrungemasco had another one: https://blueprints.launchpad.net/horizon/+spec/service-chaining-support12:12
david-lyleok looking12:12
mrungethis is a bit more controversial, at least, it's not that simple12:12
mascome and mohan developing together on this, it in well progress12:12
david-lylemasco this does not require neutronclient changes?12:13
david-lyleor neutron changes?12:13
mascoit needs12:13
david-lylethose would be "outside dependencies"12:13
mascothat is under developing12:13
masconot sure it may up for review12:13
mrungewe can not rely on unreleased features12:14
mascoagree,12:14
*** cbouch has joined #openstack-meeting-312:14
david-lyleplease update with patches if available, or at least not that changes are needed in neutron and neutronclient12:14
david-lyle*note12:15
robcresswellIMO, that bp cannot be targeted yet as it is waiting on unmerged changes to Neutron12:15
mrungeyes12:15
david-lyleright12:15
mascoi added here to get confirmation from the cores and avoid the duplicate work12:15
mascoi will add a note as you said david-lyle12:15
mrungeon the other side, it's no question, we should support that, once its implemented in neutron12:15
david-lylepriority?12:16
mascoyes12:16
mrungecurrently?12:16
david-lyleno, I'd like to prioritize12:16
*** tellesnobrega_ has quit IRC12:16
david-lylemakes sifting through later easier12:16
mrungemedium I'd say12:16
robcresswellFor now I would mark as Low. It's a very specific feature it seems, and can be reevalutated later?12:17
mrungesure12:17
david-lyleI was thinking low to medium12:17
robcresswellEither is fine.12:18
david-lyleset to low, I agree with robcresswell, once it's concrete in neutron we can increase if necessary12:18
robcresswellcool12:18
masco:)12:18
mrungeshould masco try to get guidance from UX folks for this?12:18
mrungeI think visualization might be tricky?12:18
david-lyleThat would probably be a good idea12:18
robcresswellYeah, if you have an idea on implementation, discuss the layout with Piet & co.12:18
robcresswellThen when the code is merged to neutron, there is no arguing/ delay on design12:19
mascosure, i will do12:19
mrungemasco, if you need a pointer to Piet, I can make a contact12:19
mascoyes mrunge, i will ask you about this12:19
mascothanks12:20
mrungewill do that later12:20
mascosure12:20
mrungelooking at https://blueprints.launchpad.net/horizon12:20
mrungeI was just looking at high prio bps12:21
robcresswellIs there an API for this? Interface is so useless >.<12:21
robcresswelllaunchpad blueprints I mean :)12:21
mrungethere's https://blueprints.launchpad.net/horizon/+spec/api-capability-detection12:21
mrungemaybe we should pull all bps into a google docs12:21
mrungejust to be sure, we're looking at each just once12:21
robcresswellheh, we just need some better filtering mechanisms12:22
*** pavel_bondar has joined #openstack-meeting-312:22
david-lylethat's an old bp12:23
mascomrunge, the BP is already approved12:23
mrungeyes, but nobody is working on it12:23
mrungeI thought it was a candidate for removing12:23
david-lyleI think it is12:23
david-lyleuntil someone is ready to run with it12:24
david-lylethere is no detail in there12:24
mrungelet's drop it then?12:24
david-lyleI think so12:24
*** Poornima has quit IRC12:24
robcresswellScrolling through started and unprioritised ones. This could be closed, it looks like it was solved in a patch: https://blueprints.launchpad.net/horizon/+spec/remove-unittest212:25
mascowe just remove the assignee then only other ppl will try to pick12:25
mrungeso, how to remove it...12:25
*** yamamoto has quit IRC12:25
robcresswellMark Obsolete?12:26
mascoho, i thought cores have permission ;)12:26
mrungeyes, they have12:26
mrungebut that is really obfuscated in launchpad12:26
david-lyleok marked and not added12:26
david-lyle*note12:27
vgridnevhey guys, there is an blueprint related for sahara https://blueprints.launchpad.net/horizon/+spec/sahara-node-processes-tab ; implementation is already on review and well reviewed by sahara folks12:27
mrungeyay two less to go12:27
robcresswellvgridnev: Looking12:27
david-lyleseems widely supported by the sahara team, looking at the patch12:29
robcresswellLooks like a pretty small bp. I think Liberty, Low priority. It's just a layout redesign.12:29
mrungeagree with robcresswell12:29
vgridnevrobcresswell, agreed12:29
masco+112:30
david-lyleok updated12:30
mrungethanks vgridnev for bringing this up12:31
david-lylethanks vgridnev12:31
robcresswellYou missed milestone btw12:31
david-lylethat's after the fact now12:31
david-lyleonly set when completed12:31
mrungevgridnev, that reorg does not touch tests at all?12:31
robcresswellOh, okay12:31
david-lylechange this release12:32
robcresswellGotcha12:32
robcresswellIs that the same with bugs?12:32
david-lylewe realized planning was mostly futile12:32
david-lylerobcresswell: for the most part12:32
robcresswellOr should I still be targetting the merged ones12:32
david-lylebugs that need to be fixed before release should be targetted12:32
robcresswellSure okay12:32
robcresswellYeah I tend to target any merged ones or critical blockers12:33
mascoi have one more to review https://blueprints.launchpad.net/horizon/+spec/instance-rescue-horizon-support12:33
david-lyleAt some point I would like to dig into a few of the angular related bps, but I think we need a wider audience for htat12:33
david-lyle*that12:33
mascoimplementation is done already12:34
robcresswelldavid-lyle: We can do that next week. I'll get a list together.12:34
mrungeawesome robcresswell12:34
david-lylethanks robcresswell, I think that work is too scattershot at this point, I would like to provide better focus12:35
david-lylemasco: looking12:35
robcresswellI think there is actually a fair amount of organisation behind the scenes, but it needs to be better shown to the community.12:35
mascocoming with list BP before meeting will be good12:36
mrungeyes12:36
tsufievit this meeting meant as well for drawing attention to the bps which are approved and the code is complete, but not reviewed?12:36
david-lyleunrescue instance12:36
david-lylethat sounds strange12:36
mrungetsufiev, intention is to clean up abandoned blueprints, review new ones12:37
robcresswelltsufiev: Not really, this is mainly for bp review and cleanup12:37
vgridnevmrunge, since bp was approved, we can continue discussions on patch, right? btw, right now it's was tested manually. If you want to have tests there, I will add that12:37
tsufievmrunge, robcresswell: ah, okay12:37
david-lyletsufiev, no if the bp is approved already, it's outside the scope of this, unless you think it should be abandoned12:37
masconova command itself named as unrescue :)12:37
mrungewe have alist of 297 blueprints. I'm confident, on all are being worked on12:37
tsufievgot it12:37
mascocome out from rescue is unrescue12:38
david-lylemasco: it's like I pulled you out of the flooded river and now I'm going to throw you back in12:38
mrungevgridnev, I agree, tests are out of scope for bp review. I still think, having tests would be beneficial12:38
david-lylejust sounds odd12:38
*** bharath has joined #openstack-meeting-312:38
masco:)12:39
david-lylebut word smithing can happen later12:39
david-lyleso masco in your bp, we're just setting the state, and the repair happens elsewhere?12:40
mascoyes, it is just enabling the nova rescue cmd in horizon12:41
robcresswellHow is this different to logging in via the terminals that instances already expose btw?12:41
mascoif it went to error state you can't login robcresswell12:42
mascoso you can use other image to access the error instance and do repair12:42
robcresswellInteresting12:43
*** bharath has quit IRC12:43
david-lyleseems reasonable to me12:43
robcresswellSince this is already fully supported by nova, I think medium? Also, it may be sensible to reach out to UX and see if they have any ideas on display.12:43
david-lylerobcresswell: I think we have a pattern here already for display12:44
*** alexpilotti has quit IRC12:44
mrungeyeah, it's described in the bp12:44
david-lyleit's just a modal saying here's you pass or ssh key to access the rescued instance12:44
david-lyleI'm inclined to leave it a low12:45
david-lylenot really a mainline feature12:45
mrungeyupp12:45
robcresswellSure, I was drawing the comparison with the other feature in my mind12:45
robcresswellbut Low is fine12:45
david-lyleupdated12:45
david-lylenext?12:45
robcresswellwoohoo! Is that.. 5 down?12:46
*** jcoufal has joined #openstack-meeting-312:46
*** jcoufal has quit IRC12:46
mrunge2 down from 297 bp overall12:46
*** alexpilotti has joined #openstack-meeting-312:46
mascothanks all once again :)12:46
*** jcoufal has joined #openstack-meeting-312:46
mrungewe have https://blueprints.launchpad.net/horizon/+spec/realtime-spec and https://blueprints.launchpad.net/horizon/+spec/rpc-listener12:47
robcresswellI meant from those that were not review/ prioritised, we've looked at several and obsoleted 2.12:47
robcresswellSo far so good.12:47
mrungeI'd be inclined to obsolete both12:47
mrungeagree, robcresswell12:47
david-lyleyes, that still needs to happen but probably needs a new start12:47
mrungeah, and https://blueprints.launchpad.net/horizon/+spec/realtime-communication on the same topic12:48
robcresswellAgree with obsoletion.12:48
mrungeso, obsolete all three?12:48
david-lylethe last one had code12:48
mrungeright12:48
robcresswellFirst two, havent looked at third yet, one sec12:48
david-lyleI remembered code12:49
mrungethere was code12:49
mrungehttps://review.openstack.org/#/c/40198/12:49
tsufievdavid-lyle, I've heard from Travis that he was going to do some study in the realtime communications in M release (for SearchLight)12:50
robcresswellHmm. I still think this one (third one) could be obsolete. All of the code is 2 year old demo code with no merges. Would it be picked up again, or better to start over at this point?12:51
david-lyletsufiev: yes, just wondering of leveraging some of the work tomas started would be usefule12:51
tsufievbut most likely nobody would be hurt if the old bp is obsoleted and a new one is created12:51
*** yamamoto has joined #openstack-meeting-312:51
*** terrylhowe has joined #openstack-meeting-312:52
david-lyleI marked all 3 as obsolete12:52
david-lylebut bookmarked the one with code to look at again12:52
robcresswell+112:52
mrungegreat12:53
mascoagree12:53
david-lylehttps://blueprints.launchpad.net/horizon/+spec/user-registration12:53
david-lylewon't happen12:53
mrungeyes12:53
david-lyleI had it as blocked, but I think it's best just to remove12:53
robcresswellNice. If we can keep covering 10 - 15 bps a week this could be very productive. I'll bring a list for angular next week so hopefully we can be even faster.12:54
mrungealthough has been requested several times, david-lyle12:54
mrungebut I completely agree12:54
david-lyleyeah I've been leaving as a "do not enter" sign12:54
mascokeystone will not allow to create12:54
*** yamamoto has quit IRC12:54
david-lylemasco: that's why it's blocked :)12:55
robcresswellOh, this does get mentioned often. But the bp itself is not useful/ relevant in its current state12:55
masco:)12:55
*** VW_ has quit IRC12:56
*** VW_ has joined #openstack-meeting-312:56
david-lyleobsolete12:56
mrungea last one?12:57
david-lylewith note12:57
david-lyleuser-registration12:57
mrungeyupp12:57
david-lylesure12:57
masco+112:57
david-lylemisunderstood the question12:57
david-lylewhich one mrunge?12:57
mrungeuhm, I was looking for a last bp to review/obsolete12:57
mrungee.g this one: https://blueprints.launchpad.net/horizon/+spec/scaling-trigger-ceilometer-integration12:57
mrungesounds useful; although it looks like a heat feature12:58
*** Brian_ has joined #openstack-meeting-312:58
david-lylehttps://blueprints.launchpad.net/horizon/+spec/dashboards-decoupling has not seen any progress12:58
mrungeyupp12:59
mrungeobsolete both?12:59
robcresswellYes13:00
robcresswellNeither has code13:00
robcresswellNor much detail :)13:00
*** Aish has joined #openstack-meeting-313:00
mrungegreat13:00
mrungethat was quite productive!13:00
*** VW_ has quit IRC13:01
robcresswellYup. Total reduced by 8 I think, and a few more prioritised.13:01
david-lyleexcellent13:01
robcresswellI will prep a list of angular bps today so it's ready for next week.13:01
*** nelsnelson has joined #openstack-meeting-313:01
*** nelsnelson has quit IRC13:01
robcresswellbefore I forget. Should only take a small while.13:01
robcresswellThanks all13:01
david-lylerobcresswell: when you do, can you put it on the agenda for next week13:02
mrungeawesome!13:02
robcresswellWill do13:02
*** nelsnelson has joined #openstack-meeting-313:02
mascosounds good13:02
*** jpomeroy has quit IRC13:02
david-lylethanks for your time and effort. I feel good about the progress.13:02
david-lyle#endmeeting13:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"13:02
openstackMeeting ended Wed Aug 12 13:02:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)13:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-08-12-12.00.html13:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-08-12-12.00.txt13:02
*** tsufiev has left #openstack-meeting-313:02
openstackLog:            http://eavesdrop.openstack.org/meetings/horizondrivers/2015/horizondrivers.2015-08-12-12.00.log.html13:02
mrungeyes, thanks all13:02
mascobye all13:03
*** Brian_ has quit IRC13:03
*** shwetaap has joined #openstack-meeting-313:08
*** pkarikh has joined #openstack-meeting-313:09
*** robcresswell has left #openstack-meeting-313:10
*** sreshetnyak has quit IRC13:14
*** vgridnev has quit IRC13:15
*** obondarev has quit IRC13:15
*** singlethink has joined #openstack-meeting-313:15
*** cbouch_ has joined #openstack-meeting-313:18
*** mwagner_lap has joined #openstack-meeting-313:19
*** cbouch has quit IRC13:21
*** masco has quit IRC13:21
*** vgridnev has joined #openstack-meeting-313:23
*** yamamoto has joined #openstack-meeting-313:25
*** jcoufal has quit IRC13:25
*** sreshetnyak has joined #openstack-meeting-313:26
*** Brian_ has joined #openstack-meeting-313:28
*** jpomeroy has joined #openstack-meeting-313:29
*** singleth_ has joined #openstack-meeting-313:30
*** puranamr has joined #openstack-meeting-313:31
*** neelashah has joined #openstack-meeting-313:32
*** Brian_ has quit IRC13:32
*** irenab has joined #openstack-meeting-313:33
*** singlethink has quit IRC13:33
*** VW_ has joined #openstack-meeting-313:34
*** puranamr has quit IRC13:36
*** puranamr has joined #openstack-meeting-313:38
*** stevemar has joined #openstack-meeting-313:39
*** tellesnobrega has quit IRC13:41
*** tellesnobrega has joined #openstack-meeting-313:42
*** jaypipes has joined #openstack-meeting-313:42
*** lblanchard has joined #openstack-meeting-313:43
*** stevemar has quit IRC13:43
*** mrunge has quit IRC13:49
*** moshele has joined #openstack-meeting-313:53
*** Piet has quit IRC13:54
*** yapeng has joined #openstack-meeting-313:54
*** VW__ has joined #openstack-meeting-313:54
*** amuller has joined #openstack-meeting-313:55
*** ShillaSaebi has joined #openstack-meeting-313:56
*** ShillaSaebi has left #openstack-meeting-313:56
*** VW_ has quit IRC13:57
*** ihrachyshka has joined #openstack-meeting-313:59
*** VW__ has quit IRC13:59
*** sridhar_ram has joined #openstack-meeting-314:00
*** jschwarz has joined #openstack-meeting-314:00
jschwarzwoooo meeting!!!14:00
*** jlibosva has joined #openstack-meeting-314:00
*** VW_ has joined #openstack-meeting-314:00
*** vikram has joined #openstack-meeting-314:00
jlibosvao/14:00
*** gsagie has joined #openstack-meeting-314:00
moshelehi14:00
*** Ramanjaneya has joined #openstack-meeting-314:00
*** sdake_ has joined #openstack-meeting-314:00
irenabhi14:01
RamanjaneyaHi14:01
ihrachyshkahi all. we'll wait a minute before starting14:01
ajohi :)14:01
*** Aish has joined #openstack-meeting-314:01
*** sfinucan has joined #openstack-meeting-314:01
*** Aish has quit IRC14:01
ihrachyshkaok, let's go14:01
ihrachyshka#startmeeting neutron_qos14:02
openstackMeeting started Wed Aug 12 14:02:00 2015 UTC and is due to finish in 60 minutes.  The chair is ihrachyshka. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: neutron_qos)"14:02
openstackThe meeting name has been set to 'neutron_qos'14:02
ihrachyshka#topic Announcements14:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_qos)"14:02
ihrachyshkafirst thing first: hopefully, feature/qos lives its last days: we'll request merge back today.14:02
*** VW_ has quit IRC14:02
ajoyipieeee :)14:02
* amuller cries14:02
ihrachyshkaI'll send an email later once the merge patch is up for review, and ajo said he'll post a video with the feature14:02
*** VW_ has joined #openstack-meeting-314:03
* ajo ajo is on it :)14:03
*** ajmiller has quit IRC14:03
ihrachyshkathe original plan was to request merge on Mon, but on Mon we had some things to fix, like devref or the fact that we limited ingress instead of egress ;)14:03
* jschwarz a video! \o/14:03
ihrachyshkaand yesterday we had gate failures that are now fixed14:03
ihrachyshkaI expect remaining feature/qos patches to merge in an hour. so stay tuned.14:04
ihrachyshkaany remaining work will proceed in master14:04
ajoack14:04
*** absubram has joined #openstack-meeting-314:04
ihrachyshka(unless there are major flaws that will need fix before merge-back)14:04
ajoI found a issue with policy.json that will need fix,14:04
ajoit will allow a tenant creating a policy, a rule, but crashes when updating a rule14:05
ajotenants should not create qos policies , or rules for this release14:05
ihrachyshkagood. we have stuff to fix, that's for sure.14:05
ajoyes14:05
ihrachyshka#topic ongoing work14:05
*** openstack changes topic to "ongoing work (Meeting topic: neutron_qos)"14:05
ihrachyshkaso I know that moshele was looking into refactoring qos extension drivers API. he has a patch: https://review.openstack.org/211090 but now it's abandoned14:06
ihrachyshkamoshele, I guess you'll revive it once in master, right?14:06
mosheleyes14:07
ihrachyshkaalso, jschwarz was working on fullstack tests. and we have one: https://review.openstack.org/202492 but since it requires neutronclient changes first, it will wait14:07
jschwarzyes14:07
ihrachyshkafinally, we have client changes: https://review.openstack.org/189655 and https://review.openstack.org/198277 thanks to vikram, Ramanjaneya and jschwarz for supporting those14:08
ihrachyshkaI hope we'll get them in quick after neutron merge14:08
Ramanjaneyajschwarz: anything pending on neutron-client part?14:08
ihrachyshkathen we'll be able to proceed on fullstack14:08
irenabihrachyshka: spec update is waiting for second +214:08
ihrachyshkaajo, was that an issue in client to solve with the name filter? ^14:09
ajoihrachyshka, correct,14:09
ihrachyshkaoh right. we have spec to update:14:09
jschwarzihrachyshka, as ajo mentioned, we found a but on the neutronclient where the rule might be searched for using a name14:09
ihrachyshka#link https://review.openstack.org/19911214:09
ihrachyshkaplease review ^ and we'll make sure it's in :)14:09
jschwarzthat's of course an error because rules don't have a name. I'm looking into that now14:09
ajothanks jschwarz14:09
jschwarzof course14:09
ihrachyshkaother than that, we will still have some TODOs here and there to solve, but nothing critical.14:10
ihrachyshkaI guess once client and server and spec are in, we can claim bp is done? fullstack will go as an optional beyond the blueprint I guess since it may take time to get the depending patches in first.14:10
ihrachyshkawhat do you think?14:11
*** Ramanjaneya has quit IRC14:11
ihrachyshkaanything failing beyond it should be handled as a bug I thinik14:11
jschwarzsounds good to me14:11
ihrachyshkaok, I assume silence means everyone agrees :)14:12
amullernay14:12
ajojschwarz, vikram : looking at the spec:14:12
ajoneutron qos-bandwidth-limit-rule-update <policy-name-or-id> <rule-id>14:12
ihrachyshkaNAY!14:12
amulleryou cannot claim the blueprint is complete without an integration test imo14:12
ajobut the client expects the opposite14:12
ajo<rule-id> <policy> which is counter intuitive14:12
ihrachyshkaamuller, hm. like... any other blueprint?14:12
jschwarzajo, well, that's not really something we can change I think...14:12
amullerihrachyshka: can we try and raise the bar?14:12
amulleris there anything blocking the fullstack test after merge to master?14:13
jschwarzajo, the lbaas guys did opposite of what you wrote as well.. changing that goes deep into neutronclient mechanics I think14:13
ihrachyshkaamuller, we obviously can. I just wonder what it buys us. do you think we will stop working on fullstack right after it's marked done?14:13
*** sigmavirus24_awa is now known as sigmavirus2414:13
ajojschwarz, ok, then we need to fix the spec14:13
ihrachyshkaamuller, I guess we need to go and review patches that jschwarz rebased..14:13
jschwarzamuller, the neutronclient patches also block the fullstack test, and neutronclient is blocked because the gate is broken for that repo.14:14
ihrachyshkaamuller, ok, if you are against, I take it as order :)14:14
jschwarz(for the last week)14:14
ihrachyshkaamuller, heh. and here you should put your testing hat on!14:14
*** yamahata has joined #openstack-meeting-314:14
*** jreeves has joined #openstack-meeting-314:15
amullertime to fix a gate then...14:15
ihrachyshkaamuller, are you into the fix? are you in touch with pc_m?14:15
amullernot at all14:15
amullerI'll do that though14:15
ihrachyshkathank you14:15
ihrachyshkaI think they may not see the end of the tunnel :)14:15
ihrachyshkaok, let's move to open agenda14:16
ihrachyshka#topic open agenda14:16
*** openstack changes topic to "open agenda (Meeting topic: neutron_qos)"14:16
ihrachyshkaajo, so can you update us about why tenants should not create policies?14:16
jschwarzso we need to revisit the policy.json settings14:16
ajoihrachyshka: yes14:16
ajothe initial plan was to only let admins create and maintain policies/rules14:16
ajoif a policy is shared, a tenant can attach it to a port or net14:16
ajobut not otherwise14:17
ajoin the future, RBAC will make that more modular14:17
*** banix has joined #openstack-meeting-314:17
ajopeople willing to let their tenants do qos themselves, will have to modify policy.json, and we will document that14:17
ihrachyshkaajo, but it's supported, right?14:17
ihrachyshkawith the policy change of course14:17
ajoihrachyshka, yes14:17
ihrachyshkawe have the code to handle access, kudos to jschwarz14:18
ajojschwarz++14:18
jschwarz^_^14:18
ajoyes, we have to review and tune the policies14:18
ajoand provide the 2nd alternate (open example) in documentation14:18
ihrachyshkaif we would have time, we could even get RBAC this cycle14:18
ajoI'd leave that for M14:18
ihrachyshkaI think it's quite pluggable the way kevinbenton implements it14:18
*** Ramanjaneya has joined #openstack-meeting-314:18
jschwarzihrachyshka, RBAC still has unmerged code so...14:18
ajoI believe we should focus in polishing, testing and debugging14:18
jschwarzi agree with ajo here14:19
ihrachyshkajschwarz, well, I'm almost sure it's a matter of days.14:19
ihrachyshkaI see a lot of review traction around it14:19
ihrachyshkaok, let's polish :)14:19
ihrachyshkaor czech :)14:19
ajolol14:19
jschwarz:)14:19
*** Ramanjaneya has quit IRC14:19
ajoI'm more comfortable with spanish14:19
jschwarzhebrew?14:19
ajo:)14:20
jlibosvanah, no czech :*14:20
jlibosva:(14:20
*** puranamr has quit IRC14:20
jschwarzihrachyshka, in regards to the open agenda; neutronclient still requires a bit of work - there's that rule-naming thing and a few reviews still left unhandled14:20
ihrachyshkaanything else ongoing or needs discussion?14:20
ihrachyshkajschwarz, I bet you are on it14:20
jschwarzI'll get to them by tomorrow I think - it will be ready by time for L for sure.14:20
jschwarzXD14:20
ihrachyshkasee?!! I tell ya14:21
jschwarzjust letting you know so that there are no surprises ;-)14:21
ihrachyshkaoverall people, good work on the branch, I look forward to see us polishing the feature in another one ;)14:21
irenabI have f question regarding nova flavor extra_spec settings for qos, but maybe we can discuss it next week, after pre-merge crisis is over14:22
ihrachyshkajschwarz, I don't remember when there were any surprises from your side. it's generally like 'yeah, there is an issue. and btw, the fix is up'14:22
jschwarzihrachyshka, thanks ^_^14:22
ihrachyshkairenab, ok cool.14:22
*** puranamr has joined #openstack-meeting-314:22
ajoirenab, that's documented on the spec, nova can set flavors for qos, but that's not compatible with ours14:22
irenabplease check the spec update patch and if something else need correction, lets add it14:23
*** gsagie has left #openstack-meeting-314:23
ajoirenab, just added a nit now14:23
ihrachyshkaso if there is nothing critical, I suggest we end the meeting now and I go check the queue on whether I can proceed with merge request already.14:23
irenabajo: I think we should check ifwe can integrate both14:23
ajoirenab, yes, we will certanly need to integrate for scheduling / guarantee purposes14:23
ihrachyshkaajo, I think it's two parallel things, but let's move it to the next week :)14:23
ajoirenab: I'm already talking with nikola dipanov for that :)14:23
ihrachyshkaajo++14:23
jschwarzajo, do you want to work on the spec change re: neutronclient and I'll do the review afterwards?14:24
irenabfor users its easier to manage per flavor qos requremens14:24
irenabajo: please loop me in14:24
ajoirenab, yes, also assigning neutron qos flavors to nova would be cool14:24
ajoif that's what you mean :)14:24
ajoirenab: I will :)14:24
irenabajo: I think so :-)14:24
*** jmckind has joined #openstack-meeting-314:26
ihrachyshkaok, I take the silence as the lack of more critical things to discuss14:26
ihrachyshka#endmeeting14:27
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:27
openstackMeeting ended Wed Aug 12 14:27:00 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:27
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-08-12-14.02.html14:27
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-08-12-14.02.txt14:27
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2015/neutron_qos.2015-08-12-14.02.log.html14:27
*** amuller has left #openstack-meeting-314:27
ihrachyshkao/14:27
jschwarzbb14:27
irenabbye14:27
*** bharath has joined #openstack-meeting-314:27
jlibosvabye14:27
*** jlibosva has left #openstack-meeting-314:27
*** jschwarz has left #openstack-meeting-314:28
*** carl_baldwin has joined #openstack-meeting-314:28
ajoo/14:28
ajothanks ihrachyshka ! ;)14:28
ajothanks *14:28
ajo:)14:28
irenabajo: have a min?14:29
ajoirenab, yes, sure :)14:29
irenabneutron irc?14:29
irenabhere?14:29
ajoyeah, that sounds good, irc works in general :)14:29
ajo#openstack-neutron :)14:29
*** stevemar has joined #openstack-meeting-314:30
*** bharath has quit IRC14:32
*** puranamr has quit IRC14:32
*** yamahata has quit IRC14:33
*** puranamr has joined #openstack-meeting-314:34
*** jreeves has left #openstack-meeting-314:35
*** ajmiller has joined #openstack-meeting-314:38
*** bharath has joined #openstack-meeting-314:39
*** banix has quit IRC14:39
*** jmckind has quit IRC14:44
*** Piet has joined #openstack-meeting-314:45
*** iymht has joined #openstack-meeting-314:49
*** galstrom_zzz is now known as galstrom14:52
*** moshele has left #openstack-meeting-314:56
*** cbouch_ has quit IRC14:59
*** cbouch_ has joined #openstack-meeting-314:59
*** iymht has quit IRC15:02
*** alexpilotti has quit IRC15:03
*** banix has joined #openstack-meeting-315:03
*** sridhar_ram has quit IRC15:05
*** DuncanT has quit IRC15:05
*** skath has quit IRC15:05
*** flwang has quit IRC15:06
*** jckasper has quit IRC15:06
*** skath has joined #openstack-meeting-315:07
*** DuncanT has joined #openstack-meeting-315:07
*** iben has joined #openstack-meeting-315:10
*** masco has joined #openstack-meeting-315:12
*** flwang has joined #openstack-meeting-315:13
*** woodster_ has joined #openstack-meeting-315:18
*** puranamr has quit IRC15:21
*** puranamr has joined #openstack-meeting-315:21
*** terrylhowe has left #openstack-meeting-315:26
*** iben has quit IRC15:35
*** pballand has joined #openstack-meeting-315:35
*** zhenguo has joined #openstack-meeting-315:36
*** tqtran has joined #openstack-meeting-315:37
*** salv-orl_ has joined #openstack-meeting-315:37
*** salv-orlando has quit IRC15:40
*** cbouch__ has joined #openstack-meeting-315:40
*** zhenguo has quit IRC15:42
*** cbouch_ has quit IRC15:43
*** geoffarnold has joined #openstack-meeting-315:44
*** banix has quit IRC15:48
*** jckasper has joined #openstack-meeting-315:57
*** jcoufal has joined #openstack-meeting-315:59
*** singleth_ has quit IRC16:04
*** vgridnev has quit IRC16:04
*** iymht has joined #openstack-meeting-316:04
*** puranamr has quit IRC16:04
*** puranamr has joined #openstack-meeting-316:05
*** mrmartin has quit IRC16:06
*** puranamr has quit IRC16:06
*** puranamr has joined #openstack-meeting-316:07
*** mrmartin has joined #openstack-meeting-316:07
*** mrmartin has quit IRC16:07
*** mrmartin has joined #openstack-meeting-316:08
*** singlethink has joined #openstack-meeting-316:08
*** iben has joined #openstack-meeting-316:08
*** iymht has quit IRC16:11
*** sankarshan is now known as sankarshan_away16:11
*** jkraj has quit IRC16:11
*** devvesa has quit IRC16:11
*** sdake_ is now known as sdake16:13
*** sahid has quit IRC16:13
*** ivar-lazzaro has joined #openstack-meeting-316:14
*** ivar-lazzaro has quit IRC16:14
*** ivar-lazzaro has joined #openstack-meeting-316:15
*** sigmavirus24 is now known as sigmavirus24_awa16:18
*** iymht has joined #openstack-meeting-316:19
*** vikram has quit IRC16:20
*** mrmartin has quit IRC16:22
*** mrmartin has joined #openstack-meeting-316:22
*** bharath has quit IRC16:25
*** bharath has joined #openstack-meeting-316:25
*** sigmavirus24_awa is now known as sigmavirus2416:25
*** mickeys has joined #openstack-meeting-316:27
*** VW__ has joined #openstack-meeting-316:27
*** iymht has quit IRC16:28
*** VW_ has quit IRC16:29
*** pballand has quit IRC16:29
*** iben has quit IRC16:30
*** singlethink has quit IRC16:31
*** vikram has joined #openstack-meeting-316:33
*** singlethink has joined #openstack-meeting-316:34
*** dheeraj-gupta-4 has joined #openstack-meeting-316:35
*** dheeraj-gupta-4 has quit IRC16:35
*** Brian_ has joined #openstack-meeting-316:37
*** Piet has quit IRC16:39
*** salv-orl_ has quit IRC16:40
*** salv-orlando has joined #openstack-meeting-316:41
*** Brian_ has quit IRC16:42
*** persia has quit IRC16:42
*** matrohon has quit IRC16:45
*** iben has joined #openstack-meeting-316:46
*** lalitd has joined #openstack-meeting-316:49
*** sankarshan_away is now known as sankarshan16:50
*** salv-orlando has quit IRC16:54
*** salv-orlando has joined #openstack-meeting-316:54
*** Yi has joined #openstack-meeting-316:55
*** FallenPegasus has joined #openstack-meeting-316:58
*** ivar-lazzaro has quit IRC16:58
*** dheeraj-gupta-4 has joined #openstack-meeting-316:59
*** ivar-lazzaro has joined #openstack-meeting-316:59
alaski#startmeeting nova_cells17:00
openstackMeeting started Wed Aug 12 17:00:15 2015 UTC and is due to finish in 60 minutes.  The chair is alaski. 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: nova_cells)"17:00
openstackThe meeting name has been set to 'nova_cells'17:00
alaskianyone around for the meeting today?17:00
dheeraj-gupta-4o/17:00
dansmitho/17:00
*** singleth_ has joined #openstack-meeting-317:00
melwitto/17:00
alaski#topic Tempest testing17:01
*** openstack changes topic to "Tempest testing (Meeting topic: nova_cells)"17:01
alaskimelwitt: anything to report here?17:01
lalitdhello17:01
alaskibtw, I updated the goo.gl link in the wiki because the job name changed17:01
*** Piet has joined #openstack-meeting-317:02
melwittalaski: oh cool. I don't have anything to report17:02
alaskimelwitt: great, thanks17:02
alaski#topic open reviews17:02
*** openstack changes topic to "open reviews (Meeting topic: nova_cells)"17:02
*** mlavalle has joined #openstack-meeting-317:02
alaskinew flavor tables in the api db at https://review.openstack.org/#/c/201606/17:02
alaskiand request spec persistence at https://review.openstack.org/#/c/211753, though I need to fix up tests and split that somehow17:03
*** Yi has quit IRC17:03
alaskianything else to call out?17:03
alaskimlavalle: around?17:03
*** Yi has joined #openstack-meeting-317:03
mlavalleyeah17:03
*** singlethink has quit IRC17:04
alaski#topic gather ideas for Neutron and cells v217:04
*** openstack changes topic to "gather ideas for Neutron and cells v2 (Meeting topic: nova_cells)"17:04
alaskimlavalle: want to speak to this?17:04
mlavalleI just wanted to mention that I added a etherpad to the agenda, to gather inpout on neutron suppor for cells 217:04
*** shwetaap has quit IRC17:04
*** shwetaap has joined #openstack-meeting-317:05
*** vgridnev has joined #openstack-meeting-317:05
alaskiare you looking for general ideas, or are there specific things you'd like input on?17:05
*** singleth_ has quit IRC17:05
alaski#link https://etherpad.openstack.org/p/neutron-nova-v2-cells17:06
mlavalleany ideas you think are relevant for the topic17:06
mlavalleand i'll populate it over the next few weeks17:06
alaskicool17:07
mlavallethat's all i have17:07
alaskieveryone please take a look and add anything that's important to your interactions between nova and networking17:07
alaski#topic Open Discussion17:08
*** openstack changes topic to "Open Discussion (Meeting topic: nova_cells)"17:08
alaskianyone have a topic for today?17:08
dheeraj-gupta-4alaski : We are working on flavor objects17:08
dheeraj-gupta-4maybe we will have some sort of code before end of this week17:08
*** ihrachyshka has quit IRC17:09
alaskidheeraj-gupta-4: great.  you're adding support for flavor objects to work with multiple dbs, or adding a new object?17:09
dheeraj-gupta-4Maybe I'll ping you when it is up, because there a re afew sticking points17:09
alaskidheeraj-gupta-4: that would be good17:09
dheeraj-gupta-4support for flavor object to work with 2 dbs17:09
alaskigreat17:09
melwittI started working on the db connection switching at https://review.openstack.org/#/c/161906/ yesterday. it's -W for now while I fix a circular import and do more testing17:09
*** sfinucan has quit IRC17:10
alaskimelwitt: awesome.  would you like some reviews in the meantime?17:10
alaskianything else for today?17:11
*** pkoniszewski has quit IRC17:12
melwittalaski: yes, that would be good because I feel like it might be off from what you had in mind. I was trying to materialize an initial attempt17:12
*** isq_ has quit IRC17:12
alaskimelwitt: gotcha.  I'll take a look, and encourage others to as well17:12
melwittalaski: cool, thanks17:12
alaskiI think that's it for today17:13
alaskithanks everyone17:13
alaski#endmeeting17:13
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:13
openstackMeeting ended Wed Aug 12 17:13:35 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-08-12-17.00.html17:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-08-12-17.00.txt17:13
openstackLog:            http://eavesdrop.openstack.org/meetings/nova_cells/2015/nova_cells.2015-08-12-17.00.log.html17:13
*** isq_ has joined #openstack-meeting-317:13
*** dheeraj-gupta-4 has left #openstack-meeting-317:13
*** obondarev has joined #openstack-meeting-317:17
*** mlavalle has left #openstack-meeting-317:17
*** belmoreira has joined #openstack-meeting-317:19
*** yamamoto has quit IRC17:20
*** belmoreira has quit IRC17:21
*** persia has joined #openstack-meeting-317:24
*** persia has quit IRC17:24
*** persia has joined #openstack-meeting-317:24
*** iben has quit IRC17:24
*** shwetaap has quit IRC17:27
*** vishwanathj has joined #openstack-meeting-317:27
*** iben has joined #openstack-meeting-317:28
*** shwetaap has joined #openstack-meeting-317:28
*** singlethink has joined #openstack-meeting-317:29
*** vikram has quit IRC17:29
*** VW__ has quit IRC17:30
*** VW_ has joined #openstack-meeting-317:31
*** singleth_ has joined #openstack-meeting-317:34
*** banix has joined #openstack-meeting-317:34
*** FallenPegasus has quit IRC17:35
*** VW_ has quit IRC17:35
*** singlethink has quit IRC17:36
*** shwetaap1 has joined #openstack-meeting-317:38
*** shwetaap has quit IRC17:39
*** mickeys has quit IRC17:41
*** vikram has joined #openstack-meeting-317:42
*** yamamoto has joined #openstack-meeting-317:43
*** davidmichaelkarr has quit IRC17:47
*** mickeys has joined #openstack-meeting-317:50
*** jcoufal_ has joined #openstack-meeting-317:53
*** absubram has quit IRC17:55
*** mrmartin has quit IRC17:56
*** jcoufal has quit IRC17:57
*** absubram has joined #openstack-meeting-317:57
*** salv-orl_ has joined #openstack-meeting-317:59
*** sridhar_ram has joined #openstack-meeting-318:01
*** VW_ has joined #openstack-meeting-318:01
*** salv-orlando has quit IRC18:01
*** banix has quit IRC18:01
*** singlethink has joined #openstack-meeting-318:01
*** iben has quit IRC18:01
*** FallenPegasus has joined #openstack-meeting-318:03
*** singleth_ has quit IRC18:05
*** pkoniszewski has joined #openstack-meeting-318:05
*** davidmichaelkarr has joined #openstack-meeting-318:06
*** iben has joined #openstack-meeting-318:09
*** lblanchard has quit IRC18:13
*** iben has quit IRC18:13
*** bapalm_ has joined #openstack-meeting-318:14
*** hoangcx has joined #openstack-meeting-318:16
*** masco has quit IRC18:16
*** iben has joined #openstack-meeting-318:19
*** banix has joined #openstack-meeting-318:22
sc68calwho's present for the fwaas meeting in 5 minutes?18:25
*** SridarK has joined #openstack-meeting-318:26
*** iben has quit IRC18:27
*** tfukushima has quit IRC18:27
*** tfukushima has joined #openstack-meeting-318:28
hoangcxsc68cal: you mean who is a chairman?18:28
*** tfukushima has quit IRC18:28
sc68calhoangcx: SridarK and I will co-chair18:28
*** vikram has quit IRC18:29
SridarKHi all18:29
hoangcxsc68cal: I see. Thanks18:29
hoangcxHi18:29
mickeysHi18:29
*** annp has joined #openstack-meeting-318:29
*** madhu_ak has joined #openstack-meeting-318:29
sc68cal#startmeeting networking_fwaas18:30
openstackMeeting started Wed Aug 12 18:30:16 2015 UTC and is due to finish in 60 minutes.  The chair is sc68cal. 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
openstackThe meeting name has been set to 'networking_fwaas'18:30
sc68cal#chair SridarK18:30
openstackCurrent chairs: SridarK sc68cal18:30
SridarKHi All, sc68cal: will be running the FWaaS mtgs henceforth, was happy to step in for the interim period18:30
annphi18:30
madhu_akhi18:30
*** singleth_ has joined #openstack-meeting-318:30
SridarKhi18:30
ajmillerHi18:30
*** jwarendt has joined #openstack-meeting-318:30
xgermanHi18:30
*** pc_m has joined #openstack-meeting-318:31
bharathhi18:31
mickeysHi18:31
jwarendtHello18:31
pc_mhi18:31
sc68calSo, I guess the first thing to do is announce (formally) that we have had a new core team that was appointed by the neutron core team, to help continue the work that has been done so far with the fwaas project18:31
sc68calit consists of SridarK, myself, blogan, xgerman, as well as dougwig and mestery18:32
* mestery lurks18:32
*** yapeng has quit IRC18:32
*** jcoufal has joined #openstack-meeting-318:32
*** sbalukoff has joined #openstack-meeting-318:32
madhu_ak+1 to the core team18:33
*** singlethink has quit IRC18:33
jwarendtCongrats to those involved!18:33
*** yamamoto has quit IRC18:33
sc68calI will be the first to say that I am very new to the fwaas codebase, and I will be looking to get to know everyone - and that I will also be relying heavily on the contributors who have been working on fwaas to help guide me - and I imagine the same for the new cores18:33
xgerman+118:33
SridarKsc68cal: +1 surely the whole team is behind this completely18:34
*** johnsom_ has joined #openstack-meeting-318:34
sc68calIf you hadn't seen my e-mail to the openstack-dev mailing list, earlier this week was a bit .... more eventful than I was bargaining for18:34
xgermanno kidding...18:34
sc68calI was hoping to ease into things by just +2'ing some patches that were easy18:34
*** jcoufal__ has joined #openstack-meeting-318:35
SridarK:-), sc68cal: this has happened in the past as well some how we stick out as a Red Herring :-)18:35
*** absubram has quit IRC18:35
sc68calSo I went into a little bit of an adventure yesterday - we have a fix where we are skipping the test that was failing, so we can at least now take time to figure out a fix18:36
*** jcoufal_ has quit IRC18:36
sc68calwithout having me throwing things against the wall :)18:36
SridarKsc68cal: Given the available data it was right to attempt the revert and then as more data was avail to bump it out18:36
*** iben has joined #openstack-meeting-318:37
*** Sukhdev_ has joined #openstack-meeting-318:37
*** tholtzen has joined #openstack-meeting-318:37
sc68calSridarK: agreed. So keep an eye on https://bugs.launchpad.net/neutron/+bug/148419618:37
openstackLaunchpad bug 1484196 in neutron "Re-enable test_firewall_insertion_mode_add_remove_router FwaaS test" [Undecided,New] - Assigned to Sean M. Collins (scollins)18:37
SridarKsc68cal: will do18:37
sc68caland https://bugs.launchpad.net/neutron/+bug/148387518:37
openstackLaunchpad bug 1483875 in neutron "FWaaS - firewall deleted unexpectedly by agent" [High,Confirmed]18:37
*** absubram has joined #openstack-meeting-318:38
sc68calThere's been discussion in -neutron about getting the *aaS projects into their own non-voting jobs18:38
sc68calprobably will come up in the next main meeting18:38
*** jcoufal has quit IRC18:38
*** iben has quit IRC18:39
sc68calOk - so off my podium - I'll take a look at our wiki agenda now - https://wiki.openstack.org/wiki/Meetings/FWaaS18:39
sc68calSridarK: did you have any topics that we need to discuss?18:41
*** iben has joined #openstack-meeting-318:41
*** vikram has joined #openstack-meeting-318:41
SridarKsc68cal: nothing very specific, we normally do a run down on any new critical bugs - nothing noteworthy18:41
SridarKService Groups, Logging are some projects and of course our Roadmap18:42
sc68calI see some recent activity on https://bugs.launchpad.net/neutron/+bug/147709718:43
openstackLaunchpad bug 1477097 in neutron "fwaas: firewall in error status after update firewall-rule " [Undecided,Confirmed] - Assigned to Sridar Kandaswamy (skandasw)18:43
*** iben has quit IRC18:43
SridarKyes i can definitely reproduce this so i Confirmed it18:43
SridarKi am digging thru this to see what is going on18:44
SridarKshould have something moving over the next couple of days18:44
sc68calunderstood18:44
* pc_m may want to use #topic...18:45
sc68calgood idea18:45
sc68cal#topic bugs18:45
*** openstack changes topic to "bugs (Meeting topic: networking_fwaas)"18:45
SridarKi don't believe there was something else critical that popped up (other than the action yesterday)18:46
*** salv-orl_ has quit IRC18:46
*** badveli has joined #openstack-meeting-318:46
badvelihello all sorry delayed18:47
SridarKbadveli: hi18:47
badvelisorry got delayed18:47
xgermanhi18:47
badvelihello xgerman18:48
sc68calok, if there aren't any other bugs I'll go ahead and move on to another topic18:48
*** absubram has quit IRC18:48
sc68cal#topic service groups18:49
*** openstack changes topic to "service groups (Meeting topic: networking_fwaas)"18:49
*** salv-orlando has joined #openstack-meeting-318:49
sc68calbadveli: Do you have anything to share about this topic?18:50
badvelicurrently i could not spend any time18:50
badvelii need to update the patch18:51
SridarKbadveli: Do check on my email response to u, when u have time we can sync up more if needed as well18:51
sc68calbadveli: is the patch in gerrit? I don't see it in the list of reviews18:51
badvelii have an issue with creating an extension18:52
badvelii need to fix18:52
SridarKbadveli: i think it will be good to get it out, u can mark it WIP18:52
badveliok, let me work on it, i have very limited time to work on it18:53
*** baoli has quit IRC18:53
badveliwhen is the liberty-3 schedule18:53
*** baoli has joined #openstack-meeting-318:54
sc68calvery close I think18:54
sc68calend of sept?18:54
*** absubram has joined #openstack-meeting-318:54
badvelii need to work in my spare time18:54
sc68calhttps://wiki.openstack.org/wiki/Liberty_Release_Schedule18:54
SridarKbadveli: we are fast approaching more like end of aug for FF18:54
*** lalitd has quit IRC18:54
sc68calbadveli: OK - my suggestion would be put up what you have so far, we can take a look and see if others can help chip in18:55
xgerman+118:55
badveliok thanks18:55
SridarKbadveli: we can discuss on the extensions bit - i can help18:56
sc68cal#topic usecases18:56
*** openstack changes topic to "usecases (Meeting topic: networking_fwaas)"18:56
sc68calThis might be a little old - but if you haven't seen http://lists.openstack.org/pipermail/openstack-dev/2015-July/069784.html18:56
sc68calplease do take a look - this was a work artifact from the midcycle sprint - I'd like to see veterans of the fwaas codebase (and users) take a look and validate our conclusions18:57
*** tholtzen has quit IRC18:57
*** lblanchard has joined #openstack-meeting-318:57
*** mrmartin has joined #openstack-meeting-318:57
SridarKsc68cal: we discussed the alignment with SG last mtg, and i think we are in consensus that we keep SG separate and not mess with it - u were a key part of the discussion there18:58
xgermanyep18:58
blogan+118:58
xgermanwe like to keep two API’s but use a common backend18:58
sc68calif you need to be added to the trello board let me know, I'll add you18:58
SridarKsc68cal: Hopefully if we are in agreement we formalize this and we will not be in a position where this will get revisited again.18:59
mickeysRephrase: Keep existing SG separate for compatibility with AWS, then enhance FWaaS to include new SG functionality as well as new and existing FWaaS functionality18:59
SridarKxgerman: +118:59
SridarKmickeys: definitely this was the discussion where we came to a close on - the articulation of the overlap19:00
sc68calmickeys: sounds good, overall19:00
xgerman+119:00
hoangcxmickeys: +119:00
xgermanall innovation happens in the FWaaS19:00
xgermanAPI19:00
badvelixgerman +119:01
SridarK+1 but we will be careful so that any overlap does not cause confusion for users19:01
sc68calSridarK: agreed19:01
*** vikram has quit IRC19:01
*** tholtzen has joined #openstack-meeting-319:01
*** iben has joined #openstack-meeting-319:02
sc68calI think we also have a chance to do some good cross-collaboration with other advanced services on things like classifiers, service insertion, etc..19:02
SridarKsc68cal: +119:02
xgerman+119:02
mickeys+119:02
sc68calit's going to be challenging, I don't think there has been an API extension that has tried to reach across so many other boundaries19:02
*** tqtran is now known as tqtran-afk19:03
sc68calI have two little thoughts before I turn over to open discussion19:03
sc68calI want to float the possibility of maybe once a week meeting, to keep our sync ratio high19:04
sc68caland secondly see if we need to do a rotating time to make it easier for different timezones, do alternating19:04
sc68calsomething to think about - not going to change it unilaterally19:05
SridarKsc68cal: on the frequency this was an adjustment as we did not have as much for every week but we can definitely think about19:05
xgermanyeah, with the redesign work shorter sync might be better19:05
SridarKsc68cal: on the time zone definitely a priority as we have some contributors from Japan19:05
hoangcxsc68cal: +119:06
hoangcxSridarK: +119:06
SridarKand China19:06
SridarKI know Yushiro is not here but he did request a more favorable time19:07
SridarKwe can certainly look into that19:07
hoangcxIt is 4:07 am in Japan and 2:07 in Vietnam19:07
*** Sukhdev__ has joined #openstack-meeting-319:07
SridarKhoangcx: sigh thanks for staying up so late19:07
sc68cal#action sc68cal start looking for a favorable time for asia pacific - coordinate with hoangcx and yushiro19:07
hoangcxSridarK: Yushiro really wants to attend this meeting :(19:07
hoangcxsc68cal: Thanks a lot.19:08
SridarKhoangcx: yes and +1 on sc68cal: for a new time19:08
sc68calhoangcx: no problem - the ipv6 team had a member from china so I'm no stranger to the challenge19:08
sc68calwe never fixed it - xuhanp was joining at 11pm her time - but we'll try and do better than 2 and 4am19:09
hoangcxsc68cal, SridarK: Thank you all19:09
sc68calSridarK: I think you had a topic?19:09
hoangcxsc68cal, SridarK: is there any place for "Logging" topic?19:10
sc68calyep that's the one19:10
SridarKyes that was the on19:10
SridarK#topic FWaaS Logging19:10
*** openstack changes topic to "FWaaS Logging (Meeting topic: networking_fwaas)"19:10
sc68cal++19:10
SridarKhoangcx: all yours19:10
hoangcxWe are still discussing with core team about NEW logging API which will support log feature for both SG and FW.19:10
hoangcx#link https://review.openstack.org/#/c/203509/19:10
hoangcxSource code is almost ready to upload.19:10
*** Sukhdev_ has quit IRC19:11
hoangcxSo could you all please help Yushiro and me to accelerate it into L3 before FF19:11
* sc68cal stars it19:11
SridarKhoangcx: yes will do19:11
hoangcxCurrently, HenryG help me to appended this topic to driver team's agenda19:11
hoangcxSridarK: Thanks19:12
xgermanwill have a look...19:12
hoangcxxgerman: Thanks a lot :-)19:13
*** Sukhdev_ has joined #openstack-meeting-319:13
xgermanI will try to float that with some HP Logging people19:13
hoangcxxgerman: +119:13
*** Sukhdev__ has quit IRC19:14
*** mrmartin has quit IRC19:14
sc68calcool - I guess a good action item for this topic is for the new cores to review the spec19:15
xgerman:-)19:15
SridarKhoangcx: anything else u need to discuss ?19:15
hoangcxThat's all for current status about FWaaS logging. And it really need to be accelerated to be approved in L3.19:15
xgerman$action xgerman, blogan, sc68cal review https://review.openstack.org/#/c/203509/19:15
xgerman#action xgerman, blogan, sc68cal review https://review.openstack.org/#/c/203509/19:15
sc68calThat's an agressive timeline, based on my experience L3 stuff is usually stuff that has been pretty far along in review19:16
hoangcxxgerman: Thank you so much. :-)19:16
hoangcxsc68cal: Please continue19:16
*** bpokorny has joined #openstack-meeting-319:16
sc68cals/L3/third milestone19:16
xgermanyeah, and logging surely will be controversial19:16
SridarKsc68cal: i think we can move to the next topic19:16
sc68calSridarK: ACK - suggestions?19:16
SridarKwe can move to Open Discussion19:16
SridarK#topic Open Discussion19:17
*** openstack changes topic to "Open Discussion (Meeting topic: networking_fwaas)"19:17
* sc68cal feels like captian picard - "Make it so"19:17
SridarKhehe19:17
sc68cal:)19:17
sc68calmestery: dougwig: anything you'd like to add?19:18
mickeysJust wondering if anyone is looking at enhancing FWaaS implementation with DVR: make it fully distributed, covering east/west as well as north/south, etc. We are thinking of getting someone to work on that.19:18
SridarKmickeys: that is quite complex, we can discuss with the DVR folks on this19:19
sc68calmickeys: yes - E-W was a big usecase, and there was a patch in review that enabled it for DVR - https://review.openstack.org/20349319:19
SridarKmickeys: i had worked thru the changes to get the basic N - S use cases19:19
sc68calit's surprisingly simple19:19
SridarKsc68cal: i am not comfortable with that review, i will get on gerrit for that19:19
sc68calthe trouble is I think we need constructs in the API to help expose this behavior - per my comments in the review19:19
*** jmckind_ has joined #openstack-meeting-319:19
SridarKone of the challenges is conn tracking19:20
sc68calotherwise we'll have an API that totally depends on which driver you're running for where a firewall is inserted19:20
SridarKfor E - W19:20
sc68calSridarK: indeed19:20
jwarendtAgree the async nature of East-West routing makes stateful rules very challenging; the patch doesn't address.19:20
SridarKmickeys: it is an important feature but will need more discussion, IMO19:20
* sc68cal plans on at least a design summit session in tokyo for it - if not more19:21
SridarKmickeys: the other thing is can we get more discussion on the overlap with SG on the ether pad19:21
mickeyssc68cal: Thanks for the pointer. That gives us somewhere to start, in addition to general ramp up on DVR19:21
SridarKjwarendt: yes exactly19:21
SridarKlet me get some clarifications out on gerrit for that - been meaning to do this and fell thru the cracks19:22
SridarKjwarendt: the good news is the dvr folks are super helpful we can have a constructive discussion19:22
sc68calSridarK: by the way, are you going to be going to the ops meetup next week?19:23
SridarKsc68cal: no i wish :-(19:23
SridarKsc68cal: u will probab be there ?19:23
badveli19:23
sc68calSridarK: I will not :(19:24
badveli mickeys we had a spec for east west19:24
SridarKsc68cal: oh ouch - would have been great to have some discussion19:24
badvelifirewalling19:24
mickeysI can sync up with regXboi who will be attending19:24
sc68calSridarK: exactly - if someone is going, that'd be a huge help19:24
badvelii had worked on it some time back19:24
sc68calI think I probably need to forward/cross-post that usecase e-mail to the ops list - I did forget to do that when I sent it the first time19:25
SridarKsc68cal: i will ask around too if someone from my group at work is going19:25
sc68calworst case, we'll have to see if we can get some ops feedback at the summit, or the next ops meetup during the mitaka cycle19:26
sc68calSridarK: thanks :)19:26
sc68calI'll also start bugging vichoward, aveiga and company19:26
sc68calcall in some favors ;)19:26
SridarKI was hoping that between RAX, HP and possibly Walmart we can get some use cases pushed that they will be willing to deploy19:26
vichowardwhowha?19:26
SridarKsc68cal: :-)19:27
vichowardjust kidding yes we would love to help out19:27
SridarKsc68cal: be careful to see if ur cable bill will go up mysteriously ;-)19:27
sc68calSridarK: indeed - and I know xgerman will also get us info from the hp end :)19:27
sc68calSridarK: oh it already did ;)19:27
SridarK:-)19:27
vichoward;)19:28
sc68calOK everyone, we've only got 2 minutes left - so we'll meet on the 19th worst case19:28
sc68calkeep an eye on the ML though if we find a good time for asia pacific, could try and squeeze it into next week19:29
sc68calthank you everyone - very excited to be working with you all!19:30
SridarKsc68cal: +119:30
SridarKSame here19:30
hoangcxsc68cal: +119:30
sc68cal#endmeeting19:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:31
openstackMeeting ended Wed Aug 12 19:31:02 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-08-12-18.30.html19:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-08-12-18.30.txt19:31
SridarKbye19:31
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_fwaas/2015/networking_fwaas.2015-08-12-18.30.log.html19:31
*** pc_m has left #openstack-meeting-319:31
badveligood to see more help19:31
badvelibye19:31
hoangcxbye19:31
*** hoangcx has quit IRC19:32
jwarendtbye19:32
*** VW_ has quit IRC19:33
*** tholtzen has quit IRC19:33
*** yamamoto has joined #openstack-meeting-319:33
*** VW_ has joined #openstack-meeting-319:34
*** jwarendt has quit IRC19:35
*** johnsom_ has left #openstack-meeting-319:36
*** mickeys has quit IRC19:36
*** VW_ has quit IRC19:38
*** yamamoto has quit IRC19:38
*** VW_ has joined #openstack-meeting-319:41
*** SridarK has quit IRC19:42
*** iben has quit IRC19:43
*** sc68cal has quit IRC19:44
*** crobertsrh has joined #openstack-meeting-319:46
*** sc68cal has joined #openstack-meeting-319:46
*** crobertsrh has left #openstack-meeting-319:47
*** lhcheng has joined #openstack-meeting-319:51
*** doug-fish has joined #openstack-meeting-319:55
*** crobertsrh has joined #openstack-meeting-319:56
*** matt-borland has joined #openstack-meeting-319:56
*** tqtran-afk has quit IRC19:56
*** mwhagedorn has joined #openstack-meeting-319:56
*** tqtran has joined #openstack-meeting-319:57
*** jwy has joined #openstack-meeting-319:57
*** lexholden has quit IRC19:57
*** hurgleburgler has joined #openstack-meeting-319:58
*** robcresswell has joined #openstack-meeting-319:59
*** lazy_prince has joined #openstack-meeting-319:59
*** iben has joined #openstack-meeting-319:59
*** geoffarnold has quit IRC20:00
*** iben has quit IRC20:00
lhcheng#startmeeting Horizon20:00
openstackMeeting started Wed Aug 12 20:00:33 2015 UTC and is due to finish in 60 minutes.  The chair is lhcheng. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: Horizon)"20:00
openstackThe meeting name has been set to 'horizon'20:00
robcresswello/20:00
lhchenganyone around to talk about horizon?20:00
crobertsrhhello/20:00
matt-borlando/20:00
lhchengo/20:00
hurgleburgler(◠‿◠✿)ノ20:00
rhagartyo/20:01
lhchenghello everyone20:01
doug-fishhi20:01
lhchengdavid-lyle have a conflict20:01
tqtran[-__-]/20:01
mwhagedornhello20:01
jwyhi20:01
hurgleburglernice tqtran!20:01
*** madhu_ak has left #openstack-meeting-320:01
lhchengI'm going to host the meeting for today20:01
*** geoffarnold has joined #openstack-meeting-320:01
robcresswellIt's a mutiny!20:01
lhchengtqtran stepping it up20:01
*** iben has joined #openstack-meeting-320:02
*** ongk has joined #openstack-meeting-320:02
* tqtran isn't here.20:02
*** FallenPegasus has quit IRC20:02
*** ongk has quit IRC20:02
lhcheng#topic Agenda20:02
*** openstack changes topic to "Agenda (Meeting topic: Horizon)"20:02
*** FallenPegasus has joined #openstack-meeting-320:02
lhcheng#link https://wiki.openstack.org/wiki/Meetings/Horizon20:02
*** ongk has joined #openstack-meeting-320:03
lhchengjust a quick update before we start the agenda20:03
lhcheng#link https://wiki.openstack.org/wiki/Meetings/HorizonDrivers20:03
*** Ephrem has joined #openstack-meeting-320:04
lhchengBP review meeting to cut down the open BP we have in launchpad20:04
lhchengwe'll be having the meeting until we get into a sizeable amount20:04
*** tyr has joined #openstack-meeting-320:05
jwyoops, didn't realize there was a separate meeting for bps. i can take my bp off today's horizon meeting agenda20:05
robcresswellI'm putting together a list of angular bps for next week; ping me if you have an important one that has not been reviewed/ prioritised.20:05
robcresswelljwy: There may be time, so we can look over it anyway. The other meeting is just *specifically* for bps. This a general meeting.20:05
lhchengrobcresswell: I see you already had an agenda for Aug 12?20:05
*** kellyd has joined #openstack-meeting-320:05
*** esp has joined #openstack-meeting-320:05
jwyrobcresswell: ok thanks20:06
lhchengrobcresswell: was there a meeting happened today?20:06
robcresswellFor this meeting? Yeah a couple of things, may I start?20:06
robcresswellThe first horizon drivers meeting was earlier today.20:06
*** ongk has quit IRC20:06
*** kellyd is now known as ongk20:06
*** mdavid has joined #openstack-meeting-320:06
lhchengrobcresswell: oh.. the time is 2000 UTC20:06
lhcheng:P20:06
*** ducttape_ has joined #openstack-meeting-320:07
robcresswellha, so I have a couple of agenda items for this meeting too20:07
lhchengokay20:07
lhchengjust one more update20:07
lhchengdjango1.8 tests are now all passing20:07
*** jschlueter has joined #openstack-meeting-320:08
lhchengI think the pending work is to cleanup the job for old django version20:08
lhchengand start having django18 job20:08
lhchengI think mrunge already have some patch up for that.20:08
doug-fishexcellent!20:08
lhcheng#link https://launchpad.net/horizon/+milestone/liberty-320:08
lhchengEnd of milestone-3 is coming up soon20:09
ducttape_did DOA get tagged / released then as well?20:09
ducttape_to support django1.820:09
lhchengso if you have any critical bugs make sure it is tag for L-3 so we can prioritize it for reviews20:09
rhagartylhcheng: what about normal patches? (non-bugs)20:10
lhchengducttape_: there is a 1.3.1, but that doesn't include the django1.8 yet20:10
lhcheng#action david-lyle to tag DOA20:11
*** ivar-lazzaro has quit IRC20:11
ducttape_yep, doa needs a new tag for sure, thanks lhcheng20:11
lhchengit is easy to volunteer people when they're not around lol20:11
ducttape_todo: dave should fix the bugs20:11
lhchengrhagarty: is it a new feature? maybe you can add it in the meeting agenda for today?20:12
ducttape_https://review.openstack.org/#/c/184776/  is a bug I'd like fixed asap, its a fix not from me, but I really could use that patch vs carrying it locally20:12
rhagartylhcheng: it's been around since Kilo-3... I will add20:13
*** tellesnobrega is now known as tellesnobrega_af20:13
lhchengrhagarty: ugh.. sorry about that.. add me as reviewer, I'll try to look at it20:13
*** pauloewerton has joined #openstack-meeting-320:13
lhchengducttape_: sounds like to have for L, tag it too20:14
rhagartythank you20:14
*** Brian_ has joined #openstack-meeting-320:14
lhchengokay, I'm done with the updates20:14
lhcheng#topic Discuss desire for multiple overrides, temporary fixes and long term plans20:14
*** openstack changes topic to "Discuss desire for multiple overrides, temporary fixes and long term plans (Meeting topic: Horizon)"20:14
lhchengrobcresswell o/20:14
robcresswellFirst item is a small notice: There has been a big effort to make Horizon more "bootstrap compliant" for theming and responsive purposes. When adding new HTML/ CSS please attempt to use the bootstrap styling/ elements/ classes etc. where possible. Same when reviewing designs on invision, make sure to refer to the framework :)20:14
robcresswellOops, I'm messing up your agenda ordering :p20:14
robcresswellSmall notice aside, on to the topic20:15
hurgleburglerrobcresswell +1 !20:15
robcresswellA lot of Horizon plugins use overrides.py to make deeper customisations20:15
robcresswellwith the customisation module20:15
lhcheng#undo20:16
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0xa245f10>20:16
lhcheng#topoc Small notice about using Bootstrap components where possible20:16
lhchengthere you go20:16
robcresswellhaha20:16
lhchengoops20:16
robcresswell...redo?20:16
lhchengI messed it up20:16
lhcheng#undo20:16
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0xa007590>20:16
ducttape_goto: -5 minutes20:16
lhcheng#topic Discuss desire for multiple overrides, temporary fixes and long term plans20:16
*** openstack changes topic to "Discuss desire for multiple overrides, temporary fixes and long term plans (Meeting topic: Horizon)"20:16
hurgleburglerlol20:17
robcresswellright20:17
robcresswellso20:17
*** davidmichaelkarr has quit IRC20:17
robcresswellMultiple customisation modules cannot work together, meaning multiple plugins is not viable20:17
ducttape_only when they both use overrides - right?20:17
ducttape_b/c I have like 3 or 4 plugins running right now, all working20:17
rhagartycorrect20:17
robcresswellYes20:18
lhchengrobcresswell: so that's when mixing overrides and pligins?20:18
doug-fishthey must all be new panels/dashboards?20:18
robcresswellSo adding new panels is straightforward and fairly well supported.20:18
robcresswellBut say two plugins want to override existing workflow steps20:18
*** Brian_ has quit IRC20:18
robcresswellThat cannot really be done, as the second plugin overrides the initial plugins overrides.20:18
rhagartythe last one to set 'customization_module' wins20:18
*** tyr has quit IRC20:18
ducttape_are the enabled files going to remain python?   they could move to just placing customization code in there20:19
lhchengrobcresswell: oh..it does not apply on top of it?20:19
robcresswelllhcheng: As far as I am aware, we set a key in the Horizon config and it is overriden20:19
ducttape_I think of overrides as one / deployment... and not so much for plugin enablement20:19
robcresswellIndeed20:20
lhchengducttape_: I think the enabled files should eventually move to ini files, radomir had a patch up for that.20:20
doug-fishyes - I think letting openstack UI components use the overrides is not a good approach20:20
robcresswellBut it still gets used for other features. For example, in our Cisco stuff, we customise Launch Instance and Firewalls.20:20
ducttape_ok. I'd say you still need some type of python plugin __init__.py or something20:20
robcresswellthrough overrides, currently.20:20
*** iben has quit IRC20:21
robcresswellSo I was curious about more straightforward methods for customising things like workflows and tables.20:21
robcresswellrhagarty, could you discuss your use case too?20:21
ducttape_deployers will definitely use overrides to carry a lot of ugly patches in there, or at least I sure would.  I'd vote to keep plugins from using that20:21
doug-fishducttape_: agreed20:22
doug-fishI think we covered what this might look like for angular at the mid cycle meetup, right?20:22
doug-fishand tqtran captured it in a blueprint for us20:22
rhagartyso there is currently an alternative solution for plug-ins to use?20:23
rhagartyother than "overrides"?20:23
doug-fishno. not current.20:23
lhchengadd support to allow plugin to add their hooks/overrides20:23
ducttape_there is, but not documented20:23
lhcheng?20:23
ducttape_If we move to ini formated plugin config files, I think that is the first decision.  then we can move onto how to do this type of stuff20:23
rhagartyso short term can we just fix init to handle multiple overrides?20:24
robcresswellSo overrides is not the solution, and I agree we should not use it, but I *think* we lack better options.20:24
ducttape_I don't think we want to add multiple overrides20:24
rhagartymanila_ui currently uses this20:25
*** iben has joined #openstack-meeting-320:25
ducttape_where is the code for this, maybe we can provide some other ideas ?20:25
rhagartyhttps://pypi.python.org/pypi/manila-ui/1.1.020:26
ducttape_thanks20:26
rhagartyI also have a plug-in that uses this, so if manila is installed, I'm out of luck20:26
* david-lyle heavily distracted20:27
ducttape_and I'd like to use manila eventually, but I wouldn't want it taking away my other overrides20:27
david-lylebut overrides.py is wrong another mechanism is necessary20:27
robcresswelldavid-lyle: +120:27
rhagartywe like the behavior it allows, but we just don't the overrides mechanism?20:28
rhagartydon't/don't like20:28
doug-fishthe problem is that overrides allows *everything* in Horizon to be touched20:28
doug-fishwe need an API20:28
doug-fishthat can be somewhat stablized20:28
ducttape_yep, so like the manila stuff changes quotas... it would be better to add a general api for extending quotas etc20:29
doug-fishotherwise we'll be perpetually breaking exensions20:29
*** VW__ has joined #openstack-meeting-320:29
mwhagedorndoes the oslo project have anything like this?20:29
*** singlethink has joined #openstack-meeting-320:29
mwhagedorntools to allow some sort of controlled monkey patching...20:30
*** sqchen has joined #openstack-meeting-320:30
doug-fishI think that's an oxymoron - monkey patching isn't controlled ... by definition I think20:31
*** singlet__ has joined #openstack-meeting-320:31
ducttape_they are pretty early on I think, in adding pluggable extensibility   (I think)20:31
mwhagedorntrue20:31
mwhagedornyou get my point though20:31
mwhagedornhas this been looked at before…. by others.. etc20:31
*** VW___ has joined #openstack-meeting-320:31
*** VW__ has quit IRC20:32
david-lylethis is the fine grained extensions we've been discussing20:32
ducttape_horizon is somewhat plugable, cinder is too I think.... lots of stuff have extension points, but they usually try to have a particular api to use20:32
doug-fishhttps://blueprints.launchpad.net/horizon/+spec/angular-workflow-plugin20:32
*** singleth_ has quit IRC20:33
doug-fishI know jpomeroy has been experiementing with actually implementing that blueprint20:33
doug-fishand his initial experiments looks quite promising20:33
lhchengmwhagedorn: there is stevedore in oslo, it is library for managing plugins20:33
*** VW_ has quit IRC20:33
david-lyleneeds support outside angular too  doug-fish20:33
robcresswellWould multiple overrides be bad as a temporary measure? I imagine at this point it is too late in the cycle to have a more cohesive system in place. For Liberty, would multiple overrides help?20:33
doug-fishoutside angular?20:33
david-lyleor of no use to manila-ui20:33
robcresswelldoug-fish: As in, workflows in python and angular need a plugin system.20:33
doug-fishyeah, I know. I think I'm funny.20:34
robcresswellahh20:34
robcresswellI'm tired :)20:34
*** singlethink has quit IRC20:34
doug-fishWouldn't a similar mechanism be appropriate - a way to define explicit, needed extension points in Horizon20:34
lhchengrobcresswell: if we support multiple overrides, we won't be able to remove again without breaking backward compatibility.. :P20:34
ducttape_yeah, let's not go down that path20:34
lhchengrobcresswell: no such thing as temporary20:34
robcresswellThat is true, and not something I had considered.20:34
ducttape_and what happens when you have multiple overrides, and order matter?20:34
*** mwagner_lap has quit IRC20:35
robcresswellducttape_: explosions20:35
ducttape_overrides are meant as a home to ugly code20:35
lhchengrobcresswell: everything that goes in openstack, never comes out :p20:35
*** jmckind_ has quit IRC20:35
ducttape_which is needed, but let's not promote it too widely20:35
david-lylesounds like table column addition/removal is desired as an extension point20:36
rhagartyand table/row actions20:36
david-lyleor table action addition/deletion20:36
david-lyleyup20:36
ducttape_so like for manila.... that entire overrides could go into a single __init__.py file and would still work ok20:36
doug-fishdeletion?  or strictly addition?20:36
robcresswellYeah, the main demands I've had is workflow steps and table columns.20:36
david-lylewell, if you are replacing functionality, I would imagine remove20:36
lhchengtable/column extension points - thought clu_ had some proposal about that before20:36
david-lylebut there's a question of how much power to give to plugins20:37
ducttape_rhagarty - have you tried moving the overrides into https://github.com/openstack/manila-ui/blob/master/manila_ui/dashboards/project/shares/__init__.py  ?20:37
ducttape_and then removing your overrides altogether ?20:38
rhagartyducttape_: no, but I will try that20:38
rhagartyducttape_: remove my overrides? how does that help my plugin?20:38
ducttape_b/c you don't need to use overrides, right?  that is the problem, overrides will still be open then20:39
lhchengducttape_, rhagarty adding support for extending the quota might not be a bad idea, I imagine other services would also have the same requirements20:39
rhagartysorry, my plug-in does use overrides20:39
ducttape_that is fine, at least then manila would not allow it20:40
ducttape_not need it, I mean20:40
rhagartygotchar20:40
rhagartygotcha20:40
ducttape_lhcheng - yeah, you could redo the existing quotas page to be more plugable too20:40
ducttape_and use that as the proof point for this20:40
*** crobertsrh has left #openstack-meeting-320:41
ducttape_I think most projects have the concept of quotas.   limits if you are old20:41
doug-fishright - because this is going to break if another project want to monkey patch quotas https://github.com/openstack/manila-ui/blob/master/manila_ui/overrides.py#L187 .... or maybe even if we change quota code20:41
* ducttape_ is old20:41
*** tyr has joined #openstack-meeting-320:41
* doug-fish is maybe jumping ahead a bit about what might break20:42
ducttape_I know designate also has quotas, we'd use that too... the extensible quotas thing.20:42
rhagartywill the final solution be based on adding hooks to every page?20:42
ducttape_rhagarty - not every page, but certainly to common service type things20:43
*** Rockyg has joined #openstack-meeting-320:43
*** galstrom is now known as galstrom_zzz20:43
ducttape_doug-fish - you are correct in your concern on how that might work when the quotas page changes20:43
lhchengrobcresswell: so for short term plan, maybe the workaround from ducttape_ would work20:43
*** VW___ has quit IRC20:43
doug-fishthis is where multiple overrides for quota will break https://github.com/openstack/manila-ui/blob/master/manila_ui/overrides.py#L26720:43
robcresswellducttape_: Would you have time to add your init suggestion to the docs?20:43
*** davidmichaelkarr has joined #openstack-meeting-320:44
lhchengrobcresswell: and for long term, look at providing more extension points20:44
robcresswelllhcheng: beat me to it :)20:44
doug-fishthere can be only one workflow class20:44
*** VW_ has joined #openstack-meeting-320:44
lhchengand don't recommend to operators to use the overrides in their plugin20:44
rhagartyor maybe leave the plug-in model alone and have some type of certification for plug-ins?20:44
robcresswellThat sounds time consuming :/20:45
mwhagedornI am missing something.. how does the future existence of extention points help the use case of “pluginA and pluginB both want to mutate default behavior?"20:45
ducttape_here is the thing for overrides:  <operators place all your garbage in here/>20:45
mwhagedornwho wins?20:45
mwhagedornlast?20:45
mwhagedornis that better?20:45
*** carl_baldwin has quit IRC20:45
doug-fishif there is an addQuotaStep mechanism we can all win20:45
robcresswellprecisely20:46
rhagartyrobcresswell: more work than adding entry points to all potential pages that may be extended?20:46
robcresswellrhagarty: Realistically it would be one piece of code replicated, like a mixin or something. It's not like every table in Horizon is unique.20:46
*** Ephrem has quit IRC20:46
ducttape_right now with monkey patching and creative use of __init__.py etc... you could have two plugins modify the same thing, if they are both  good citizens20:46
ducttape_and if they are both lucky20:47
robcresswellWhereas certifying plugins work puts another blocker on plugins, which we wanted to avoid in the first place, and takes a lot of time in understanding plugin code for cores (which we also wanted to avoid)20:47
doug-fishducttape_: how could they both resolve this https://github.com/openstack/manila-ui/blob/master/manila_ui/overrides.py#L26720:47
ducttape_luck always helps20:47
lhchengrobcresswell: it doesn't sounds like we can address all concerns now20:47
lhcheng*can't20:47
robcresswelllhcheng: No, agreed. It also sounds like people are resistant to the idea of multiple overrides, which is fine too.20:47
robcresswellJust wanted to see what was suggested :)20:48
ducttape_doug-fish - hopefully they extend the base class, and the base class might be patched already... and you'd get the super and super versions20:48
lhchengyup, at least we know something for the short term :)20:48
robcresswellIf we could get the init ideas doc'd somewhere, that would be handy.20:48
lhchengrobcresswell: 12 mins - ready to move to the next item?20:48
ducttape_I can add docs robcresswell20:48
robcresswellSure, go ahead lhcheng20:48
robcresswellducttape_: Ah, awesome!20:49
robcresswellThanks!20:49
lhchengcool20:49
* ducttape_ not shure aboute my zpellings for docs20:49
lhcheng#action ducttape_ to add init docs ideas20:49
lhcheng:)20:49
robcresswellWell I spell everything with Britlish and get told off for it :(20:49
lhcheng#topic Small notice about using Bootstrap components where possible20:49
*** openstack changes topic to "Small notice about using Bootstrap components where possible (Meeting topic: Horizon)"20:49
* robcresswell copy paste time20:50
lhchengrobcresswell: you got 3 mins, to give some time to the other two items :)20:50
* lhcheng bad at time management20:50
*** vgridnev has quit IRC20:50
robcresswellpass it along, I mentioned it earlier, but for convenience at topic time: There has been a big effort to make Horizon more "bootstrap compliant" for theming and responsive purposes. When adding new HTML/ CSS please attempt to use the bootstrap styling/ elements/ classes etc. where possible. Same when reviewing designs on invision, make sure to refer to the framework :)20:50
robcresswellneeext.20:50
lhchengrobcresswell: cool thanks for the reminder20:51
lhcheng#topic Add option for users to import images20:51
*** openstack changes topic to "Add option for users to import images (Meeting topic: Horizon)"20:51
lhchengjwy: o/20:51
jwyhere's the blueprint #link https://blueprints.launchpad.net/horizon/+spec/import-images20:51
jwymy colleague Sabari (smurugesan) had presented it at the glance midcycle summit and folks there were on board20:52
jwyi have some screenshots in there20:52
*** Yi has quit IRC20:52
ducttape_how is this different from the current glance image from a url ?20:52
jwybasically, i want to put the existing images table in a tab and add a tab to show a table of glance tasks20:52
jwyit's a different way of creating images20:52
jwythere's some introspection done during the creation20:52
lhchengjwy: would this require a new release of glanceclient?20:53
robcresswelljwy: If you get chance, fill out the bp a little more according to the template: https://blueprints.launchpad.net/horizon/+spec/template20:53
jwyall the code for the glance side is already there, they just need support in horizon to allow users to use it20:53
jwysure20:54
lhchengrobcresswell: ++20:54
robcresswellMakes it easier for us to review.20:54
robcresswellThanks!20:54
jwya question about making changes in the Create Image form -20:54
ducttape_image management and importing, if this helps automate some of that it would be awesome.  If we can make the user experience obvious of this mode vs the old mode that would be nice20:54
jwythere's a currently a "copy data" option, and in my screenshot, i've changed it to "import data"20:54
jwythe new way of image creation is preferred20:54
jwydo i need to keep the old option around?20:55
*** Rockyg has quit IRC20:55
doug-fishyes, please20:55
*** jmckind has joined #openstack-meeting-320:55
lhchengjwy: yes20:55
ducttape_what happens when new horizon encounters an older version of glance?20:55
doug-fishI added that after getting a consumer requirement for it20:55
jwydoug-fish: that = ?20:56
jwyducttape_: hm good question20:56
jwyhow do we handle that normally in horizon, different client versions20:56
doug-fishthat = "copy data" option, - I think you are saying this isn't just a rename of the same function, right?20:56
lhchengducttape_: horizon should check if that extension is available or have a config to hide the import task by default20:56
david-lylewhat did I miss ;)20:57
ducttape_you might want to make a upload form that extends from the current form, and make a config file to switch between versions... or what lhcheng said20:57
jwylhcheng: it's not an extension, though, a new api added in v2 of glanceclient20:57
*** stevemar has quit IRC20:57
lhcheng I think we can discuss the implementation details20:57
lhchenglater20:57
jwydoug-fish: right, it would be replacing "copy data". i'll let users pick from "import" or "copy" then20:57
lhchengthis sounds good for L-3, it is not intrusive and just add new feature20:58
*** krtaylor has quit IRC20:58
lhchengjwy: sorry have to move to last item20:58
david-lylewe already check for glance API version, so you can use that20:58
doug-fishjwy: doesn't that exclude the option to not import or copy?20:58
lhcheng#topic Added volume type description for volume type20:58
*** openstack changes topic to "Added volume type description for volume type (Meeting topic: Horizon)"20:58
rhagartyI would appreciate any core reviews for https://review.openstack.org/#/c/133872/20:59
lhchengdoug-fish, jway: we can continue the discussion on the horizon room20:59
rhagartyit's been out there since Kilo-3, but needed a cinder client20:59
rhagartyso it was held back till liberty20:59
*** matt-borland has left #openstack-meeting-320:59
lhchengrhagarty: is the cinderclient requirement bump available now?20:59
rhagartyanyway, hoping to get some core reviewers20:59
rhagartylhcheng: yes, it is in Kilo21:00
lhchengrhagarty: let's try to get it into L-321:00
lhchengthanks21:00
lhchengtime's up21:00
rhagartyreally appreciate it.21:00
lhchengthanks everyone21:00
rhagartybye21:00
lhcheng#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:01
openstackMeeting ended Wed Aug 12 21:00:59 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-08-12-20.00.html21:01
robcresswellThanks all. Sorry for the time hog and topic confusion at the start. Poor organisation on my part, making it difficult for lhcheng :p21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-08-12-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2015/horizon.2015-08-12-20.00.log.html21:01
*** ducttape_ has left #openstack-meeting-321:01
*** hurgleburgler has left #openstack-meeting-321:01
lhchengrobcresswell: lol, I'm a newb on the meeting command21:01
*** pauloewerton has left #openstack-meeting-321:02
david-lyleThanks lhcheng!21:03
*** mickeys has joined #openstack-meeting-321:04
*** esp has left #openstack-meeting-321:04
*** vgridnev has joined #openstack-meeting-321:07
*** jckasper has quit IRC21:07
*** cbouch__ has quit IRC21:08
*** jmckind_ has joined #openstack-meeting-321:11
*** krtaylor has joined #openstack-meeting-321:11
*** jmckind has quit IRC21:12
*** Sukhdev_ has quit IRC21:13
*** yamamoto has joined #openstack-meeting-321:13
*** ongk has left #openstack-meeting-321:14
*** pballand has joined #openstack-meeting-321:16
*** yamamoto has quit IRC21:19
*** VW_ has quit IRC21:21
*** VW_ has joined #openstack-meeting-321:21
*** VW__ has joined #openstack-meeting-321:25
*** VW_ has quit IRC21:26
*** iben has quit IRC21:27
*** iben has joined #openstack-meeting-321:29
*** singlethink has joined #openstack-meeting-321:31
*** singlet__ has quit IRC21:34
*** jwy has left #openstack-meeting-321:34
*** tyr has quit IRC21:39
*** mwagner_lap has joined #openstack-meeting-321:41
*** Ephrem has joined #openstack-meeting-321:42
*** iben has quit IRC21:42
*** singleth_ has joined #openstack-meeting-321:42
*** jmckind_ has quit IRC21:44
*** iben has joined #openstack-meeting-321:45
*** singlethink has quit IRC21:46
*** singlethink has joined #openstack-meeting-321:47
*** singleth_ has quit IRC21:50
*** jcoufal__ has quit IRC21:54
*** lblanchard has quit IRC21:54
*** VW__ has quit IRC21:56
*** yamamoto has joined #openstack-meeting-321:57
*** VW_ has joined #openstack-meeting-321:57
*** VW_ has quit IRC21:58
*** VW__ has joined #openstack-meeting-321:58
*** bpokorny_ has joined #openstack-meeting-321:58
*** neelashah has quit IRC21:59
*** bpokorny has quit IRC22:01
*** VW__ has quit IRC22:02
*** VW_ has joined #openstack-meeting-322:03
*** achippa has joined #openstack-meeting-322:03
achippahello22:03
achippasorry it was a test22:03
*** carl_baldwin has joined #openstack-meeting-322:03
*** achippa_ has joined #openstack-meeting-322:04
*** shwetaap1 has quit IRC22:05
*** VW_ has quit IRC22:07
*** carl_baldwin has quit IRC22:09
*** vgridnev has quit IRC22:21
*** achippa_ has quit IRC22:24
*** achippa has quit IRC22:24
*** achippa_ has joined #openstack-meeting-322:24
*** achippa has joined #openstack-meeting-322:24
*** mwhagedorn has left #openstack-meeting-322:26
*** achippa_ has quit IRC22:29
*** achippa has quit IRC22:29
*** bpokorny has joined #openstack-meeting-322:29
*** krtaylor has quit IRC22:30
*** iben has quit IRC22:31
*** sqchen has quit IRC22:32
*** bpokorny_ has quit IRC22:33
*** killer_prince has joined #openstack-meeting-322:33
*** sqchen has joined #openstack-meeting-322:34
*** lazy_prince has quit IRC22:36
*** iben has joined #openstack-meeting-322:38
*** qwebirc20754 has joined #openstack-meeting-322:39
*** qwebirc20754 has quit IRC22:40
*** sqchen has quit IRC22:40
*** killer_prince is now known as lazy_prince22:41
*** ivar-lazzaro has joined #openstack-meeting-322:42
*** esp has joined #openstack-meeting-322:43
*** devlaps has joined #openstack-meeting-322:44
*** sqchen has joined #openstack-meeting-322:45
*** jmckind has joined #openstack-meeting-322:45
*** singlethink has quit IRC22:47
*** sqchen has quit IRC22:50
*** jpomeroy has quit IRC22:50
*** galstrom_zzz is now known as galstrom22:51
*** sqchen has joined #openstack-meeting-322:52
*** yamamoto has quit IRC22:54
*** sqchen has quit IRC22:55
*** sqchen has joined #openstack-meeting-322:56
*** FallenPegasus has quit IRC23:00
*** sqchen has quit IRC23:05
*** tqtran has left #openstack-meeting-323:12
*** jpomeroy has joined #openstack-meeting-323:14
*** markvoelker has quit IRC23:14
*** lazy_prince has quit IRC23:15
*** carl_baldwin has joined #openstack-meeting-323:18
*** doug-fish has left #openstack-meeting-323:20
*** carl_baldwin has quit IRC23:27
*** sridhar_ram1 has joined #openstack-meeting-323:31
*** sridhar_ram has quit IRC23:32
*** iben has quit IRC23:35
*** salv-orl_ has joined #openstack-meeting-323:35
*** banix has quit IRC23:36
*** mickeys has quit IRC23:37
*** salv-orlando has quit IRC23:37
*** sridhar_ram1 has quit IRC23:38
*** FallenPegasus has joined #openstack-meeting-323:38
*** geoffarnold has quit IRC23:41
*** galstrom is now known as galstrom_zzz23:45
*** geoffarnold has joined #openstack-meeting-323:45
*** geoffarnold has quit IRC23:45
*** Brian_ has joined #openstack-meeting-323:48
*** baoli has quit IRC23:52
*** Brian_ has quit IRC23:52
*** yamamoto has joined #openstack-meeting-323:55
*** baoli has joined #openstack-meeting-323:56
*** FallenPegasus has quit IRC23:58

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