Thursday, 2014-05-08

*** MaxV has quit IRC00:04
*** yamahata has joined #openstack-meeting-300:08
*** SumitNaiksatam has quit IRC00:08
*** overlayer has joined #openstack-meeting-300:19
*** overlayer has quit IRC00:23
*** overlayer has joined #openstack-meeting-300:25
*** overlayer has quit IRC00:26
*** banix has joined #openstack-meeting-300:28
*** chuckC has quit IRC00:32
*** TravT has quit IRC00:35
*** markmcclain1 has quit IRC00:52
*** nacim has quit IRC01:05
*** mestery has quit IRC01:08
*** SumitNaiksatam has joined #openstack-meeting-301:10
*** eghobo has quit IRC01:20
*** mestery has joined #openstack-meeting-301:25
*** garyduan has quit IRC01:25
*** shakamunyi has joined #openstack-meeting-301:27
*** jaypipes has quit IRC01:28
*** mestery has quit IRC01:34
*** shakamunyi has quit IRC01:42
*** beyounn has joined #openstack-meeting-301:47
*** mestery has joined #openstack-meeting-301:48
*** shakamunyi has joined #openstack-meeting-301:57
*** sankarshan is now known as sankarshan_away02:12
*** shakayumi has joined #openstack-meeting-302:15
*** shakamunyi has quit IRC02:19
*** beyounn has quit IRC02:21
*** chuckC has joined #openstack-meeting-302:34
*** mestery has quit IRC02:49
*** otherwiseguy has joined #openstack-meeting-302:52
*** sankarshan_away is now known as sankarshan02:53
*** shakayumi has quit IRC03:01
*** david-lyle has joined #openstack-meeting-303:02
*** otherwiseguy has quit IRC03:10
*** otherwiseguy has joined #openstack-meeting-303:19
*** lcheng_ has joined #openstack-meeting-303:21
*** david-lyle has quit IRC03:23
*** shakayumi has joined #openstack-meeting-303:31
*** devlaps has quit IRC03:31
*** TravT has joined #openstack-meeting-303:33
*** garyduan has joined #openstack-meeting-303:33
*** coolsvap|afk is now known as coolsvap03:35
*** eghobo has joined #openstack-meeting-303:35
*** lcheng_ has quit IRC03:45
*** lcheng_ has joined #openstack-meeting-303:46
*** otherwiseguy has quit IRC04:01
*** shakayumi has quit IRC04:08
*** mestery has joined #openstack-meeting-304:24
*** beyounn has joined #openstack-meeting-304:34
*** lcheng_ has quit IRC04:39
*** lcheng_ has joined #openstack-meeting-304:56
*** eghobo has quit IRC04:58
*** eghobo has joined #openstack-meeting-304:59
*** sankarshan is now known as sankarshan_away04:59
*** banix has quit IRC05:18
*** amotoki has joined #openstack-meeting-305:19
*** lcheng_ has quit IRC05:32
*** krotscheck has quit IRC05:40
*** krotscheck has joined #openstack-meeting-305:45
*** shakayumi has joined #openstack-meeting-305:52
*** shakayumi has quit IRC05:57
*** lcheng_ has joined #openstack-meeting-306:10
*** lcheng_ has quit IRC06:17
*** sankarshan_away is now known as sankarshan06:50
*** SumitNaiksatam_ has joined #openstack-meeting-307:11
*** SumitNaiksatam has quit IRC07:13
*** SumitNaiksatam_ has quit IRC07:17
*** eghobo has quit IRC07:24
*** mrunge has joined #openstack-meeting-307:37
*** ttrifonov_zZzz is now known as ttrifonov07:56
*** lcheng_ has joined #openstack-meeting-308:10
*** lcheng_ has quit IRC08:12
*** jcoufal has joined #openstack-meeting-308:24
*** jcoufal has quit IRC08:27
*** beyounn has quit IRC08:32
*** jamie_h has joined #openstack-meeting-308:32
*** jcoufal has joined #openstack-meeting-308:40
*** jcoufal has quit IRC08:45
*** jcoufal has joined #openstack-meeting-308:45
*** MaxV has joined #openstack-meeting-309:04
*** MaxV has quit IRC09:04
*** jcoufal has quit IRC09:09
*** jcoufal has joined #openstack-meeting-309:09
*** coolsvap is now known as coolsvap|afk10:37
*** rkukura_ has joined #openstack-meeting-310:48
*** coolsvapl has joined #openstack-meeting-310:54
*** coolsvap|afk has quit IRC10:55
*** rkukura_ is now known as rkukura10:55
*** davidlenwell_ has joined #openstack-meeting-311:02
*** troytoman_ has joined #openstack-meeting-311:08
*** troytoman has quit IRC11:23
*** davidlenwell has quit IRC11:23
*** haleyb has quit IRC11:23
*** haleyb has joined #openstack-meeting-311:38
*** lblanchard has joined #openstack-meeting-312:04
*** julim has joined #openstack-meeting-312:33
*** jcoufal has quit IRC13:00
*** david-lyle has joined #openstack-meeting-313:11
*** cjellick has quit IRC13:19
*** coolsvapl is now known as coolsvap|afk13:22
*** peristeri has joined #openstack-meeting-313:24
*** cgascoig has joined #openstack-meeting-313:27
*** cgascoig has quit IRC13:29
*** coolsvap|afk is now known as coolsvap13:29
*** cgascoig has joined #openstack-meeting-313:29
*** mwagner_ has quit IRC13:29
*** banix has joined #openstack-meeting-313:30
*** mrunge has quit IRC13:30
*** cgascoig has quit IRC13:33
*** david-lyle has quit IRC13:34
*** sankarshan is now known as sankarshan_away13:45
*** sankarshan_away is now known as sankarshan13:48
*** yamahata has quit IRC13:50
*** yamahata has joined #openstack-meeting-313:51
*** cjellick has joined #openstack-meeting-313:55
*** ajo has joined #openstack-meeting-313:59
*** otherwiseguy has joined #openstack-meeting-314:00
*** terryw has joined #openstack-meeting-314:03
*** otherwiseguy has quit IRC14:03
*** julim has quit IRC14:06
*** overlayer has joined #openstack-meeting-314:10
*** coolsvap is now known as coolsvap|afk14:15
*** TravT has quit IRC14:21
*** coolsvap|afk is now known as coolsvap14:27
*** ttrifonov is now known as ttrifonov_zZzz14:33
*** enykeev has quit IRC14:33
*** terryw has quit IRC14:36
*** otherwiseguy has joined #openstack-meeting-314:36
*** markmcclain has joined #openstack-meeting-314:37
*** markmcclain has quit IRC14:42
*** carl_baldwin has joined #openstack-meeting-314:49
carl_baldwinHi Neutron L3 team15:00
carl_baldwin#startmeeting neutron_l315:00
*** pcm_ has joined #openstack-meeting-315:00
openstackMeeting started Thu May  8 15:00:52 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_baldwinSummit is next week. We will not hold this meeting on the 15th. It will continue on the 22nd.15:01
carl_baldwinI have updated the team meeting page with summit information partaining to design sessions from this team.  There are a number of them.15:01
carl_baldwin#link https://wiki.openstack.org/wiki/Meetings/Neutron-L3-Subteam15:02
carl_baldwinIf you have a session, please create an etherpad and post it.15:02
carl_baldwin#link https://wiki.openstack.org/wiki/Summit/Juno/Etherpads#Neutron15:02
*** Swami has joined #openstack-meeting-315:03
carl_baldwinAlso, there will be a Neutron mid-cycle meeting in July.  There is an etherpad but I’m unable to reach it.15:03
carl_baldwin#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting15:03
Swamihi15:03
carl_baldwinSwami: hi15:04
carl_baldwinOkay, etherpad came up for me now.15:04
carl_baldwinLooks like it is still between the weeks of the 7th and 14th.15:05
carl_baldwinLocation is between Minneapolis and San Jose.15:05
carl_baldwinI expect decisions will be made soon.15:05
carl_baldwinAny other announcements?15:06
carl_baldwin#topic Bugs15:06
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:06
carl_baldwinI’ll start discussing bugs in the team meeting.  Our bugs will be tagged with l3-ipam-dhcp.15:07
carl_baldwin#link https://bugs.launchpad.net/neutron/+bugs?field.tag=l3-ipam-dhcp15:07
carl_baldwinLooks like there are a few High priority but all have owners.  I’ll go through the Undecided and try to get them triaged the remainder of this week.15:08
*** nextone92 has joined #openstack-meeting-315:08
carl_baldwin#action carl_baldwin to triage undecided bugs15:08
carl_baldwin#topic l3-svcs-vendor-*15:09
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:09
carl_baldwinpcm_: hi15:09
*** julim has joined #openstack-meeting-315:09
carl_baldwinI added information about your summit session on the page for a little extra visibility.15:09
pcm_hi15:09
pcm_thanks!15:09
carl_baldwinAnything to report?15:09
carl_baldwinIf you’re like me, you’re just busy preparing for the discussion.15:10
pcm_no. just need to know more about Mark McClain's TaskFlow and how it impacts.15:10
* pcm_ very busy15:10
carl_baldwinAh, right.  That will be good to explore before the discussion a bit.15:11
pcm_Please look at the etherpad and and anything...15:11
pcm_and add15:11
carl_baldwinLast I knew, there was no blueprint available for Mark’s.  Has be posted something?15:11
pcm_Didn't check today,15:11
pcm_but nothing yesterday.15:12
Swamiwhat is this task flow?15:12
carl_baldwinI’m checking to see if he has an etherpad.15:12
pcm_#link https://wiki.openstack.org/wiki/TaskFlow15:12
carl_baldwinpcm_: I see your etherpad and I will have a look.15:13
carl_baldwinIt is linked from our subpage for others to find it too.15:13
pcm_Swami: Allows you to create tasks for actions, flows (collection of tasks), and engine (how to apply the flow)15:13
pcm_carl_baldwin: nice15:13
pcm_Question is whether we'll consider using TaskFlow at a low and/or high level.15:13
carl_baldwinI will also read through this task flow page.  I think this will touch everyone’s work in some way.15:14
pcm_IOW: to do the flow for one command (validation, persistence, appy), or for one action (create VPN policy, create PSK, and create conneciton)15:14
pcm_carl_baldwin: yes. need to understand more, have some examples, and discuss how to apply.15:15
carl_baldwinpcm_: That is a good question.  We should keep that in mind as we review the two subjects.15:15
pcm_I'm not sure (yet) how TaskFlow can be used with vendors (conditional tasks)15:15
pcm_where we want to do a vendor validation, based on some flavor.15:16
*** BrianB_ has joined #openstack-meeting-315:16
pcm_anyhow, add thoughts/comments/questions.etc on the Etherpad. Will really help.15:17
pcm_Could use some eyes on the client capabilities BP, as I'm not sure how feasible that is.15:17
carl_baldwinWe’ll use the next week to review and think about it.  We can use etherpad and ML to discuss over the next week before the discussion.15:17
pcm_roger that15:17
pcm_that's if for me15:18
pcm_it15:18
carl_baldwinWhat is the link for the BP?15:18
pcm_#link https://review.openstack.org/#/c/89366/1/specs/juno/l3-svcs-vendor-client-cap.rst15:18
carl_baldwinThanks, I see you have three BPs up now.  I had only seen the validation one.15:19
carl_baldwinI’ll be sure the subteam links to them all.15:19
pcm_Yeah, 3 BP and 3 specs, all interrelatted.15:19
carl_baldwinpcm_: Thanks for your update.  You’ve done a lot of work to get that all posted.15:20
carl_baldwin#action carl_baldwin will update subteam page to show all BP and specs.15:20
pcm_welcome15:20
carl_baldwin#topic l3-high-availability15:20
*** openstack changes topic to "l3-high-availability (Meeting topic: neutron_l3)"15:20
carl_baldwinI don’t see safchain15:21
carl_baldwinThe activity I’ve seen on this is with dvr so we can discuss later.15:22
carl_baldwin#topic bgp-dynamic-routing15:22
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:22
carl_baldwinnextone92: hi15:22
*** overlayer has quit IRC15:22
*** markmcclain has joined #openstack-meeting-315:22
nextone92Hi!15:22
nextone92Thank you everyone for providing comments15:22
*** rkukura has left #openstack-meeting-315:23
carl_baldwinI see you’ve posted a new revision of the bp.15:23
nextone92I have responded to code review feedback and took down some action items for changes I haven't yet made15:23
carl_baldwinGreat.15:23
nextone92There was a recommendation from Pedro Marques to consider merging this with VPN blueprint15:24
*** overlayer has joined #openstack-meeting-315:24
carl_baldwinI didn’t see that.15:24
nextone92It's the first comment BGP L3VPN15:24
carl_baldwinTo me, the two topics are distinct.15:25
nextone92I believe we have discussed this early in L3 subteam meetings15:25
nextone92I don't have a strong opposition for more BGP use cases, but think it would be prudent to start slow15:25
nextone92start *small15:25
nextone92and then expand to more use cases15:25
carl_baldwinYes.  I don’t think BGP L3VPN will be the first use case.15:26
carl_baldwinI guess I had seen his comments on L3VPN.15:26
nextone92Okay - the next action item are improvement comments from Mark Mcclain - I have responded on the code review and sent him an email from launchpad15:27
nextone92I haven't heard back and will send him another emaik15:27
nextone92The last action item is quagga HA question asked by you15:27
carl_baldwinI recall some discussion in Hong Kong about BGP and L3 VPN.  I think there are some who get stuck on L3VPN whenever BGP comes up.15:28
carl_baldwinWe may have to be prepared for that in the discussion.15:28
carl_baldwinnextone92:  You and I are sharing the session on Friday at 4pm.  We should probably have a discussion about how we’re going to use that time.15:29
nextone92Okay, and I will try to see if I can meet Pedro in person and ask more questions15:29
*** jaypipes has joined #openstack-meeting-315:29
carl_baldwinThat would be great.15:29
nextone92Yes, my schedule is very open so any time that works for you would work for me. I will private message you.15:29
carl_baldwinWould you like to talk before Atlanta or in Atlanta?15:30
*** eghobo has joined #openstack-meeting-315:30
carl_baldwinOkay, we’ll discuss privately.15:30
*** YorikSar has joined #openstack-meeting-315:30
carl_baldwinAnything else?15:30
*** terryw has joined #openstack-meeting-315:30
nextone92I think we can talk about Quagga HA quicklt15:31
nextone92One approach would be not to HA quagga, but to have multiple servers running quagga with their own uplinks15:31
nextone92so when one quagga dies, there is a duplicate uplink with corresponding routes15:31
carl_baldwinnextone92: I totally agree.  That is how I envisioned it.15:31
nextone92Thank you for the clarification15:32
carl_baldwinBGP kindof has that HA built in to the protocol.15:32
nextone92Yes, and that seems the easiest approach15:32
carl_baldwinJust run multiple BGP speakers to the same set of upstream routers.15:32
carl_baldwinnextone92: Agreed15:32
carl_baldwinAnything else?15:33
nextone92The final question that I had is whether there is a routing daemon preference15:33
nextone92Mark Mcclain has recommended to look into Bird vs Quagga15:33
*** otherwiseguy has quit IRC15:33
carl_baldwinAh, my only reason for a preference is because I’ve only had experience with Quagga.  I’m open to suggestions.15:33
nextone92Same here, if there are no other recommendations I will follow up with Mark15:34
carl_baldwinThe solution should be pluggable but we’ll need to discuss the options for a reference implementation.15:34
carl_baldwinnextone92: great.15:34
*** emagana has joined #openstack-meeting-315:34
carl_baldwin#action nextone92 will follow up with markmcclain about comments and routing daemon.15:34
carl_baldwin#topic rootwrap-daemon-mode15:34
*** openstack changes topic to "rootwrap-daemon-mode (Meeting topic: neutron_l3)"15:34
carl_baldwinYorikSar: ajo: hi15:35
YorikSaro/15:35
carl_baldwinI posted information about the summit session.15:35
carl_baldwinYorikSar: you will not be at summit, right?15:35
YorikSarcarl_baldwin: Right. Roman Popolyaka agreed to represent me there15:36
YorikSar*Podolyaka15:36
carl_baldwinGreat.  I also plan to attend.  I’ll introduce myself.  It will be good to have someone there who is up to date on your work.15:36
YorikSarcarl_baldwin: I also haven't came around to post the blueprint yet. I've been wrapped up in Nova scheduler specs...15:37
YorikSarI hope to put together one soon.15:37
carl_baldwinOkay.  Will you have one before the design session?15:37
YorikSarI've also finally made my patch work with Neutron.15:37
YorikSarcarl_baldwin: Sure.15:38
carl_baldwinYorikSar: Great.  I’d like to test it out.15:38
carl_baldwinI’m sure others will too.15:38
carl_baldwinI’ll grab the patches and give it a go.15:39
YorikSarAnd I've found weird behavior in DHCP agent. It creates an instance of driver for every action needed to be done which makes it hard to link with rootwrap daemon's client - one daemon instance ends up running for each request.15:39
carl_baldwin#action YorikSar will post blueprint before summit design talk.15:39
YorikSarI'll file a bug on this topic and put together a fix15:39
YorikSarOh, my patch is there:15:40
YorikSar#link https://review.openstack.org/8466715:40
carl_baldwinThanks for the link.15:40
*** TravT has joined #openstack-meeting-315:40
YorikSarYou can see example of weird behavior here: (traceback for every creation of new Client is there)15:41
YorikSar#link http://logs.openstack.org/67/84667/20/check/check-tempest-dsvm-neutron/3a7768e/logs/screen-q-dhcp.txt.gz?level=INFO15:41
carl_baldwinAh, yeah.  Send me the bug number when you’ve filed it.15:42
YorikSarcarl_baldwin: Ok.15:43
carl_baldwinOne last thing.  Thierry will drive this as part of the Oslo track.  As long as they keep sufficient traction in it then we won’t have this on this subteam agenda any more.15:43
carl_baldwinI’ll watch from the background and try to fan the flames if it starts to die out.15:43
YorikSarHuh... Ok. I guess I'll attend their meetings then15:43
*** coolsvap is now known as coolsvap|afk15:43
*** rudrarugge has joined #openstack-meeting-315:44
carl_baldwinI guess we’ll see how the transition goes at the summit discussion.15:44
YorikSarcarl_baldwin: It won't. Current overhead of rootwrap actually troubles me :)15:44
carl_baldwinYorikSar: Me too.  :)15:44
carl_baldwinAnything else?15:44
YorikSarcarl_baldwin: Sure.15:44
YorikSarcarl_baldwin: I'll also try to put together a patch for Nova next week.15:44
YorikSarcarl_baldwin: Nope. That's it.15:45
carl_baldwinYorikSar: Great work.  I’m excited to see this improve rootwrap.15:45
carl_baldwin#topic neutron-ovs-dvr15:45
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:45
carl_baldwinSwami: hi15:45
*** Rajeev has joined #openstack-meeting-315:46
Swamihi15:46
SwamiYes DVR work is progressing in fast pace.15:46
SwamiWe are currently working on the SNAT for the North-South15:46
SwamiHopefully we will complete this work with a couple of weeks.15:47
SwamiI will also update the Wiki with the Howto on configuring and running the DVR15:47
carl_baldwinHow close are we to having something the community can test?15:47
carl_baldwinAh, great timing for that comment.  Exactly what I was after.  :)15:48
SwamiSome parts of the code was not yet merged with the Master, so will be merging it in the next week or so and should be able to run with the Wiki's help15:48
carl_baldwinThat would be a great thing to have prepared before your summit session.15:49
*** lcheng_ has joined #openstack-meeting-315:49
carl_baldwinLet’s see.  Wednesday at 5:20pm.15:49
SwamiYes our plan was to have all the code as WIP before the summit and then start working on pushing the non-WIP code to upstream by the Juno milestone115:50
carl_baldwinIf you have workable code published I might just skip whatever party is that night and go try it out.  ;)15:50
SwamiThat's all I had from my end.15:50
carl_baldwinSwami: Thanks for your report.15:51
carl_baldwinSwami: It is great to see it coming together.15:51
*** devlaps has joined #openstack-meeting-315:51
carl_baldwin#topic pluggable-ext-net15:51
*** openstack changes topic to "pluggable-ext-net (Meeting topic: neutron_l3)"15:51
Swamicarl: It is a great team effort15:51
carl_baldwin#link http://junodesignsummit.sched.org/event/562393582543b1a0da0db766a5c4a7b3#.U2fC2K1dVcM15:52
carl_baldwin#link https://etherpad.openstack.org/p/juno-neutron-pluggable-external-network15:52
carl_baldwin#action carl_baldwin will start fleshing out the etherpad by the end of the week.15:52
carl_baldwinThis is the sharing I’m sharing with nextone9215:52
carl_baldwinThat’s all I have.15:52
carl_baldwin#topic *-dns-resolution15:53
*** openstack changes topic to "*-dns-resolution (Meeting topic: neutron_l3)"15:53
carl_baldwinMy design topic got bumped at the last minute before the schedule came out.15:53
carl_baldwinHowever, there is a lot of interest in having a discussion.  Looks like we’ll try to get together late afternoon on Monday.15:54
carl_baldwin#link https://etherpad.openstack.org/p/juno-dns-neutron-nova-designate15:54
carl_baldwin#topic Open Discussion15:55
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:55
carl_baldwinWe got through it all.15:56
SwamiI think you covered a lot of items today15:57
*** overlayer has quit IRC15:57
SwamiI don't have any open items at this time.15:57
pcm_See you all at the summit!15:58
carl_baldwinI look forward to meeting most of you at the summit.  We have some good discussions coming up.15:58
carl_baldwinThanks for all your work.  Things are progressing well.15:58
SwamiSee you , bye15:58
*** pcm_ has left #openstack-meeting-315:59
carl_baldwin#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Thu May  8 15:59:07 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-08-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-08-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-08-15.00.log.html15:59
*** nextone92 has left #openstack-meeting-316:00
*** Swami has quit IRC16:01
*** markmcclain has quit IRC16:02
*** YorikSar has left #openstack-meeting-316:04
*** sankarshan is now known as sankarshan_away16:07
*** chuckC has quit IRC16:18
*** eghobo has quit IRC16:26
*** eghobo has joined #openstack-meeting-316:28
*** catherineD has joined #openstack-meeting-316:48
*** SridarK has quit IRC16:49
*** davidlenwell_ is now known as davidlenwell16:49
*** eghobo has quit IRC16:51
*** eghobo has joined #openstack-meeting-316:51
*** jamie_h has quit IRC16:51
*** jamie_h_ has joined #openstack-meeting-316:51
*** zehicle_at_dell has joined #openstack-meeting-316:53
*** jamie_h_ has quit IRC16:55
*** jamie_h has joined #openstack-meeting-316:56
*** banix has quit IRC16:58
*** markmcclain has joined #openstack-meeting-316:58
*** zehicle_ has joined #openstack-meeting-317:01
*** chuckC has joined #openstack-meeting-317:01
davidlenwell#startmeeting refstack17:01
openstackMeeting started Thu May  8 17:01:54 2014 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: refstack)"17:01
openstackThe meeting name has been set to 'refstack'17:01
zehicle_o/17:02
davidlenwellroll call17:02
catherineDHere17:02
davidlenwellagenda: simplified tester, TCUP, api->api authentication, communication channels, refstack meetups at summit. summit sessions17:03
*** eguz has joined #openstack-meeting-317:03
*** rockyg has joined #openstack-meeting-317:03
*** eguz has quit IRC17:03
*** rudrarug_ has joined #openstack-meeting-317:03
zehicle_cool17:03
davidlenwellzehicle_: can you think of anything else ?17:03
rockygo/17:03
davidlenwellrockyg: you missed this : agenda: simplified tester, TCUP, api->api authentication, communication channels, refstack meetups at summit. summit sessions17:03
zehicle_capabilities page?17:03
rockygtnx17:04
davidlenwellokay we'll just cover that one first.17:04
*** eghobo has quit IRC17:04
*** sadasu has joined #openstack-meeting-317:04
davidlenwell#topic capabilities page17:04
*** openstack changes topic to "capabilities page (Meeting topic: refstack)"17:04
davidlenwellyou have the floor zehicle_17:05
zehicle_thanks17:05
zehicle_the DefCore committee has put out a draft of the capabilities17:05
zehicle_and I wanted to be able to put it out as a simple render.17:05
davidlenwellI did get your email .. but it seems like troy and I were both unsure who you meant should put that up some place17:05
zehicle_we have a JSON format that looks OK17:05
zehicle_sorry about that  -I was thinking restack.org17:06
zehicle_should have been specific17:06
davidlenwelloh.. yeah .. no biggy ..17:06
*** rudrarugge has quit IRC17:06
zehicle_if the format of the json is OK then I'll do a patch w/ the HTML page17:06
davidlenwellwhy don't you commit to the repo with those in the static files folder and link to it on the home page .. I'll pretty up the html if you need me to17:06
zehicle_and also update the capabilities counts so they are not all 017:06
zehicle_yes please > pretty++17:06
davidlenwellokay go ahead and do that today ..17:06
rockygYeah.  the first pass is good enough to approve and get in.17:06
zehicle_thanks17:07
davidlenwellzehicle_: please make sure you don't have dependanies on your commit17:07
zehicle_can do once I get out from behind the firewall17:07
davidlenwellwhich reminds me of another agenda item we'll jump to next17:07
rockyg++17:07
zehicle_will do, may ping you to make sure17:07
zehicle_offline17:07
davidlenwell#topic code reviews17:07
*** openstack changes topic to "code reviews (Meeting topic: refstack)"17:07
davidlenwellspecifically17:08
davidlenwellhttps://review.openstack.org/#/c/91640/17:08
davidlenwellneeds to be rebased17:08
davidlenwellI'd like to be able to merge it17:08
* zehicle_ done17:08
davidlenwellthank you17:09
davidlenwellthere is also a new draft of the v1 api specs I'd like to merge if everyone can review it today.17:09
davidlenwellhttps://review.openstack.org/#/c/90044/17:09
* zehicle_ can do17:09
rockygwill do17:10
davidlenwellThank you17:10
*** banix has joined #openstack-meeting-317:10
davidlenwellokay this leads nicely into the next topic17:10
davidlenwell#topic simplified tester17:10
*** openstack changes topic to "simplified tester (Meeting topic: refstack)"17:10
davidlenwellyou may have noticed if you were watching that we merged this last night ..17:10
davidlenwellhttps://review.openstack.org/#/c/92552/17:10
*** praveen_dell has joined #openstack-meeting-317:11
davidlenwellits actually not finished yet .. I have another patch that will hit it probably tomorrow afternoon that will complete the circle .. but there is enough of the tool finished to prep the env .. and start tests on it .. should be very useful for tcup17:11
*** zehicle_at_dell has quit IRC17:11
rockygmissed that.  saw stuff fly by related.17:12
davidlenwellI have a diagram and some slides for it in the deep dive session17:12
rockygwe gonna sync f2f at summit on tha beforehand?17:13
zehicle_the sooner the better - we're down to the wire17:13
davidlenwellrockyg: we'll get to that in a minute17:13
davidlenwellits an agenda item17:13
rockygping us all when code is ready for us to try.17:14
davidlenwellzehicle_: you should be able to test with it now17:14
zehicle_ok, I'll be on #refstack and look for help17:14
davidlenwellthe tests won't pass because the cloud prep piece is just a stub17:14
rockygSounds like we can try now.17:14
zehicle_will make my day17:14
davidlenwellbut it preps and launches tests..17:14
davidlenwellthen sends them home17:14
*** mestery_ has joined #openstack-meeting-317:14
*** mestery has quit IRC17:14
davidlenwelland reports status to the api when it fails ..17:14
zehicle_I just need to be able to launch - we can iterate in parallel after that17:15
davidlenwelland interactively asks you for any values it needs in env that its missing17:15
davidlenwellso its actually a useful tester more in line with our original specs17:15
praveen_delllet me know if you want me to test any code17:15
davidlenwellpraveen_dell: you can test it now17:15
zehicle_we may need to document the steps17:16
*** tedchang has joined #openstack-meeting-317:16
praveen_dellsure,will do it17:16
rockygEveryone who has cloud access should try against their cloud.17:16
zehicle_+117:16
davidlenwellsome q/a on the parts that are done would be very useful for me to refine it into a finished state17:16
*** mestery_ is now known as mestery17:16
davidlenwellnote* it only works in havana right now17:16
*** terryw is now known as otherwiseguy17:16
rockygAnd file bugs once they get it working for missing parts, etc.17:16
davidlenwellrockyg: ++17:17
rockygCan we run afainst others since the test don't run anyway?17:17
davidlenwellit does run tests17:17
rockygkewl.17:17
davidlenwellthey'll just fail because the config isn't complete17:17
davidlenwellI also put in a stub for scrubing results before sending them home17:17
catherineDrockyg: File bug against Tempest Havana17:17
catherineD?17:18
davidlenwellfile bugs on the refstack lp page for the code I just put up17:18
davidlenwellthe tester is a central part of refstack17:18
davidlenwelland filed bugs will help me make it stronger17:18
rockygwhat david said.17:18
davidlenwellwe're at a stage were we'll have to do some q/a passes17:19
davidlenwellI can call it "finished" but it really isn't until we've worked out the kinks .. and that means lots of different people need to use it.17:19
davidlenwelland give feed back17:19
catherineDOK I will get off line with you on how to file bug against Refstack17:20
davidlenwellI know of some kinks off hand .. thats why I'm saying its still a wip17:20
davidlenwellcatherineD: just go to launchpad.com/refstack and click file bug17:20
catherineDok17:20
rockygQuestion:  I've never seen a way to idenitfy the version in the various openstack projects.  Is ther?17:20
davidlenwellim sure we can figure that out later17:21
davidlenwelloffline that one17:21
davidlenwellwe should move into our next topic .. TCUP17:21
zehicle_+117:21
davidlenwell#topic TCUP17:22
*** openstack changes topic to "TCUP (Meeting topic: refstack)"17:22
davidlenwellSo with the tester in its current state .. we should be able to get the tcup code in better working order.17:22
zehicle_basicaslly, nothing since last meeting.  I've been blocked on the launcher.17:22
zehicle_I think we should be able to jump ahead now17:22
zehicle_are all the pending patches looking good to go?  it will help w/ debug and instructions17:23
davidlenwellexcelent17:23
rockygfor catherineD, last topic:  #link https://bugs.launchpad.net/refstack17:23
zehicle_I can also make sure to hand off to praveen_dell17:23
davidlenwellzehicle_: I'll look more closely offline and ping you if I need you to take any action17:23
zehicle_so he can get an early jump on it17:23
zehicle_thanks - I'm available this afternoon for TCUP17:23
catherineDThx Rocku17:23
davidlenwellI will be hyper viligent with code reviews leading up into the summit17:24
zehicle_praveen_dell, you have time tomorrow AM to try out the latest?17:24
praveen_dellyeah17:24
praveen_delli will try tomorrow17:24
praveen_delllatest tcup? right?17:24
zehicle_davidlenwell, we should be in good shape.17:24
davidlenwellgood ..17:24
davidlenwellwe should move on17:25
davidlenwell#topic api->api authentication17:25
*** openstack changes topic to "api->api authentication (Meeting topic: refstack)"17:25
zehicle_yes - I may have to give you directions because the patch may not be accepted tomorrow17:25
praveen_dell<zehicle_> ok please ping me tomorrow or send me an email a17:25
zehicle_praveen_dell, will do!17:25
praveen_dell<zehicle_> thanks17:25
davidlenwellcatherineD: rockyg and zehicle_ and I were having a discussion on irc the other day about how to handle auth for the api ->api sync feature17:26
davidlenwelland I think that as  an openstack project we should eat our own dogfood and use keystone for this17:26
davidlenwellit ends up openstack already built a tool for just this sort of thing and I think we should use it..17:27
rockygThe big question for me is whether vendors consider it secure enough to accept it.17:27
davidlenwellSo asap I will put a running keystone server on refstack.org17:27
davidlenwellrockyg: as I said the other day .. I don't care what they think17:27
davidlenwellif they are openstack vendors they can trust keystone17:27
rockygWe will if they won't send test results.17:27
davidlenwellif they don't trust keystone they should help fix whatever they think is broken in it17:28
davidlenwellrockyg: im not aware of any vendors who wouldn't trust it.17:28
davidlenwellplease inform me thusly if I am wrong17:28
zehicle_it's good for a first pass17:28
zehicle_if there are issues, we can address as they come up17:28
rockygYes.  Good first pass.17:28
davidlenwelldissagree17:28
zehicle_ok17:28
davidlenwellI think its the long term solution17:28
zehicle_davidlenwell, perhaps it is17:29
* zehicle_ wants it to be17:29
davidlenwellI just don't understand why it would be up for debate17:29
rockygBut, whether problems arise with it or not, we have a working solution to demo.17:29
zehicle_davidlenwell, I don't have issues.  was mainly asking for us to hold any issues for later to see if they emerge17:30
*** beyounn has joined #openstack-meeting-317:30
davidlenwellthere is a team that works on it full time .. they understand the problem space and are constantly working to keep it secure.. that is way more than we can bring to the problem.. and I won't participate in re-inventing wheels in the openstack ecosystem.17:30
catherineDMaybe this is a topic for the face-2-face.  Using Keystone practically we will have 2 Keystone one on refstack.or and the other one on local?  How do we sync? Why not using lainchpad? Why do we use launchpad to log in and keystone for others?17:31
davidlenwellperiod.. so if someone thinks there is a good reason why Vendors woldn't trust there keys in keystone on a foundation run server.. please speak up ..17:31
davidlenwellcatherineD: not at all.. the farside will just have the client libs17:31
zehicle_+1 catherineD on discussion f2f not here17:31
*** chuckC has quit IRC17:32
davidlenwellcatherineD: lets talk online .. its actually a topic that should be in a written up spec .. which we are supposed to have in progress for this topic already.17:32
catherineDdavidlenwell: +1.  Better face-2-face next week17:32
davidlenwellthat is why this process is in place .. to refine ideas.. lets use them17:32
davidlenwellthis leads me nicely into the next topic of discussion17:33
davidlenwell#topic communication channels17:33
*** openstack changes topic to "communication channels (Meeting topic: refstack)"17:33
rockygDavid, whether or not ther is an issue, I always prepare for the worst.  Having an awareness that we might need to refactor something means we are thinking ahead and may have better solutions, or ways to strengthen current solution to answer concerns.17:33
davidlenwellrockyg: I think its the solution.. its how openstack projects authenticate between client and sever .. its ludicris for us to discuss doing it any other way.17:34
davidlenwelldiscussion over.17:34
davidlenwellwe'll work out the how later17:34
rockygcoom channels17:35
rockygcomm17:35
davidlenwellOver a month ago I implimented a new policy called specs17:35
davidlenwellin general we've started to head down the right path with them. working out the how before writing code and having to work in a lot of refactors.17:36
davidlenwellI know its an od idea.. but this is how projects in the ecosystem are dealing with distributed teams .. and for nova and others it has been very effective.17:36
davidlenwellI believe it can be for us.. But we all need to get on board with the work flow.17:37
davidlenwellit is very tempting to just want to work things out in f2f meetings..17:37
davidlenwellthe problem is our team is likely about to grow..17:37
davidlenwelland almost certainly the people we talk into jumping into the stream with us won't live in the bay area.17:37
rockygThe problem is that until we have a good foundation, we need to determine directions brefore we can drill down to the deail level of specs.17:38
davidlenwellSo we cannot rely on those meetings in order for progress to happen17:38
davidlenwellrockyg: .. yes you can17:38
davidlenwellwrite down how you see it and submit it for review17:38
davidlenwellif you are wrong you will be corrected17:38
rockygNo.  You casnt'.  Until we know the requirements, specs don't mean much because req17:38
rockygs are the foundation.17:38
davidlenwellthe very first part of the spec should be a list of requirements17:39
davidlenwellthe problem is this process needs to work async17:39
davidlenwellotherwise we can't be productive ..17:39
zehicle_IMHO, there's a balance here and part of the reason for having f2f summits is to work out the top level issues and then use specs to make sure we have agreement17:39
rockyg++17:39
*** sankarshan_away is now known as sankarshan17:39
davidlenwellzehicle_: rockyg.. the specs work without the agreement17:39
catherineD++17:40
zehicle_davidlenwell, yes but not as quickly17:40
rockygHow many different specs do we have for TCUP?17:40
davidlenwellzehicle_: we can't always rely on face to face or phone calls17:40
davidlenwellI hope a lot17:40
davidlenwellthats the point of it17:40
rockygI mean alreday?17:40
davidlenwellits called a "process"17:40
davidlenwellone spec has been written .. and its been merged17:41
zehicle_davidlenwell, I agree!  I think with the summit looming it's easy to say next week.17:41
*** sadasu has quit IRC17:41
davidlenwellrob didn't need us to tell him what to write in the first version.. he wronte it17:41
davidlenwellthen we all jumped in and commented on it17:41
davidlenwelland then he refined it17:41
rockygAnd it got trashed.  And written aggain.  And trashed.  And never checked in.17:41
davidlenwellwe all have full time jobs and we live all over the world17:41
* zehicle_ <3 being the positive role mode *blush*17:41
davidlenwellrockyg:  its merged now17:41
davidlenwellit did get checked in17:42
rockygWe are not working effectively because we don't have enough info to do so.17:42
davidlenwellrather it will be because of how zehicle_ submitted it we have to merge something else first that wasn't rebased the right way .. now thats fixed and its in17:42
davidlenwellif used propperly this allows the team to work async and distributed .. which is how openstack projects work17:43
davidlenwellwe are not all under the same roof17:43
davidlenwellwe all have different time zones and schedules and personal responsibilites17:43
davidlenwellwe can't always sysnc up on the phone or in person and we cannot rely on that to make progress17:43
davidlenwellthat is what this process was designed to solve17:43
rockygI underrstand thaat and have actually worked with teams that weay before.  I've managed off shore teams and had them work with teams here.  We were very productive.17:44
davidlenwellwhere there 12 differnet employers involved in 8 time zones ?17:44
catherineDWe only have about 15 mins left.  I think we should discuss summit meet up and prep for the session ... who is presenting and at the center chair etc ...17:44
davidlenwellthats how openstack projects go17:44
davidlenwellI am17:44
rockygBecaue we were all on the same page.  To get there, we had a foundational understanding of what we were doing.17:44
davidlenwellrockyg: lets talk about this offline ..17:44
davidlenwellcatherine is right it is time to move on17:45
davidlenwellrefstack meetups at summit17:45
davidlenwell#topic refstack meetups at summit17:45
*** openstack changes topic to "refstack meetups at summit (Meeting topic: refstack)"17:45
rockygI'm going to call the f2f working session at11:30am Monday in the infra pod.17:45
davidlenwellI won't be there17:45
*** jamie_h has quit IRC17:46
davidlenwellflight doesn't land until 3pm on monday17:46
rockygK.17:46
*** jamie_h has joined #openstack-meeting-317:46
*** Rajeev has quit IRC17:46
rockygThere's lots we can work on without you.  Not the pres. unless you give us direction for thaat.17:46
davidlenwellrockyg: I'd preffer to be present for meetups regarding this project17:46
rockygWe can get supporting stuff together if you give us pointers, though.17:46
davidlenwellits coutner productive otherwise17:47
rockygNo it's not.  we can work on specs.17:47
davidlenwellI've got the session it self planned..17:47
rockygWe can research keystone.17:47
davidlenwellyou could do that without a f2f17:47
catherineDdavidlenwell: That is good ... so you will be at the center chair and we will be on first row ...17:47
davidlenwellyes17:48
davidlenwellI have slides and diagrams and a whole thing planned .. you'll love it17:48
davidlenwellthen we'll do q/a17:48
davidlenwellq and a17:48
rockygDo you need anything beyond your lapop and a projector for the pres?17:48
davidlenwellno17:48
davidlenwellI do not17:48
catherineDand you have stuff (slide , lauchpad ..) ready ...17:48
davidlenwellyes I do17:48
catherineDthat is good ....17:48
rockygkewl.17:48
davidlenwellstill putting images and stuff together for it and refining diagrams17:48
*** krotscheck has quit IRC17:49
rockygPraveen, will you be at summit?17:49
davidlenwellas far as meetups are concerned17:49
davidlenwellI'd be open to a team breakfast .. or us eating lunch together on tuesday before the session17:49
zehicle_+117:49
davidlenwellwe also have the session it self to use fot planning and discussion .. that is what it is for17:49
rockyg+117:49
*** krotscheck has joined #openstack-meeting-317:50
zehicle_Breakfast w/ the board is Wed.  would be cool to have you (all) there too17:50
*** chuckC has joined #openstack-meeting-317:50
davidlenwellalso you should all note that at 5:30 pm there is another session that concerns us17:50
rockygWe need to try to get meeting with QA so that we get better comm channels re; tempest17:50
catherineD+1 say we meet for lunch how do we connect and know the table location ?17:50
davidlenwellcatherineD: we'll jump into irc and figure it out17:50
davidlenwellsince none of us know the venue now its silly to pick a meeting place here17:51
davidlenwellthe conf has wifi .. we should all be prepared to use irc while there and probably follow each other on twitter17:51
davidlenwell@davidlenwell is me17:51
praveen_dell] <rockyg>you didn't approve me for summit17:51
praveen_dell] <rockyg> sorry my boss didnt approve me for summit :)17:51
davidlenwellboo zehicle_17:51
zehicle_was not me17:52
rockygThe pods.  Infr has one.  We can try to sign up for it Tuesday lunch time on Monday.17:52
davidlenwellwell maybe he can come to paris17:52
* zehicle_ activities != Dell activities17:52
davidlenwellrockyg: we don't need a pod17:52
rockygIt's a lovation.17:52
davidlenwellI don't know how much time you ahve spent at a summit17:53
rockyglocation.  Just sayin17:53
davidlenwellbut finding meeting space is really easy17:53
davidlenwellwe designed most of tripple o sitting in a hall way in san diego17:53
rockygWhich session 5:30 Tues?17:53
davidlenwellthere are hotel lobby's and couches and eating tales all over17:53
rockygTest natrices and feature parity?17:53
*** SumitNaiksatam has joined #openstack-meeting-317:53
davidlenwellhttp://junodesignsummit.sched.org/event/fd84ec7ddc3252270fb73e8e9e09cfba#.U2vEt61dUa017:54
davidlenwellyes17:54
davidlenwell#link http://sched.co/1h3Xca917:54
rockygAlready in personal schedule ;-)17:54
davidlenwellmine too17:54
davidlenwellI'll see you there17:54
*** mestery has quit IRC17:55
catherineDSo no meeting on Monday?17:55
*** mandeep has joined #openstack-meeting-317:55
rockygWith lots of questions in hand.  That may spur the conversattion to better sync us to temprst17:55
davidlenwellI won't be in town until the afternoon ..17:55
*** mestery has joined #openstack-meeting-317:55
davidlenwellrockyg: we'll just see when we are there17:55
rockygWe can still do Monday.  We can work on getting specs cleaned up and filed.  Or teesting and filing bugs.17:55
davidlenwellour long term goals are to be an infra project17:55
zehicle_I need to build a sched but I never manage to get where I'm going17:56
davidlenwellyou guys are free to meet up and work without me.. wouldn't consider them meetings17:56
zehicle_so it's like a tasty desert that I never get to eat17:56
davidlenwellzehicle_: I'll rangle you around on tueaday .. covers most of the refstack things17:56
rockygSo that fits meeting should be on tuesday or later.  Tuesday is tight so, Wednesday?17:56
zehicle_once I make it to the design summit, I can usually seek in17:57
davidlenwellwhat fits meeting ?17:57
rockygOr we could just announce we'll be hanfging out somewhere for some timeperiod for q/a17:57
davidlenwelllets move offline .. we're out of time in here17:57
davidlenwell#endmeeting17:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:57
openstackMeeting ended Thu May  8 17:57:58 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-08-17.01.html17:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-08-17.01.txt17:58
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-08-17.01.log.html17:58
zehicle_gotta drive home and eat.  then back in #refstack.  nice work davidlenwell17:58
*** rkukura has joined #openstack-meeting-317:58
*** tedchang has quit IRC17:59
*** Sukhdev has joined #openstack-meeting-317:59
*** catherineD has left #openstack-meeting-318:00
*** s3wong has joined #openstack-meeting-318:00
SumitNaiksatamrkukura banix s3wong mandeep: hi18:01
banixhi SumitNaiksatam and all18:01
s3wongSumitNaiksatam: hello18:01
s3wongand hello to everyone else18:01
SumitNaiksatamlets get started18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu May  8 18:01:42 2014 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
*** rockyg has left #openstack-meeting-318:01
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:01
SumitNaiksatam#topic GP bp spec review18:02
*** openstack changes topic to "GP bp spec review (Meeting topic: networking_policy)"18:02
*** thinrichs has joined #openstack-meeting-318:02
SumitNaiksatam #link https://review.openstack.org/#/c/8946918:02
SumitNaiksatamthis was merged18:02
SumitNaiksatamthanks all for contributing and working towards this18:02
SumitNaiksataman important milestone in the process18:02
banixSumitNaiksatam: great. thanks to you for all your work as well18:03
SumitNaiksatambanix: thanks, great team effort18:03
SumitNaiksatamso we have to transition to the next step for pushing the patches18:03
rkukurahi18:03
SumitNaiksatamrkukura: hi18:04
SumitNaiksatamwe are obviously already working towards that18:04
mandeepSumitNaiksatam: hi18:04
SumitNaiksatammandeep: hi18:04
SumitNaiksatamour PoC is a step in that direction18:04
SumitNaiksatamlets first touch quickly on the model18:04
SumitNaiksatam#topic Policy Model18:04
*** openstack changes topic to "Policy Model (Meeting topic: networking_policy)"18:04
SumitNaiksatamwe made some minor tweaks18:05
SumitNaiksatami am referring to the EPG to Contract relationship change18:05
SumitNaiksatammost of you already know this18:05
*** Louis_ has joined #openstack-meeting-318:05
SumitNaiksatamjust reiterating here18:05
*** prasadv has joined #openstack-meeting-318:05
SumitNaiksatamthe ContractProvider/ConsumerScope is now optional when specifying the relationship18:06
*** marun has joined #openstack-meeting-318:06
SumitNaiksatamso you can say EPG X consumes/provides Contract Y (without having to create the relationship object)18:06
SumitNaiksatamthis probably makes it much simpler and easier to incrementally consume this model18:07
banixI agree18:07
SumitNaiksatambanix: thanks, yeah i mostly heard everyone in agreement with this change18:07
*** davidlenwell has quit IRC18:07
Louis_so a contract can consume a list of EPGs?18:07
SumitNaiksatamLouis_: er…its the other way around18:08
mandeepYes, agreed18:08
SumitNaiksatammandeep: ok18:08
SumitNaiksatamLouis_: EPGs can consume one or more Contracts18:08
*** davidlenwell has joined #openstack-meeting-318:09
SumitNaiksatamok, just wanted to highlight that change18:09
SumitNaiksatamif no other thoughts/questions, then moving on18:09
Louis_ok, so a EPG can provide one or more contracts?18:09
SumitNaiksatamLouis_: yes (and/or consume one or more contracts)18:10
*** SumitNaiksatam has left #openstack-meeting-318:10
s3wongwe lost SumitNaiksatam18:10
Louis_is this shown in an updated model diagram?18:10
*** SumitNaiksatam has joined #openstack-meeting-318:10
mandeepLet us wait for SumitNaiksatam to join18:10
Louis_is this shown in an updated model diagram?18:11
SumitNaiksatamsorry, i got bumped out18:11
SumitNaiksatamLouis_: yes18:11
SumitNaiksatamLouis_: see: https://docs.google.com/a/noironetworks.com/presentation/d/1Nn1HjghAvk2RTPwvltSrnCUJkidWKWY2ckU7OYAVNpo/edit?pli=1#slide=id.g1d6aae2d8_565118:11
SumitNaiksatamand: https://docs.google.com/a/noironetworks.com/presentation/d/1Nn1HjghAvk2RTPwvltSrnCUJkidWKWY2ckU7OYAVNpo/edit?pli=1#slide=id.g12c5a79d7_404418:11
SumitNaiksatamLouis_: looks okay?18:13
*** rudrarug_ has quit IRC18:13
SumitNaiksatamLouis_: perhaps we can come back to this18:13
SumitNaiksatam#topic PoC Status Update18:14
*** openstack changes topic to "PoC Status Update (Meeting topic: networking_policy)"18:14
SumitNaiksatam#info PoC branch is: https://github.com/noironetworks/neutron-group-policy/tree/group-policy-poc18:14
*** zehicle_ has quit IRC18:14
SumitNaiksatamwe are full steam ahead on this18:14
*** mwagner_ has joined #openstack-meeting-318:14
*** markmcclain has quit IRC18:14
SumitNaiksatamyesterday we created the first EPG and EP!18:15
SumitNaiksatamyay!18:15
mandeep+118:15
SumitNaiksatambaby steps18:15
s3wongamazing18:15
SumitNaiksatamthanks all18:15
SumitNaiksatamso as of now, EPG, EP, Contract, Policy Rule, Policy Classifier, and Policy Action resources are implemented18:16
SumitNaiksatamthis is what we will have in the first iteration18:16
mandeepIt was a significant integration across devstack, python-neutronclient + CLI, group-policy manager + plugin, ... so a good ene-toend flowe18:16
rkukuraalso BD and RD18:16
SumitNaiksatammandeep: +118:16
SumitNaiksatamrkukura: yes, thanks!18:16
SumitNaiksatamrkukura: i only keep thining about the app guy! :-P18:16
SumitNaiksatam*thinking18:16
rkukuraSumitNaiksatam: need to do a bit more of that myself ;)18:17
Louis_ok i see the provided_contracts/consumed_contracts list in the EPG REST table18:17
SumitNaiksatamrkukura: we need the balance :-)18:17
SumitNaiksatamLouis_: yes18:17
*** rudrarugge has joined #openstack-meeting-318:17
SumitNaiksatamon the model implementation, there are things which are not tested yet18:18
SumitNaiksatamlike the Contract hierarchy18:18
marunstill not on gerrit :p18:18
SumitNaiksatammarun: getting there :-)18:18
marunthat should be the first step, not the last.18:18
marunI guarantee patch review is going to be more complicated by this path.18:18
marunBut, sometimes lessons need to be learned the hard way :)18:19
SumitNaiksatammarun: well its not yet ready for gerrit yet, there are many moving peices and we are in teh process validating how well the peices fit18:19
SumitNaiksatammarun: hence this is called a PoC18:19
marundisagree entirely18:19
marunbut we can agree to disagree18:20
SumitNaiksatammarun: we dont want to waste reviewers cycles on things which are not baked18:20
marun'waste time'?18:20
marunyou mark it as 'WIP'18:20
SumitNaiksatammarun: absolutely18:20
marunor 'DRAFT'18:20
marunworking outside of gerrit limits visibility to the subteam, and that's not a good thing.18:20
marunit also encourages monolithic changes without oversight.18:21
SumitNaiksatammarun: disagree18:21
marunall of which will bite in actual review18:21
marunas you will see soon enough :)18:21
rkukuramarun: We could push the whole thing as a single WIP review on gerrit, but will probably want to push the real code in smaller chunks for review18:21
SumitNaiksatammarun: that sounds more like a threat!18:21
maruntake it as you will18:21
SumitNaiksatammarun: not a very constructive to phrase it18:21
SumitNaiksatamok moving on18:22
marunI hold all feature additions to the same standards.18:22
SumitNaiksatammarun: as does everyone else here18:22
marunIf only!18:22
SumitNaiksatamrkukura: over to you on the mapping implementation18:22
banixrkukura: can you give a two line brief description of the mapping work if you don’t mind18:23
SumitNaiksatamrkukura: great progress on the keeping in sync with the model changes18:23
*** praveen_dell has quit IRC18:24
rkukuraok18:24
rkukurabasically, the mapping does two things now:18:24
rkukurafirst, if an EPG is created without passing in a BD, one is implicitly created for the EPG18:25
rkukurasimilarly, if a BD is created (implicitly or explicitly) and no RD is passed in, a default RD for the tenant is created/found18:26
rkukurasecond, the RD is mapped to a neutron router, the BD is mapped to a neutron network, the EPG is mapped to  a neutron subnet, and the EP is mapped to a neutron port18:27
rkukuraso we were able to use the GP API to create an EPG, create an EP in it, and then get a port for EP and use it to launch  a nova VM18:28
banixthanks rkukura for the summary18:28
rkukurathat’s basically where the mapping stands18:28
rkukurawe’re starting to work on mapping the policy to SG and FW rules18:28
SumitNaiksatamalso some aspects of the mapping are configuration driven18:29
SumitNaiksatamrkukura: great summary18:29
Louis_why is there a 1-1 binding and a many-many association between a RD and a router?18:29
banixthe BD and RD are created implicitly. right? at least that is the desired workflow?18:29
SumitNaiksatambanix: yes18:30
rkukurabanix: either implicit or explicit BR and RD creation should work18:30
SumitNaiksatambanix: however its possible to provide them explicitly as well18:30
rkukuraLouis_: Right now, I think the mapping will use one router per RD18:30
banixok thanks18:30
SumitNaiksatamLouis_: RD to routers is 1:many18:30
rkukurawould be good to know if we really need multiple routers in a single RD18:31
Louis_i see in the code there is both a binding and an association18:31
SumitNaiksatamrkukura: there might be use cases18:31
SumitNaiksatamLouis_: good question18:31
*** markmcclain has joined #openstack-meeting-318:31
SumitNaiksatamLouis_: we want to remove the association18:32
rkukurawe allow multiple subnets per EPG in order to support adding more EPs than one subnet will hold18:32
*** eghobo has joined #openstack-meeting-318:32
s3wongrkurkura: certainly makes it easier for me to just fetch the router via context18:33
rkukuraagreed we should remove both association tables from the DB model if we can18:33
SumitNaiksatamrkukura: yeah18:33
SumitNaiksatamany more thoughts/questions on the mapping?18:34
rkukuras3wong: Unless we have a use case for the PoC, I think we should limit the PoC to one router per RD18:34
banixjust a general question on the model:18:34
SumitNaiksatamrkukura: yes, agree18:34
Louis_wouldn't it be better to remove the binding?18:34
*** devlaps has quit IRC18:34
s3wongrkukura: and I do not disagree with that :-)18:34
banixwe had discussed this early on but not recently. what is the connectivity within an EPG?18:35
Louis_and just have the association?18:35
SumitNaiksatamLouis_: its actually not a many:many to relationship18:35
SumitNaiksatamLouis_: RD to routers, that is18:35
rkukuras3wong: do you see an immediate need for multiple routers in the same RD? If so, we should talk about how we decide which one(s) the EPG’s subnets get connected to, which I’m working on today18:36
SumitNaiksatamrkukura s3wong: i think in the implicit workflow, one router is good18:36
s3wongrkukura: no, there isn't. We should focus on getting contract done. One per RD is definitely good for PoC18:36
SumitNaiksatambanix: EPs within EPG have connectivity18:37
*** devlaps has joined #openstack-meeting-318:37
banixSumitNaiksatam: they do in our implementation but in the model?18:37
SumitNaiksatambanix: this behavior can be overriden by setting attributes in teh BD18:38
rkukuras3wong: I see now that you said “I do not DISAGREE with that”, which I read as “I do not AGREE with that”18:38
SumitNaiksatambanix: yes, that is the current default semantics in the model as well18:38
s3wongrkukura: sorry - should have cap-lock the word :-)18:38
SumitNaiksatamrkukura: two negatives :-)18:38
SumitNaiksatambanix: any concerns with those semantics?18:39
rkukuraneed to take it easy on us native English speakers ;)18:39
banixSumitNaiksatam: ok we can disucss more later18:39
s3wongrkukura SumitNaiksatam: my crooked English... :-(18:39
SumitNaiksatams3wong rkukura: :-)18:39
rkukuraI just need to read more carefully18:39
banixSumitNaiksatam: not a big concern but in general the app developer expectation may be different18:39
SumitNaiksatambanix: ok, any examples?18:40
banixSumitNaiksatam: app servers in a tier may not need talking to each other18:40
SumitNaiksatambanix: ok18:40
SumitNaiksatamso the proposal was to put attributes in the BD, which can define that behavior18:41
rkukurabanix: As I recall, SGs have an implicit rule allowing all traffic within the subnet. Not sure if we’d be able to use the existing SG API to limit this.18:41
banixSumitNaiksatam: i think in the model we may want to have the default as no connectivity but i realize in the mapping driver we may not be able to do that18:42
banixrkukura: yes i understand18:42
SumitNaiksatambanix: we can probably have attribute in the BD, like “ISOLATED” (probably not a a good name)18:43
SumitNaiksatambanix: and its setting can be driven by configuration18:43
banixsure let’s discuss at the summit or after the summit18:44
SumitNaiksatambanix: if the default BD creation is with this attribute set, then we can support that behavior18:44
SumitNaiksatambanix: that way we dont ahve to set it for the ref impl18:44
SumitNaiksatambanix: ok18:44
banixSumitNaiksatam: ok18:44
SumitNaiksatamrkukura: thanks!18:44
SumitNaiksatamfor the update18:44
SumitNaiksatams3wong: over to you for the service integration18:45
s3wongWorking on the code now. Couple things I want to raise here, to ensure I am on the right path18:45
*** otherwiseguy has quit IRC18:45
*** BrianB_ has quit IRC18:45
s3wong(1) since the API is REDIRECT -> [the actual service UUID]. I don't see a need to add anything on the mapping db18:46
SumitNaiksatams3wong: agree (at least for PoC)18:46
s3wongso what it amounts to would be writing out the create_policy_action_postcommit18:46
SumitNaiksatams3wong: well let me take that back18:46
s3wongSumitNaiksatam: yes?18:47
SumitNaiksatams3wong: how would we undo the action, when we remove the contract?18:47
SumitNaiksatams3wong: never mind, that will still work, becaue the uuid will still be in the contract18:47
s3wongSumitNaiksatam: for now? update_firewall to disable it from router18:47
s3wongand yes, the UUID would still be in the db18:47
SumitNaiksatams3wong: sorry, you are right, i think it will work18:47
s3wong(just not the mapping db)18:48
s3wong(2) this is really question for SumitNaiksatam: is update_firewall the right call to enable FW?18:48
SumitNaiksatams3wong: yes18:49
s3wongmy understanding (via reading FW code yesterday) is, there is one instance of FWaaS per tenant18:49
SumitNaiksatams3wong: one can also enable at the granularity of the rule level (but not needed here)18:49
s3wongso it would automatically be enable on all the routers belonging to the tenant?18:50
SumitNaiksatams3wong: yes, one per tenant18:50
SumitNaiksatams3wong: i think default might be that its enabled by default18:50
SumitNaiksatams3wong: but while creating the firewall, i think you can set the admin state to be down18:50
SumitNaiksatams3wong: so although the firewall is there on each router, its not enabled18:51
s3wongSumitNaiksatam: OK - so it case the policy_action is removed, I just set the admin state of the FW to down to remove the redirect action?18:51
rkukuras3wong: wouldn’t that effect all traffic for the tenant, not just traffic for that one action?18:52
Louis_but what of mulitple contracts use that FW instance?18:52
SumitNaiksatams3wong: yes, the iptables rule should get removed18:53
s3wongrkukura: yes - unfortunately we need to complete the work of service insertion and steering to change this behavior18:53
*** emagana has quit IRC18:53
banixLouis_: i think for now only one contract using the fw is ok18:53
SumitNaiksatamLouis_, rkukura: yes as s3wong mentioned, this has much broader scope18:53
Louis_agree for the poc18:53
SumitNaiksatamthe current discussion is in teh context of the PoC18:53
s3wongLouis_: for PoC, I think it is fine18:53
SumitNaiksatamLouis_: yesh18:53
mandeepLouis_: And we need to get started in parallel with the services work that is also still in discussion18:54
SumitNaiksatammandeep: yes18:54
s3wongmandeep Louis_: with pretty much the same people in that subteam :-)18:54
SumitNaiksatamLouis_: thats a whole other discussion that is happening in parallel18:54
*** emagana has joined #openstack-meeting-318:54
mandeeps3wong: :-)18:55
*** sankarshan is now known as sankarshan_away18:55
mandeeps3wong: At least marun will be happy that it is not a monolithic change18:55
marun:)18:56
*** Cathy_ has joined #openstack-meeting-318:56
SumitNaiksatamok moving on18:56
SumitNaiksatam#topic CLI and Client18:56
*** openstack changes topic to "CLI and Client (Meeting topic: networking_policy)"18:56
SumitNaiksatamHemanth made greate progress18:56
SumitNaiksatam*great18:56
SumitNaiksatamhe could not attend today18:56
SumitNaiksatambanix followed that up with quick progress as well18:56
s3wongbanix would have to proxy hemanthravi :-)18:57
SumitNaiksatambanix: thanks for jumping in yesterday and pushing out the patch yesterday night18:57
mandeep+1 That was phenomenal, first pass integration ;-)18:57
mandeep+1, thanks banix18:57
banixsure18:57
Louis_will there be irc meeting next week?18:58
SumitNaiksatamLouis_: no meetings next week18:58
*** emagana has quit IRC18:58
SumitNaiksatam#announcement no Group policy IRC meeting next week18:58
SumitNaiksatambefore s3wong demands that it be made official :-P18:58
SumitNaiksatamthanks mandeep for the cue!18:58
Louis_but there is design session at summit18:58
SumitNaiksatamLouis_: yes18:59
*** emagana has joined #openstack-meeting-318:59
SumitNaiksatamdesign summit session discussion is on the agenda18:59
SumitNaiksatambut we have not gotten to it18:59
s3wongone minute to our next meeting :-)18:59
SumitNaiksatamgot distracted with some unnecessary discsussions earlier!18:59
SumitNaiksatamis ronak here?19:00
SumitNaiksatamperhaps not.19:00
SumitNaiksatamwe probably have to yield to the next meeting19:00
SumitNaiksatamso lets call it a wrap19:00
SumitNaiksatamthanks all for the awesome work19:00
SumitNaiksatamsee you at the summit next week19:00
SumitNaiksatamsafe travels!19:01
SumitNaiksatam#endmeeting19:01
mandeepthanks19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu May  8 19:01:09 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-08-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-08-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-08-18.01.log.html19:01
rkukurathanks SumitNaiksatam!19:01
banixbye19:01
rkukurabye19:01
s3wongthanks!19:01
*** mandeep has left #openstack-meeting-319:01
s3wongbye19:01
*** rkukura has left #openstack-meeting-319:01
*** sadasu has joined #openstack-meeting-319:01
*** sadasu has quit IRC19:01
*** Cathy_ has quit IRC19:02
*** thinrichs has quit IRC19:03
*** eghobo has quit IRC19:04
*** sankarshan_away is now known as sankarshan19:07
*** eghobo has joined #openstack-meeting-319:08
*** peristeri has quit IRC19:15
*** ttrifonov_zZzz is now known as ttrifonov19:20
*** eghobo has quit IRC19:27
*** Louis_ has quit IRC19:33
*** glenc has joined #openstack-meeting-319:39
*** zehicle_at_dell has joined #openstack-meeting-319:42
*** jamie_h has quit IRC19:43
*** eghobo has joined #openstack-meeting-319:44
*** krotscheck has quit IRC19:50
*** krotscheck has joined #openstack-meeting-319:51
*** d0ugal has quit IRC19:51
*** chuckC has quit IRC19:54
*** otherwiseguy has joined #openstack-meeting-319:56
*** zehicle_at_dell has quit IRC19:56
*** markmcclain has quit IRC19:58
*** marun is now known as maru_afk19:58
*** Sukhdev has quit IRC19:59
*** markmcclain has joined #openstack-meeting-320:01
*** devlaps has quit IRC20:02
*** markmcclain1 has joined #openstack-meeting-320:03
*** markmcclain has quit IRC20:06
*** julim has quit IRC20:08
*** devlaps has joined #openstack-meeting-320:10
*** prasadv has quit IRC20:12
*** ttrifonov is now known as ttrifonov_zZzz20:15
*** eghobo has quit IRC20:16
*** scotty95747 has joined #openstack-meeting-320:32
*** s3wong has left #openstack-meeting-320:32
*** scott-millward has quit IRC20:34
*** eghobo has joined #openstack-meeting-321:06
*** lcheng_ has quit IRC21:07
*** emagana has quit IRC21:09
*** mwagner_ has quit IRC21:10
*** garyduan has quit IRC21:11
*** ttrifonov_zZzz is now known as ttrifonov21:13
*** emagana has joined #openstack-meeting-321:14
*** devlaps has quit IRC21:21
*** devlaps has joined #openstack-meeting-321:21
*** fredas has joined #openstack-meeting-321:23
*** fredas has quit IRC21:27
*** emaganap has joined #openstack-meeting-321:45
*** emagana has quit IRC21:47
*** terryw has joined #openstack-meeting-321:58
*** otherwiseguy has quit IRC22:00
*** markmcclain1 has quit IRC22:06
*** rudrarugge has quit IRC22:12
*** chuckC has joined #openstack-meeting-322:14
*** cgascoig has joined #openstack-meeting-322:25
*** eghobo has quit IRC22:29
*** cgascoig has quit IRC22:29
*** eghobo has joined #openstack-meeting-322:29
*** maru_afk is now known as marun22:32
*** mwagner_ has joined #openstack-meeting-322:35
*** markmcclain has joined #openstack-meeting-322:36
*** banix has quit IRC22:36
*** terryw has quit IRC22:40
*** beyounn has quit IRC22:59
*** cgascoig has joined #openstack-meeting-323:00
*** beyounn has joined #openstack-meeting-323:01
*** markmcclain has quit IRC23:02
*** cgascoig has quit IRC23:05
*** ttrifonov is now known as ttrifonov_zZzz23:09
*** markmcclain has joined #openstack-meeting-323:17
*** carl_baldwin has quit IRC23:23
*** marun is now known as maru_afk23:24
*** maru_afk has quit IRC23:25
*** marun has joined #openstack-meeting-323:25
*** edleafe has quit IRC23:26
*** marun has quit IRC23:26
*** marun has joined #openstack-meeting-323:27
*** edleafe has joined #openstack-meeting-323:28
*** cgascoig has joined #openstack-meeting-323:28
*** cgascoig has quit IRC23:33
*** eguz has joined #openstack-meeting-323:37
*** eghobo has quit IRC23:42
*** emaganap has quit IRC23:51
*** markmcclain has quit IRC23:54

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