Tuesday, 2014-05-06

*** chuckC has quit IRC00:07
*** terryw has joined #openstack-meeting-300:12
*** otherwiseguy has quit IRC00:12
*** sarob_ has joined #openstack-meeting-300:19
*** sarob has quit IRC00:22
*** TravT has quit IRC00:27
*** sarob_ has quit IRC00:28
*** sarob has joined #openstack-meeting-300:29
*** terryw has quit IRC00:33
*** sarob has quit IRC00:33
*** rand738 has quit IRC00:38
*** rand738 has joined #openstack-meeting-300:39
*** lenrow has joined #openstack-meeting-300:42
*** shakamunyi has joined #openstack-meeting-301:05
*** lenrow has quit IRC01:12
*** shakayumi has joined #openstack-meeting-301:15
*** shakamunyi has quit IRC01:18
*** chuckC has joined #openstack-meeting-301:51
*** devlaps has quit IRC01:53
*** julim has joined #openstack-meeting-302:08
*** lcheng_ has joined #openstack-meeting-302:16
*** otherwiseguy has joined #openstack-meeting-302:20
*** julim has quit IRC02:25
*** sankarshan_away is now known as sankarshan02:35
*** shakayumi has quit IRC02:58
*** coolsvap|afk is now known as coolsvap03:04
*** banix has joined #openstack-meeting-303:10
*** lcheng_ has quit IRC03:11
*** lcheng_ has joined #openstack-meeting-303:12
*** jpomero_ has quit IRC03:15
*** coolsvap is now known as coolsvap|afk03:21
*** lcheng_ has quit IRC03:27
*** TravT has joined #openstack-meeting-303:29
*** coolsvap|afk is now known as coolsvap03:35
*** lcheng_ has joined #openstack-meeting-303:46
*** otherwiseguy has quit IRC03:47
*** beyounn has quit IRC03:49
*** banix has quit IRC03:49
*** lcheng_ has quit IRC03:57
*** sankarshan is now known as sankarshan_away04:14
*** yamahata has quit IRC04:34
*** yamahata has joined #openstack-meeting-304:35
*** yamahata has quit IRC04:58
*** yamahata has joined #openstack-meeting-304:59
*** chuckC has quit IRC05:11
*** chuckC has joined #openstack-meeting-305:34
*** ttx has quit IRC05:53
*** ttx has joined #openstack-meeting-305:57
*** alexpilotti has quit IRC06:28
*** mrunge has joined #openstack-meeting-306:53
*** MaxV has joined #openstack-meeting-306:56
*** MaxV has quit IRC06:56
*** ttx has quit IRC07:03
*** ttx has joined #openstack-meeting-307:03
*** sankarshan_away is now known as sankarshan07:20
*** jamielennox is now known as jamielennox|away07:29
*** nacim has joined #openstack-meeting-307:45
*** ttrifonov_zZzz is now known as ttrifonov07:46
*** MaxV has joined #openstack-meeting-307:57
*** ttrifonov is now known as ttrifonov_zZzz08:04
*** safchain has joined #openstack-meeting-308:17
*** ttrifonov_zZzz is now known as ttrifonov08:19
*** ttrifonov is now known as ttrifonov_zZzz08:35
*** ttrifonov_zZzz is now known as ttrifonov08:36
*** ttrifonov is now known as ttrifonov_zZzz08:53
*** ttrifonov_zZzz is now known as ttrifonov08:54
*** SumitNaiksatam has quit IRC08:55
*** MaxV has quit IRC08:56
*** SumitNaiksatam has joined #openstack-meeting-308:57
*** MaxV has joined #openstack-meeting-308:59
*** jcoufal has joined #openstack-meeting-309:02
*** enikanorov has joined #openstack-meeting-309:03
*** ttrifonov is now known as ttrifonov_zZzz09:09
*** ttrifonov_zZzz is now known as ttrifonov09:10
*** ttrifonov is now known as ttrifonov_zZzz09:14
*** ttrifonov_zZzz is now known as ttrifonov09:16
*** TravT has quit IRC09:17
*** amotoki has quit IRC09:50
*** amotoki has joined #openstack-meeting-309:58
*** MaxV has quit IRC10:10
*** ttrifonov is now known as ttrifonov_zZzz10:19
*** ttrifonov_zZzz is now known as ttrifonov10:20
*** ttrifonov is now known as ttrifonov_zZzz10:38
*** ttrifonov_zZzz is now known as ttrifonov10:39
*** ttrifonov is now known as ttrifonov_zZzz10:52
*** ttrifonov_zZzz is now known as ttrifonov10:54
*** ttrifonov is now known as ttrifonov_zZzz10:54
*** ttrifonov_zZzz is now known as ttrifonov10:55
*** ttrifonov is now known as ttrifonov_zZzz10:57
*** MaxV has joined #openstack-meeting-310:58
*** ttrifonov_zZzz is now known as ttrifonov11:00
*** ttrifonov is now known as ttrifonov_zZzz11:01
*** ttrifonov_zZzz is now known as ttrifonov11:01
*** ttrifonov is now known as ttrifonov_zZzz11:05
*** ttrifonov_zZzz is now known as ttrifonov11:06
*** ttrifonov is now known as ttrifonov_zZzz11:09
*** ttrifonov_zZzz is now known as ttrifonov11:10
*** sankarshan is now known as sankarshan_away11:22
*** nacim has quit IRC11:39
*** ttrifonov is now known as ttrifonov_zZzz11:43
*** ttrifonov_zZzz is now known as ttrifonov11:43
*** jtomasek has quit IRC11:45
*** ttrifonov is now known as ttrifonov_zZzz11:46
*** nacim has joined #openstack-meeting-311:55
*** ttrifonov_zZzz is now known as ttrifonov12:04
*** jamie_h has joined #openstack-meeting-312:17
*** mwagner_ has joined #openstack-meeting-312:26
*** mwagner_lap has quit IRC12:30
*** nacim has quit IRC13:05
*** nacim has joined #openstack-meeting-313:06
*** coolsvap is now known as coolsvap|afk13:15
*** banix has joined #openstack-meeting-313:16
*** lcheng_ has joined #openstack-meeting-313:22
*** lblanchard has joined #openstack-meeting-313:22
*** julim has joined #openstack-meeting-313:25
*** peristeri has joined #openstack-meeting-313:26
*** jpich has joined #openstack-meeting-313:32
*** nacim has quit IRC13:33
*** david-lyle has joined #openstack-meeting-313:35
*** chuckC has quit IRC13:37
*** david-lyle has quit IRC13:37
*** david-lyle has joined #openstack-meeting-313:38
*** david-lyle has quit IRC13:43
*** nacim has joined #openstack-meeting-313:51
*** otherwiseguy has joined #openstack-meeting-313:57
*** julim has quit IRC13:58
*** MaxV has quit IRC13:59
*** julim has joined #openstack-meeting-314:02
*** mestery has joined #openstack-meeting-314:02
*** mwagner_ has quit IRC14:02
*** MaxV has joined #openstack-meeting-314:04
*** mrunge has quit IRC14:11
*** peristeri has quit IRC14:13
*** lcheng_ has quit IRC14:13
*** peristeri has joined #openstack-meeting-314:13
*** markmcclain has joined #openstack-meeting-314:19
*** MaxV has quit IRC14:20
*** alexpilotti has joined #openstack-meeting-314:20
*** MaxV has joined #openstack-meeting-314:25
*** ttrifonov is now known as ttrifonov_zZzz14:28
*** chuckC has joined #openstack-meeting-314:32
*** TravT has joined #openstack-meeting-314:32
*** david-lyle has joined #openstack-meeting-314:35
*** david-lyle has quit IRC14:35
*** david-lyle has joined #openstack-meeting-314:36
*** cjellick_ has joined #openstack-meeting-314:45
*** cjellick has quit IRC14:49
*** cjellick_ has quit IRC14:49
*** cjellick has joined #openstack-meeting-314:50
*** shakayumi has joined #openstack-meeting-314:51
*** mestery has quit IRC15:06
*** mwagner_ has joined #openstack-meeting-315:07
*** MaxV has quit IRC15:09
*** MaxV has joined #openstack-meeting-315:09
*** devlaps has joined #openstack-meeting-315:15
*** lsmola has quit IRC15:18
*** cloudtoad has joined #openstack-meeting-315:19
*** absubram_ has joined #openstack-meeting-315:29
*** shakayumi has quit IRC15:31
*** shakamunyi has joined #openstack-meeting-315:32
*** emagana has joined #openstack-meeting-315:34
*** alexpilotti_ has joined #openstack-meeting-315:41
*** crobertsrh has joined #openstack-meeting-315:43
*** alexpilotti has quit IRC15:44
*** alexpilotti_ is now known as alexpilotti15:44
*** jpomero has joined #openstack-meeting-315:48
*** otherwiseguy has quit IRC15:56
*** chuckC has quit IRC15:59
jristo/15:59
*** fixedgary has joined #openstack-meeting-315:59
*** tzumainn has joined #openstack-meeting-316:00
tzumainnhi everyone!16:01
*** safchain has quit IRC16:01
*** mrunge has joined #openstack-meeting-316:01
*** pbelanyi has joined #openstack-meeting-316:01
*** johnma has joined #openstack-meeting-316:02
david-lyle#startmeeting Horizon16:02
openstackMeeting started Tue May  6 16:02:55 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: Horizon)"16:02
openstackThe meeting name has been set to 'horizon'16:03
lblanchardo/ hey all16:03
david-lyleHello everyone16:03
jpichHello16:03
*** doug-fish has joined #openstack-meeting-316:03
mrungehello o/16:03
pbelanyihi16:03
fixedgaryhi16:03
doug-fishhi all!16:03
david-lyleThe summit is next week, so I expect this meeting to be short16:04
mrungegreat! I like short meetings :D16:04
jristo/16:04
david-lyleThanks to everyone for starting the session discussions on the mailing list, that will help make the sessions in Atlanta more productive16:05
*** clu__ has joined #openstack-meeting-316:05
david-lylehttps://wiki.openstack.org/wiki/Summit/Juno/Etherpads16:06
david-lylefor talk outlines16:06
jcoufalo/16:06
david-lyleThe other outstanding issue is the review back up.16:07
david-lyleWe have a high number of reviews, I personally have been pulled away for the past couple weeks and need to dig back in16:07
mrungeyeah, same here16:08
david-lyleI understand the frustration around the wait times, to speed things up please help review patches16:08
david-lyleI would love to grow the horizon core team to help spread the review load, but I need individuals who are providing consistent high value reviews to do that16:09
david-lyleI don't have any other general remarks, so16:09
david-lyle#topic Open Discussion16:10
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:10
*** tqtran has joined #openstack-meeting-316:10
crobertsrhIf anyone wants to talk about the Sahara UI and the merging of that code, I'll be at Summit.  I think the change requests are all available now.16:10
doug-fishI've noticed that the QA team is planning an informal meetup for their team at the summit.  That sounds like a great idea.  Is there a plan for such a thing for the Horizon team?16:10
jpichThere's going to be "project pods" for folks to informally meet at any time, I think16:11
crobertsrhThere will also be a couple sahara-related sessions at summit that might give a better look into what the UI is in its current state.16:11
mrungecrobertsrh, yes, at least some of us should show up there as well16:12
david-lylecrobertsrh, I look forward to the sessions and speaking with you16:12
crobertsrhExcellent16:12
jristdoug-fish, jpich, jonwoon - I am interested in working with accessibility in Horizon, among other things. looking forward to seeing you in Atlanta16:12
doug-fishcool!16:12
doug-fishI guess we'll need to hang out at the pod.  :-)16:12
*** lcheng_ has joined #openstack-meeting-316:13
jristyeah16:13
jpichand at the session :P16:13
jristyeah of course16:13
doug-fishnaturally16:13
jristopen the fire hose16:13
lblanchard:)16:13
mrungecool. sounds like a plan.16:13
david-lyledoug-fish: we're you thinking more socially, or more along the project pods?16:13
doug-fishI was thinking more socally16:14
doug-fishThat's not what the project pods are about?16:14
jristso-cal-ly16:14
jristscotch tastings?16:14
doug-fishI'm more of a beer man.16:14
jristI'm allergic :(16:14
david-lylewasn't sure beer vs no beer16:14
doug-fishI guess my thinking is that meeting informally over a beer early in the week may lead to more productive discussions as we dig into the technical issues.16:15
jpichI imagine the pods to be pretty chilled out and informal, though I guess we'll see how these turn out16:15
doug-fish(beer not required - just trying to set the tone with that statement)16:16
david-lyleunderstood16:16
mrungewhat about an informal beer on Sunday evening?16:16
doug-fishyeah that sounds great16:16
mrunge(or tea)?16:16
lblanchardmrunge: +1 would be nice to meet folks early!16:16
doug-fish:-)16:16
clu__beer/tea = icebreaker16:16
doug-fishI'm not an experience conference goer.  How should we choose a time/location?16:17
*** vkmc has joined #openstack-meeting-316:17
tqtran+1 to beer/tea time16:17
lblancharddoug-fish: maybe suggest a location and time on the ML?16:17
lblanchardor is that too public? :)16:18
doug-fishlol16:18
david-lylethat seems a bit broad16:18
jristI agree with clu, doug-fish16:18
doug-fishwe don't want to be overwhelmed by our groupies!16:18
jcoufalShould we create an etherpad where we will keep info about Sunday's evening, where the people will meet? So that everybody can check the latest info?16:18
lblancharddoug-fish: lol16:18
lblanchardjcoufal: +1!!16:18
jrist+116:18
david-lyle+116:18
tqtran+1 doug-fish lol16:18
jristhorizon groupies16:18
jristdressed in suns and sunsets16:19
jcoufalperfect, I will create one16:19
jpichIt'd be useful to also send it on list for Horizon folks who aren't at this meeting to see it on time16:19
david-lyleHorizon IRC subject line?16:19
jcoufaljpich: sure16:19
david-lyleas in put it in16:20
jcoufaldavid-lyle: +1 for it as well16:20
doug-fishjcoufal, jpich, david-lyle:  all 3 of those sound like a good idea.16:20
mrunge+1 sounds good to me16:20
jcoufalhttps://etherpad.openstack.org/p/juno-summit-horizon-sunday-evening16:21
david-lylethanks jcoufal16:21
clu__nice, thanks jcoufal16:21
jristjcoufal: now we just need an offline version lol16:22
*** lsmola has joined #openstack-meeting-316:22
mrungeshould we collect interested persons and ways to connect?16:22
tqtranthats a good idea16:23
doug-fishyep16:23
tzumainn8pm at some hotel bar?16:24
jpichI suspect it might be simpler to just pick a time and place and whoever can make it will come16:24
jcoufaldavid-lyle: I don't think I can setup the horizon channel topic (not an operator)16:24
jpichtzumainn: that's a good idea16:24
jpichI don't think anyone's been an operator on the Horizon channel in 2 years16:25
jpichBased on the last update :-)16:25
david-lylejpich, true, it was on my list to try to remedy, hasn't bubbled to the top yet16:25
jristSundial!16:26
*** pballand has joined #openstack-meeting-316:26
jristhttp://sundialrestaurant.com/the-bar/16:26
jristhehe16:26
jpichIs that close to the conference venue?16:27
jristit's atop the westin16:27
tqtranoh wow, good choice jrist!16:27
tzumainnyeah, pretty close16:27
david-lylewell that's close for me :)16:27
jristsame haha16:27
jristthey'll never expect a dozen people16:27
jristat 8PM on a sunday16:27
tzumainnalthough16:28
tzumainnit is mother's day16:28
jristtouche16:28
doug-fishWe could call ahead and warn them16:28
mrungecould someone call them to make a reservation?16:28
mrunge20 persons?16:28
* lsmola will come too16:28
*** MaxV has quit IRC16:29
jristmaybe we should all use glassboard16:30
jristto coordinate16:30
jristsince some are from out of town16:30
david-lylesays no reservation for bar16:30
jristhttp://glassboard.com/16:30
david-lyle3 levels, levle 73 is all bar 240 capacity16:30
tzumainnI dunno, why don't we just show up there at 8pm?16:30
david-lylelevel16:31
lsmolaor g+ event?16:31
jristyeah or g+16:31
lsmolatzumainn: we should use some app :-)16:32
jpichAgreed, with tzumainn, sounds like we have a time and location, let's see what happens :)16:32
lsmolacool16:32
*** MaxV has joined #openstack-meeting-316:32
tzumainnfrom my experience in tuskar, overplanning leads to tears : (16:32
lsmolalol16:33
*** MaxV has quit IRC16:33
jristcry every time16:33
tqtranlol16:34
david-lylenow that we have the most important item resolved, any others?16:34
doug-fishMaybe we should promote the time/location from "Proposed" to "Decided"16:34
doug-fish:-)  I'm good now.16:34
*** chuckC has joined #openstack-meeting-316:34
*** pballand has quit IRC16:34
jrist:)16:35
david-lylewe now have two emails to the dev list16:35
david-lyleif you're planning a third, we can likely hold off ;)16:35
doug-fishoveracheivers.16:35
lblanchardlol16:35
lblanchardso much passion around this topic though!!16:36
jcoufalI am sorry :)16:36
david-lyleno worries16:36
tzumainnsooo - can we tentatively say we have a place and time, and send out an update on the etherpad and mailing list if it changes?16:37
jristyes16:37
*** pballand has joined #openstack-meeting-316:37
david-lylesounds good16:37
tzumainn /thumbsup16:37
* jrist seconds the motion16:37
jcoufaltzumainn: IShould we send the change to mailing list?16:37
jcoufalWouldn't it be easier to follow just one source?16:37
tzumainnsure!  someone reply with the tentative location and time, I vote jrist so he gets credit for finding the place16:38
jcoufaltzumainn: looks like your motivation was not good enough :)16:38
jcoufalit was... thanks jrist16:41
*** markmcclain has quit IRC16:41
jristsure16:41
david-lylealright, looks like we're saving it for Atlanta.  I'm looking forward to seeing all who can make it.  No IRC meeting next week, for those reading at home.16:41
*** pballand has quit IRC16:42
david-lyleSee everyone on Sunday16:42
david-lyle#endmeeting16:42
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:42
openstackMeeting ended Tue May  6 16:42:31 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-05-06-16.02.html16:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-05-06-16.02.txt16:42
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-05-06-16.02.log.html16:42
jcoufalthanks all, see you soon!16:42
*** fixedgary has left #openstack-meeting-316:42
jristo/16:42
*** shakamunyi has quit IRC16:42
lsmolathanks, see you at the summit16:43
pbelanyibye16:43
*** pbelanyi has left #openstack-meeting-316:43
*** jcoufal has quit IRC16:43
*** clu__ has quit IRC16:43
*** doug-fish has left #openstack-meeting-316:44
lblanchardsee you all!16:44
*** thinrichs has joined #openstack-meeting-316:44
*** tqtran has left #openstack-meeting-316:44
*** johnma has left #openstack-meeting-316:45
*** tzumainn has left #openstack-meeting-316:45
*** pballand has joined #openstack-meeting-316:47
*** jpich has quit IRC16:48
*** beyounn has joined #openstack-meeting-316:49
*** gothicmindfood has left #openstack-meeting-316:50
*** TravT has quit IRC16:55
*** nacim has quit IRC16:56
*** crobertsrh has left #openstack-meeting-316:58
*** thinrichs_ has joined #openstack-meeting-316:59
*** thinrichs has quit IRC16:59
*** thinrichs_ is now known as thinrichs16:59
*** rajdeep has joined #openstack-meeting-317:00
pballandhey17:00
thinrichsHi all17:00
rajdeephi17:01
pballand!startmeeting CongressTeamMeeting17:01
openstackpballand: Error: "startmeeting" is not a valid command.17:01
pballand#startmeeting CongressTeamMeeting17:02
openstackMeeting started Tue May  6 17:02:14 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.17:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:02
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:02
openstackThe meeting name has been set to 'congressteammeeting'17:02
pballandAgenda today: recap on action items, then planning for Atlanta17:02
pballandrajdeep: do you mind going first?17:03
*** kudva has joined #openstack-meeting-317:03
rajdeepsure17:03
kudvaHi17:03
thinrichskudva: hi17:03
rajdeeplast two weeks spent adding more get data to nova driver17:03
pballandkudva: just getting started on recap17:03
kudvaok17:04
rajdeepadded details about hosts and floating_ips17:04
rajdeepnow our nova driver has four tuple types17:04
*** ttrifonov_zZzz is now known as ttrifonov17:04
rajdeepservers, flavours, floating_ips and hosts17:04
rajdeepand their associated field elements17:05
thinrichsThat definitely gives a richer feel to the Nova integration.  Good work.17:05
rajdeepthanks!17:05
rajdeepnow i am planning to add some test cases as suggested by thinrichs17:06
rajdeepneed some guidance on test case structure17:06
pballandI would suggest starting with unit tests, and everyting mocked up17:06
rajdeepok, we use mock framework?17:07
pballandup to you17:07
rajdeepwhere should these test cases be added in the tree.17:08
pballand‘tests’ subtree of the module17:08
rajdeepok17:08
thinrichsWhile on the topic of subtrees, I think we ought to pull out the service_pluggins from the server directory and make it its own dir.17:09
thinrichsAnd maybe rename it to just "datasources".17:09
thinrichsI've been importing those things, and the paths are cumbersome.17:09
rajdeepthats a good idea17:09
pballandgreat, other questions on datasources?17:09
rajdeepso we will have a tests directory under service_pluggins/datasources17:10
*** otherwiseguy has joined #openstack-meeting-317:10
pballandjust /congress/datasources/tests17:10
rajdeepok..17:10
pballandkudva: do you mind sharing an update?17:11
rajdeepi will take the AI of changing the location and name of the directory service_pluggin17:11
kudvaYes. I sent some code to Tim to review, and he responded with some nice suggestions, specifically17:11
pballand#action rajdeep will change location of the service_plugin directory17:11
kudvaI have a builtin.py program, which gets imported into runtime.py (which was Tim's recommendation). I added code to runtime.py17:12
kudvaNow, I am writing tests using mock17:12
kudvaI will put these test locally for now. Once the tests pass, I will move them to the tests directory (should be simple to move).17:12
pballandany estimate on when you may have soemthing for code reveiw?17:13
kudvaWe talked a bit if the the working code into git, but he wasn't sure whether some of the jenkins test need to be disabled.17:13
pballandcurrently, jenkins isn’t running the tests because i17:13
kudvaTim has looked through the code. For the team, I would say next tuesday.17:13
pballand‘make’ isn’t wired in17:14
pballandthat’s on my plate (and has been for too long)17:14
pballandyou can still run the tests locally17:14
kudvathat way, I have some tests passing17:14
kudvaokay17:14
pballand#action kudva to submit first pass of builtins for review next week17:15
pballandthat’s very exciting - I’m looking forward to having this fuctionality17:15
pballandother questions or comments on builtins?17:15
*** s3wong has joined #openstack-meeting-317:15
pballandok, thinrichs: do you have any updates to share?17:16
thinrichsI've been working on integrating the Plexxi code.17:16
thinrichsIt's been slow going, but I'm finally starting to understand that code.17:16
thinrichsI've got the first test case working.17:17
cloudtoadExcellent!17:17
thinrichsThat test case is just getting 2 data drivers to talk over the amqp bus.17:17
pballandthats great - this will be really importaint for tying everything together in a nice runnable package!17:18
thinrichsNext test case will be to get a data source and the policy engine to talk.17:18
thinrichscloudtoad: good to see you here!17:18
thinrichseveryone else: cloudtoad wrote the Plexxi code.17:18
cloudtoadThanks, I'm glad to be a part of this.17:18
rajdeephi cloudtoad17:18
thinrichsAnd we should probably start calling it DSE (Data services engine), instead of Plexxi code.17:18
rajdeepor integration engine17:19
pballandsince cloudtoad is the author, I think he should get naming rights :)17:19
pballand(it’s currently called dse)17:19
pballanddo you think you will be able to push some tests/examples soon?17:20
thinrichsMaybe--depends on how things go.17:20
thinrichscloudtoad has also been planning on making some tweaks here and there.17:20
thinrichsSo I don't want to step on those.17:20
pballandok, fair enough :)17:21
thinrichsBut I'll push for review as soon as I have something solid.17:21
pballandcloudtoad: anything add?17:21
cloudtoadYep..17:21
pballand#action thinrichs to push tests for dse17:21
pballands/anything add/anything to add/17:22
cloudtoadDSE needs a bit of cleanup work, I believe we will convert from Threading model to eventlets.17:22
cloudtoadComments, and perhaps some readme.md files in the DSE directory to walk through how it works and how to write data source modules.17:22
pballandcloudtoad: yes, I took a peek at that, but haven’t made any changes yet - I was hesitant to change code without tests :)17:22
thinrichsMaybe I'll push my baby unit test, so you've got a starting point.17:23
pballandthe dox would be a great help too17:23
pballand!action cloudtoad to add documentation to DSE modules17:23
openstackpballand: Error: "action" is not a valid command.17:23
pballand#action cloudtoad to add documentation to DSE modules17:23
* pballand is !-happy today for some reason17:24
rajdeepquick question17:24
rajdeepwill the data source drivers need some rework for dse integration?17:24
pballandit shouldn’t be much - just some boilerplate if anything17:25
thinrichsI was playing around with that for my tests.17:25
thinrichsI think we'll just have DataSourceDriver inherit from dse.deepSix17:25
rajdeepok that is good news17:25
rajdeep!17:25
*** absubram_ has quit IRC17:25
thinrichsMight need to tweak __init__ but otherwise I think they should be completely compatible.17:25
thinrichsAs long as we're not stepping on the function names deepsix uses.17:26
pballandanything else on DSE?17:26
pballandI have been working on the API design, and have a proposal to send out17:27
cloudtoadNot from me (that I can remember/think of)17:27
pballandI started as a google doc for ease of comments: http://goo.gl/1E5MeY17:27
pballandbasically, I propose modeling all data as a data-source (including data output from a policy)17:28
cloudtoadGood plan..17:29
pballandI also left placeholders in for multi-tenancy, but will stick to just one ‘default’ policy for the first cut17:29
cloudtoadIf you can model policies and rules as tables, then policy data can be published on the DSE bus.17:29
thinrichsWe can publish policies/data/whatever on the DSE bus, right?  There's nothing about tables built into DSE.17:31
cloudtoadSorry, that's correct...17:31
thinrichsBut right I think we're expecting the API calls to be sent via the bus.17:31
cloudtoadYou can structure the information however you wish17:31
thinrichscloudtoad: agreed17:32
pballandthinrichs: raises a good point - I envisioned the entire API running over the bus (it is just a REST projection of the bus)17:32
cloudtoadHow will that interface with Horizon, if at all?17:32
pballandat this point, we don’t have any resources to work on horizon intergration, but that is definitely something we will need to takel17:33
pballandtackle17:33
rajdeepi thought REST was more for HTTP rather than messaging style interaction17:33
pballandrajdeep: yes, they are different styles - the point is that the fundamental data interchange style of the core of the system is the message bus17:34
pballandthis model will facilitate scale-out in the future17:35
rajdeepso it is json in a message body17:35
pballand(and not lock us in to inefficient REST calls when we need better performance)17:35
cloudtoadRest calls really are requests for data...  Perhaps the URL will translate to AMQP address and body of request will be passed to policy module (or even a data source module).17:35
cloudtoadrajdeep: Yes.17:35
pballandcloudtoad: exactly17:36
pballandthe scalability is a bit of overkill at this point, but the pattern is pretty nice to work in17:36
pballandother comments or questions about the API?17:37
pballand(we can continue the conversation in the google doc)17:37
pballandok - I wanted to talk a bit about the conference next week17:38
pballandthere is one session scheduled for Congress on Wed evening, and a developer track on Friday morning 9-12:2017:38
*** rajdeep has quit IRC17:39
pballandI’ll just be giving an overview on Wed, but it would be great to have everyone in attendance17:39
pballandOn Friday, it will be an interactive design session17:40
pballand#topic Open Discussion17:40
*** openstack changes topic to "Open Discussion (Meeting topic: CongressTeamMeeting)"17:40
pballandany other topics to discuss?17:41
cloudtoadWhat is the actual agenda for Friday or is that freeform?17:41
pballandWe’re still working on that17:41
*** Prashanth has joined #openstack-meeting-317:42
cloudtoadLet me rephrase that... should I prepare something re: DSE for Wed or Fri?17:42
pballandthat would be awesome - for Fri17:42
*** rajdeep has joined #openstack-meeting-317:42
rajdeepsorry got disconnected17:42
pballandI’ll get in touch with you about specifics17:42
cloudtoadok17:43
pballandanything else?17:43
pballandThanks everyone, and I’m looking forward to seeing you in Atlanta next week!17:44
thinrichsSee you there!17:44
*** jamie_h has quit IRC17:44
pballand#endmeeting17:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:44
rajdeepbye17:44
openstackMeeting ended Tue May  6 17:44:43 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-05-06-17.02.html17:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-05-06-17.02.txt17:44
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-05-06-17.02.log.html17:44
*** thinrichs has left #openstack-meeting-317:45
*** ttrifonov is now known as ttrifonov_zZzz17:46
*** Prashanth has quit IRC17:47
*** thinrichs has joined #openstack-meeting-317:47
*** kudva has quit IRC17:47
*** ttrifonov_zZzz is now known as ttrifonov17:48
*** thinrichs has quit IRC17:48
*** eghobo has joined #openstack-meeting-317:49
*** ttrifonov is now known as ttrifonov_zZzz17:49
*** rajdeep has quit IRC17:51
*** ttrifonov_zZzz is now known as ttrifonov17:51
*** peristeri has quit IRC17:52
*** ttrifonov is now known as ttrifonov_zZzz17:52
*** ttrifonov_zZzz is now known as ttrifonov17:54
*** peristeri has joined #openstack-meeting-317:54
*** pballand has quit IRC17:55
*** SumitNaiksatam has quit IRC17:55
*** emagana has quit IRC17:56
*** emagana has joined #openstack-meeting-317:56
*** coolsvap|afk is now known as coolsvap17:58
*** emagana has quit IRC17:59
*** sankarshan_away is now known as sankarshan18:00
*** emagana has joined #openstack-meeting-318:01
*** ttrifonov is now known as ttrifonov_zZzz18:01
*** ttrifonov_zZzz is now known as ttrifonov18:03
*** eguz has joined #openstack-meeting-318:03
*** eguz has quit IRC18:05
*** ttrifonov is now known as ttrifonov_zZzz18:05
*** jamielennox|away is now known as jamielennox18:05
*** eguz has joined #openstack-meeting-318:05
*** ttrifonov_zZzz is now known as ttrifonov18:05
*** eghobo has quit IRC18:06
*** ttrifonov is now known as ttrifonov_zZzz18:07
*** chuckC has quit IRC18:08
*** ttrifonov_zZzz is now known as ttrifonov18:08
*** SumitNaiksatam has joined #openstack-meeting-318:08
*** iben_ has joined #openstack-meeting-318:10
*** ttrifonov is now known as ttrifonov_zZzz18:11
*** ttrifonov_zZzz is now known as ttrifonov18:11
*** alexpilotti has quit IRC18:17
*** overlayer has joined #openstack-meeting-318:17
*** alexpilotti has joined #openstack-meeting-318:20
*** emagana has quit IRC18:27
*** emagana has joined #openstack-meeting-318:27
*** emaganap has joined #openstack-meeting-318:33
*** emagana has quit IRC18:35
*** lcheng_ has quit IRC18:38
*** lcheng_ has joined #openstack-meeting-318:39
*** ttrifonov is now known as ttrifonov_zZzz18:46
*** ttrifonov_zZzz is now known as ttrifonov18:48
*** chuckC has joined #openstack-meeting-318:50
*** rockyg has joined #openstack-meeting-318:50
*** coolsvap is now known as coolsvap|afk18:52
*** markmcclain has joined #openstack-meeting-318:54
*** lcheng_ has quit IRC18:54
*** garyduan has joined #openstack-meeting-318:55
*** ttrifonov is now known as ttrifonov_zZzz18:56
*** ttrifonov_zZzz is now known as ttrifonov18:56
*** dtroyer has joined #openstack-meeting-318:56
*** beyounn has quit IRC18:57
*** gduan has quit IRC18:57
*** beyounn has joined #openstack-meeting-318:57
*** briancurtin has joined #openstack-meeting-318:59
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue May  6 19:00:21 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
briancurtinI setup an agenda at https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-05-06_1900_UTC19:00
*** jcoufal has joined #openstack-meeting-319:01
briancurtinstarts by just going through reviews, least contentions to most, so we can get a few small things out of the way and off the plate19:01
briancurtinanyway, can anyone here for python-openstacksdk meeting state their name and affiliation?19:01
briancurtinBrian Curtin, Rackspace19:02
dtroyerDean Troyer, Nebula19:02
jamielennoxJamie Lennox, Red Hat19:03
briancurtinpotentially light meeting i guess, but may as well get started19:04
briancurtin#topic https://review.openstack.org/#/c/90301/ - Resource properties (Jamie)19:04
*** openstack changes topic to "https://review.openstack.org/#/c/90301/ - Resource properties (Jamie) (Meeting topic: python-openstacksdk)"19:04
briancurtinjamielennox: this had two +1s and just that AttributeError question - i looked around and it seems like AttributeError is the way to go. the descriptor tutorial also does it19:05
jamielennoxok, i guess that makes as much sense as anything19:06
jamielennoxi had missed that comment19:06
edleafe-Ed Leafe, Rackspace19:06
briancurtin#topic https://review.openstack.org/#/c/91448/ - Example code for presentation (Terry)19:07
*** openstack changes topic to "https://review.openstack.org/#/c/91448/ - Example code for presentation (Terry) (Meeting topic: python-openstacksdk)"19:07
*** terrylhowe has joined #openstack-meeting-319:08
dtroyerI'm still trying to get caught up but this looks fine to me so far.  Terry's comment thought brings up something that I don't know if we have talked about in general.19:08
dtroyerThat being if attribute names must match the names used in the REST API19:08
briancurtinthis change depends on a later one that doesn't work, but it's an easy fix for that - so this and its dependency are close19:08
*** wchrisj_ has joined #openstack-meeting-319:09
dtroyerI'll answer no in the hopes that we can set come consistency here, ie, all resources have a 'name'19:09
jamielennoxdtroyer: related to which patch?19:09
dtroyerThe resource properties.  Terry has a coment in resource.py that made me think of this.19:10
dtroyerWe don't need to answer it now but I'd like to eventually come to a consensus19:10
briancurtinsetting consistency here seems like a good goal to me19:11
dtroyerMy canonical example of this is using 'project' vs 'tenant', which is what I did in OSC19:11
edleafe-All resources should have a name and id attribute. When the service doesn't supply one or the other, make them properties.19:12
jamielennoxdtroyer: right, so the way descriptors work in general it's easier to specify a name in the constructor19:12
*** edleafe- has left #openstack-meeting-319:12
*** edleafe- has joined #openstack-meeting-319:12
jamielennoxso name = prop('name')19:12
jamielennoxbut it has the side effect that you could easily do:19:13
jamielennoxproject = prop('project')19:13
jamielennoxtenant = prop('tenant')19:13
jamielennoxbah19:13
*** ttrifonov is now known as ttrifonov_zZzz19:13
jamielennoxtenant = prop('project')19:13
jamielennoxand have them set the same value in the underlying message19:13
*** ttrifonov_zZzz is now known as ttrifonov19:13
terrylhoweor in cinder name = prop('display_name')19:14
dtroyerI was thinking at a layer or two up, as in what names we choose for properties/attributes to document and expose to SDK users19:14
dtroyerI like this way of handling it19:14
briancurtinsince we have a few reviews to cover, is the usage of prop important to figure out now, or is the code in that review fine to go in?19:14
wchrisj_jamielennox: dtroyer: won't that sort of thing be handled properly once we version services on the SDK side, or not?19:14
dtroyerwe don't need to answer this now…  let's get back to reviews19:15
dtroyercan talk in #-sdks later19:15
briancurtinnow that terrylhowe is here, https://review.openstack.org/#/c/91448/ - Example code for presentation19:16
jamielennoxwchrisj_: propably - either way19:16
briancurtinpending the dep change working, seems fine to me19:16
briancurtin(and the dep has a comment on how to fix)19:16
terrylhoweexcellent, thanks briancurtin I was having py33 on my dev box and couldn't recreate19:17
briancurtini dont think there's much there to discuss, and it's pretty quiet, so moving on to the two bigger reviews19:18
briancurtin#topic https://review.openstack.org/#/c/90538/ - Add presentation layer19:18
*** openstack changes topic to "https://review.openstack.org/#/c/90538/ - Add presentation layer (Meeting topic: python-openstacksdk)"19:18
dtroyerI would like to not remove lower-level examples… if they need to be moved, fine.  I like the idea of building in a series of scripts, not  a single massive sample19:19
dtroyeragain, I may just be behind here19:19
jamielennoxdtroyer: right, i like keeping the lower levels accessible19:20
*** lcheng_ has joined #openstack-meeting-319:21
terrylhowedtroyer, I did have this kind of CLI command like thing going, but I removed it to simplify19:21
terrylhoweI could bring it back into the example19:21
dtroyerI was thinking about the make_transport() being removed from common.py.  I may have not added the bits that use it yet, so I can then if necessary,19:22
jamielennoxuploaded https://review.openstack.org/#/c/90301 with AttributeError fixes19:23
terrylhowemake_transport got moved into the connection class dtroyer19:23
dtroyerI'll dig into it more, but IIRC that breaks the lower-layer stuff I had going…again, I may not have included it all yet19:24
terrylhowethe connection class could maybe be changed to just create a transport for some commands19:25
dtroyermaybe, but then to do a transport/session example we need the next layer up?19:25
terrylhoweyeh19:26
jamielennoxi have a general question about how we represent nested resources when we get a chance, i have User and Roles as top level, but with a Resource class how do we specify a User's Roles, eg /user/xxx/roles19:26
dtroyerjamielennox: according to the reviews in OSC right now, Assignments!19:27
dtroyerthat's too general for my tastes, but I don't have a better suggestion yet19:27
jamielennoxdtroyer: i haven't seen that yet19:27
dtroyerhttps://review.openstack.org/9163419:27
jamielennoxi spent a while on it directly after the last meeting and otherwise haven't looked at sdk much since19:27
*** lsmola has quit IRC19:28
*** ttrifonov is now known as ttrifonov_zZzz19:29
*** ttrifonov_zZzz is now known as ttrifonov19:29
jamielennoxdtroyer: i can't even tell what that's trying to do19:29
dtroyerapparently it's for a new v3 API to get the mapping info between users/groups/domains/project/roles19:29
dtroyerit's all new to me too19:30
dtroyerlooks like a special case of 'role list' to me19:30
dtroyerbut that's off-topic here19:30
terrylhoweWhere are we on the presentation https://review.openstack.org/#/c/90538 ?19:31
jamielennoxdtroyer: oh yea, i didn't realize we were exposing that19:31
jamielennoxterrylhowe: sorry, we should finish talking about that first19:31
dtroyerterrylhowe: how is the Json class different from the JSON encoding/decoding already in Transport?19:32
terrylhoweWell, it pulls all that out of the transport class so the one class controls encode/decode19:32
terrylhoweOSI model style19:32
dtroyerI'm −2 on that19:33
terrylhowewhy the hate :)19:33
dtroyerRealistically, what other encoding is going to be usable here?  Maybe XML.19:33
terrylhowexml and maybe plain text19:34
dtroyerThat forces me up another layer or two to do things like API discovery19:34
terrylhoweapi discovery is a bit different kind of like authentication because you don't have a session19:34
dtroyerexactly, I dont' always want a session19:35
terrylhowewell, you have have a presentation, session and you still could use the transport19:35
*** lcheng_ has quit IRC19:36
jamielennoxthe only problem i have with presentation is the assumption that you can always change between them19:36
dtroyerbut I lose JSON, or I have to do another subclass to put it back?19:37
jamielennoxit works if JSON or XML or plain text is available and interchangable for every interface on every services19:37
jamielennoxbut if i pass the JSON presentation to the whichever cinder API that makes plain text requests what does it do?19:37
terrylhowefailure19:38
*** ttrifonov is now known as ttrifonov_zZzz19:38
terrylhowewe could also create some sort of no authenticate session if we wanted presentation with no session19:39
*** ttrifonov_zZzz is now known as ttrifonov19:40
dtroyerwhy is having this layer be distinct important?19:40
terrylhoweonly for xml support19:41
jamielennoxterrylhowe: in which case then the user of the resource/operation needs to know which presentation layer to pass?19:41
dtroyerwhere do we see needing XML support?19:41
terrylhoweI'm not a big xml fan, but if developers want to test that API it would be handy19:41
dtroyerIIRc only Nova really has usable (?) XML API, does novalicent have it today?  (I should know that but I don't...)19:42
terrylhoweneutron has xml19:42
terrylhoweI think nova has gaps in xml support19:43
*** ttrifonov is now known as ttrifonov_zZzz19:43
dtroyerand it's tested on par with JSON?19:43
edleafe-Am I the only one who gets the feeling that we are making things overly complex? All the services speak JSON, and we are taking that and creating Python objects, no?19:43
*** ttrifonov_zZzz is now known as ttrifonov19:44
dtroyeredhall: no you are not...19:44
terrylhowecould be, it also may be that neutron, nova, etc devs might lend more support if they could use the sdk for testing19:44
*** ttrifonov is now known as ttrifonov_zZzz19:45
dtroyerSo to get a bit more pragmatic, what about Presentation is there that couldn't be retro-fitted into Session later if necessary?19:45
*** ttrifonov_zZzz is now known as ttrifonov19:46
*** mrunge has quit IRC19:46
dtroyerclass XML_Session(Session):19:46
*** ttrifonov is now known as ttrifonov_zZzz19:47
jamielennoxdtroyer: the reason i made original session take a json= parameter rather than a body= parameter is to distinguish them19:47
jamielennoxyou can add an xml= if you wanted19:47
*** ttrifonov_zZzz is now known as ttrifonov19:48
dtroyerjamielennox: right, and that's why I'm trying to understand why another wrapper above Session is necessary to do this.19:48
terrylhowemy first patch on the presentation, the session just had one19:48
terrylhowehttps://review.openstack.org/#/c/90538/1/openstack/session.py19:48
*** lcheng_ has joined #openstack-meeting-319:48
*** lsmola2 has joined #openstack-meeting-319:48
terrylhoweit is kind of less pure, but maybe less complicated at the same time19:49
jamielennoxi'm not opposed to the layer, just the assumption that it should be passed19:50
jamielennoxif the Resource creates the wrapper then that makes sense because the resource knows what it needs to talk19:51
dtroyerI'm not convinced we need the layer…not necessarily opposed to it (I'll linkely never use it), but want to understand what it's value-add is19:51
edleafe-I would prefer keeping things simple at first, and adding complexity only where it turns out we really need it.19:51
dtroyerIOW, right now I can't defend it to someone outside this room…19:52
*** ttrifonov is now known as ttrifonov_zZzz19:54
*** eguz has quit IRC19:55
jamielennoxterrylhowe: having the prenstation embeded in there doesn't solve the issue because you still can't differentiate for when a resource needs to use a different format19:55
*** eghobo has joined #openstack-meeting-319:55
*** ttrifonov_zZzz is now known as ttrifonov19:55
terrylhoweIf presentation was an argument to _request, they could specify a one off presentation19:56
*** lsmola2 has quit IRC19:56
*** markmcclain1 has joined #openstack-meeting-319:57
briancurtin(couple minutes left, then probably continue in -sdks)19:57
*** lsmola2 has joined #openstack-meeting-319:58
terrylhoweauthentication is still out there19:59
*** pballand has joined #openstack-meeting-319:59
*** markmcclain2 has joined #openstack-meeting-319:59
terrylhowethere are a lot of comments there I need to address19:59
briancurtinterrylhowe: yeah, with that one, i think it's generally fine given some cleanup to not bring in a lot of that deprecated stuff19:59
*** markmcclain has quit IRC19:59
dtroyerre: auth, I'd like to see the backeard-compat stuff gone before we commit it19:59
*** markmcclain2 has quit IRC19:59
*** jpomero has quit IRC19:59
terrylhowecool19:59
briancurtinand i believe jamie got most of them, i think i caught one or two possible areas. other than that, seemed cool20:00
jamielennoxterrylhowe: yea, for my comments anything not marked as deprecated is fine to bring in20:00
briancurtintime to head back to -sdks20:00
briancurtin#endmeeting20:00
terrylhoweI'll get on it20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue May  6 20:00:56 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-06-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-06-19.00.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-05-06-19.00.log.html20:01
briancurtinthanks everyone20:01
*** otherwiseguy has quit IRC20:01
*** terrylhowe has left #openstack-meeting-320:01
*** markmcclain has joined #openstack-meeting-320:01
*** chuckC has left #openstack-meeting-320:01
*** ttrifonov is now known as ttrifonov_zZzz20:01
*** jcoufal has quit IRC20:01
*** markmcclain1 has quit IRC20:02
*** dtroyer has left #openstack-meeting-320:02
*** ttrifonov_zZzz is now known as ttrifonov20:02
*** chuckC has joined #openstack-meeting-320:03
*** chuckC has left #openstack-meeting-320:04
*** briancurtin has left #openstack-meeting-320:05
*** lcheng_ has quit IRC20:07
*** pballand has quit IRC20:08
*** jamielennox has left #openstack-meeting-320:13
*** ttrifonov is now known as ttrifonov_zZzz20:15
*** ttrifonov_zZzz is now known as ttrifonov20:17
*** ttrifonov is now known as ttrifonov_zZzz20:20
*** ttrifonov_zZzz is now known as ttrifonov20:21
*** ttrifonov is now known as ttrifonov_zZzz20:25
*** gduan has joined #openstack-meeting-320:25
*** otherwiseguy has joined #openstack-meeting-320:25
*** ttrifonov_zZzz is now known as ttrifonov20:26
*** beyounn has quit IRC20:26
*** garyduan has quit IRC20:27
*** terryw has joined #openstack-meeting-320:27
*** ttrifonov is now known as ttrifonov_zZzz20:27
*** ttrifonov_zZzz is now known as ttrifonov20:27
*** beyounn has joined #openstack-meeting-320:28
*** ttrifonov is now known as ttrifonov_zZzz20:28
*** lsmola2 has quit IRC20:29
*** pballand has joined #openstack-meeting-320:29
*** otherwiseguy has quit IRC20:30
*** julim has quit IRC20:31
*** pballand has quit IRC20:32
*** lcheng_ has joined #openstack-meeting-320:33
*** chuckC has joined #openstack-meeting-320:42
*** terryw has quit IRC20:44
*** otherwiseguy has joined #openstack-meeting-320:45
*** mestery has joined #openstack-meeting-320:46
*** troytoma- has quit IRC20:47
*** troytoman has joined #openstack-meeting-320:47
*** otherwiseguy has quit IRC20:51
*** rockyg has quit IRC20:52
*** otherwiseguy has joined #openstack-meeting-321:06
*** lblanchard has quit IRC21:10
*** otherwiseguy has quit IRC21:12
*** eguz has joined #openstack-meeting-321:18
*** eghobo has quit IRC21:22
*** chuckC has quit IRC21:30
*** jaypipes has quit IRC21:30
*** peristeri has quit IRC21:38
*** otherwiseguy has joined #openstack-meeting-321:39
*** david-lyle has quit IRC21:48
*** chuckC has joined #openstack-meeting-321:48
*** otherwiseguy has quit IRC21:53
*** otherwiseguy has joined #openstack-meeting-321:53
*** otherwiseguy has quit IRC21:58
*** otherwiseguy has joined #openstack-meeting-321:59
*** pballand has joined #openstack-meeting-322:01
*** SumitNaiksatam has quit IRC22:06
*** catherineD has joined #openstack-meeting-322:09
*** catherineD has left #openstack-meeting-322:10
*** mwagner_ has quit IRC22:27
*** pballand has quit IRC22:27
*** TravT has joined #openstack-meeting-322:36
*** TravT has quit IRC22:36
*** overlayer has quit IRC22:48
*** pballand has joined #openstack-meeting-322:48
*** SumitNaiksatam has joined #openstack-meeting-322:50
*** s3wong has quit IRC22:55
*** emaganap has quit IRC22:56
*** eguz has quit IRC22:56
*** lcheng_ has quit IRC23:04
*** pballand has quit IRC23:04
*** lcheng_ has joined #openstack-meeting-323:05
*** eghobo has joined #openstack-meeting-323:07
*** eguz has joined #openstack-meeting-323:13
*** eghobo has quit IRC23:17
*** eguz has quit IRC23:19
*** banix has quit IRC23:25
*** markmcclain has quit IRC23:27
*** yamahata has quit IRC23:45
*** mwagner_ has joined #openstack-meeting-323:58

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