Thursday, 2014-03-20

*** MaxV has quit IRC00:01
*** julim has quit IRC00:03
*** eguz has quit IRC00:05
*** eghobo has joined #openstack-meeting-300:05
*** julim has joined #openstack-meeting-300:05
*** eghobo has quit IRC00:10
*** eghobo has joined #openstack-meeting-300:10
*** MaxV has joined #openstack-meeting-300:33
*** dguitarbite_ has quit IRC00:38
*** dguitarbite has joined #openstack-meeting-300:40
*** devlaps has quit IRC00:47
*** yamahata has joined #openstack-meeting-300:48
*** MaxV has quit IRC00:53
*** eguz has joined #openstack-meeting-301:14
*** eghobo has quit IRC01:18
*** eguz has quit IRC01:19
*** alexpilotti_ has joined #openstack-meeting-301:28
*** alexpilotti has quit IRC01:30
*** alexpilotti_ is now known as alexpilotti01:30
*** jpomero has quit IRC01:33
*** SumitNaiksatam has quit IRC01:39
*** alexpilotti has quit IRC01:44
*** SumitNaiksatam has joined #openstack-meeting-302:22
*** banix has joined #openstack-meeting-302:33
*** mwagner__ is now known as mwagner__zzzz02:37
*** eghobo has joined #openstack-meeting-303:11
*** eghobo has quit IRC03:38
*** david-lyle has joined #openstack-meeting-303:50
*** banix has quit IRC04:12
*** saju_m has joined #openstack-meeting-304:12
*** carl_baldwin has joined #openstack-meeting-305:09
*** carl_baldwin has quit IRC05:17
*** amotoki has joined #openstack-meeting-305:29
*** lpetrut has joined #openstack-meeting-305:39
*** jtomasek has joined #openstack-meeting-305:40
*** eghobo has joined #openstack-meeting-305:44
*** saju_m has quit IRC06:02
*** jtomasek has quit IRC06:03
*** saju_m has joined #openstack-meeting-306:04
*** saju_m has quit IRC06:07
*** saju_m has joined #openstack-meeting-306:08
*** saju_m has quit IRC06:35
*** eghobo has quit IRC06:47
*** wchrisj has quit IRC06:54
*** jrist has joined #openstack-meeting-307:14
*** lpetrut has quit IRC07:22
*** MaxV has joined #openstack-meeting-307:24
*** ttrifonov_zZzz is now known as ttrifonov07:29
*** MaxV has quit IRC07:33
*** saju_m has joined #openstack-meeting-307:56
*** lpetrut has joined #openstack-meeting-307:57
*** jtomasek has joined #openstack-meeting-308:08
*** jcoufal has joined #openstack-meeting-308:19
*** johnthetubaguy has joined #openstack-meeting-308:27
*** SumitNaiksatam has quit IRC08:35
*** lpetrut has quit IRC08:40
*** MaxV has joined #openstack-meeting-308:50
*** nacim has joined #openstack-meeting-308:52
*** dguitarbite has quit IRC09:04
*** ttrifonov is now known as ttrifonov_zZzz09:17
*** safchain has joined #openstack-meeting-309:27
*** safchain has quit IRC09:37
*** lpetrut has joined #openstack-meeting-309:46
*** safchain has joined #openstack-meeting-309:50
*** SumitNaiksatam has joined #openstack-meeting-309:53
*** yamahata has quit IRC10:02
*** jcoufal has quit IRC10:06
*** safchain has quit IRC10:18
*** safchain has joined #openstack-meeting-310:20
*** yamahata has joined #openstack-meeting-310:53
*** MaxV has quit IRC11:02
*** MaxV has joined #openstack-meeting-311:02
*** jtomasek has quit IRC11:15
*** jtomasek has joined #openstack-meeting-311:16
*** markmcclain has joined #openstack-meeting-311:35
*** markmcclain1 has joined #openstack-meeting-311:35
*** markmcclain1 has quit IRC11:35
*** markmcclain1 has joined #openstack-meeting-311:36
*** alexpilotti has joined #openstack-meeting-311:37
*** markmcclain1 has quit IRC11:37
*** lpetrut has quit IRC11:39
*** markmcclain has quit IRC11:39
*** markmcclain has joined #openstack-meeting-311:41
*** safchain_ has joined #openstack-meeting-311:42
*** safchain has quit IRC11:42
*** MaxV has quit IRC11:49
*** david-lyle has quit IRC11:52
*** banix has joined #openstack-meeting-311:59
*** lblanchard has joined #openstack-meeting-312:02
*** MaxV has joined #openstack-meeting-312:05
*** saju_m has quit IRC12:09
*** saju_m has joined #openstack-meeting-312:27
*** banix has quit IRC12:31
*** xuhanp has joined #openstack-meeting-312:35
*** saju_m has quit IRC12:53
*** mwagner__zzzz is now known as mwagner_13:04
*** jrist has quit IRC13:06
*** saju_m has joined #openstack-meeting-313:07
*** jrist has joined #openstack-meeting-313:08
*** lpetrut has joined #openstack-meeting-313:13
*** jthopkin has joined #openstack-meeting-313:21
*** saju_m has quit IRC13:23
*** MaxV has quit IRC13:31
*** peristeri has joined #openstack-meeting-313:33
*** saju_m has joined #openstack-meeting-313:39
*** wchrisj has joined #openstack-meeting-313:43
*** jtomasek has quit IRC13:47
*** yamahata has quit IRC13:48
*** saju_m has quit IRC13:48
*** jtomasek has joined #openstack-meeting-313:48
*** yamahata has joined #openstack-meeting-313:49
*** jcorbin has joined #openstack-meeting-313:51
*** ajo has joined #openstack-meeting-314:02
*** MaxV has joined #openstack-meeting-314:08
*** mfer has joined #openstack-meeting-314:11
*** jcoufal has joined #openstack-meeting-314:16
jcorbin:q14:17
*** jthopkin has quit IRC14:29
*** jcorbin has left #openstack-meeting-314:35
*** jthopkin has joined #openstack-meeting-314:38
*** devvesa has joined #openstack-meeting-314:45
*** ttrifonov_zZzz is now known as ttrifonov14:52
*** carl_baldwin has joined #openstack-meeting-314:52
*** mestery has joined #openstack-meeting-314:54
*** mwagner is now known as mwagner_notHere14:55
*** Swami has joined #openstack-meeting-314:56
ajohi Swami , carl_baldwin , safchain_  :)14:56
Swamiajo: hi14:56
ajowhat was Yuriy nick? :)14:57
safchain_ajo, Swami, carl_baldwin Hi all14:57
Swamisafchain: hi14:57
Swamicarl: hi14:57
*** jthopkin has left #openstack-meeting-314:57
carl_baldwinHi all.  Where did this last week go?14:57
ajoI don't know :)14:57
ajoTime passes very fast ;)14:57
carl_baldwinI guess I know where it went for me.  I was dragged in to operations and I was under the weather a bit.14:58
Swamiwhen we have too many work, we don't feel the week fly by14:59
carl_baldwin#startmeeting neutron_l315:00
openstackMeeting started Thu Mar 20 15:00:48 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:00
openstackThe meeting name has been set to 'neutron_l3'15:00
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwinI never came to a decision about a meeting time change.15:01
carl_baldwinajo: You said that an hour earlier would be better but would two hours later be bad?15:01
Swamicarl: I too feel the same, because of the time change it just affects our regular schedule, childrens school time.15:02
ajocarl_baldwin, hmm, yes for me, two hours later I have another fixed meeting :(15:02
ajoI mean, yes, it would be bad for me15:02
carl_baldwinSwami: which time would you prefer?15:03
ajo-1h, or +0h works for me, other option would be +3h15:03
xuhanpcarl_baldwin, two hour later will be too late for Asia folks :-(15:03
safchain_2 hours later bad for me too15:03
ajoxuhanp, you're right15:03
Swamiprobably 1 hour earlier would be better.15:03
carl_baldwinIt sounds like the current time is the best.15:04
*** rook has joined #openstack-meeting-315:04
Swaminever mind, its ok,15:04
carl_baldwinOh, maybe 1 hour earlier would be better.15:04
*** amuller has joined #openstack-meeting-315:04
ajohi rook & amuller15:04
amullerajo: heya15:04
rookajo hi15:04
ajowe were talking about this meeting time15:04
*** YorikSar has joined #openstack-meeting-315:05
ajomay be changing -1h, staying, or +1h15:05
*** nextone92 has joined #openstack-meeting-315:05
amullerok, no preference here15:05
rooksame15:05
carl_baldwinWell let's take a vote between an hour earlier and keeping the same time.15:05
ajothere was +2h too, but that's bad for asia, and collides with our weekly team meeting :)15:05
*** mwagner_ has quit IRC15:06
carl_baldwinKeep in mind that the next daylight savings time shift will shift it yet another hour earlier.15:06
carl_baldwin+2 hours I think is out.15:06
SwamiSame time slot will work. +115:07
safchain_+1 for the same time15:07
ajowhat's the meeting time reference? UTC/GMT ?15:07
ajo+1 for the same time (considering day light saving time changes..)15:07
carl_baldwinCurrent meeting time is 1500 UTC with no regard for DST.15:08
xuhanp+1 to same time or -1 hour :-)15:08
ajowell, sorry, changing my vote for: +1 same time or -1 hour15:08
carl_baldwinThanks.  I'll see what I can do to keep the same time.15:09
ajoThanks carl15:09
carl_baldwin#topic l3-high-availability15:09
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:09
carl_baldwinsafchain_: Any update since last week?15:10
safchain_Not really, I have to rebase all my patches to update db migration version15:10
safchain_I also submitted a patch to show how the conntrackd patch could be used15:10
safchain_I'm working on a patch to send a notification to the neutron server when a master is elected15:11
carl_baldwinHas anyone had the chance to run through the document about testing the patches?15:11
amullersafchain_: I've been meaning to talk to you - I think it would be more productive if you took over the conntrackd patch that I originally created... Fix it up according to your needs15:11
safchain_amuller, ok why not15:12
amullercool :)15:12
safchain_any suggestion about the notification about the vrrp status ?15:12
ajoamuller, safchain_ can you point to your current conntrackd patches ?15:12
safchain_https://review.openstack.org/#/c/80332/15:13
safchain_ajo ^15:13
amullerajo: https://review.openstack.org/#/c/71586/, https://review.openstack.org/#/c/80332/15:13
safchain_ajo, not working today since there are some few things to change in the conntrackd patch15:13
ajothanks amuller , safchain_15:14
carl_baldwinI'll have another look at the patches this week and begin going through your test document.15:14
carl_baldwinAnything else?15:15
safchain_thanks carl_baldwin15:15
Swamiamuller: you had a blueprint for the active /active solution, are you targeting that Juno15:15
SwamiWill it be merged with safchain_ vrrp solution.15:15
safchain_amuller, it could be a nice improvement15:15
SwamiOr will be patch that will go after the current vrrp solution15:15
*** banix has joined #openstack-meeting-315:15
amullerSwami: I'm not 100% on the value of it. I think with DVR, the VRRP stuff will only be used for SNAT traffic15:16
*** david-lyle has joined #openstack-meeting-315:16
Swamiamuller: yes you are right.15:16
carl_baldwinIf it could slow down the original patches then it should go in after.15:16
carl_baldwinscope creep and all  ;)15:17
amullercarl_baldwin: The original plan was to file a follow up blueprint, and add patches later15:17
Swamiamuller: Have you started the work.15:17
amullerSwami: No, I have an early draft for a blueprint, haven't touched it since15:17
amullerAssuming DVR is merged for Juno I am not 100% sure about the value of a VRRP optimization15:17
SwamiAs I mentioned in my previous discussions, we need to figure out for Juno how the VRRP solution will complement the DVR solution.15:18
Swamiamuller: thanks15:18
carl_baldwinamuller: We can discuss it at a later time.  There is also a possible bp for distributed SNAT or some other alternative to centralized SNAT.15:18
carl_baldwinSo, I agree the value of active / active should be in question.15:18
carl_baldwinLet's move on.15:19
amullercarl_baldwin: I am not keen on the details of DVR yet or why distributed SNAT is an issue, but that would be preferable15:19
carl_baldwin#topic neutron-ovs-dvr15:19
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:19
carl_baldwinSwami: hi15:19
SwamiHi carl15:19
ajoVRRP also has a value15:19
SwamiThe DVR team has posted the L2 and L3 documents for review.15:20
ajowhen there is a need to cut down the physical network nodes15:20
SwamiTeaming is trying to address the comments that come in.15:20
ajoor there are many physical networks15:20
Swamicarl: thanks for yur comments.15:20
ajosorry : when there's a need to cut down public/physical network connections15:21
SwamiWe are currently progressing on the East-West story.15:21
SwamiThe issue that we had with the East-west was with some rules, and we are now trying to sort it out with sylvain.15:21
SwamiBecause there was dup learning in the bridges.15:22
*** carl_baldwin has quit IRC15:22
*** carl_baldwin has joined #openstack-meeting-315:22
SwamiThat's all I have.15:22
SwamiSome of the sub team members requested for the WIP code, we are planning to post the WIP code when the East-west is completely working.15:22
carl_baldwinI got disconnected momentarily.  I'll go read the log to see if I missed anything.15:23
amullerVery cool15:23
carl_baldwinI'm anxious to look at the implementation, too.  :)15:23
SwamiIt should be there soon15:23
carl_baldwin#topic bgp-dynamic-routing15:23
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:23
carl_baldwinnextone92: Are you around?15:24
SwamiThat's all from my side15:24
nextone92Hi Carl!15:24
carl_baldwinSwami: thanks15:24
nextone92From the last discussion: made it more clear in the blueprint that primary use case is to exchange the routes for the whole OpenStack system15:24
nextone92And also added list of permitted users who can adjust bgp settings on the router15:25
carl_baldwinI'll have a look at your updates.15:25
nextone92I've looked at MPLS BGP blueprint: https://blueprints.launchpad.net/neutron/+spec/neutron-bgp-mpls-vpn15:25
nextone92Based on the available information, I think dynamic routing implementation should benefit VPN deployment that requires dynamic routing15:26
nextone92One question that I had, should the dynamic routing document primarily concentrate on dynamic routing? With bgp being the first available implementation?15:27
carl_baldwinI'll admit that I don't have much experience with dynamic routing outside of BGP.15:29
*** ttrifonov is now known as ttrifonov_zZzz15:29
Swaminextone92: Yes you are right, that should compliment the VPN15:29
carl_baldwinI guess to answer that question we would need to understand what other dynamic routing protocols are out there and find out what can be abstracted.15:29
amullerOSPF and ISIS stand out15:30
amulleropen, standardized15:30
ajoyes, an abstraction would be interesting, if we can gather the knowledge15:30
SwamiWith respect to protocols, we can start with one and then add others.15:30
*** ttrifonov_zZzz is now known as ttrifonov15:30
SwamiThe most used one and the immediate requirement would be the bgp.15:31
ajosounds good15:31
carl_baldwinSwami: That is the plan.  BPG will be the first implementation.  The question is how much can we abstract the interface so that it is applicable to others down the road.15:31
nextone92Okay, sounds good!15:32
nextone92What do you think about the idea of having a main virtual "provider" router to handle dynamic routing? This entity will exchange routing information but doesn't necessarily have to forward packets15:32
amullerLooking at the blueprint, I really don't understand what is the use case / what problem are we trying to solve15:32
carl_baldwinnextone92: I think the idea is good.  It coincides with what I was thinking.  My only problem with it is calling it a "router" since it doesn't route.15:32
nextone92carl_baldwin: let me think of a good alternate name15:33
SwamiBut if it is abstracted as a dynamic routing service, then can be used with any other variable..15:34
carl_baldwinamuller: A use case that I have in mind is to use dynamic routing to announce IPs on an external network.  There are some advantages to using routing over a flat L2 network.15:34
nextone92amuller: and another user case would be for external network to provide routing information to OpenStack15:35
amullerDoes this blueprint have a use outside of VPNaaS?15:35
nextone92amuller: this could be useful if you have multiple uplinks15:35
carl_baldwinnextone92: Maybe we call it the "main dynamic routing service" instead of a router.15:35
amullerI mean, current OpenStack virtual routers only have a single uplink so no routing is needed15:36
carl_baldwinamuller: Both use cases just mentioned are outside of VPNaaS.15:36
nextone92amuller: virtually there may have a single uplink, but it doesn't have to be a single uplink physically15:36
amullerok, then I don't understand "A use case that I have in mind is to use dynamic routing to announce IPs on an external network" - The end goal is for virtual routers to know how to route to certain IPs outside of the cloud?15:37
amullerSo virtual routers would be connected to multiple external networks?15:38
ajomultiple uplinks15:38
*** banix has quit IRC15:38
nextone92amuller: in the use case that carl has mentioned, when you add an external network and/or floating IPs, the routing information to that network will be announced to the uplink router(s)15:39
nextone92amuller: simplifying network administration15:39
*** jthopkin has joined #openstack-meeting-315:39
amullerahh, so you're talking about routers outside of the cloud to know how to route into the cloud, not the other way around15:39
carl_baldwinamuller: In current neutron, floating ips are all on a big flat L2 network.15:39
carl_baldwinamuller: Both are use cases that we have discussed.15:40
amullerI understand the 2nd one - Instead of configuring your cloud's physical edge router, and adding the external networks so they're advertised via BGP, the openstack virtual routers will automatically generate BGP advertisements whenever an external net is defined15:41
amullerBasically saving you a few lines of configuration on your physical routers15:42
nextone92amuller: great! Going in another direction, a system administrator may add a route to a segment of a corporate network on one of the uplinks15:42
nextone92amuller: or define a load balancing policy based on routes and their weights15:43
carl_baldwinamuller: We can do some work on the document to make the use cases more clear and discuss them individually after that.15:43
amullercarl_baldwin: That would be fantastic15:44
ajo+1 :)15:44
nextone92great!15:44
carl_baldwin#action carl_baldwin will take a crack at describing the use cases.15:44
amullercarl_baldwin: If you could state things explicitly (Such as virtual routers having more than one uplink / connected to more than a single external network at a time)15:44
amullercarl_baldwin: + Why the other direction is interesting as well (Virtual routers advertising their own external networks via a routing protocol)15:44
carl_baldwinI will try to be as clear as possible.15:45
carl_baldwin#topic DNS lookup of instances15:45
*** openstack changes topic to "DNS lookup of instances (Meeting topic: neutron_l3)"15:45
amullerI don't know how customers set up routing on their clouds atm - Do they have an IGP running, then redistributing out to BGP, or what...15:45
amullerThat would affect our choice of a routing protocol15:45
*** Rajeev has joined #openstack-meeting-315:46
carl_baldwinamuller: that is an open question.  Maybe we can do some discovery here.15:46
*** ttrifonov is now known as ttrifonov_zZzz15:46
carl_baldwinNo progress on DNS since my whole week was consumed with unplanned work.15:46
*** jnoller has joined #openstack-meeting-315:47
carl_baldwin#topic Agent Performance with Wrapper Overhead15:47
*** openstack changes topic to "Agent Performance with Wrapper Overhead (Meeting topic: neutron_l3)"15:47
carl_baldwin#link https://etherpad.openstack.org/p/neutron-agent-exec-performance15:47
ajoYuriy, are you around?15:48
carl_baldwinI made some progress on a change to L3 agent to make it more responsive to RPC.15:48
carl_baldwin#link https://review.openstack.org/#/c/7881915:48
YorikSarajo: o/15:48
carl_baldwinThe patch is still a WIP but pretty much works.  I could use some feedback.15:48
*** devlaps has joined #openstack-meeting-315:49
YorikSarI've pushed first version of rootwrap changes to make it run in agent mode.15:49
YorikSarI've also though of another speedup we can get dealing with namespaces (see ML and etherpad)15:49
carl_baldwinYorikSar: hi15:49
carl_baldwinDo you have a link?15:49
YorikSarhttps://review.openstack.org/8179815:49
ajo#link https://review.openstack.org/8179815:50
ajoYorikSar, your results look promising15:50
YorikSarIt shows good performance (~2x speedup compared to plain sudo, ~22x compared to rootwrap)15:50
*** jcoufal has quit IRC15:50
carl_baldwinGreat, I'll have a look.15:51
*** MaxV has quit IRC15:51
ajoYorikSar, yes, I thought about using setns too, instead of using the full blown ip netns exec15:51
YorikSarI think I can add some namespace-related stuff there. But I wonder if it should be done in Neutron itself, not in common rootwrap.15:51
ajono mounting or normal network env configuration, but it should do for many cases15:52
ajoand we cut out the overhead a lot15:52
YorikSarI didn't investigate if any command running in namespace actually needs conf files etc15:52
ajoYorikSar,  may be we could add some filter, to do setns15:52
ajosetns xxxxxxxxxxxx ip a15:52
YorikSarBut from what I see in filters it looks like only ip itself runs within ip netns15:53
ajoget's handled by the filter, which sets the namespace, and calls ip a15:53
carl_baldwinI'm not familiar with setns.15:53
ajoip netns exec does several things15:53
YorikSarajo: Hm... Sideeffects are bad...15:53
ajocalls "setns(xxxx) system calls...15:53
YorikSarajo: I think we can add an argument to that RPC call.15:54
ajoand mounts several files around to simulate a normal environment on /etc/ or other places for the child process15:54
carl_baldwinOh, I see.  I'm following you.15:54
YorikSarajo: And leave plain rootwrap ip setns exec slow.15:54
ajothe mounting itc.. it's very expensive in performance terms, and may processes probably would need the setns only15:54
ajoYorikSar,15:54
ajodo you think it would be possible to implement in neutron, with a switch to allow the old root_helper method , or the new daemon?15:55
ajothis would allow for a testing transition during icehouse, for example15:55
YorikSarajo: Yes, that's the next step I'm thinking about.15:56
ajowho's more worried about performance could enable the mechanism, and who's not, can relay on rootwrap, or even plain sudo15:56
ajoYorikSar,15:57
ajodid you read my concerns about "BaseManager"15:57
ajoI yet don't have the details, but it seems that other projects using a similar mechanism for the same purpose have hit race conditions & bugs on the BaseManager implementation15:57
YorikSarajo: Yes. I hope you'll be able to get what issues there was from your people.15:57
ajodo you think we could have some other alternatives if we hit those?15:57
YorikSarajo: We can backport any changes necessary.15:58
ajosure, I should get the information sure15:58
ajosure->soon15:58
YorikSarajo: In fact... I think we shouldn't hit races with running only one background process.15:58
*** devvesa has quit IRC15:58
ajoI have also built a POC on the py->C++ translation15:59
ajoit works with very little overhead, I was aiming a solution for havana/icehouse15:59
ajobut may be your solution will be soon enough, and backportable15:59
carl_baldwinajo: What have you found out about popen and logging?16:00
ajocarl_baldwin, was about to write on this,16:00
*** MaxV has joined #openstack-meeting-316:00
ajowe would need to implement those modules,16:00
ajoI suppose is doable, but I'm more concerned about the auditability of the code16:00
ajoeverything looks to me like dynamic, std::list<> ... etc...16:01
ajoand with bounds checkings everywhere16:01
*** Swami has quit IRC16:01
ajobut, of course, it's machine generated C, which is hard to read16:01
ajothe performance is good, did my message on performance arrived to the list?16:01
carl_baldwinI'm not sure.  I'm a little behind reading the list.16:02
carl_baldwinWith the need to hand-implement some modules, this looks less attractive but maybe we can keep it in our back pocket.16:02
ajo#link http://lists.openstack.org/pipermail/openstack-dev/2014-March/030561.html16:02
carl_baldwinI don't know if there is a meeting after this but I'm running out of time.16:03
ajoI must leave too,16:03
carl_baldwinajo: Have you written anything on the ether pad about setns?  I'd like to think about it some more.16:03
YorikSarajo: I think given my rootwrap daemon beats sudo itself, running C++ version of rootwrap will be behind anyway.16:03
*** xuhanp has quit IRC16:03
ajobut yes, I agree, it's a solution to keep in the back pocket16:03
*** eguz has joined #openstack-meeting-316:04
*** Rajeev has quit IRC16:04
ajoYorikSar, I agree, if the neutron side implementation gets working fast, and work reliably , we should not need for any C++16:04
YorikSarWhat's the deadline for such change?16:04
ajocarl_baldwin, sure I could try to expand the information on ip netns16:04
ajocarl_baldwin, man ip-netns explains the logic16:05
ajoon the first few lines16:05
*** carl_baldwin has quit IRC16:05
YorikSarI've added some info on setns to the etherpad16:05
ajoah, good YorikSar  :)16:05
*** jrist has quit IRC16:05
*** carl_baldwin has joined #openstack-meeting-316:05
carl_baldwinI got disconnected again.  :(16:05
YorikSarBut I didn't explain how netns exec works there.16:05
ajoYorikSar, I'd aim on having something that can work in icehouse.16:06
*** devvesa has joined #openstack-meeting-316:06
carl_baldwinWe may need to be content with potential back port to Icehouse.  But, we can always ask.16:07
ajoSure, if we keep backporting in mind, it should be ok16:07
YorikSarOh... According to schedule, we just a week away from RC...16:08
carl_baldwinThanks, all.  Have a great week.16:08
ajoYorikSar, I will spend some time tomorrow morning on review to your rootwrap daemon, it looks very good to me, so far, simple & effective16:08
carl_baldwinI will review as well.16:08
YorikSarajo: Thanks, I appreciate that.16:08
carl_baldwin#endmeeting16:08
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:08
openstackMeeting ended Thu Mar 20 16:08:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-20-15.00.html16:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-20-15.00.txt16:08
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-03-20-15.00.log.html16:08
*** carl_baldwin has quit IRC16:09
ajoYorikSar, and the benchmarking tool, is a good detail, so they can keep an eye on how implementation affects performance :)16:09
YorikSarajo: You can use it for your version, btw16:09
*** jtomasek has quit IRC16:10
ajoI'll better spend my time on testing your solution, providing review, and trying to help16:10
YorikSarajo: Thanks :)16:11
ajoif for any chance we don't find the final solution suitable for icehouse backport, then we can go back to it at any time... or rewrite a C thing...16:11
*** nextone92 has quit IRC16:11
ajoYorikSar, feel free to add me to any reviews related to this:   miguelangel@ajo.es16:11
*** carl_baldwin has joined #openstack-meeting-316:11
YorikSarajo: Ok, will do.16:12
*** carl_baldwin has quit IRC16:13
*** YorikSar has left #openstack-meeting-316:15
*** eguz has quit IRC16:15
*** eghobo has joined #openstack-meeting-316:16
*** eguz has joined #openstack-meeting-316:16
*** eguz has quit IRC16:16
*** eghobo has quit IRC16:17
*** eguz has joined #openstack-meeting-316:17
*** eghobo has joined #openstack-meeting-316:17
*** jnoller has quit IRC16:20
*** eguz has quit IRC16:21
*** SumitNaiksatam has quit IRC16:28
*** banix has joined #openstack-meeting-316:30
*** banix has quit IRC16:32
*** SumitNaiksatam has joined #openstack-meeting-316:43
*** amuller has left #openstack-meeting-316:46
*** eghobo has quit IRC16:51
*** carl_baldwin has joined #openstack-meeting-316:51
*** eghobo has joined #openstack-meeting-316:59
*** devvesa has quit IRC17:05
*** mwagner_ has joined #openstack-meeting-317:07
*** eguz has joined #openstack-meeting-317:08
*** eghobo has quit IRC17:11
*** eguz has quit IRC17:12
*** eghobo has joined #openstack-meeting-317:13
*** carl_baldwin has quit IRC17:14
*** carl_baldwin has joined #openstack-meeting-317:18
*** banix has joined #openstack-meeting-317:34
*** banix has quit IRC17:41
*** carl_baldwin has quit IRC17:45
*** troytoman-away is now known as troytoman17:46
*** banix has joined #openstack-meeting-317:47
*** tshirtman has quit IRC17:48
*** banix has quit IRC17:49
*** troytoman is now known as troytoman-away17:51
*** banix has joined #openstack-meeting-317:53
*** banix has quit IRC17:54
*** MaxV has quit IRC17:55
*** safchain_ has quit IRC17:55
*** troytoman-away is now known as troytoman18:00
*** OSM has joined #openstack-meeting-318:02
*** lpetrut has quit IRC18:04
*** nacim has quit IRC18:06
*** OSM has left #openstack-meeting-318:17
*** lpetrut has joined #openstack-meeting-318:28
*** thinrichs has joined #openstack-meeting-318:30
*** jnoller has joined #openstack-meeting-318:33
*** johnthetubaguy has quit IRC18:34
*** markmcclain has quit IRC18:34
*** thinrichs has quit IRC18:34
*** sarob has joined #openstack-meeting-318:42
*** banix has joined #openstack-meeting-318:55
*** troytoman is now known as troytoman-away18:58
*** eguz has joined #openstack-meeting-319:59
*** lpetrut has quit IRC20:01
*** eguz has quit IRC20:03
*** eghobo has quit IRC20:03
*** nacim has joined #openstack-meeting-320:03
*** jthopkin has quit IRC20:04
*** jthopkin has joined #openstack-meeting-320:23
*** sarob has quit IRC20:26
*** sarob has joined #openstack-meeting-320:26
*** lenrow has joined #openstack-meeting-320:27
*** julim has quit IRC20:28
*** sarob has quit IRC20:31
*** banix has quit IRC20:35
*** carl_baldwin has joined #openstack-meeting-320:37
*** lpetrut has joined #openstack-meeting-320:43
*** peristeri has quit IRC20:45
*** mwagner_ has quit IRC20:46
*** lpetrut has quit IRC20:52
*** ajo has quit IRC20:57
*** davidlenwell has joined #openstack-meeting-320:58
*** troytoman-away is now known as troytoman20:58
*** jthopkin has quit IRC20:59
*** RaymondWong has joined #openstack-meeting-321:00
*** nacim has quit IRC21:00
*** zehicle has joined #openstack-meeting-321:02
*** catherineD has joined #openstack-meeting-321:02
zehiclehello!21:03
davidlenwellhello21:03
davidlenwellI don't think anyone knows about the new meeting time21:03
zehicle:(21:03
*** fcarpenter has joined #openstack-meeting-321:03
*** rockyg has joined #openstack-meeting-321:03
zehicleI sent out the email to our team and list21:03
RaymondWonghi21:03
zehicleI think they are here...just running late21:03
davidlenwelloh good21:03
fcarpenterafternoon21:03
catherineDhello21:03
zehicleo/21:04
rockygo/21:04
davidlenwellwhos running this ?21:04
zehicle#meeting-start RefStack21:04
davidlenwellperfect21:04
zehicle#meetingstart RefStack21:04
zehicle#startmeeting RefStack21:04
openstackMeeting started Thu Mar 20 21:04:32 2014 UTC and is due to finish in 60 minutes.  The chair is zehicle. Information about MeetBot at http://wiki.debian.org/MeetBot.21:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:04
rockyghad to find the room and forgot the exact name...21:04
*** openstack changes topic to " (Meeting topic: RefStack)"21:04
openstackThe meeting name has been set to 'refstack'21:04
davidlenwellthere it goes21:04
zehicleagenda for today?21:05
davidlenwellcode merge, documentation, front page of website, tcup21:05
zehicle+121:05
zehicle#topic code_merge21:06
*** openstack changes topic to "code_merge (Meeting topic: RefStack)"21:06
*** sarob has joined #openstack-meeting-321:06
davidlenwellso first on the list is this .. https://review.openstack.org/#/c/81670/21:06
davidlenwellRaymondWong: you -1'd this patch .. I thought you could go into it now .. tell us your main problems with it21:07
zehicleyes please - some of these requests are going to be addressed by work that I'm doing21:09
*** carl_baldwin has quit IRC21:09
RaymondWongas of now, the code in the master branch works and we can kick off tempest test. if this code get merge, i don't think the code will run.21:09
davidlenwellzehicle: can you submit a patch on top of this review that addresses them ..21:09
*** carl_baldwin has joined #openstack-meeting-321:09
davidlenwellRaymondWong: I won't merge this until we are sure that it will21:10
davidlenwellI will personally cherry pick and test before merging it21:10
davidlenwellzehicle: I'd like to keep things going in the same review if you can ..21:10
zehicleI'd rather have it in trunk and merge than keep working off jmc's branch21:10
davidlenwellzehicle: I'd rather not keep working that way .. we have this workflow for a reason21:10
*** sarob has quit IRC21:10
davidlenwellother wise it gets very hard to manage21:11
*** sarob has joined #openstack-meeting-321:11
*** carl_baldwin has quit IRC21:11
davidlenwellif you need support in working in this work flow I am happy to help you21:11
zehicleI can do that21:11
davidlenwellthank you21:11
zehicleI'll reach out if I have questions, I suspect I just need to pull against Josh's branch21:11
zehicleor check it out directly21:12
davidlenwellzehicle:  you can pull against that review id21:12
davidlenwellsuper easy21:12
davidlenwellokay .. moving on ... https://review.openstack.org/#/c/81402/21:12
davidlenwellcatherineD:21:12
catherineDyes sir21:12
davidlenwelli am going to work on a patch set for this review before it can get merged21:13
catherineDthat is great21:13
davidlenwellthere are some python tools that do some of the things you built all those nested loops for21:13
davidlenwellin general .. I want you and your team to re-read the pep8 manual21:13
rockyg+1 for upstreamed tools21:13
davidlenwellstop using single character variable names for things .. and don't use CamelCase for function names21:14
rockyggot a link for that manual?21:14
*** MaxV_ has joined #openstack-meeting-321:14
fcarpenterhttp://legacy.python.org/dev/peps/pep-0008/21:14
davidlenwellhttp://legacy.python.org/dev/peps/pep-0008/21:14
rockygThanks!21:14
catherineDsure ..21:14
davidlenwellI know you guys are more java in your background and thats the standard in java .. but its considered bad practice in python21:15
davidlenwellwhich is the only reason I didn't approve this one ted .. https://review.openstack.org/#/c/81653/21:15
davidlenwellI know it seems trivial .. but in general the openstack community strictly follows pep8 .. and we should too21:16
RaymondWongsure. will do.21:16
davidlenwellthank you guys21:16
catherineDthat is no problem at all ..21:16
davidlenwellgood .. I know sometimes it sounds like I am being nit picky about it .. and I don't want to discourage future contributions from any of you21:16
davidlenwellokay .. moving right along ..21:17
davidlenwelldocumentation..21:17
rockygYo!21:17
davidlenwellsomeone set the topic?21:17
catherineDOnce the subunit stuff is in ... we will work withj davidlenwell: on report21:17
rockyg#topic Documentation21:17
davidlenwellIthink zehicle has to do it21:17
zehicle#topic documentation21:18
*** openstack changes topic to "documentation (Meeting topic: RefStack)"21:18
rockygYah.  You're right.21:18
davidlenwellthere we go21:18
davidlenwellso rockyg would you be up for coming up to piston at the end of next week for some face to face time on documentation ?21:18
zehicleI've got some docs changes in my pending pull21:18
rockygSo, tomorrow or next week?21:18
zehicleI'll see if I can split it out21:18
davidlenwellrockyg: next friday21:18
davidlenwelltomorrow im moving into my apartment in oakland21:19
rockygSure.  No problem.21:19
davidlenwellhopfully21:19
davidlenwellokay .. we'll set up an invite and make it official21:19
zehicleI'm going to be in town later in April (and bring Alex w/ me this time).  April 14-15.  should we plan another f2f then too?21:19
zehicleThat's a Monday21:19
davidlenwellI might be in canada .. I'll let you know21:19
rockygAnother team just published a requirements wiki doc.  I'm looking at mimicing it 'cause it looks good.21:19
davidlenwellI think I get back on monday night21:19
zehiclekk21:20
davidlenwellzehicle: we can do tuesday I think21:20
zehicleAlex could be available, but I've got RH summit on 15th21:20
rockygWe can do a f2f with the rest of the folks.21:20
davidlenwellsure ..21:20
davidlenwellI can always skype in21:20
zehiclelet's plan for Tues21:20
davidlenwellokay .. we'll settle it next meeting with times and places21:20
rockygMonday is definitely out for me.21:21
rockygSo Tuesday is it.21:21
davidlenwelldone ..21:21
zehicle4/15 then21:21
zehicleback to docs...21:21
davidlenwellso between now and then I'll spit out some shiny new graphs and diagrams21:21
davidlenwelland I'll communicate with defcore people to make sure we are meeting the use case requirements21:22
zehicleI created a /doc directory and moved the RefStack and TCUP setup into those21:22
rockygCan we get them to review and update if possible?21:22
zehicleyy21:22
zehiclethey had been part of my pull21:22
davidlenwellwe need ; a developer quickstart , install quide, high level arch.21:23
zehicleyou want me to split them or just base on topic of the existing JMC patch?21:23
davidlenwellsplit them21:23
davidlenwelltry to keep reviews to a single topic21:23
rockygYes.21:23
davidlenwellwe don't want to act like congress and squeeze in last minute changes to reviews21:23
davidlenwellthat are totally unrelated21:24
fcarpentercongress does code reviews?21:24
zehicle+1 (JMC has some doc changes already, that's why I asked)21:24
davidlenwellzehicle: yes .. but you know how hard he is to nail down on submitting code21:24
rockygYes.  all those funky numbers.  codification of law, I think they call it.21:24
zehicledavidlenwell, agreed21:25
davidlenwellso .. next topic ..  front page of website21:25
zehicle#topic front page21:25
*** openstack changes topic to "front page (Meeting topic: RefStack)"21:25
*** mfer has quit IRC21:25
davidlenwellright now we don't do a very good job of really communicating what refstack is or what its used for on the website21:25
davidlenwellwe need to fix that21:25
*** banix has joined #openstack-meeting-321:25
rockygYes.21:25
davidlenwellrockyg: we can tack that on to the face to face next week21:26
rockygGreat!21:26
davidlenwellI'll try to steel some cycles from a designer at piston to help .. if not I'm sure we can get through it21:26
davidlenwellzehicle: can you be available on skype that day for input21:27
rockygDepends on what it was written in, but these days, should be not too difficult to modify the code beneath.21:27
* zehicle checking21:27
davidlenwellrockyg: im less worried about the coding  and more worried about the design astetic21:27
davidlenwell*spelling21:28
* zehicle blocked out 3/2821:28
rockygmight not be too pretty until we get a designer to clean up.21:28
zehiclecan we do a lighthouse theme?21:28
rockygUnless we can come up with a mockup earler and we just add URLs/links21:28
davidlenwellI've done my fair share of website design21:28
rockygKewl.21:28
davidlenwellso lets deal with the details/requirements for that next meeting21:29
rockygGet us a wallpaper photo;-)21:29
*** banix has quit IRC21:29
catherineDwhat is the time for f2f on 3/28?21:29
*** MaxV_ has quit IRC21:29
davidlenwellcatherineD: lets plan for after lunch .. say 1 or 2 pm21:29
rockygYeah.  The more the merrier21:29
catherineDsure .. thx21:30
zehiclelater is harder for me on a Friday21:30
rockygCarpool?21:30
davidlenwellearlier is hard to reserve time at piston21:30
davidlenwellBART21:30
zehiclecan we try to 1?21:30
davidlenwellyes21:30
davidlenwell1 I can do21:30
rockygthe carpool was for catherineD21:31
*** lblanchard has quit IRC21:31
davidlenwellrockyg: I was teasing21:31
rockygk.  anything else on this?  I can review site and list out some of my issues/suggestion in a list email21:32
*** tedchang has joined #openstack-meeting-321:32
davidlenwellI think thats it on the website21:32
davidlenwellnext .. TCUP21:32
davidlenwelllets identify what is missing for the defcore team to all be able to install and run it by next friday21:32
zehicleI'm updating the wkii Meetings page #link https://wiki.openstack.org/wiki/Meetings#DefCore_.2F_RefStack_Development_Meeting21:33
zehicle#topic TCUP21:33
*** openstack changes topic to "TCUP (Meeting topic: RefStack)"21:33
RaymondWongif they download the whole refstack, they can run it now without seeing the report.21:33
zehicleI've got the basics of TCUP running21:33
rockygI'll probably be late for the 4/15 meeting.  First DAY of Passover.  and Hangover.21:34
davidlenwellso what is missing is mostly displaying the results21:34
catherineDyes that is why we need the subunit stuff ..21:34
davidlenwellwhich means catherineDand I need to finish the parser and I need to finish the display portion of that21:34
zehicleI have not been able to create a good config file to run the tests21:34
RaymondWongyou got the code to save the subunit in db already... so, just need to display that in html.21:34
davidlenwellshould be doable by next week ]21:35
davidlenwell:)21:35
catherineDOnce the subunit stuff is in, we  then need to map back to  capacity ...21:35
davidlenwelltechnically speaking if we stay on schedule tomorrow closes out the last sprint.. I think we mostly accomplished what we set out to .. however .. probably some better project manament is required moving forward21:35
zehicleRaymondWong, I'm a little confused.  what are we trying to dusplay?21:35
rockygWe should provide a list of what someone would need and what info they need to run it against a devstack.21:36
zehicleit sounds like you are running the code outside of the container?21:36
RaymondWongzehicle: I am talking about running from the refstack web GUI, I can kick off tempest test, and recevice back the results stream.21:36
catherineDwe are not running tempest outside of container21:36
RaymondWongthe web GUI shows test done, but does not  display the results.21:37
davidlenwellzehicle: they are talking about displaying the results from the web gui21:37
catherineDtempest is running inside a docker container21:37
*** david-lyle has quit IRC21:37
rockygand I'm talking about a prereqs list.21:38
zehicleok, there's more working here than I was thinking21:38
rockygYay, team!21:38
davidlenwellyay ..21:38
davidlenwellokay .. I'm happy to end now so we can all go get back to work21:38
zehicleare there docs that show how to setup the webserver for this?21:38
davidlenwellno .. but there will be21:39
davidlenwellbasically the readme does tell you how to get it working21:39
*** MaxV_ has joined #openstack-meeting-321:40
rockygThat readme is all there is to it to build/run the default?21:41
davidlenwellSo we have the board room reserved here at piston for next friday from 1-3:3021:41
catherineDI just build an ubuntus to host refstack yesterday.  I can send out my note after this .. pretty simple21:42
rockygThanks21:43
RaymondWongrockyg: the readme has the command to create the db, and start refstack app server.21:43
rockygYeah.  It didn't look like it has enough yet to really make all the magic happen.21:43
davidlenwellrockyg: we'll nail down a cleaner howto next week21:46
rockygGood.  Thanks.21:46
davidlenwellwhat is the mailing address list?21:47
davidlenwellI'll invite the whole list21:47
fcarpenterack, i joined it but don't remember ;)21:47
zehicledefcore-committee21:47
rockygfits@lists.openstack.org21:48
fcarpenterthat one!21:48
davidlenwellthats what I was looking for21:48
davidlenwellyes21:48
rockygAnd, it can be on the slow side. We need to make sure it gets' flushed regularly.21:48
davidlenwellfcarpenter: can you invite that .. I don't seem to be able to add people to the invite21:49
davidlenwellalright .. talk to you guys later on21:50
fcarpenterdavidlenwell Done21:50
rockygThanks everyone.21:50
zehicleok, wrapping up21:50
zehicle#endmeeting21:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:50
openstackMeeting ended Thu Mar 20 21:50:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-03-20-21.04.html21:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-03-20-21.04.txt21:50
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-03-20-21.04.log.html21:50
*** banix has joined #openstack-meeting-322:18
*** lenrow has quit IRC22:19
*** lenrow has joined #openstack-meeting-322:20
*** Sukhdev has joined #openstack-meeting-322:20
*** MaxV_ has quit IRC22:22
*** MaxV_ has joined #openstack-meeting-322:30
*** MaxV_ has quit IRC22:36
*** david-lyle has joined #openstack-meeting-322:38
*** jnoller has quit IRC23:05
*** rockyg has quit IRC23:08
*** banix has quit IRC23:19
*** fcarpenter has left #openstack-meeting-323:22
*** sarob has quit IRC23:26
*** sarob has joined #openstack-meeting-323:26
*** sarob has quit IRC23:31
*** david-lyle has quit IRC23:31
*** mwagner_notHere has quit IRC23:37
*** banix has joined #openstack-meeting-323:43
*** rockyg has joined #openstack-meeting-323:45
*** alexpilotti has quit IRC23:55
*** eghobo has joined #openstack-meeting-323:56
*** eghobo has quit IRC23:57
*** eghobo has joined #openstack-meeting-323:57
*** rockyg has quit IRC23:58

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