Monday, 2014-05-19

*** lifeless has joined #openstack-meeting-300:07
*** otherwiseguy has joined #openstack-meeting-300:34
*** lcheng_ has joined #openstack-meeting-300:34
*** eghobo has quit IRC00:37
*** rgbkrk has quit IRC00:42
*** glenc has quit IRC00:49
*** glenc| has quit IRC00:50
*** glenc- has quit IRC00:50
*** glenc has joined #openstack-meeting-300:50
*** glenc_ has joined #openstack-meeting-300:50
*** glenc- has joined #openstack-meeting-300:50
*** otherwiseguy has quit IRC01:07
*** lcheng_ has quit IRC01:42
*** nati_ueno has joined #openstack-meeting-301:46
*** rgbkrk has joined #openstack-meeting-301:52
*** Sukhdev has joined #openstack-meeting-301:52
*** nati_ueno has quit IRC02:09
*** nati_ueno has joined #openstack-meeting-302:13
*** nati_ueno has quit IRC02:16
*** lifeless has quit IRC02:16
*** nati_ueno has joined #openstack-meeting-302:21
*** lifeless has joined #openstack-meeting-302:24
*** nati_ueno has quit IRC02:30
*** Sukhdev has quit IRC02:34
*** kenhui1 has quit IRC02:55
*** sankarshan_away is now known as sankarshan02:57
*** kenhui has joined #openstack-meeting-303:05
*** nati_ueno has joined #openstack-meeting-303:06
*** eghobo has joined #openstack-meeting-303:19
*** kenhui has quit IRC03:21
*** kenhui has joined #openstack-meeting-303:21
*** nati_ueno has quit IRC03:21
*** kenhui has quit IRC03:22
*** coolsvap|afk is now known as coolsvap03:32
*** rgbkrk has quit IRC03:37
*** eghobo has quit IRC03:39
*** rm_work is now known as rm_work|away03:49
*** rm_work|away is now known as rm_work03:50
*** HenryG has joined #openstack-meeting-304:13
*** HenryG has quit IRC04:16
*** ttrifonov_zZzz is now known as ttrifonov04:18
*** eghobo has joined #openstack-meeting-304:20
*** HenryG has joined #openstack-meeting-304:22
*** nati_ueno has joined #openstack-meeting-304:32
*** nati_ueno has quit IRC04:37
*** Sukhdev has joined #openstack-meeting-305:14
*** nati_ueno has joined #openstack-meeting-305:34
*** ttrifonov is now known as ttrifonov_zZzz06:00
*** jtomasek has joined #openstack-meeting-306:08
*** nati_ueno has quit IRC06:17
*** nati_ueno has joined #openstack-meeting-306:35
*** eghobo has quit IRC06:40
*** eghobo has joined #openstack-meeting-306:40
*** rm_work is now known as rm_work|away06:43
*** rm_work|away is now known as rm_work06:44
*** eguz has joined #openstack-meeting-306:57
*** eghobo has quit IRC06:57
*** eguz has quit IRC06:59
*** nati_ueno has quit IRC07:00
*** yamamoto_ has joined #openstack-meeting-307:04
*** yamamoto_ has joined #openstack-meeting-307:05
*** d0ugal has joined #openstack-meeting-307:06
*** mrunge has joined #openstack-meeting-307:12
*** Sukhdev has quit IRC07:14
*** nati_ueno has joined #openstack-meeting-307:29
*** jtomasek has quit IRC07:33
*** nati_ueno has quit IRC07:33
*** jtomasek has joined #openstack-meeting-307:44
*** john3213 has joined #openstack-meeting-307:49
*** john3213 has left #openstack-meeting-307:54
*** nacim has joined #openstack-meeting-308:01
*** kenhui has joined #openstack-meeting-308:13
*** jpomero_ has quit IRC08:16
*** jpomero_ has joined #openstack-meeting-308:16
*** kenhui has quit IRC08:20
*** safchain has joined #openstack-meeting-308:29
*** sankarshan is now known as sankarshan_away08:54
*** sankarshan_away is now known as sankarshan09:02
*** yamamoto_ has quit IRC09:18
*** lsmola has joined #openstack-meeting-309:31
*** lsmola has quit IRC09:32
*** yamamoto_ has joined #openstack-meeting-309:40
*** sankarshan is now known as sankarshan_away09:40
*** rgbkrk has joined #openstack-meeting-309:40
*** lsmola has joined #openstack-meeting-309:44
*** rgbkrk has quit IRC09:56
*** yamamoto_ has quit IRC10:10
*** coolsvap is now known as coolsvap|afk10:16
*** mfer has joined #openstack-meeting-310:38
*** jamie_h has joined #openstack-meeting-310:43
*** mwagner_ has quit IRC10:48
*** mrunge has quit IRC10:49
*** mrunge has joined #openstack-meeting-311:04
*** overlayer has joined #openstack-meeting-311:16
*** sankarshan_away is now known as sankarshan11:26
*** mfer has quit IRC11:30
*** vnyyad has joined #openstack-meeting-311:47
*** danpb has joined #openstack-meeting-312:19
*** mrunge has quit IRC12:25
*** dhellmann is now known as dhellmann_12:31
*** lblanchard has joined #openstack-meeting-312:53
*** vnyyad has quit IRC12:53
*** safchain has quit IRC13:01
*** mfer has joined #openstack-meeting-313:01
*** mfer has quit IRC13:02
*** mfer has joined #openstack-meeting-313:02
*** mfer has quit IRC13:03
*** mfer has joined #openstack-meeting-313:03
*** safchain has joined #openstack-meeting-313:03
*** mfer_ has joined #openstack-meeting-313:05
*** mfer has quit IRC13:06
*** kenhui has joined #openstack-meeting-313:09
*** haleyb has joined #openstack-meeting-313:18
*** kenhui has quit IRC13:19
*** mfer_ is now known as mfer13:28
*** otherwiseguy has joined #openstack-meeting-313:41
*** jrist has joined #openstack-meeting-313:59
*** haleyb has quit IRC14:04
*** otherwiseguy has quit IRC14:07
*** otherwiseguy has joined #openstack-meeting-314:29
*** haleyb has joined #openstack-meeting-314:32
*** jtomasek has quit IRC14:33
*** jtomasek has joined #openstack-meeting-314:35
*** mwagner_lap has joined #openstack-meeting-314:42
krotscheck#startmeeting storyboard15:01
openstackMeeting started Mon May 19 15:01:25 2014 UTC and is due to finish in 60 minutes.  The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: storyboard)"15:01
openstackThe meeting name has been set to 'storyboard'15:01
NikitaKonovalovkrotscheck, hi15:01
krotscheckAnyone recovered/back from Atlanta yet?15:02
krotscheckNikitaKonovalov: Hey there!15:02
krotscheckThere was a lot of interest in storyboard at the summit, but I’m not certain everyone’s gotten their meeting agenda updated yet.15:02
krotscheckI know that gothicmindfood is stuck in traffic.15:02
krotscheckAnd ttx might be on a plane.15:03
krotscheckAnyway15:03
krotscheck#topic Atlanta Summit15:03
*** openstack changes topic to "Atlanta Summit (Meeting topic: storyboard)"15:03
krotscheckSo given that right now it’s just the two of us, let me just give you a recap.15:03
NikitaKonovalovok15:03
krotscheckFirstly, the etherpad is a good lineup of what Infra wants/needs to start moving over.15:03
krotscheckIn addition, we did a bunch of sit-down-and-talk-to-users UX testing, which resulted in the videos:15:04
krotscheckhttps://drive.google.com/folderview?id=0B6LxnAZQ6G4GUlQxRFNOZlJDa3c&usp=sharing15:04
krotscheckI’m still working through this, but the issues raised fall into basically three categories:15:04
krotscheck1- issues with things we’ve already built.15:04
krotscheck2- issues with things that infra needs and we’re going to build shortly.15:04
krotscheck3- Feature requests and things that we’ll build in the future, but may change by the time we get around to them.15:04
ttxAAH!15:05
krotscheckIt’s a ttx!15:05
ttxsorry, was distracted bu another long-running meeting15:05
ttxby*15:05
krotscheckNo worries :)15:05
krotscheckSo, anyway.15:05
jeblairo/15:05
krotscheckSo re: UX sessions, I think it makes sense to actually address the issues with things that we’ve already build. Case and point, the new-story modal received a lot of criticism and needs a little love.15:06
krotscheck*built15:06
jeblairthis session was also very informative wrt to storyboard needs: https://etherpad.openstack.org/p/juno-cross-project-tracking-features15:07
krotscheckjeblair: Thanks15:07
ttxkrotscheck: would be interested to see your summary of the "future issues" too, any chance you could summarize in an email (maybe pointing to segments of videos) sometimes this week ?15:07
krotscheckttx: Absolutely.15:08
krotscheckThat folder I linked actually contains all my notes as I’m working through it.15:08
krotscheckFuture issues: For instance, we got a LOT of good feedback from the UX team.15:08
*** kenhui has joined #openstack-meeting-315:08
krotscheckI’ll send a summary out to openstack-dev methinks.15:09
krotscheckLast item from the Atlanta summit is that I inquired with jeblair about what the process is to get another +2 on storyboard, and subsequently nominated NikitaKonovalov for that.15:09
jeblairkrotscheck: clarification: you asked me to consider nominating NikitaKonovalov15:10
krotscheckAh, right15:10
NikitaKonovalovkrotscheck: thanks15:10
ttxkrotscheck: I've been considering NikitaKonovalov +1s as a second +2 when the patch was from krotscheck for some time now15:10
krotscheckSo moving forward on that, I assume that you two will be discussing the matter out-of-band?15:11
jeblairi should be able to look into that this week15:11
ttxkrotscheck: (until you told me to stop doing that)15:11
krotscheckttx: Hey, that wasn’t me :).15:11
krotscheckBut anyway15:11
jeblairkrotscheck: actually the process is that we do it publicly15:11
krotscheckjeblair: openstack-dev?15:11
jeblairkrotscheck: yes15:11
ttxmaybe -infra15:11
krotscheckkk15:11
ttxok15:11
ttxOK, quick feedback from me on summit15:12
krotscheckGo for it.15:12
ttxthe "Tracking incoming features" workshop definitely gave StoryBoard some publicity15:13
ttxThere is a good overview of the overarching mission on the etherpad15:13
ttxIn the "Problem(s) we are trying to solve" section15:13
*** markmcclain has joined #openstack-meeting-315:14
ttxeven if that's the goal across the range of tools we are using15:14
ttx(i.e. including -specs repos)15:14
* SergeyLukjanov lurking - going to the atlanta zoo15:14
ttxAfter that session (and the StoryBoard one) a lot of projects just proposed dogfooding StoryBoard early15:14
krotscheckReally?15:14
jeblairyes, lots15:14
krotscheckHuhn.15:14
ttxAs in, almost all of them.15:14
ttxI pushed back a bit -- I think it's waaaay not ready for them15:15
ttxbut there sure is a lot of enthusiasm15:15
jeblairit came up in this one too: https://etherpad.openstack.org/p/juno-summit-qa-policy15:15
jeblairand this one: https://etherpad.openstack.org/p/juno-summit-grenade15:15
jeblair(just off the top of my head)15:15
ttxI think the good targets for early dogfooding are the projects that have a simple release process (like only a master branch)15:16
krotscheckI got a lot of interest from devs wanting to be involved as well, and I’m advising the vinz team on toolchain.15:16
ttxlike Infra15:16
NikitaKonovalovif that matters, I've sent one of our deployment engineeres to file a story for nodepool in storyboard15:16
jeblairttx: yes, i discouraged it as well15:16
ttxbecause everything else will require pretty advanced features15:16
ttx(from a release management pov)15:16
jeblairNikitaKonovalov: cool, thanks15:16
krotscheckSo the pressure’s on.15:17
ttxyes! I generally can help more during the first half of the cycle, so I plan to do just that15:17
krotscheckWorks for me.15:17
ttxbut then, I also increased travel / conferences so I prefer not to promise too much15:18
ttxanyway, that was my feedback15:18
krotscheckGot it. Anything from jeblair?15:18
krotscheck(Do you have a summit summary?)15:18
jeblairthat covers it15:18
krotscheckOk, so just to reiterate:15:18
krotscheck1- Good list of requirements from design session15:19
krotscheck2- needs-to-be-filtered list from UX testing.15:19
krotscheck3- Lots of exposure.15:19
krotscheck4- Lots of interest, people are chomping at the bit.15:19
ttxyep15:19
krotscheck5- Some of the process design sessions came up with features we haven’t even anticipated.15:19
krotscheckAlright, everyone ok with moving on to Ongoing work?15:20
ttx+115:20
NikitaKonovalovsure15:20
krotscheck#topic Ongoing work15:20
*** openstack changes topic to "Ongoing work (Meeting topic: storyboard)"15:20
krotscheckNikitaKonovalov? What’ve you been working on?15:20
NikitaKonovalovI've spent some time on creating small changes to fix some small issues, misspellings, etc15:21
NikitaKonovalovthen the change with ProjectGroups api is wating for reviews15:21
NikitaKonovalovso I've got the controllers work like I wanted15:22
krotscheckNice. I saw some of your comments in pecanpy, did you get the answers you needed there?15:22
NikitaKonovalovkrotscheck: I found an answer after a closer look at pecan's source15:22
krotscheckEven better.15:23
NikitaKonovalovone more thing is change for filtering timeline event in UI https://review.openstack.org/#/c/93563/15:23
krotscheckGot it, will look at that.15:23
NikitaKonovalovand now I'm working on refresh tokens as we discussed before the summit15:23
NikitaKonovalovthe change will come soon I think15:24
NikitaKonovalovso this is my update15:24
krotscheckNikitaKonovalov: Excellent.15:24
NikitaKonovalovand I've been testing your dashboard changes locally to see how it works15:25
krotscheckAny feedback?15:25
NikitaKonovalovand it works!15:25
krotscheckYay things that work!15:25
krotscheckAs for myself, I was at the summit last week. I have a bunch of outstanding patches regarding the dashboard and/or minor UI tweaks in various locations, including vertically-expanding text areas and typeahead stuff.15:25
krotscheckOh, and I think I put priority in there as well.15:26
krotscheckSimple, stupid priority.15:26
krotscheckSo that’s my update.15:26
krotscheck#topic Upcoming work15:27
*** openstack changes topic to "Upcoming work (Meeting topic: storyboard)"15:27
krotscheckLOTS OF IT15:27
krotscheckI think that about sums it up :)15:27
krotscheckOf the 1.1 list, I think the one that’ll be the most contentious is subscription.15:28
ttxkrotscheck: how do you think we should track it ? We have an etherpad on one side, and some stories on the other15:28
ttxfile them all and use the dumb prio ?15:29
krotscheckttx: Well, there’s two things we need; milestone targeting and priority.15:29
krotscheckWe’ve got priority (more or less)15:29
jeblairwe also are about to have an infra-specs repo -- obviously we sholudn't use it to track small things, but major changes should probably go through it.15:29
krotscheckWe don’t have milestone yet, so I’m thinking labeling the stories as [1.1] would work.15:29
jeblairwe could consider filing a spec that covers each MVP...15:29
jeblairkrotscheck: ++ filing stories and labeling15:30
krotscheckjeblair: MVP-per-spec rather than MPV-per-feature? I feel that having several features in one spec will be difficult to approve.15:31
krotscheckWe can try eitehr.15:31
ttxkrotscheck: about milestones: one use of the "task lists" thing was to have per-milestone task lists at the project level ("release task lists")15:31
ttxrather than LP-like milestone targeting15:31
ttxso we'll probably have to discuss that a bit15:32
ttxabusing title for now is fien by me15:32
jeblairkrotscheck: yeah, i'm trying to not overload the specs repo right now for something fast-moving like storyboard.  i actually think we don't really need it for most of the stuff on the juno-infra-storyboard etherpad.  but i think we will get to a point where larger/more complicated features should have design review pre-impl.15:32
krotscheckjeblair: The idea of a pre-impl design review makes me want to change my pants.15:33
ttxI'd keep one separate spec for complex stuff (like the ones that have wiki pages at https://wiki.openstack.org/wiki/StoryBoard#Design)15:33
ttxbut I guess some "basic LP partity" features could be lumped into a single spec15:33
ttxparity*15:33
jeblairkrotscheck: you don't want to get agreement about new features from the core team before writing code?15:34
ttxor he does want ?15:34
ttxdepends on why he needs to change those pants15:34
jeblairttx: oh, i guess i'm not sure whether dirty pants are good or bad...15:34
krotscheckjeblair: Wrong kind of pants changing.15:34
krotscheckjeblair: I like that kind of review.15:34
krotscheckjeblair: LIKE Like.15:34
jeblairkrotscheck: oh, ok.  i like clean pants.  ;)15:34
krotscheckRighto, so enough about my pants.15:35
krotscheckOk, so of the upcoming features, I feel that subscriptions is the one that needs a spec.15:35
ttxkrotscheck: yes, good example15:35
ttxjeblair: when infra-specs is up we can add it as a project so that we can have tasks targeted to it15:36
jeblaircool, we should have a repo to put in in within a few days15:36
krotscheckBecause that’s going to be one of those x-by-x complexity matrixes which will die a horrid death if we don’t implement it properly.15:36
jeblairttx: ++15:36
ttxthen it's easy to add missing stories15:36
ttxkrotscheck: agreed15:36
jeblairand i suppose it will be good to dogfood the specs integration process that we expect other projects to use15:37
krotscheckFeels like Storyboard is the testbed for all things process these days :)15:37
ttxkrotscheck: it's also a use case for task lists, but I'm not that sure it's the best way to handle personal interest15:37
ttxmaybe makes more sense to keep subscription more.. atomic and not handle it through a personal task list15:37
ttxmakes "subscribing to a task list" a thing, too15:38
ttxso yeah, spec++15:38
NikitaKonovalov+1 for spec from me15:39
krotscheckExactly15:39
krotscheckOk, so we’ll wait on the infra-spec repo and then start discussing the subscription implementation.15:39
krotscheckI suspect that emails will also build off of that.15:39
ttxack15:40
krotscheckOf the upcoming features in 1.1, are there any others that need a spec?15:40
jeblairthe lp data import/transition plan might be a good one15:41
* ttx looks15:41
jeblairpossibly emails.15:42
ttxtags ?15:42
jeblair(mostly to hash out when/where/how they should be sent)15:42
krotscheckjeblair: Agreed, especially since we’ll need some kind of a Rainbow table to map LP to SB from gerrit15:42
*** cjellick has joined #openstack-meeting-315:42
ttxprogram groups could use one, so that we actually agree that we mean the same thing by that :)15:43
krotscheckThough I feel we already had the discussion and realized that we could actually port the launchpad ID’s verbatim.15:43
ttxit's pretty simple from where I stand, but then I'm on the right side of my skull15:43
krotscheckttx: It gets REALLY complicated as soon as you try to get lists of tasks in stories that belong to projects in a group.15:43
jeblairkrotscheck: the lp one may not be 'contentious', but would be a really good thing to have a reference doc on since it's a long process (it will still be relevant a year from now)15:44
krotscheckAnd subscribing tot hem.15:44
krotscheckjeblair: Makes sense.15:44
ttxkrotscheck: yeah.. just wondering if at this point (since work has started on that) it's not easier to just see the POC rather than work on design spec15:44
krotscheckOk, items that needs specs: Subscription, Emails, LP Migration15:44
krotscheckNikitaKonovalov: Any thoughts on that?15:45
krotscheckNikitaKonovalov: (What ttx just said)15:45
ttxkrotscheck: so no Tags, ProjectGroups ?15:45
NikitaKonovalovI just wanted to add ProjectGroups15:45
ttx(for tags, I think the 1.1 tags can be very simple so no spec needed)15:46
ttxonce we try to encourage the use of certain tags (like "official tags") then it gets hairier, but we don't really need that  now15:46
krotscheckttx: Wait, don’t you have a design doc for that?15:46
NikitaKonovalovttx: agree tags should be pretty straightforward15:46
ttxkrotscheck: oooh! I have!15:47
krotscheckLinky?15:47
ttxhttps://wiki.openstack.org/wiki/StoryBoard/Story_Tags15:47
*** jaypipes has joined #openstack-meeting-315:48
krotscheckRight, I remember this.15:48
ttxfunny, I didn't :)15:48
*** chuckC has quit IRC15:48
krotscheckThe idea being that eventually, even things like priority, milestone, assignee, etc are tags.15:48
ttxanyway, it could use some iteration and approval, certainly15:48
ttxso I can add it as proper spec when infra-specs is a thing15:48
krotscheckYeah, let’s do that.15:49
krotscheckOk, so let’s add tags to the list of specs we want to discuss.15:49
krotscheck#action Once infra-specs is up, add discussion specs for subscriptions, email, tags, and LP migration15:49
ttxkrotscheck: OK, so I'll take tags15:49
NikitaKonovalovI guess ProjectGroups will go under LP migrations spec15:49
krotscheckttx: Got it. I’ll take subscriptions.15:50
*** rm_work is now known as rm_work|away15:50
krotscheckNikitaKonovalov: Well, ttx mentioned that actually just using what you’ve built for now might be best.15:50
ttxNikitaKonovalov: no, it goes under the "let's implement it and then do a v2 if needed"15:50
krotscheckI’m open for discussion on that.15:50
ttxI'm fine with writing a spec for it... all depends how advanced you are in impl15:50
NikitaKonovalovrigh now the groups can be loaded along with project and superusers can modify them through API (no UI support)15:52
ttxso far we did a "let's look at what was done and complain afterwards" approach -- I agree it doesn't really scale but we can do it one more time !)15:52
NikitaKonovalovttx: agree15:52
ttxNikitaKonovalov: if a v2 is needed, then I'll spec it15:53
krotscheckAlright, so moving forward on proejct groups and then whining about it later.15:53
ttx+115:53
NikitaKonovalovok15:53
krotscheckThat’s it for the agenda, I’ll promise to come up with something more substantial next week.15:53
krotscheck#topic Open Discussion15:54
*** openstack changes topic to "Open Discussion (Meeting topic: storyboard)"15:54
krotscheckIncidentally, if any of you have 3 hours, go watch the videos. They’re VERY interesting.15:54
* krotscheck apologizes because he forgot to hit record when David Lyle was doing his thing.15:54
krotscheckAnything else?15:55
NikitaKonovalovOne small question we have already discussed but still, Storyboard or StoryBorad?15:55
krotscheckAh, right15:55
ttxStoryBorat!15:55
jeblair:)15:55
* krotscheck files that away for april fools.15:56
NikitaKonovalovI mean capital B in the middle or ont?15:56
NikitaKonovalovnot15:56
ttxSo far it's been StoryBoard, but I don't really care that much15:56
jeblairi think at the meetup we said capital b15:56
ttxwhoever really cares can decide15:56
ttxjeblair: yes we did15:56
jeblairttx: you cared then.  :)15:56
ttxjeblair: yes, but just can't remember why :)15:57
NikitaKonovalovok, capital B then15:57
krotscheckOh man, that’s going to bug me forever.15:57
*** eghobo has joined #openstack-meeting-315:57
krotscheckBut sure, capital B15:58
krotscheckAnything else?15:58
ttxnope15:58
jeblairnak15:58
krotscheck#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon May 19 15:59:00 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-05-19-15.01.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-05-19-15.01.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-05-19-15.01.log.html15:59
krotscheckAllllrightey.15:59
*** kenhui has quit IRC16:00
*** rgbkrk has joined #openstack-meeting-316:01
*** chuckC has joined #openstack-meeting-316:02
*** emagana has joined #openstack-meeting-316:05
*** chuckC has quit IRC16:08
*** rm_work|away is now known as rm_work16:18
*** mfer is now known as mattfarina16:21
*** mattfarina is now known as mfer16:23
*** david-lyle has joined #openstack-meeting-316:29
*** chuckC has joined #openstack-meeting-316:31
*** danpb has quit IRC16:43
*** cjellick_ has joined #openstack-meeting-316:57
*** cjellick has quit IRC17:00
*** yamamoto has joined #openstack-meeting-317:01
*** otherwiseguy has quit IRC17:08
*** otherwiseguy has joined #openstack-meeting-317:08
*** yamamoto has quit IRC17:08
*** otherwiseguy has quit IRC17:10
*** chuckC has quit IRC17:18
*** ttrifonov_zZzz is now known as ttrifonov17:19
*** julim has joined #openstack-meeting-317:21
*** devlaps has joined #openstack-meeting-317:21
*** lenrow has joined #openstack-meeting-317:31
*** lcheng has joined #openstack-meeting-317:36
*** emagana has quit IRC17:46
*** emagana has joined #openstack-meeting-317:49
*** nati_ueno has joined #openstack-meeting-317:49
*** safchain has quit IRC17:52
*** krotscheck has quit IRC18:01
*** krotscheck has joined #openstack-meeting-318:02
*** chuckC has joined #openstack-meeting-318:02
*** julim has quit IRC18:11
*** krotscheck has quit IRC18:12
*** krotscheck has joined #openstack-meeting-318:13
*** julim has joined #openstack-meeting-318:13
*** nati_ueno has quit IRC18:17
*** mwagner_lap has quit IRC18:18
*** emaganap has joined #openstack-meeting-318:20
*** emagana has quit IRC18:22
*** krotscheck has quit IRC18:24
*** krotscheck has joined #openstack-meeting-318:24
*** chuckC has quit IRC18:27
*** eghobo has quit IRC18:29
*** nati_ueno has joined #openstack-meeting-318:32
*** ttrifonov is now known as ttrifonov_zZzz18:34
*** kenhui has joined #openstack-meeting-318:39
*** emaganap has quit IRC18:42
*** chuckC has joined #openstack-meeting-318:43
*** krotscheck has quit IRC18:56
*** krotscheck has joined #openstack-meeting-318:57
*** nati_uen_ has joined #openstack-meeting-318:59
*** eghobo has joined #openstack-meeting-318:59
*** nati_ueno has quit IRC19:02
*** rgbkrk has quit IRC19:03
*** rgbkrk has joined #openstack-meeting-319:04
*** emagana has joined #openstack-meeting-319:05
*** kenhui has quit IRC19:20
*** lenrow has quit IRC19:21
*** lcheng has quit IRC19:24
*** nati_uen_ has quit IRC19:26
*** nati_ueno has joined #openstack-meeting-319:26
*** mwagner_lap has joined #openstack-meeting-319:35
*** emaganap has joined #openstack-meeting-319:37
*** eguz has joined #openstack-meeting-319:37
*** emagana has quit IRC19:38
*** rgbkrk_ has joined #openstack-meeting-319:40
*** emaganap has quit IRC19:40
*** nati_ueno has quit IRC19:41
*** eghobo has quit IRC19:41
*** emagana has joined #openstack-meeting-319:43
*** rgbkrk has quit IRC19:43
*** emagana has quit IRC19:47
*** julim has quit IRC19:49
*** markmcclain has quit IRC19:51
*** julim has joined #openstack-meeting-319:53
*** jaypipes has quit IRC19:53
*** jaypipes has joined #openstack-meeting-319:54
*** jrist has quit IRC19:55
*** sarob has joined #openstack-meeting-319:56
*** pleia2 has joined #openstack-meeting-319:57
*** nati_ueno has joined #openstack-meeting-319:58
*** devlaps has quit IRC20:05
*** jrist has joined #openstack-meeting-320:06
*** banix has joined #openstack-meeting-320:08
*** banix has quit IRC20:11
*** sarob has quit IRC20:17
*** sarob has joined #openstack-meeting-320:17
*** kenhui has joined #openstack-meeting-320:22
*** mwagner_lap has quit IRC20:22
*** sarob has quit IRC20:22
*** lcheng has joined #openstack-meeting-320:30
*** banix has joined #openstack-meeting-320:31
*** devlaps has joined #openstack-meeting-320:31
*** julim has quit IRC20:32
*** kenhui has quit IRC20:34
*** ttrifonov_zZzz is now known as ttrifonov20:41
*** emagana has joined #openstack-meeting-320:43
*** cjellick_ has quit IRC20:45
*** cjellick has joined #openstack-meeting-320:45
*** MaxV has joined #openstack-meeting-320:57
*** SumitNaiksatam has joined #openstack-meeting-320:59
*** yamahata has joined #openstack-meeting-320:59
*** Sukhdev has joined #openstack-meeting-321:02
*** markmcclain has joined #openstack-meeting-321:02
*** mfer has quit IRC21:05
*** emaganap has joined #openstack-meeting-321:15
*** emagana has quit IRC21:16
*** lblanchard has quit IRC21:16
*** rgbkrk_ has quit IRC21:31
*** rgbkrk has joined #openstack-meeting-321:32
*** ttrifonov is now known as ttrifonov_zZzz21:34
*** ttrifonov_zZzz is now known as ttrifonov21:38
*** mwagner_lap has joined #openstack-meeting-321:46
*** TravT has joined #openstack-meeting-321:52
*** kenhui has joined #openstack-meeting-321:54
*** jtomasek has quit IRC21:54
*** chuckC has quit IRC21:59
*** markmcclain has quit IRC21:59
*** danpb has joined #openstack-meeting-322:04
*** MaxV has quit IRC22:08
*** TravT has quit IRC22:10
*** emaganap has quit IRC22:10
*** TravT has joined #openstack-meeting-322:11
*** banix has quit IRC22:16
*** danpb has quit IRC22:29
*** emagana has joined #openstack-meeting-322:38
*** SumitNaiksatam has quit IRC22:47
*** yamahata has quit IRC22:47
*** SumitNaiksatam has joined #openstack-meeting-322:47
*** jamie_h has quit IRC22:53
*** overlayer has quit IRC22:57
*** chuckC has joined #openstack-meeting-323:00
*** Sukhdev has quit IRC23:02
*** emagana has quit IRC23:04
*** yamamoto has joined #openstack-meeting-323:11
*** safchain has joined #openstack-meeting-323:14
*** sarob has joined #openstack-meeting-323:19
*** david-lyle has quit IRC23:23
*** devlaps has quit IRC23:26
*** kenhui has quit IRC23:33
*** kenhui has joined #openstack-meeting-323:34
*** kenhui1 has joined #openstack-meeting-323:35
*** kenhui has quit IRC23:39
*** emagana has joined #openstack-meeting-323:40
*** emaganap has joined #openstack-meeting-323:42
*** emagana has quit IRC23:45
*** kenhui has joined #openstack-meeting-323:46
*** lcheng has quit IRC23:47
*** kenhui1 has quit IRC23:48
*** chuckC has quit IRC23:49
*** chuckC has joined #openstack-meeting-323:50
*** SumitNaiksatam has quit IRC23:51
*** emaganap has quit IRC23:52
*** emagana has joined #openstack-meeting-323:52
*** chuckC has quit IRC23:54

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