Thursday, 2014-03-27

*** alexpilotti has joined #openstack-meeting-300:02
*** cjellick has quit IRC00:06
*** banix has joined #openstack-meeting-300:07
*** david-lyle has joined #openstack-meeting-300:09
*** lblanchard has joined #openstack-meeting-300:12
*** lblanchard has quit IRC00:18
*** lblanchard has joined #openstack-meeting-300:19
*** lblanchard has quit IRC00:20
*** lblanchard has joined #openstack-meeting-300:36
*** lblanchard has quit IRC00:37
*** troytoman-away is now known as troytoman00:46
*** mestery has quit IRC00:51
*** MaxV has quit IRC00:53
*** alexpilotti has quit IRC00:57
*** markmcclain has quit IRC00:59
*** eghobo has quit IRC01:02
*** enikanorov has joined #openstack-meeting-301:04
*** SumitNaiksatam has quit IRC01:11
*** Kanzhe has quit IRC01:12
*** jpomero has quit IRC01:12
*** enikanorov_ has quit IRC01:12
*** amotoki has quit IRC01:12
*** dolphm has quit IRC01:12
*** d0ugal has quit IRC01:12
*** zigo has quit IRC01:12
*** jrist has quit IRC01:12
*** persia has quit IRC01:12
*** eghobo has joined #openstack-meeting-301:41
*** eghobo has quit IRC01:45
*** david-lyle has quit IRC01:46
*** SumitNaiksatam has joined #openstack-meeting-301:47
*** SumitNaiksatam has joined #openstack-meeting-301:48
*** amotoki has joined #openstack-meeting-301:49
*** dolphm has joined #openstack-meeting-301:49
*** d0ugal has joined #openstack-meeting-301:49
*** zigo has joined #openstack-meeting-301:49
*** jrist has joined #openstack-meeting-301:49
*** persia has joined #openstack-meeting-301:49
*** SumitNaiksatam has left #openstack-meeting-301:51
*** dguitarbite has joined #openstack-meeting-302:00
*** david-lyle has joined #openstack-meeting-302:28
*** vkozhukalov has joined #openstack-meeting-302:30
*** persia has quit IRC02:30
*** persia has joined #openstack-meeting-302:30
*** lifeless has joined #openstack-meeting-302:30
*** persia has quit IRC02:31
*** persia has joined #openstack-meeting-302:31
*** lifeless has quit IRC02:35
*** lcheng has joined #openstack-meeting-302:38
*** HenryG has quit IRC02:46
*** devlaps has quit IRC02:46
*** lifeless has joined #openstack-meeting-302:53
*** lcheng has quit IRC02:56
*** amotoki has quit IRC03:37
*** devlaps has joined #openstack-meeting-303:40
*** yamahata has joined #openstack-meeting-303:51
*** yamahata has quit IRC04:05
*** banix has quit IRC04:14
*** eghobo has joined #openstack-meeting-304:20
*** saju_m has joined #openstack-meeting-304:39
*** tmazur has joined #openstack-meeting-304:49
*** dguitarbite has quit IRC05:22
*** amotoki has joined #openstack-meeting-305:32
*** devlaps has quit IRC05:55
*** devlaps has joined #openstack-meeting-306:00
*** lpetrut has joined #openstack-meeting-306:04
*** lcheng has joined #openstack-meeting-306:06
*** saju_m has quit IRC06:07
*** vkozhukalov has quit IRC06:10
*** jtomasek has joined #openstack-meeting-306:14
*** jtomasek has quit IRC06:14
*** tmazur has quit IRC06:26
*** tmazur has joined #openstack-meeting-306:39
*** yamahata has joined #openstack-meeting-306:39
*** saju_m has joined #openstack-meeting-306:51
*** dguitarbite has joined #openstack-meeting-307:01
*** lcheng has quit IRC07:03
*** devlaps has quit IRC07:16
*** dguitarbite_ has joined #openstack-meeting-307:19
*** dguitarbite has quit IRC07:19
*** MaxV has joined #openstack-meeting-307:20
*** lpetrut has quit IRC07:22
*** eghobo has quit IRC07:28
*** vkozhukalov has joined #openstack-meeting-307:38
*** mrunge has joined #openstack-meeting-307:41
*** mrunge is now known as mrunge_brb07:41
*** jcoufal has joined #openstack-meeting-307:58
*** MaxV has quit IRC08:07
*** troytoman is now known as troytoman-away08:19
*** dguitarbite has joined #openstack-meeting-308:23
*** ttrifonov_zZzz is now known as ttrifonov08:23
*** dguitarbite_ has quit IRC08:26
*** MaxV has joined #openstack-meeting-308:39
*** MaxV has quit IRC08:40
*** MaxV has joined #openstack-meeting-308:40
*** saju_m has quit IRC08:43
*** mrunge_brb is now known as mrunge08:48
*** nacim has joined #openstack-meeting-308:52
*** johnthetubaguy has joined #openstack-meeting-308:52
*** johnthetubaguy1 has joined #openstack-meeting-308:55
*** saju_m has joined #openstack-meeting-308:56
*** johnthetubaguy has quit IRC08:56
*** safchain has joined #openstack-meeting-309:08
*** saju_m has quit IRC09:16
*** saju_m has joined #openstack-meeting-309:28
*** johnthetubaguy1 is now known as johnthetubaguy09:30
*** ycombinator has quit IRC09:30
*** ycombinator has joined #openstack-meeting-309:31
*** jtomasek has joined #openstack-meeting-309:57
*** amotoki has quit IRC10:00
*** tmazur has quit IRC10:12
*** saju_m has quit IRC10:24
*** mwagner_lap has quit IRC10:26
*** tmazur has joined #openstack-meeting-310:28
*** mwagner_notHere has quit IRC10:28
*** tmazur has quit IRC10:58
*** david-lyle has quit IRC11:03
*** yamahata has quit IRC11:07
*** saju_m has joined #openstack-meeting-311:14
*** MaxV has quit IRC11:25
*** saju_m has quit IRC11:33
*** saju_m has joined #openstack-meeting-311:36
*** vkozhukalov has left #openstack-meeting-311:37
*** HenryG has joined #openstack-meeting-311:39
*** dguitarbite has quit IRC11:39
*** mwagner_lap has joined #openstack-meeting-311:42
*** MaxV has joined #openstack-meeting-311:51
*** mwagner_ has joined #openstack-meeting-311:59
*** alexpilotti has joined #openstack-meeting-312:11
*** alexpilotti has quit IRC12:17
*** mestery has joined #openstack-meeting-312:26
*** mestery has joined #openstack-meeting-312:26
*** lblanchard has joined #openstack-meeting-312:29
*** wchrisj has joined #openstack-meeting-312:56
*** xuhanp has joined #openstack-meeting-312:58
*** markmcclain has joined #openstack-meeting-313:08
*** julim has joined #openstack-meeting-313:18
*** alexpilotti has joined #openstack-meeting-313:21
*** wchrisj has quit IRC13:28
*** mfer has joined #openstack-meeting-313:29
*** yamahata has joined #openstack-meeting-313:36
*** mestery has quit IRC13:55
*** peristeri has joined #openstack-meeting-313:57
*** zigo has quit IRC14:01
*** zigo has joined #openstack-meeting-314:03
*** banix has joined #openstack-meeting-314:06
*** ajo has joined #openstack-meeting-314:07
*** ttrifonov is now known as ttrifonov_zZzz14:17
*** jcoufal has quit IRC14:23
*** jcoufal has joined #openstack-meeting-314:24
*** amotoki has joined #openstack-meeting-314:26
*** david-lyle has joined #openstack-meeting-314:28
*** cjellick has joined #openstack-meeting-314:30
*** cjellick has quit IRC14:32
*** cjellick has joined #openstack-meeting-314:33
*** carl_baldwin has joined #openstack-meeting-314:40
*** devlaps has joined #openstack-meeting-314:51
*** amuller has joined #openstack-meeting-314:53
*** YorikSar has joined #openstack-meeting-314:59
carl_baldwinHi all.15:00
YorikSarHi15:00
carl_baldwinI hope all are well.  We'll get started...15:00
xuhanphi15:00
*** troytoman-away is now known as troytoman15:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu Mar 27 15:01:03 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. 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: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** mestery has joined #openstack-meeting-315:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:01
ajoHi , hello carl_baldwin , YorikSar , amuller , safchain15:01
amullerhiya15:01
safchainHi15:02
*** troytoman is now known as troytoman-away15:02
carl_baldwinIn general, I encourage you to add your action items.  Please feel free.  Look up meetbot for commands that you can use during the meeting.15:02
*** julim has quit IRC15:02
carl_baldwinIs there anything that we need to discuss related to the Icehouse release?15:03
carl_baldwinThe only thing that I'm still working on is documentation of the sudo fix that we've identified.15:04
carl_baldwinI've been in contact with Edgar about that.15:04
ajocarl_baldwin, do you mean, the sudo performance fix?15:04
*** cjellick has quit IRC15:04
*** julim has joined #openstack-meeting-315:04
carl_baldwinajo: yes15:04
carl_baldwinSome of our testing has shown good promise for it.15:05
ajo#link http://www.sudo.ws/repos/sudo/rev/e9dc28c7db6015:05
*** nextone92 has joined #openstack-meeting-315:05
carl_baldwinajo: Thanks for the link.15:05
ajoIt's supposed to slow down as you have more network interfaces unless you disable the new option in this patch.15:05
carl_baldwinCorrect.15:06
ajook, that's good, I haven't been able to test it yet15:06
ajoneither the iproute one15:06
carl_baldwinIt is looking good from my perspective.15:06
carl_baldwinI haven't been able to get much testing on the iproute one.15:06
carl_baldwin#topic l3-high-availability15:07
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:07
carl_baldwinsafchain: Any update?15:07
safchaincarl_baldwin, nothing this week15:08
*** Hao has joined #openstack-meeting-315:08
*** Swami has joined #openstack-meeting-315:08
Swamihi15:09
carl_baldwinOkay.  I'm getting closer to having some time to test but I haven't yet.15:09
carl_baldwinSwami: hi.  Your timing is good.15:09
carl_baldwin#topic neutron-ovs-dvr15:09
Swamithanks15:09
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:09
carl_baldwinSwami: Any updates for the team?15:09
SwamiYes15:09
SwamiDVR Progress update was provided to the subteam.15:09
SwamiThe Plugin extension is almost done15:09
SwamiAgent work is done for most part of the East-West15:10
SwamiWe still have some issues with the ovs rules to resolve, we fixing it right now.15:10
SwamiDesign docs are out there and we are addressing all the comments from it.15:10
carl_baldwinGood progress.15:10
*** Hao_ has joined #openstack-meeting-315:11
SwamiThat's all from me.15:11
carl_baldwinSwami: Thanks.  I know we're all dying to see code.  :)15:11
*** Hao_ has quit IRC15:11
ajo=)15:11
*** hao_ has joined #openstack-meeting-315:12
carl_baldwin#topic bgp-dynamic-routing15:12
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:12
Swamicarl: Yes I understand the problem, and we will upload it soon.15:12
carl_baldwinSwami: You know us developers.  :)15:12
amullersafchain: Swami: I saw the patch that optionally removes the "normally learned" flows from br-tun15:13
Swamisafchain: Thanks for the patch15:13
*** hao_ has quit IRC15:13
*** hao_ has joined #openstack-meeting-315:13
carl_baldwinnextone92: hi15:14
safchainSwami,  thank for suggesting this improvement15:14
nextone92Hi15:14
*** hao_ has quit IRC15:14
nextone92The proposed changes to dynamic routing blueprint remove BGP functionality from tenant routers15:14
*** hao_ has joined #openstack-meeting-315:14
nextone92And then add a data structure “GatewaySpec” to external network15:14
nextone92this new, optionally specified, data structure will contain dynamic routing configuration15:15
*** Hao has quit IRC15:15
nextone92it may only be configured by the openstack administrator15:15
carl_baldwinI like the association with a network.15:15
nextone92If that sounds good to everyone, I will update the document shortly :)15:15
carl_baldwinFor one, it should remove all of my scale concerns.15:15
nextone92I think it's clean and will only impact those who want additional routing services at the edge of neutron network15:16
Swaminextone92: what does this GatewaySpec datastructure hold.15:16
nextone92Here's what I'm thinking: routing type: static/dynamic-bgp (more in the future)15:17
nextone92and then information to accomplish the type of routing15:17
nextone92for bgp it will be such information as remote peers, AS, and shared secrets15:17
*** hao_ is now known as hao15:17
carl_baldwinBTW, I took a crack at outlining the use cases as I promised to last week.  It needs more detail but it is a start.15:18
carl_baldwin#link https://wiki.openstack.org/wiki/Neutron/DynamicRoutingUseCases15:18
nextone92Oooh great!15:18
carl_baldwinThe first use case is lifted directly from nextone92 's document.15:19
carl_baldwinI added the second.15:19
ajonice carl_baldwin15:19
carl_baldwinThe third is the result of my trying to wrap my head around the BGP/MPLS blueprint and use case.15:19
carl_baldwinHopefully, this will aid in our discussions about the topic.15:19
Swamicarl: I will go through the doc and provide my comments15:20
amullercarl_baldwin: Thanks for that15:20
*** dhellmann_ is now known as dhellmann15:21
carl_baldwinamuller: Feel free to ask questions that come up on IRC on on the ML.  I will be adding more detail as questions come up.15:21
SwamiOne question I had is, will this be configurable by a tenant or will it be intelligent enough to add "static/versus dynamic" based on the service type that we choose. Or is it all controlled by the Admin at this point.15:21
nextone92It would only be configurable by the administrator15:22
carl_baldwinIn my personal view of the world, this will all be controlled by the admin.  What do others think?15:22
carl_baldwinWith any dynamic routing relationship, I think it requires some administrative knowledge of the relationship of the openstack cloud with the infrastructure around it.15:23
SwamiToday for example VPN service is configured by a Tenant and not by administrator and if the VPN Service requires Dynamic routing capability then it should be done already by an admin. Is that what you are suggesting.15:24
carl_baldwinIt might make sense on a provider network or something where the tenant is given some control or knowledge of the outside.15:24
carl_baldwinSwami: the difference with BGP/MPLS is that it doesn't rely on strong endpoint authentication or encryption for privacy.15:25
carl_baldwinInstead, it relies on trust between customer and provider and, now, the cloud provider who is a third provider.15:25
nextone92Also, Swami, Carl - if the dynamic routing is attached to the external network, would it be difficult to setup dynamic routing just for the tenant and not the rest of the network?15:25
nextone92Maybe if a tenant owns the external network wholly?15:26
carl_baldwinnextone92: I wrote a few words on that.  I think if the external network is shared between tenants, it will be very difficult.15:26
nextone92agreed, carl_baldwin15:26
carl_baldwinnextone92: Yes, agreed.15:27
SwamiYes, that is what I am not clear. Is it per tenant basis or global flag that enables the dynamic routing. Or is it based on a router context.15:27
carl_baldwinSwami: the association is shifting from the router context to the external network context.15:27
*** safchain has quit IRC15:28
Swamicarl: thanks for the clarification.15:28
nextone92carl_baldwin, Swami - to clarify, it would be good to associate one or more external networks with the same gatewayspec15:28
nextone92so a quagga instance could potentially serve more than one external network15:28
carl_baldwinSwami: yw, you're questions are very well-timed.  These are the details we need to get out in the open.15:29
Swamicarl: Yes we need to do it.15:30
carl_baldwinI think we're on track for a good discussion at the summit.  nextone92 will you be updating your document?15:31
nextone92Yes, I will take an action item to update the document15:31
SwamiI will join briefly after a break.15:32
carl_baldwinGreat.  Feel free to use the action command to take action items.15:32
*** mrunge has quit IRC15:33
carl_baldwin#action carl_baldwin will announce use case wiki on ML and field questions.15:33
carl_baldwin#action nextone92 will update bhp-dynamic-routing document15:34
carl_baldwin#topic DNS lookup of instances15:34
*** openstack changes topic to "DNS lookup of instances (Meeting topic: neutron_l3)"15:34
carl_baldwinI wrote up a draft.  It is pending approval to make public.  So, soon.15:35
*** Swami_ has joined #openstack-meeting-315:35
carl_baldwin#topic Agent Performance with Wrapper Overhead15:35
*** openstack changes topic to "Agent Performance with Wrapper Overhead (Meeting topic: neutron_l3)"15:35
ajocarl15:35
ajosorry,15:35
ajoahh, nothing, you'll make it public soon15:35
ajoI was going to ask about the DNS lookup of instances15:35
ajoyou mean, from outside tenant networks, right?15:35
carl_baldwinFeel free to ping me on IRC.15:36
ajosure15:36
*** Swami has quit IRC15:36
ajoYorikSar,15:36
carl_baldwinajo: I've tagged you as the lead on this performance stuff though I know YorikSar has been very active.15:36
Swami_hi15:36
*** peristeri has quit IRC15:36
YorikSaro/15:37
ajoYes, yorikstar is doing an awesome work15:37
YorikSarI've started working on Neutron changes to integrate rootwrap daemon15:37
carl_baldwinMostly just because ajo brought it up on the ML originally.15:37
YorikSarhttps://review.openstack.org/82787 - I've already added carl_baldwin and ajo to that CR15:37
carl_baldwinYorikSar: I am part-way through a review of each of your two patches.15:37
ajo#link https://review.openstack.org/8278715:37
carl_baldwinI have draft comments but it may take me a couple more days.15:37
YorikSarIt became rather intrusive but I hope it won't be opposed too strongly.15:38
carl_baldwinI encourage others to review.  Especially those who have been active in the ML thread.15:38
ajoYorikSar, did you see the security issues Thierry found in https://review.openstack.org/#/c/81798/  ?15:38
ajo#link https://review.openstack.org/#/c/81798/7/oslo/rootwrap/daemon.py15:39
YorikSarI doubt I will be able to work on this more this week (well, maybe only weekend) so it'll most likely be on hold till Tuesday.15:39
YorikSarI appreciate any comments or thoughts you can provide.15:39
YorikSarajo: Let me check...15:39
ajoit seems that basemanager doesn't process the "serializer" parameter15:39
ajoand it will rely on pickle always15:40
YorikSarOh... I'll respond there.15:40
ajoat least from the doc perspective, I didn't check the actual code of BaseManager15:40
YorikSarBaseManager does support this, but it's undocumented.15:40
ttxYorikSar: heh15:40
ajoahhhh, that explains a lot15:40
carl_baldwin#action carl_baldwin will communicate details about sudo patch to Edgar to be included in the release documentation.15:40
carl_baldwin^ Just throwing that in there.  :)15:41
YorikSarThat's unfortunate but it shouldn't change in future releases.15:41
ajoYorikSar, is that true for py26 too?15:41
YorikSarI can try to push change to CPython to include this parameter into docs.15:41
YorikSarajo: Em.. I'm not sure. Let me check py2615:42
carl_baldwinYorikSar: That'd be great to get some commitment on the feature.15:42
ajoI can see, the code is there for py2715:42
carl_baldwinajo: Good call on checking py26.15:42
YorikSarajo: Yes, it's there in py2615:42
YorikSarAnd py3215:43
YorikSarAnd py3315:43
ajoahh, good YorikSar15:43
ajoand, is it documented for py3.3 ?15:43
YorikSarGentoo is cool - you can have as many Python interpreters as you want installed in the system :)15:43
*** david_lyle_ has joined #openstack-meeting-315:43
ajohehe :)15:43
*** saju_m has quit IRC15:44
YorikSarNope, it's not documented...15:44
ajoI wonder why15:44
YorikSarFor 3.4 I mean.15:44
YorikSarI guess noone ever used this.15:44
ajoI hope we don't find bugs because of this, or that they change the implementation in the future unexpectedly15:45
ajomay be we should git-blame and ask the original authors of that feature.15:45
YorikSarWe're switching off pickle just for security reasons and this might be never anticipated by authors of this :)15:45
YorikSarajo: Since it's in 2.6, it might be svn-blame :)15:46
ajo:)15:46
*** david-lyle has quit IRC15:46
YorikSarI'll ask on python-dev15:46
ajoYorikSar, I'll do it if you want15:46
ajoI was writting an #action line15:47
ajoto provide some help :)15:47
YorikSarOh, no. It's not for python-dev, but for python@, I guess.15:47
YorikSarajo: I'll do it myself. I want to get to the bottom of it :)15:48
carl_baldwin#action carl_baldwin will finish review of root wrap daemon patches.15:48
ajo#action ajo ask in python-dev / python@ mail list about the undocumented 'serializer' parameter of multiprocessing.BaseManager object15:48
ajoahh :D15:48
ajo':D15:48
ajo#action YorikSar ask in python-dev / python@ mail list about the undocumented 'serializer' parameter of multiprocessing.BaseManager object15:49
ajo#action ajo finish review on neutron-side root wrap daemon patches15:49
carl_baldwinGood progress.  Anything else?15:49
YorikSarNope15:50
carl_baldwin#topic General Discussion15:51
*** openstack changes topic to "General Discussion (Meeting topic: neutron_l3)"15:51
YorikSarOn, maybe I have a question about rootwrap.15:51
YorikSarDo you think it worth creating a blueprint?15:51
carl_baldwinI think so.15:52
YorikSarI guess, on for oslo and one for Neutron (and one for each of Nova and Cinder later)15:52
ajoYorikSar, yes, probably, you just need a link to your etherpad.15:52
*** troytoman-away is now known as troytoman15:52
YorikSarOk, will do15:52
ajoI was listening to some concerns, minutes ago, about the qrouter- namespace memory usage (due to neutron-ns-metadata-proxy)15:52
carl_baldwinYeah, it shouldn't be too much work at this point.  Just formalizing the blueprint's existence and linking.15:52
ajowhat was the initial reason to use this + domain socket  ?15:53
carl_baldwinajo: I'm not sure I understand the question yet.15:54
ajothinking about it again... there isn't a decent way to route that via iptables to the neutron-metadata-server directly15:54
ajoWe use the neutron-ns-metadata-proxy in every qrouter namespace15:54
haleybajo: because that proxy doesn't have access to the management network15:54
ajo(or qdhcp, when isolated_metadata is enableD)15:54
YorikSarI think those proxies will be replaced with one process with one thread per ns later.15:54
ajohaleyb, right,15:55
ajoYorikSar, is it possible to setns  per thread?15:55
haleybi could not find a way to reduce it's memory footprint, it's all just based on what it imports15:55
YorikSarajo: Yes. setns works per-thread.15:55
ajohmm, that's interesting15:55
YorikSarajo: I didn't verify it with fork calls, so if we ever want to add this to rootwrap it'll require some investigation.15:56
ajoso we could just start a thread + setns for every tenant network we're serving15:56
carl_baldwinI imagine those threads must be OS level threads.15:56
YorikSarcarl_baldwin: Sure.15:56
*** xuhanp has quit IRC15:56
ajocarl_baldwin, sure,15:56
ajoalthough python GIL doesn't provide much benefit of os threads... in this case, memory benefit... could do the work15:56
YorikSarI guess we can even spawn thread, do setns(), create socket, pass it to main thread and let helper thread die.15:56
carl_baldwinjust clarifying.  :)15:57
ajobut then there's the problem of scaling15:57
YorikSarajo: Ah.. Those prejudices again...15:57
ajoif we don't get real threading speedup, and just memory speedup15:58
ajowe could end up being a bottleneck here15:58
ajomemory speedup -> memory usage reduction15:58
ajocan be ok if we fork once per "N" threads15:59
YorikSarI don't think there will be any measurable difference between thread per socket and greenthread per socket.15:59
YorikSarSince threads sleep on I/O anyway and GIL won't be held by them.15:59
carl_baldwinYorikSar: Can it still listen and accept connections on the address inside the ns if the worker thread dies?15:59
YorikSarcarl_baldwin: I don't know. It should. Need more research here :)16:00
ajoI suppose it can't but just guessing16:00
YorikSarcarl_baldwin: I guess I will be able to get to this task during J cycle16:00
ajomay be we should start the performance subteam ;)16:01
carl_baldwinWe can discuss more on IRC, ML, or later meetings.  For now, we're out of time.16:01
YorikSarsure16:01
ajosure, thanks carl_baldwin , YorikSar , *16:01
carl_baldwinGreat meeting.  Thanks everyone.16:01
carl_baldwin#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
openstackMeeting ended Thu Mar 27 16:01:53 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-27-15.01.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-27-15.01.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-27-15.01.log.html16:01
*** eghobo has joined #openstack-meeting-316:03
*** amuller has left #openstack-meeting-316:03
*** Swami_ has left #openstack-meeting-316:03
*** YorikSar has left #openstack-meeting-316:03
*** SridarK has quit IRC16:03
*** SumitNaiksatam has joined #openstack-meeting-316:04
*** carl_baldwin has left #openstack-meeting-316:14
*** carl_baldwin has joined #openstack-meeting-316:14
*** carl_baldwin has left #openstack-meeting-316:14
*** troytoman-away has joined #openstack-meeting-316:21
*** zigo has quit IRC16:41
*** nacim has quit IRC16:48
*** nacim has joined #openstack-meeting-316:48
*** wchrisj has joined #openstack-meeting-316:52
*** SumitNaiksatam has quit IRC17:00
*** dguitarbite has joined #openstack-meeting-317:01
*** hao has quit IRC17:01
*** mfer has quit IRC17:05
*** enykeev has quit IRC17:06
*** enykeev has joined #openstack-meeting-317:10
*** enykeev has joined #openstack-meeting-317:10
*** alexpilotti_ has joined #openstack-meeting-317:12
*** nextone92 has quit IRC17:13
*** alexpilotti has quit IRC17:15
*** alexpilotti_ is now known as alexpilotti17:15
*** SumitNaiksatam has joined #openstack-meeting-317:25
*** rockyg has joined #openstack-meeting-317:27
*** HenryG_ has joined #openstack-meeting-317:28
*** david_lyle_ is now known as david_lyle17:31
*** banix has quit IRC17:34
*** HenryG has quit IRC17:37
*** MaxV has quit IRC17:38
*** zigo has joined #openstack-meeting-317:39
*** mwagner_ has quit IRC17:44
*** banix has joined #openstack-meeting-317:44
*** mfer has joined #openstack-meeting-317:47
*** nacim has quit IRC17:48
*** hao has joined #openstack-meeting-318:02
*** jpomero has joined #openstack-meeting-318:04
*** thinrichs_ has joined #openstack-meeting-318:07
*** hao has quit IRC18:07
*** rockyg has quit IRC18:07
*** jpomero has quit IRC18:10
*** thinrichs_ has quit IRC18:11
*** jpomero has joined #openstack-meeting-318:17
*** johnthetubaguy has quit IRC18:19
*** mfer has quit IRC18:47
*** ttrifonov_zZzz is now known as ttrifonov18:59
*** mfer has joined #openstack-meeting-319:00
*** hao has joined #openstack-meeting-319:03
*** lcheng has joined #openstack-meeting-319:04
*** hao has quit IRC19:08
*** mfer has quit IRC19:10
*** jpomero has quit IRC19:17
*** amotoki has quit IRC19:19
*** vkozhukalov has joined #openstack-meeting-319:31
*** jcoufal has quit IRC19:38
*** zehicle has joined #openstack-meeting-319:39
*** jcoufal has joined #openstack-meeting-319:39
*** troytoman-away is now known as troytoman_19:48
*** dguitarbite has quit IRC19:56
*** lblanchard has quit IRC20:00
*** HenryG_ has quit IRC20:03
*** HenryG has joined #openstack-meeting-320:03
*** hao has joined #openstack-meeting-320:04
*** hao has quit IRC20:09
*** HenryG has quit IRC20:10
*** julim has quit IRC20:29
*** waiman has joined #openstack-meeting-320:51
*** catherineD has joined #openstack-meeting-320:52
*** rockyg has joined #openstack-meeting-320:53
*** rockyg has quit IRC20:56
*** rockyg has joined #openstack-meeting-320:56
*** vkozhukalov has quit IRC20:59
rockyg#startmeeting refstack21:02
openstackMeeting started Thu Mar 27 21:02:22 2014 UTC and is due to finish in 60 minutes.  The chair is rockyg. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: refstack)"21:02
openstackThe meeting name has been set to 'refstack'21:02
rockygWho's here?21:02
davidlenwellI'm here21:02
davidlenwellagenda: code reviews, py26 gate, tomorrows f2f,  tcup methods21:03
rockygOpen discussion....21:03
rockygCatherineD?21:03
rockygWaiman?21:03
davidlenwellzehicle: ?21:03
waimano/21:03
catherineDHi Rocky,  I am here21:04
* zehicle running late21:04
davidlenwellalso on the agenda but we can push it to tomorrows f2f .. docs21:05
*** hao has joined #openstack-meeting-321:05
rockygOkay, since zehicle is running late, let's talk #topic py2621:05
*** tedchang has joined #openstack-meeting-321:05
rockyg#topic py2621:05
*** openstack changes topic to "py26 (Meeting topic: refstack)"21:05
davidlenwellokay .. so I'm planning to remove py26 from the gate all together21:05
*** fcarpenter has joined #openstack-meeting-321:05
rockygWhat do we need to do to get it working?21:05
davidlenwella lot21:06
ajoproject stats for lot, 90 days21:06
davidlenwellrockyg: so far nobody has expressed interest in running our code in a py26 env .. and a lot of our code does things that didn't exist in py2621:06
davidlenwellplus .. for those who want centos and rehl .. they can still run py2721:07
rockygBut, tthe first pass is for Havana.  and I though RHEL was py2.6?21:07
rockygAh.21:07
davidlenwellrockyg: so it doesn't matter what env we are testing .. it matters what the test is running from21:07
rockygMaybe we get a redhat contributor to help/work on 2.6?21:08
davidlenwellthe thing running refstack.org right now needs to be py.27 or py321:08
davidlenwellrockyg: maybe .. but right now having py2.6 in the gate slows down our merges21:08
davidlenwellpy 26 is old .. we're hanging on to the past21:08
rockygTrue.21:08
rockygWith time being precious, let's deal with 2.6 after we have working 2.721:09
davidlenwellSo unless we have any objection I am going to remove py26 from the gate21:09
zehicleo/21:09
davidlenwellrockyg: im not sure I'll ever care about py26 . but we can bring it back into discussion at a later time21:09
rockygI don't think we want to gate on py3 yet, either.21:09
*** hao has quit IRC21:09
davidlenwellrockyg: I don't agree with you there21:10
davidlenwellesp since we pass py33 tests now21:10
rockyghow about we vote to not bother with 2.6 until someone shows a need for it?21:10
*** mwagner_lap is now known as mwagner_bbl21:11
davidlenwellI vote we vote on it later21:11
davidlenwelland put it out of our heads21:11
rockyg#action table 2.6 discussion for sometime in the future, by request21:11
davidlenwellthank you21:11
davidlenwellnext topic .. code reviews21:11
rockygNow that zehicle is here, let's go back to reviews21:12
rockyg#topic code reviews21:12
*** openstack changes topic to "code reviews (Meeting topic: refstack)"21:12
davidlenwellSo several things got merged today including teds change for discovery of config options21:12
davidlenwellI made some minor dock changes..21:12
davidlenwellzehicle has a few reviews that need some work21:13
zehicleI've got the pep8 fixes in21:13
davidlenwellzehicle: I don't see the review yet21:13
zehiclecannot upload from the office.... in a hour or so21:14
davidlenwellit doesn't exist until there is a review ;)21:14
davidlenwellI've been working on https://review.openstack.org/#/c/81402/ .. will push it later today21:14
rockyg#link https://review.openstack.org/#/c/81402/21:15
davidlenwellI think that covers the open reviews for now unless anyone else has anything?21:15
rockygI've got similar network issues... can be on corporate network and get emails, or on guest net and get work done.21:15
*** mwagner_bbl has quit IRC21:16
rockygAnything major besides zehicle's stuff still out there?21:16
zehicleI will need some support on the last step of TCUP21:16
zehiclebecause the execute test is not working for me yet21:16
davidlenwellzehicle: I can make time for you this afternoon21:16
zehiclethanks21:16
davidlenwellrockyg: I merged all the other open reviews today .. I think we're abandoning joshua's reviews from last week in favor of zehicle21:16
rockygDo we want to do tcup next or f2f?21:16
zehiclehave you been able to try the stuff to prep the environment?21:16
davidlenwellI was pushing tcup for last because it could drag on21:17
davidlenwellzehicle: yes .. I have21:17
zehicle+121:17
rockygI passed CatherineD's instructions on to our infra guy.  Haven't heard back from him yet weher he could make it work.21:18
davidlenwellrockyg: all of that will simplify21:18
davidlenwellwe'll work out the details tomorro w21:18
rockygThought it would, but wanted to get him started.21:18
rockygSo, on to f2f?21:18
davidlenwellsure21:19
rockyg#topic F2F21:19
*** openstack changes topic to "F2F (Meeting topic: refstack)"21:19
davidlenwellso I have the room booked from 1-3:3021:19
fcarpenter(And that 3:30 is a hard stop)21:20
rockygI'm working on getting sphinx to generate docs.  Some of it is working.21:20
*** ttrifonov is now known as ttrifonov_zZzz21:20
*** mfer has joined #openstack-meeting-321:20
davidlenwellthe agenda for the f2f is mostly centered around our docs21:21
catherineDIs the f2f strictly for doc? Have room for code discussion?21:21
rockygWe'll do handoff of davidlenwell's verbiage and drawings tomorrow.  and yes, code is also happening tomorrow.21:21
davidlenwellyeah.. we'll cover both ..21:21
davidlenwellbut my primary objective is to make sense of our docs .21:22
davidlenwellwe can have some stuff happening in parallel21:22
rockygDo you have a drwing/graphics package to recommend I have preloaded?21:22
davidlenwellI use a cloud based one21:22
davidlenwellgliffy21:23
rockygI've used that before, but it was part of Confluence.21:23
rockygI'll check it out after this meeting.21:23
davidlenwellsure ..21:23
davidlenwellokay.. so on to tcup..21:24
rockygSo, code and docs tomorrow.  Plus the Defcore meeting.21:24
rockyg#topic tcup21:24
*** openstack changes topic to "tcup (Meeting topic: refstack)"21:24
davidlenwellwait .. when is the defcore meeting ?21:24
rockygzehicle?21:24
rockygMaybe it's today?21:24
* zehicle checking21:24
zehicle#link https://etherpad.openstack.org/p/DefCoreElephant.721:25
zehicleIt's on 4/1 at 2pm21:25
rockygAh.  Not today *or* tomorrow.  Good.21:26
davidlenwellthis is good21:26
davidlenwellits monday21:26
zehicleoh, there is something tomorrow too21:26
zehiclean Interlock w/ the TC21:26
fcarpentermonday == tuesday21:26
rockygOh, right.  I knew there was something.21:26
zehicle#link https://etherpad.openstack.org/p/openstack-designated-sections21:26
zehicleFriday 3/28 @ 8pm UTC21:26
rockyg'which is 1pm PDT21:27
*** jcoufal has quit IRC21:27
zehicleyes21:27
davidlenwellso we'll be here at piston durring that21:27
rockygSo, first hour tomorrow we'll be at least listening in while working21:27
zehicleit's all about designated sections21:28
rockygOK, that' means we should be on time.21:28
davidlenwelldoes that immidiately effect us .. because we do have limited time21:28
zehicleso, it's not likely to hit RefStack stuff just yet21:28
davidlenwellas fcarpenter said the 330 end is a hard stop21:28
davidlenwellwe'll be kicked out of that room and will have to go to the local bar to keep talking21:29
* zehicle buying tx to join in RefStack happy hour21:29
rockygWhich is your favorite work bar?21:29
rockygback to tcup.21:30
davidlenwellrockyg: as I am new here I don't have one yet ..21:30
davidlenwellyes .. so we've had some discussion in the past about what is the right way to run things in docker21:30
rockygThirsty Bear is a bit far, but really good;-)21:30
davidlenwellzehicle: do you want to state your position21:30
zehicleso, I've been working to make TCUP into something that runs RefStack21:31
zehiclebasically, it puts all of into a container and then kicks off the test21:31
zehicleso it should be the same to use it from the dev setup, production infratructure or TCUP21:31
zehiclethat makes it really really light for people to use21:32
zehiclebasicially, it's just run one py file21:32
zehicleand it gets the container and runs the tests inside it21:32
davidlenwellI also want to discuss the generating the docker file from a template vs env variables21:32
rockygI like the template idea.21:33
zehiclethe template approach is a non-starter for me21:33
davidlenwellrockyg: there is a reason it won't work21:33
zehicleI have some issues with it21:33
davidlenwellzehicle: can you spell those out please21:33
zehicle1st, it makes the code more complex for generating it21:33
zehicle2nd, it means that the container is unique each time instead of standard21:33
davidlenwell#2 is actually what I am hung up on21:33
zehicle#2 is my biggest issue21:33
catherineDNo the container is not unique for each run21:34
zehicleIMHO, the goal is that we have a standard environement that everyone uses21:34
zehicleand we pass in the unique stuff as env variables21:34
zehiclevery easy to repeat and troubleshoot21:34
zehicleif we have custom templates then it's hard to troubleshoot21:34
zehicleand we can't upload the standard template for everyone to use in a single shot21:35
davidlenwellso it sounds to me like maybe we have a slight communication problem about what the template is used for and wather or not it caches or makes every container unuiqe21:35
rockygQuestion:  lots of people are expressing a desire to "run [api|acceptance|custom|etc] tests against their cloud"  Mostly ops guys.  How does this play in the two options?21:35
catherineDif you look at the way we build the container, we push the most stable variables up front.  This will allow docker to cache .. and at the same time will rebuild image when it detected  changes ..21:35
zehiclethe tcup script I've been working on does exactly that - you put in the differents as environement variables21:36
catherineDI can send out the log files after the meeting you will see the evident of caching21:36
davidlenwellcatherineD: please do ..21:37
davidlenwellthat said ..21:37
catherineDEvironment variables only work in the case of local docker container .... we plan for it to work with gearman remotely21:37
catherineDwill send dthe logs ...21:37
davidlenwellcatherineD: the gearman remote thing won't use docker at all21:37
davidlenwellit will run the scripts that docker runs21:37
zehicle+121:38
davidlenwelldoesn't need docker21:38
zehiclethe scripts should work anywhere21:38
davidlenwelland refstack.org CANNOT have docker as a dependancy21:38
zehicleI'm trying to keep the docker stuff as a wrapper, not an internal dependency21:38
catherineDThe scripts will work anywhere but will paring with RefStack21:38
davidlenwell+121:38
davidlenwellso for remote execution from the gui.. refstack should be able to be configured to use docker .. but in those instances I think that running them locally will be fine21:39
davidlenwellenv variables are a more secure way of passing in creds .. and also keeps the container more of a container and less of a one off gererated thing for this one test21:40
davidlenwellthen docker doesn't have to genreate anything at all and all of it is cached21:40
zehicle+121:40
catherineD+1 for security ..21:40
davidlenwelland rockyg as far as ops people using it to run there own tests .. nobody is stopping them from modifying things in the tcup thing for their own build21:40
zehicleI've been pretty happy w/ using env variables for this21:40
zehicle(it was not my original approach)21:41
*** lcheng has quit IRC21:41
catherineDone of the improvement that we will be doing is to improve security now that the code are merged21:41
waimanhow about passing in as arg?  the current execute_test.py takes them as command line arg.21:41
davidlenwellso catherineD I'd like to see us transition from the template generated docker into one that uses env variables21:41
zehicleeffectively, the env variables ARE passed as args21:41
davidlenwellwaiman: ^^ that21:41
zehiclethe code sets them when the container is started21:41
catherineDwe need to discuss  who will set the ENV21:41
davidlenwellso the thing that calls the script from the command line can just pass them in21:42
davidlenwellcatherineD: we can whiteboard tomorrow if that will help21:42
catherineDWhen you actually run the tests you will realized that some on need to pass in variables ...21:42
zehiclemy code (and Josh's code) both build a set of input parameters to the container that set the env variables needed to run thetests21:42
catherineDyes let's discuss stomorrow21:42
rockygWhiteboard sounds good.21:42
davidlenwellokay then .. I think we can move to open discussion21:43
rockyg#topic Open Discussion21:43
*** openstack changes topic to "Open Discussion (Meeting topic: refstack)"21:43
zehicleoh, one minor note: Docker 0.8 has a bug that makes the Dockerbuild files return EOF21:43
zehicleI had to upgrade to 0.9.121:44
davidlenwellzehicle: thats one reason I was so hesitant to use docker at all21:44
zehiclejust so you don't have to repeat my learning exprience21:44
davidlenwellits in a super early alpha stage21:44
davidlenwellriddled with bugs and a moving target21:44
zehicleI understand the concern21:44
davidlenwellthats why I will continue to support the need for it .. but refstack.org won't be dependant on it21:44
davidlenwelland in our docs we have to be clear that it is just one of many options21:45
rockygwhat would be an alternative for the remote runs?21:45
davidlenwella vm running the py scripts that run the tests and clean up afterwards .. probably triggered from gearman21:45
davidlenwellrockyg:  its essentially the same thing .. just not in a throw away container21:46
davidlenwellmy goals are to make us hostable by infra long term21:46
rockygI figured everything but the gearman part.  Would gearman be a requirement, though?21:46
davidlenwellthey aren't going to play with docker21:46
davidlenwellgearman would be a requirement if you chose that option .. just like docker would be if you wanted to use that21:46
davidlenwellgearman is also a lot more mature and in heavy use by the infra team now21:47
rockygOK.  I'll need to document options for remote execution.  In case others don't want to use docker.21:47
zehiclerealistically, we should also be able to clone and run the code too!21:47
davidlenwellso refstack.org will use gearman to queue tests21:47
davidlenwellthats what local tests are for21:48
rockygQuestion on tests:  are we cloning them fro the Havana branch?21:48
davidlenwellso far the three options for triggering tests are : local, tcup, and remote (gearman)21:48
davidlenwellrockyg:  we abslutely should be21:48
davidlenwelldamnit my spelling .. absolutely21:49
waimandavidlenwell: 3 options from refstack web ui, right?21:49
davidlenwellwaiman: yes21:49
rockygI think we need a way to advertise the branch the tests are cloned from in the test log and the UI.21:49
davidlenwell3 options for the refstack ui21:50
davidlenwellrockyg: file a blueprint21:50
rockygWill do.21:50
zehicleis the documentation for running the UI up to date?21:50
davidlenwellwe are selecting the version at the time of making the tests21:50
waimandavidlenwell:  i have one related to that21:50
davidlenwellthats right .. you ahve one for displaying the results21:51
waimanwe talk about allowing users to pick version. each version will be mapped to a tempest url.21:51
davidlenwellit should say what version .. so rockyg just add to the whiteboard of the existing blueprint21:51
rockygOK.21:51
davidlenwellwe also talked about allowing them to specify a url of a specific tempest branch they want to run21:51
waiman#link https://blueprints.launchpad.net/refstack/+spec/support-different-tempest-versions21:52
*** Praveen-dell has joined #openstack-meeting-321:52
waimandavidlenwell:  yes. i am working on this.21:52
davidlenwellexcelent21:52
davidlenwellokay .. I think we all have lots of things to do .. lets all this meeting ajourned21:53
rockygI think my homework before tomorrow is to review all the BPs.21:53
Praveen-dellHi,this is praveen from Dell,Ireland,working for Rob on Refstack project21:53
davidlenwellrockyg: good plan21:53
*** lcheng has joined #openstack-meeting-321:53
rockygCall to end...21:53
davidlenwellhi Praveen-dell21:53
Praveen-dellHi David21:53
zehiclePraveen-dell is from my team here21:53
zehicleHe's time zone disadvantaged (in the UK)21:53
rockygAre you in Ireland?21:53
davidlenwellPraveen-dell: we're just wrapping up here .. wanna jump over to #refstack and introduce your self21:53
Praveen-dellsure21:54
Praveen-dellwill do21:54
Praveen-dellthanks21:54
rockygOK, then time to move back to our "home"21:54
zehiclecan we have a short topic about potentially changing time?21:54
rockygHere?  Now?21:54
rockyg#topic meeting time21:54
*** openstack changes topic to "meeting time (Meeting topic: refstack)"21:54
davidlenwellzehicle: what time did you want to change to  ?21:54
zehicleif we're going to change it for next week21:54
davidlenwellthursdays at 2 was your idea21:54
davidlenwellI'm fine with keeping it how it is21:55
zehicletrue, did not have anyone from Europe at the time21:55
davidlenwellahh21:55
davidlenwellhow much time is Praveen-dell going to have for refstack ?21:55
rockygYeah.  It's likely at least midnight start for Praveen21:55
Praveen-dellGMT 5pm or 6pm should be fine for me21:55
rockygSo, 11am or noon PDT21:56
davidlenwellso I'd like to keep meetings as static as we can .. if we keep moving it we're just going to loose poeple .21:56
zehicle+121:57
rockygSorry.  10am or 11am21:57
davidlenwell10am is fine for me21:57
davidlenwell11 is a nogo21:57
rockyg10am works for me.21:57
davidlenwellany objections to changing the meeting time to 10am pst on thursdays?21:57
rockygthat's pDt21:58
zehicleI can make that work21:58
davidlenwellwhats the diff between pdt and pst ?21:58
catherineDgood for us21:58
*** eguz has joined #openstack-meeting-321:58
rockygStandard vs Daylight savings21:58
zehicleI'd like to agree that we'll follow daylight time21:58
zehiclesorry, follow the changes21:58
davidlenwellI'm good with it .. zehicle wanna change the meeting time on the wiki thing ?21:59
zehicle+1 will do21:59
zehiclethanks21:59
zehicleThursdays @ 10 am Pacific21:59
rockygyes, thanks.21:59
Praveen-dellthanks for the time change21:59
zehiclelikely to stay on this channel21:59
davidlenwelljust update the email list21:59
rockygYeah.  I know QA alternates between this time and the new time on the meeting channel.22:00
rockygTime!22:00
rockyglast call.22:00
rockyg#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"22:01
openstackMeeting ended Thu Mar 27 22:01:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-03-27-21.02.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-03-27-21.02.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-03-27-21.02.log.html22:01
waimannow our previous reviews have been merged, i can now continue to commit my new code on top...22:01
rockygPraveen_dell, the team channel is #refstack22:02
*** eguz has quit IRC22:02
Praveen-delljoining now22:03
rockygPraveen-dell, the team channel is #refstack22:03
*** eghobo has quit IRC22:03
*** Praveen-dell has quit IRC22:03
*** eghobo has joined #openstack-meeting-322:03
*** lcheng has quit IRC22:03
*** hao has joined #openstack-meeting-322:05
*** yamahata has quit IRC22:06
*** mfer has quit IRC22:08
*** hao has quit IRC22:09
*** fcarpenter has left #openstack-meeting-322:09
*** lcheng has joined #openstack-meeting-322:18
*** alexpilotti_ has joined #openstack-meeting-322:20
*** peristeri has joined #openstack-meeting-322:22
*** alexpilotti has quit IRC22:22
*** alexpilotti_ is now known as alexpilotti22:22
*** rockyg has quit IRC22:24
*** lcheng has quit IRC22:28
*** zehicle has quit IRC22:29
*** lcheng has joined #openstack-meeting-322:36
*** jtomasek has quit IRC22:37
*** MaxV has joined #openstack-meeting-322:41
*** banix has quit IRC22:43
*** mwagner_bbl has joined #openstack-meeting-322:48
*** MaxV has quit IRC22:59
*** hao has joined #openstack-meeting-323:06
*** hao has quit IRC23:07
*** hao has joined #openstack-meeting-323:07
*** hao has quit IRC23:09
*** hao has joined #openstack-meeting-323:09
*** markmcclain has quit IRC23:14
*** hao has quit IRC23:14
*** eghobo has quit IRC23:15
*** alexpilotti has quit IRC23:18
*** david_lyle has quit IRC23:19
*** gduan has quit IRC23:32
*** garyduan has joined #openstack-meeting-323:33
*** Sukhdev has joined #openstack-meeting-323:39
*** lcheng has quit IRC23:40
*** lcheng has joined #openstack-meeting-323:40
*** mestery has quit IRC23:53
*** lcheng has quit IRC23:55
*** cgoncalves has quit IRC23:56
*** lcheng has joined #openstack-meeting-323:57
*** cgoncalves has joined #openstack-meeting-323:57

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