Thursday, 2014-05-29

*** tomoe_ has quit IRC00:01
*** julim has quit IRC00:09
*** lcheng_ has quit IRC00:19
*** lcheng_ has joined #openstack-meeting-300:19
*** tomoe__ has quit IRC00:20
*** tomoe_ has joined #openstack-meeting-300:20
*** rgbkrk has quit IRC00:26
*** eguz has joined #openstack-meeting-300:28
*** eguz has quit IRC00:28
*** sunrenjie6 has joined #openstack-meeting-300:30
*** eghobo has quit IRC00:33
*** tomoe__ has joined #openstack-meeting-300:34
*** tomoe_ has quit IRC00:37
*** jtomasek has quit IRC00:38
*** chuckC has quit IRC00:38
*** yamahata has joined #openstack-meeting-300:41
*** chuckC has joined #openstack-meeting-300:42
*** lcheng_ has quit IRC00:43
*** banix has joined #openstack-meeting-300:43
*** chuckC has quit IRC00:47
*** nati_ueno has quit IRC00:50
*** tomoe__ has quit IRC00:52
*** tomoe_ has joined #openstack-meeting-300:53
*** TravT has quit IRC00:56
*** devlaps has quit IRC00:59
*** dkorn has quit IRC00:59
*** davlaps has quit IRC00:59
*** igordcard has quit IRC01:04
*** nelsnelson has quit IRC01:08
*** nelsnelson has joined #openstack-meeting-301:08
*** shakamunyi has quit IRC01:16
*** nati_ueno has joined #openstack-meeting-301:21
*** nati_ueno has quit IRC01:32
*** chuckC has joined #openstack-meeting-301:34
*** baojg has joined #openstack-meeting-301:35
*** nati_ueno has joined #openstack-meeting-301:42
*** nati_ueno has quit IRC01:42
*** yamahata has quit IRC01:43
*** yamahata has joined #openstack-meeting-301:43
*** garyduan has quit IRC02:06
*** garyduan has joined #openstack-meeting-302:07
*** tomoe__ has joined #openstack-meeting-302:09
*** tomoe_ has quit IRC02:12
*** beyounn_1 has quit IRC02:58
*** nelsnelson has quit IRC03:02
*** nelsnelson has joined #openstack-meeting-303:03
*** eghobo has joined #openstack-meeting-303:46
*** shakamunyi has joined #openstack-meeting-303:49
*** shakamunyi has quit IRC04:05
*** baojg has quit IRC04:07
*** baojg has joined #openstack-meeting-304:07
*** lcheng_ has joined #openstack-meeting-304:16
*** tomoe_ has joined #openstack-meeting-304:46
*** tomoe_ has quit IRC04:47
*** tomoe__ has quit IRC04:49
*** eghobo has quit IRC04:57
*** eghobo has joined #openstack-meeting-304:57
*** eguz has joined #openstack-meeting-304:59
*** tomoe_ has joined #openstack-meeting-305:02
*** shakamunyi has joined #openstack-meeting-305:03
*** eghobo has quit IRC05:03
*** banix has quit IRC05:12
*** shakamunyi has quit IRC05:14
*** tomoe_ has quit IRC05:16
*** lcheng_ has quit IRC05:25
*** ttrifonov_zZzz is now known as ttrifonov05:33
*** ttrifonov is now known as ttrifonov_zZzz05:34
*** nelsnelson has quit IRC05:40
*** shakamunyi has joined #openstack-meeting-305:40
*** lcheng_ has joined #openstack-meeting-305:48
*** shakamunyi has quit IRC05:50
*** xuhanp has joined #openstack-meeting-306:06
*** lcheng_ has quit IRC06:24
*** dkorn has joined #openstack-meeting-306:26
*** HenryG has quit IRC06:27
*** jtomasek has joined #openstack-meeting-306:33
*** HenryG has joined #openstack-meeting-306:33
*** dkorn has quit IRC06:35
*** ttrifonov_zZzz is now known as ttrifonov06:40
*** shakamunyi has joined #openstack-meeting-306:47
*** ttrifonov is now known as ttrifonov_zZzz06:50
*** shakamunyi has quit IRC06:59
*** ttrifonov_zZzz is now known as ttrifonov07:07
*** kashyap is now known as kashyap_lunch07:10
*** eguz has quit IRC07:22
*** shakamunyi has joined #openstack-meeting-307:25
*** kashyap_lunch is now known as kashyap07:29
*** shakamunyi has quit IRC07:36
*** xuhanp has quit IRC07:41
*** baojg has quit IRC07:58
*** shakamunyi has joined #openstack-meeting-308:03
*** shakamunyi has quit IRC08:14
*** baojg has joined #openstack-meeting-308:28
*** igordcard has joined #openstack-meeting-308:35
*** shakamunyi has joined #openstack-meeting-308:40
*** jcoufal has joined #openstack-meeting-308:46
*** tomoe_ has joined #openstack-meeting-308:47
*** tomoe_ has quit IRC08:47
*** sunrenjie6 has quit IRC08:52
*** sunrenjie6 has joined #openstack-meeting-308:52
*** shakamunyi has quit IRC08:52
*** sunrenjie6 has quit IRC08:57
*** shakamunyi has joined #openstack-meeting-309:19
*** armax has joined #openstack-meeting-309:19
*** shakamunyi has quit IRC09:31
*** shakamunyi has joined #openstack-meeting-309:58
*** jtomasek has quit IRC10:03
*** shakamunyi has quit IRC10:05
*** jtomasek has joined #openstack-meeting-310:05
*** samchoi has quit IRC10:07
*** tomoe_ has joined #openstack-meeting-310:16
*** HenryG has quit IRC10:41
*** jamie_h has joined #openstack-meeting-310:46
*** Youcef has quit IRC10:56
*** HenryG has joined #openstack-meeting-310:56
*** Youcef has joined #openstack-meeting-310:56
*** Youcef_ has joined #openstack-meeting-311:01
*** Youcef has quit IRC11:01
*** Youcef_ has quit IRC11:11
*** Youcef has joined #openstack-meeting-311:12
*** prad_ has joined #openstack-meeting-311:17
*** prad__ has joined #openstack-meeting-311:22
*** prad_ has quit IRC11:22
*** igordcard_ has joined #openstack-meeting-311:23
*** igordcard has quit IRC11:24
*** prad__ has quit IRC11:38
*** tomoe__ has joined #openstack-meeting-311:48
*** tomoe___ has joined #openstack-meeting-311:51
*** tomoe_ has quit IRC11:52
*** tomoe__ has quit IRC11:53
*** prad_ has joined #openstack-meeting-312:00
*** mwagner_lap has quit IRC12:02
*** tomoe_ has joined #openstack-meeting-312:10
*** tomoe___ has quit IRC12:12
*** prad_ has quit IRC12:14
*** prad_ has joined #openstack-meeting-312:15
*** baojg has quit IRC12:27
*** baojg has joined #openstack-meeting-312:28
*** baojg has quit IRC12:32
*** jtomasek has quit IRC12:42
*** yamahata has quit IRC12:51
*** jtomasek has joined #openstack-meeting-312:55
*** rkukura_ has joined #openstack-meeting-312:59
*** rkukura_ is now known as rkukura13:01
*** thomasem has joined #openstack-meeting-313:06
*** lblanchard has joined #openstack-meeting-313:07
*** jaypipes has quit IRC13:10
*** banix has joined #openstack-meeting-313:12
*** prad_ has quit IRC13:15
*** jaypipes has joined #openstack-meeting-313:16
*** shakamunyi has joined #openstack-meeting-313:16
*** banix has quit IRC13:16
*** shakayumi has joined #openstack-meeting-313:19
*** banix has joined #openstack-meeting-313:19
*** julim has joined #openstack-meeting-313:21
*** shakamunyi has quit IRC13:21
*** eghobo has joined #openstack-meeting-313:22
*** HenryG has quit IRC13:30
*** HenryG has joined #openstack-meeting-313:31
*** shakayumi has quit IRC13:34
*** carl_baldwin has joined #openstack-meeting-313:34
*** jamie_h has quit IRC13:38
*** kenhui has joined #openstack-meeting-313:40
*** banix has quit IRC13:43
*** yamahata has joined #openstack-meeting-313:44
*** shakayumi has joined #openstack-meeting-313:48
*** prad_ has joined #openstack-meeting-313:49
*** prad_ has quit IRC13:53
*** peristeri has joined #openstack-meeting-313:58
*** lsmola2 has joined #openstack-meeting-313:59
*** PaulMurray has joined #openstack-meeting-314:00
*** mfer has joined #openstack-meeting-314:01
*** PaulMurray has left #openstack-meeting-314:01
*** tomoe__ has joined #openstack-meeting-314:03
*** tomoe_ has quit IRC14:04
*** eghobo has quit IRC14:08
*** gangadhar has joined #openstack-meeting-314:08
*** rkukura has left #openstack-meeting-314:12
*** gangadhar has quit IRC14:12
*** nelsnelson has joined #openstack-meeting-314:16
*** eghobo has joined #openstack-meeting-314:23
*** eghobo has quit IRC14:24
*** lsmola2 has quit IRC14:25
*** lsmola2 has joined #openstack-meeting-314:28
*** david-lyle has joined #openstack-meeting-314:28
*** ttrifonov is now known as ttrifonov_zZzz14:33
*** xuhanp has joined #openstack-meeting-314:35
*** devvesa has joined #openstack-meeting-314:35
*** banix has joined #openstack-meeting-314:36
*** OSM has joined #openstack-meeting-314:37
*** nati_ueno has joined #openstack-meeting-314:37
*** jamie_h has joined #openstack-meeting-314:38
*** OSM has quit IRC14:40
*** yamamoto has joined #openstack-meeting-314:46
*** baojg has joined #openstack-meeting-314:53
*** nextone92 has joined #openstack-meeting-314:57
carl_baldwinhi all15:00
devvesahi15:00
yamamotohi15:00
*** gangadhar has joined #openstack-meeting-315:01
carl_baldwin#startmeeting neutron_l315:01
openstackMeeting started Thu May 29 15:01:06 2014 UTC and is due to finish in 60 minutes.  The chair is carl_baldwin. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"15:01
openstackThe meeting name has been set to 'neutron_l3'15:01
carl_baldwin#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
carl_baldwinJuno-1 is in about two weeks.15:01
*** Sudhakar has joined #openstack-meeting-315:01
carl_baldwinI’m not sure exactly what the date is.15:02
carl_baldwinJune 12th.15:02
carl_baldwin#link https://wiki.openstack.org/wiki/Juno_Release_Schedule15:02
carl_baldwinAlso, there will be two mid-cycle meetings.  One focused on nova/neutron parity and the other on LBaaS.15:03
carl_baldwin#link https://etherpad.openstack.org/p/neutron-juno-mid-cycle-meeting15:03
carl_baldwin#link https://etherpad.openstack.org/p/neutron-juno-lbaas-mid-cycle15:03
carl_baldwin#topic Bugs15:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:04
carl_baldwinAs you may have seen, there is a bug czar appointed for the neutron team.15:04
carl_baldwin#link https://wiki.openstack.org/wiki/NeutronBugs15:05
carl_baldwinI don’t see any new bugs for this subteam now but we’ll be going through them.15:05
carl_baldwin#topic l3-svcs-vendor-*15:05
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:05
carl_baldwinI don’t see pcm on.15:06
carl_baldwin#undo15:06
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x1f2eb10>15:06
carl_baldwin#topic bgp-dynamic-routing15:06
*** openstack changes topic to "bgp-dynamic-routing (Meeting topic: neutron_l3)"15:06
*** keshava-hp has joined #openstack-meeting-315:06
carl_baldwinnextone92: Hi15:06
nextone92Hi Carl15:06
keshava-hpHi15:06
nextone92Jaume has updated the latest version of the document and will provide feedback15:06
devvesaThere is just a new patch of the blueprint15:06
devvesawe have made several changes from the previous one15:07
carl_baldwinnextone92: Could you edit the topic in gerrit to bp/bgp-dynamic-routing15:07
carl_baldwinI look forward to seeing the changes.  Thanks for getting that up there.15:08
gangadharif we have some comments.. can we update in the doc?15:08
nextone92Sorry about that - topic will be updated correctly15:08
carl_baldwingangadhar: Yes, please do add comments to the doc in gerrit.15:08
gangadharok15:08
carl_baldwingangadhar: If you mean the google doc, nextone92 has closed comments on that so that the comments will be in the gerrit review.15:09
devvesai'll be aware of any comment, so I hope to give you quick feedback15:09
keshava-hpI have added some comments and submitted for BGP use case and BGP-VPN documents15:09
carl_baldwindevvesa: thanks for staying on top of it.15:09
carl_baldwinkeshava-hp: great15:10
carl_baldwinHave you guys had a chance to begin getting your hands dirty with a proof of concept yet?15:10
carl_baldwinI’m curious to see a comparison of the various BGP speakers that have been suggested.15:10
devvesabasic changes from the previous one is to add the idea of a new agent, as we talked in the summit and try to avoid protocol names (as BGP in table names and entities)15:11
*** pcm_ has joined #openstack-meeting-315:11
* pcm_ sorry, I'm late15:12
devvesacarl_baldwin: i can begin the development, yes15:12
carl_baldwin#action carl_baldwin to review blueprint15:12
devvesabut I haven't had the opportunity until now15:12
carl_baldwindevvesa: where do you think is a good place to begin?15:12
devvesaI think I have to start with the agent that implements the BGP functionality15:13
devvesaand that would be a good chance to try BGP speakers15:14
devvesa(understanding BGP speaker as an implementation of the API that the agent will expose)15:14
carl_baldwindevvesa: Sounds reasonable.  Could you add a few items to the “Work Items” section in the bp?15:15
devvesaok15:15
*** BrianB_ has joined #openstack-meeting-315:15
devvesa#action devvesa to ad work items at bp15:15
keshava-hpHi, when we do BGP we are thinking these CN Nodes = CE ( BGP-VPN Scenario) ? or only adding BGP routing ?15:15
carl_baldwinPlease review the blueprint15:15
carl_baldwin#link https://review.openstack.org/#/c/9083315:16
carl_baldwinnextone92: devvesa: anything else to discuss?15:16
nextone92Looking forward to the team feedback15:16
carl_baldwin#topic l3-svcs-vendor-*15:16
*** openstack changes topic to "l3-svcs-vendor-* (Meeting topic: neutron_l3)"15:16
carl_baldwinpcm_: hi15:16
pcm_hi!15:16
pcm_Been trying to split out validation for VPNaaS. Hit some problems with initial approach. Trying another approach now, that is working better.15:17
carl_baldwinI see your blueprint is marked WIP.  So, I haven’t spent much time looking at it.15:17
carl_baldwinpcm_: did you get what you need out of the ML discussion?15:18
pcm_carl_baldwin: I think so... some is moot point as cannot really do validation before persistence15:18
pcm_carl_baldwin: Need to do from within persistence (to handle case of multiple clients changing same config)15:19
pcm_so, no issue of pre/post commit vs validate/apply.15:19
pcm_I've got validation separated for one API and am trying to modify vendor code to see if I can override.15:20
pcm_looks promising.15:20
carl_baldwinSounds good.  Let us know when you have something to look over.15:20
pcm_Once I get one API done, I can put out as WIP.15:20
pcm_For some early feedback.15:21
*** Sudhakar has quit IRC15:21
carl_baldwinpcm_: That’ll be good.  Anything else?15:21
pcm_carl_baldwin: Made a bug for the client side validation removal, but no action on it yet.15:22
pcm_carl_baldwin: That's all for me.15:22
carl_baldwinpcm_: Could you paste a link here for the bug just for reference?15:22
*** gangadhar has quit IRC15:23
pcm_sure. I'll look it up...15:23
carl_baldwinroaet_: ping15:23
*** tomoe_ has joined #openstack-meeting-315:25
carl_baldwinSorry I’m kind of rushing through the topics this morning and leaving a few off.  I want to have time to discuss DVR when Swami joins.15:25
keshava-hpBGP summarlization also we have plan to add ?15:25
*** kenhui has quit IRC15:25
pcm_#link https://bugs.launchpad.net/python-neutronclient/+bug/132265915:25
carl_baldwinpcm_: Right, I was looking in the neutron bugs even knowing it was a client bug.15:26
carl_baldwin#topic Open Discussion15:26
*** openstack changes topic to "Open Discussion (Meeting topic: neutron_l3)"15:26
pcm_carl_baldwin: Yeah, took me a bit to get to the right queue15:26
carl_baldwinWe’ll move to DVR when Swami is on.15:26
*** tomoe_ has quit IRC15:26
*** tomoe_ has joined #openstack-meeting-315:27
*** nati_ueno has quit IRC15:27
carl_baldwinkeshava-hp: I don’t understand the question, could you elaborate?15:27
*** tomoe__ has quit IRC15:28
*** mwagner_lap has joined #openstack-meeting-315:28
yamamotohow about creating a bgp speakers comparison chart somewhere eg. on wiki?15:28
nextone92Sounds good - maybe we could reuse the etherpad?15:29
nextone92https://etherpad.openstack.org/p/juno-dynamic-routing15:29
devvesayamamoto: that would be good. I think is the best moment to do it15:29
carl_baldwinyamamoto: I would like to see that.  Would you mind getting a wiki page started?  Add a link to it in the bp?15:29
keshava-hpwhen there are many prefix from multiple Nodes, then it possible to aggregates routes and advertize to peer speaker. This will help to reduce number of route entries in the upstream BGP. This will also help to reduce route flapping when a particular VM prefix is withdraw15:30
carl_baldwinI’m okay with wiki or etherpad.15:30
devvesacarl_baldwin: btw, we think we can have the development ready for j15:30
yamamotoi can create a wiki.  any suggested url?15:30
devvesajuno-315:30
yamamotowiki is easier for a table than etherpad15:31
*** Swami has joined #openstack-meeting-315:31
devvesaagree15:31
carl_baldwin#action yamamoto will create bgp speaker comparison table on wiki and link from bp.15:32
carl_baldwinSwami: hi15:32
Swamihi15:32
carl_baldwin#topic neutron-ovs-dvr15:32
*** openstack changes topic to "neutron-ovs-dvr (Meeting topic: neutron_l3)"15:32
SwamiDVR progress update15:33
SwamiThe DVR spec was approved this week15:33
SwamiDVR is targetted for Juno Milestone 1.15:33
carl_baldwinYes, thank you for addressing comments very quickly.15:33
SwamiWe are still working on the SNAT part.15:33
SwamiIt seems that it might take another 5 working days to complete the SNAT portion.15:34
carl_baldwinSwami: does that come as a patch separate from the east/west and floating ip north/south?15:34
*** lcheng_ has joined #openstack-meeting-315:34
SwamiSo I was thinking about pushing just east-west first.15:35
SwamiAnd then later the FIP and SNAT together will be another patch.15:35
carl_baldwinIf so, I’d be thrilled to see the other stuff land for Juno-1 even before default SNAT lands.15:35
SwamiThat way we can target for reviewing and pushing the code for Juno Milestone 115:35
SwamiAlso to address any unit test issues and add any unit tests it would be easy to handle one at a time rather than all together.15:36
carl_baldwinCould fip and snat be separated in order to review the distributed north south earlier?15:36
SwamiBut this would be the worst case.15:36
SwamiNo right now we are not planning to split the fip and snat. They will go together.15:36
*** lsmola2 has quit IRC15:37
SwamiIf we have everything working for the North-South by next week, then we can push everything for Juno 1 milestone, otherwise we should have a back up plan.15:37
SwamiSo just targetting East-West will be the back up plan.15:37
SwamiDoes that sound reasonable.15:37
carl_baldwinSwami: when can you push the east / west code?15:38
SwamiYes I have already pushed the plugin code, Vivek is also addressing the comments on the ML2/OVS work for East-West.15:39
armaxit's my understanding that reviews here:15:39
armaxhttps://review.openstack.org/#/q/topic:bp/neutron-ovs-dvr,n,z15:39
armaxare addressing the east/west case15:39
armaxand they also introduce the api/model changes15:39
SwamiThen I will ask Mike and Murali to push in just the East-West for the L3 Agent and Scheduler part.15:39
armaxis there any review missing to the lot?15:40
carl_baldwinSwami: That will be great.15:40
*** lsmola2 has joined #openstack-meeting-315:40
Swamiarmax: No all the reviews should be in the same page.15:40
SwamiWe starting pushing everything earlier.15:40
carl_baldwinarmax: that link contains all of them.15:40
armaxcool15:41
SwamiBut to be safe and to have something to be merged for Juno 1 I am proposing that we might only push the East-West .15:41
armaxso if at least we get all of them by J115:41
armaxit's a good start15:41
SwamiYes that is my plan. Hopefully everything should fall in at the right time.15:41
SwamiCarl: For the next month I will be working in different time zone. I am on FTO, so will be working from India.15:42
carl_baldwinSwami: In your email to me yesterday you mentioned some patches that should be reviewed first.  I plan to add that to the how to wiki page that you created.  Are you okay with that?15:42
carl_baldwinSwami: Good to know.15:42
armaxswami: I can help you with https://review.openstack.org/#/c/84223/ if you like15:42
SwamiYes I wanted the "Base L3 Plugin Extension" code to be reviewed first since all other patches have dependency on it.15:42
Swamiarmax: Thanks15:43
armaxSwami: unless you have it almost ready15:43
carl_baldwinSwami: Is that the link that armax pasted ^15:44
armaxcarl_baldwin: I think it is15:44
Swamiarmax: The current patch that I uploaded last night has everything that is required for East-West, I still need to add unit test for the code that I added.15:44
Swamicarl: yes15:44
armaxSwami: feel free to poke me individually to coordinate efforts15:44
Swamivivek has also posted the L2 code.15:44
carl_baldwinGreat.  armax and Swami let me know if I can help.  I’ll stick to that review like glue.15:44
Swamiarmax: sure will do.15:44
*** rudrarugge has joined #openstack-meeting-315:45
armaxcarl_baldwin: I am sure you're not the only one ;)15:45
carl_baldwin#action carl_baldwin will document patch dependencies on the wiki for other reviewers.15:45
*** devvesa has quit IRC15:45
Swamicarl: Also the ML2 / OVS code is also posted for review. Vivek is addressing the review comments, that should also be addressed.15:45
carl_baldwinIt is very encouraging to see that Jenkins gave it a +1.15:46
Swamithe other patches can follow these two patches.15:46
*** baojg has quit IRC15:46
SwamiYes I was working last night to make sure everything works. I have not broken any unit test as of now.15:46
carl_baldwinSwami: Great work.15:46
carl_baldwin#link https://review.openstack.org/#/c/87730/15:46
SwamiI will start to work on adding new test cases for handling the distributed one.15:46
carl_baldwinThis is Vivek’s ^15:46
Swamicarl: Yes that is vivek's patch.15:47
*** tomoe_ has quit IRC15:47
carl_baldwinIt needs a rebase.  Jenkins couldn’t merge it.15:48
SwamiI will speak to Murali and also ask him to push his scheduler code with my code as a dependency, so that everything for East-West will come through.15:48
carl_baldwinSwami: Sounds good.15:49
*** jcoufal has quit IRC15:50
carl_baldwinSwami: Is there anything more that you need from me or the subteam?15:50
Swamicarl: I will let you know if I need any help.15:51
SwamiFor now we might have to focus on these two reviews and try to finalize it.15:51
carl_baldwinI’m still trying to set up my multi-node test bed.  Our datacenter guys took my machines out from under me.  So, I had a little set back.15:51
*** jackib has joined #openstack-meeting-315:51
SwamiBy monday I will ask Mike and murali to push their updated code for review.15:52
carl_baldwinSwami: Sounds like a plan.  I may mark the other patches as WIP to keep them from drawing focus away from these two.15:52
SwamiOk, sounds good to me.15:53
armaxSwami: it's good to do it sooner rather than later so that in the process they can incorporate feedback while the patch shapes up15:53
carl_baldwinarmax: +115:53
Swamiarmax: Are you talking about the other two patches or the North/South.15:54
armaxSwami: mine it's more like a general comment, if the patches are really early stages then it's worth waiting a little more15:54
armaxbut I am assuming that's not the case15:55
carl_baldwinSwami: I have a question about https://review.openstack.org/#/c/9638915:55
carl_baldwinI have the feeling that this ^ should be squashed in to another patch.15:55
SwamiYes, that is the reason we had all our patches out there for a while now.15:55
Swamicarl: I have fixing a merge conflict issue with the HEAD. And unfortunately it ended up as a separate patch.15:56
armaxcarl_baldwin: I am taking this one over, I'll take care of it15:56
*** emagana has joined #openstack-meeting-315:56
carl_baldwinSwami: It has been helpful for me to see the early patches up there.  I have had a head start in understanding the code/patch structure.15:56
armaxcarl_baldwin: this one actually: https://review.openstack.org/#/c/84223/15:56
carl_baldwinarmax: Great.15:57
Swamiarmax: carl: thanks for your help.15:58
carl_baldwinSwami: yw.  Glad to help.  It is fun!15:58
armaxcarl_baldwin: I abandoned patch 96389 fyi15:58
carl_baldwinarmax: good15:59
carl_baldwinSwami: Anything else?15:59
*** shakayumi is now known as shakamunyi15:59
carl_baldwinThat’s a wrap.  Thanks everyone!16:00
armaxnone from me16:00
carl_baldwin#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Thu May 29 16:00:16 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-29-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-29-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2014/neutron_l3.2014-05-29-15.01.log.html16:00
pcm_ye16:00
pcm_bye16:00
yamamotobye16:00
*** pcm_ has left #openstack-meeting-316:00
Swamithanks carl.16:00
Swamibye16:00
nextone92Thanks!16:01
*** nextone92 has quit IRC16:01
*** xuhanp has quit IRC16:05
*** keshava-hp has quit IRC16:08
*** nati_ueno has joined #openstack-meeting-316:12
*** terryw has joined #openstack-meeting-316:14
*** otherwiseguy has quit IRC16:17
*** devlaps has joined #openstack-meeting-316:17
*** devlaps1 has joined #openstack-meeting-316:17
*** nati_ueno has quit IRC16:26
*** BrianB_ has quit IRC16:26
*** jackib has quit IRC16:28
*** emagana has quit IRC16:31
*** beyounn has joined #openstack-meeting-316:34
*** emagana has joined #openstack-meeting-316:37
*** catherine|2 has joined #openstack-meeting-316:42
*** yamamoto has quit IRC16:43
*** lsmola2 has quit IRC16:43
*** lcheng_ has quit IRC16:46
*** amotoki has quit IRC16:48
*** shivharis has joined #openstack-meeting-316:49
*** nelsnelson has quit IRC16:49
*** nelsnelson has joined #openstack-meeting-316:49
*** TravT has joined #openstack-meeting-316:50
*** ivar-lazzaro has joined #openstack-meeting-316:51
*** shivharis has left #openstack-meeting-316:53
*** rockyg has joined #openstack-meeting-316:54
*** SumitNaiksatam has quit IRC16:54
davidlenwell#startmeeting refstack16:57
openstackMeeting started Thu May 29 16:57:18 2014 UTC and is due to finish in 60 minutes.  The chair is davidlenwell. Information about MeetBot at http://wiki.debian.org/MeetBot.16:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:57
*** openstack changes topic to " (Meeting topic: refstack)"16:57
openstackThe meeting name has been set to 'refstack'16:57
*** zehicle_at_dell has joined #openstack-meeting-316:57
davidlenwellRoll call16:57
*** BrianB_ has joined #openstack-meeting-316:57
*** dhandy has joined #openstack-meeting-316:59
*** dhandy has quit IRC16:59
*** fcarpenter has joined #openstack-meeting-316:59
davidlenwellroll call?16:59
zehicle_at_dello/16:59
rockygo/16:59
fcarpentero/17:00
davidlenwellDo we have catherine|2?17:00
catherine|2yes17:00
davidlenwellexcelent17:00
davidlenwellagenda: storyboard, specs, f2f, open discussion17:00
davidlenwell#topic storyboard17:00
*** openstack changes topic to "storyboard (Meeting topic: refstack)"17:00
davidlenwellSo I spent some time in the last week getting to know storyboard.17:01
zehicle_at_dellcould we also talk about Havana vs Icehouse tempest?17:01
davidlenwellsure17:01
davidlenwellwe do that before specs17:01
davidlenwellso next17:01
davidlenwellwhile storyboard is an incomplete product.. I feel its as usable as launchpad.. and the storyboard team is very open to our feedback.17:02
zehicle_at_dell+117:02
davidlenwellI'll probably even commit some code it to my self.17:02
zehicle_at_dellwould like to have names instead of IDs in the URL, FWIW17:02
davidlenwellyep17:02
davidlenwellI filed a story for that on friday17:02
*** lenrow has joined #openstack-meeting-317:02
davidlenwellthey want it to17:02
davidlenwelltoo17:02
davidlenwellSo make sure when you are writing specs and making commits to reference your storyboard link.17:03
rockyggood point.17:03
davidlenwellfor those of you who didn't catch my emails to fits  .. storyboard is at storyboard.openstack.org17:04
zehicle_at_dellare all the blueprints migrated to storyboard at this pont?17:04
davidlenwellif you have not already .. go sign in for the first time so I can assign you work ;)17:04
fcarpenterwill you update restack.org to include that link?17:04
*** sarob has joined #openstack-meeting-317:04
davidlenwellzehicle_at_dell: yes17:04
rockygi've filed the story and will file spec later today17:04
davidlenwellfcarpenter: yes.. I will do that today.. there is actually a story that includes that task17:04
*** annegentle has joined #openstack-meeting-317:05
davidlenwellokay .. so thats that .. everyone on board with storyboard?17:05
davidlenwellany objections will need to be voiced now ;)17:06
catherine|2yes17:06
davidlenwellawesome.. moving right along..17:06
zehicle_at_dell+117:06
davidlenwell#topic icehouse vs havana tempest17:06
*** openstack changes topic to "icehouse vs havana tempest (Meeting topic: refstack)"17:06
sarobIt looks good17:06
davidlenwellso this should be short17:06
davidlenwelluse trunk tempest always .. moving along17:06
zehicle_at_dell+1 but want to talk about timing17:07
davidlenwellbranchless tempest is what we want.. when do we want it?  now17:07
zehicle_at_dellsince I know that we have to update TCUP17:07
davidlenwellI was actually surprised not to see a commit updating the version of tempest the tester is using17:07
davidlenwellbut I guess I can do that since I wrote that17:07
*** sarob_ has joined #openstack-meeting-317:07
davidlenwellzehicle_at_dell: I'll update that as soon as I finish writing my specs17:08
zehicle_at_dellthanks17:08
*** dhandy has joined #openstack-meeting-317:08
davidlenwellwhich I plan to have done in the next 24 hours17:08
zehicle_at_dellif we can get it running outside of tcyup that would be a good gate17:08
zehicle_at_dellbefore I work on making it work inside of it17:08
catherine|2there are about 600 testcase in for API in Havana... In Icehouse this number is about 2000+ ...17:08
davidlenwellcatherine|2: yes .. is that a problem?17:09
*** emaganap has joined #openstack-meeting-317:09
catherine|2no except for test time and extra configuration needed17:09
catherine|2I am trying to use master Tempest to test my Havana clouds ...17:10
davidlenwellcatherine|2: yes .. thats an issue.. but its an issue we have to solve refardless17:10
zehicle_at_dellare the test IDs the same?17:10
*** emagana has quit IRC17:10
zehicle_at_dellit would be a problem for defcor if not17:10
catherine|2test IDs --> full test case name ?17:11
zehicle_at_dellsince we need havana results for havana clouds17:11
zehicle_at_dellyy17:11
*** sarob has quit IRC17:11
catherine|2yes I think it is more a problem for DefCore ..17:11
*** SumitNaiksatam has joined #openstack-meeting-317:12
zehicle_at_dellit should be OK unless the test really changes funciton but keeps the same name17:12
catherine|2I am trying to take a inventory to see whether 1) full test name are retain ..2) what additional17:12
zehicle_at_dellwhich I think would have much more serious implications17:12
davidlenwellcatherine|2: good thinking17:12
catherine|2I don't think so but I am trying to verify with Havana cloud before going to Icehouse cloud ..17:12
davidlenwellSo there is no icehouse tempest .. just to be clear17:13
davidlenwellafter havana its branchless17:13
zehicle_at_delldavidlenwell, I think moving to trunk tempest is the right thing but it's a bit of scope creep for Havana17:13
catherine|2just using the sme master tempest for both Havana and Icehouse cloud ...17:13
zehicle_at_delltotally able to justify, we just need to be transparent17:13
davidlenwellof course17:13
* zehicle_at_dell is thinking about impact on reports and happy to have single tempest17:14
catherine|2since I have lots of data from testing havana tempest with havana cloud17:14
davidlenwellI don't want to keep focusing on havana tempest17:14
catherine|2I can make tht comparison ..17:14
zehicle_at_delldavidlenwell, +117:14
zehicle_at_dellIt seems to me that we17:14
zehicle_at_dellare ok as long as the IDs are consistent17:14
zehicle_at_dellsince that's the ultimate handle we're using, not the source17:14
davidlenwelleven if they are not .. we have to find a way to migrate17:14
davidlenwellbranched tempest is a thing of the past17:15
zehicle_at_dellif they are not, then it's even more urgent to move to the consinstent one17:15
davidlenwell+117:15
davidlenwellokay .. moving on17:15
zehicle_at_dellkk17:15
davidlenwell#topic specs17:15
*** openstack changes topic to "specs (Meeting topic: refstack)"17:15
catherine|2I am more concern about the consistency of test name/ID for core and capability test list17:15
davidlenwellso specs are rolling in.. catherine|2 I started to review the one you posted last night but my eyes didn't want to read anymore.. so I'll review it this morning.17:16
davidlenwellzehicle_at_dell: what is the status of your specs?17:16
zehicle_at_dellI'm working on the designs for both17:16
zehicle_at_dellmaking some progress on layout and approach17:16
davidlenwellDo you have an eta?17:17
zehicle_at_dellI'd be happy to upload partials if people want to see the problem statement17:17
zehicle_at_delltomorrow17:17
rockygI think partials would be informative17:17
zehicle_at_dellI think I've cracked the design for the comparison one17:17
davidlenwellI'd always like to see partials if you are into feedback17:17
zehicle_at_dellhappy to do that17:17
zehicle_at_dellwill upload by EOD for them17:17
davidlenwellexcelent17:17
davidlenwellwhat about your specs rockyg17:17
davidlenwell?17:17
rockygMatrix will be in today.17:18
davidlenwellyay!17:18
rockygLooks like you got the example unit test cooking?17:18
davidlenwelland catherine|2 has one more riht ?17:18
zehicle_at_dellI had a question about catherine|2 spec https://review.openstack.org/#/c/96311/17:18
davidlenwellrockyg:  I did17:18
catherine|2yes working on it17:18
zehicle_at_dellit looks like it overlaps w/ the other API upload spec17:18
zehicle_at_dellI called that out in review, but figured we could talk here if that helps17:18
rockygdavidlenwell: great on example unit test17:19
davidlenwellha ha test_nothing is a good start17:19
*** terryw is now known as otherwiseguy17:19
rockygDow we need a spec on breaking out the config into the three sections?  If so, we should do it cross project with storyboard.17:20
davidlenwellrockyg: not yet17:20
rockygCan storyboard do cross project?17:20
davidlenwellfor our imidiate porposes we are going to consider config a blackbox17:20
davidlenwellrockyg: yes it can17:20
rockygkewl x217:20
zehicle_at_dellone of the items I17:21
zehicle_at_dellnoticed in review was that we may want to have a client library for the API17:21
zehicle_at_dellso that we could use it from multiple places in the same way17:21
davidlenwellzehicle_at_dell: indeed17:21
rockygsounds right17:21
davidlenwelllets add a story for that17:21
davidlenwellassign it to me .. made the first task write a spec17:22
rockyg+117:22
davidlenwellnext topic17:22
davidlenwell#topic f2f17:22
catherine|2wait17:22
*** openstack changes topic to "f2f (Meeting topic: refstack)"17:22
davidlenwellyes catherine|2?17:23
catherine|2zehicle_at_dell:suggest we should merge the api--api-sync with an API upload spec?17:23
catherine|2I am open for that ..17:24
zehicle_at_dellcatherine|2, there are parts of it that overlap17:24
zehicle_at_dellbut I think you also have use-cases that are different17:24
zehicle_at_dellI'd suggest that we pull the API spec out and use the current one17:24
zehicle_at_dellbut leave in the refstack to refstack synch part17:24
zehicle_at_dellbecause that was distinct.17:24
catherine|2davidlenwell: I avouid the sync word ...17:25
zehicle_at_dell+117:25
zehicle_at_dellcould we call it "private refstack to public refstack push" ?17:25
catherine|2because I don't think we sync the data because both sides do not have identical data17:25
zehicle_at_dellI think that's the primary use case17:25
catherine|2zehicle_at_dell: +117:25
rockyggood point.  push sounds good to me.17:25
davidlenwell+117:26
davidlenwell"private refstack to public refstack push" seems like a better title17:26
zehicle_at_dellthat would make it easier for me to review.  I'll save additional comments for the revision17:26
zehicle_at_delllet's put "push" first now that I'm reading it back17:26
catherine|2so we change the story?17:26
catherine|2story title17:26
davidlenwellyep17:26
catherine|2+117:26
davidlenwellokay.. so moving on to face to face17:26
davidlenwellzehicle_at_dell: will be in town in june for a few days.. thought we should take the time and have a f2f17:27
rockygyup17:28
catherine|2+117:28
davidlenwellzehicle_at_dell: are your dates final ?17:28
*** csd has joined #openstack-meeting-317:28
zehicle_at_dellI have some flex if needed17:29
zehicle_at_dellbut they are getting pretty locked17:29
davidlenwellso I think the original plan was for us to get together at the piston office on the 11th17:29
zehicle_at_dellyy17:29
davidlenwellor am I off base?17:29
zehicle_at_dellthat's right.  defcore f2f is 12th17:29
zehicle_at_dellI was planning to be at CF summit on 10th17:30
davidlenwellexcelent .. fcarpenter can you reserve us a conf room that can hold 7 people comfortably?17:30
fcarpenteron 6/11?17:30
davidlenwellyes17:30
fcarpentertime of day,?17:30
davidlenwellI'd say noon to 6pm17:31
fcarpenteryes I can probably get panama17:31
rockygyou'll send out new address for us?17:31
fcarpenter126 Post St 5th Floor San Francisco CA 9410817:31
fcarpenterbut we'll send it out, too17:31
davidlenwellyeah .. we'll email fits with the info17:32
davidlenwellpanama would be great17:32
zehicle_at_delldo you want an etherpad for an agenda?17:32
davidlenwellzehicle_at_dell: yes17:32
* zehicle_at_dell making pad17:32
davidlenwellokay.. so im going to sneak in another topic here17:32
davidlenwell#topic swagger17:33
*** openstack changes topic to "swagger (Meeting topic: refstack)"17:33
davidlenwell#link https://helloreverb.com/developers/swagger17:33
zehicle_at_dell#link https://etherpad.openstack.org/p/refstack.2014-06-1117:33
davidlenwellthis is swagger.. I won't go into describing it because .. well they have done a good job of that17:33
davidlenwellit does do client generation .. but not currently in python.. however I'm told that is in the works.17:34
*** eghobo has joined #openstack-meeting-317:34
rockyginteresting....17:35
davidlenwellyes it is17:35
davidlenwellSo I'm going to put some serious thought into if and how we can use it.. will probably update the v1 api spec to include it if I think we need to use it17:36
rockygif it does what it says, it is tes cool.17:36
davidlenwellindeed17:36
davidlenwellwe shall see17:36
rockygtres17:36
davidlenwellso moving along.. one more sneak in topic17:36
davidlenwell#topic py26 gate is no more17:37
zehicle_at_dellI've got some parking lots....17:37
*** openstack changes topic to "py26 gate is no more (Meeting topic: refstack)"17:37
*** nati_ueno has joined #openstack-meeting-317:37
davidlenwellanyone who submitted a patch to refstack and payed attention to its testing might have noticed that I took py26 testing out of the gate.17:37
davidlenwellas I said I would a few months ago17:38
zehicle_at_dellI've noticed that we're faiing patches because we have no tests17:38
rockyghow does this work with havana refstack, or will the advisory status of H refstack suffice to let us do away with it?17:38
davidlenwellzehicle_at_dell: that is no longer true17:39
zehicle_at_dellrockyg, yes.  that's a general hall pass17:39
zehicle_at_delldavidlenwell, cool!17:39
davidlenwellI posted an empty test yesterday .. if you rebase your patch it will make it through17:39
davidlenwellI did send you a message on skype saying this17:39
* zehicle_at_dell ok, will do17:39
zehicle_at_dellyes, I saw and did rebase17:39
zehicle_at_dellI know that praveen had the same issue17:40
davidlenwellyes .. its because infra made a change on the 9th17:40
davidlenwell0 tests is no longer acceptable17:40
davidlenwellso now we have 1 tests17:40
davidlenwellteset17:40
davidlenwelltest17:40
davidlenwelltyping is hard17:40
rockygespecially when low on caffeine17:41
davidlenwell#topic open discussion17:41
*** openstack changes topic to "open discussion (Meeting topic: refstack)"17:41
zehicle_at_dellI've got a pending change to the coretest.json file17:41
zehicle_at_dellbased on DefCore discussion, it needed some more info17:41
*** rudrarugge has quit IRC17:41
zehicle_at_dellspecifically, the criteria description17:41
rockygright.17:41
catherine|2About the spec that only send passing data17:42
zehicle_at_dellalso needed to open it up a little so we could add scores17:42
davidlenwellyes catherine|217:42
davidlenwell?17:42
zehicle_at_dellwe need to enable people to post changes to single test criteria via gerrit for review17:42
catherine|2davidlenwell: is that just for TCUP .17:42
zehicle_at_delldoes that make sense?17:42
davidlenwellcatherine|2: no17:42
catherine|2I mean for data collection to determine core17:42
zehicle_at_dellcatherine|2, I think that we want the public refstack to only take pass results17:42
davidlenwellcatherine|2: that is for everything17:42
zehicle_at_dellwe may want private refstacks to also have fail tests17:43
davidlenwellwhich is why it includes an option for not scrubbing the data ..so you can use it inhouse without only submitting pass.17:43
zehicle_at_delldavidlenwell, +117:43
rockygAll test info needs to get scrubbed before sent to/added to refstack.org17:43
davidlenwellI did include that in the spec.. thanks to zehicle_at_dell and rockyg feedback17:43
catherine|2so from refstack.org point of view we only save passing dta no logs or raw data for debug ...17:44
davidlenwellcatherine|2: so you will also need to add that to your api-api sync17:44
*** tedchang has joined #openstack-meeting-317:44
zehicle_at_dellrockyg, if someone does send the wrong data, then I suspect we should scrub it again just in case17:44
rockygbut local copies not officially on refstack.org can have everything17:44
davidlenwellyes17:44
zehicle_at_dellperhaps we should 500 on uploads that have non-pass info17:44
zehicle_at_dellIMHO, that data could be toxic17:45
catherine|2so the scrub data ill be in a format that refstack define?  It is no longer a subunit defined format?17:45
rockygRight.  So, scrubbed in remote refstack and tcup  before upload then verified/rescrubbed on arrival at refstack.org17:45
davidlenwellcatherine|2: we should be able to keep it in subunit format17:45
rockygI think it's still subunit, but no tests left that fail or are skipped.17:46
zehicle_at_dellI'm backing away from rescrubbed.  I'd think to just bounce it17:46
davidlenwellzehicle_at_dell: I agree17:46
zehicle_at_dellwe don't want that information hanging out on public servers anywhere17:46
davidlenwellthe client submitting it will have the tools to scrub17:46
rockygagreed.17:46
davidlenwellwe don't want to liability17:46
catherine|2davidlenwell: that would be a big job ... essentially we are writing a different version ofr subunit output data ...17:46
davidlenwelllast thing I want is storys of how someones cloud was comprimised only after submitting data to refstack17:46
rockygbut it still means we need to verify it's prescrubbed.17:46
davidlenwellrockyg: thats easy enough17:47
rockygcool17:47
davidlenwellif it includes a fail .. its not scrubbed17:47
rockygor skipped17:47
davidlenwellskip == fail from our perspective17:47
zehicle_at_dell+117:47
rockygcan we insert a tag or some metadata in the subunit that will indicate the file has passed through our scrubber?17:48
davidlenwellcatherine|2: lets discuss that offline17:48
catherine|2yup17:48
zehicle_at_delldifferent topic > does anyone have a preference for wireframe tools?17:48
davidlenwellbalsamiq17:48
zehicle_at_dellkk, will check that you.17:48
davidlenwellSo everyone.. re: storyboard..17:50
davidlenwellas you are using it and you percieve an limitation .. please discuss it with them.. they are very open17:50
davidlenwelleither file a story .. or chat with them in #storyboard17:50
davidlenwellwe are an early adoptor17:50
davidlenwelland our feedback is very valuable to them17:50
krotscheckping me17:50
krotscheckVERY valuable17:51
krotscheckI love feedback.17:51
davidlenwellhi krotscheck17:51
krotscheckAlso, we JUST got our second +2, so things should move faster now.17:51
davidlenwellawesome news!17:51
davidlenwelllet the patches flow!17:51
rockygkk.  You know me, I'm not shy;-) you'll hear frim me.17:51
krotscheck…that sounds like a sewage metaphor.17:51
davidlenwellkrotscheck: it did didn't it17:52
krotscheckdavidlenwell: It really did.17:52
davidlenwellI'll be careful with that in the future17:52
*** emaganap has quit IRC17:52
davidlenwellanything else for open discussion?17:53
rockygI got nuthin17:53
zehicle_at_dellwe've got some backlog17:53
zehicle_at_dellof patches17:53
davidlenwellzehicle_at_dell: ping me in an hour or so and we'll sift through them17:53
davidlenwellnow that patches can land ..17:53
zehicle_at_dellok17:53
zehicle_at_dellreasonable17:53
*** emagana has joined #openstack-meeting-317:53
* sarob_ lurking still17:53
zehicle_at_dellthem I'm good17:54
davidlenwellsarob_: can you remind me of your real name?17:54
rockygsean roberts17:54
sarob_Sean Roberts17:54
davidlenwelloh thanks .. thats right17:54
davidlenwellsarob_: did you have any more thoughts on tempest config that we didn't already talk about at the summit?17:54
*** mandeep has joined #openstack-meeting-317:55
sarob_Not yet17:55
davidlenwellokay .. well don't be shy when youd o17:55
sarob_I've got too much plate17:55
*** mandeep has left #openstack-meeting-317:55
sarob_Or small plate17:55
davidlenwellsarob_: understood .. thanks for paying attention17:55
sarob_Either one17:55
rockygis the meetup in SV tonight?17:55
sarob_Yup17:55
davidlenwellmeetup?17:56
rockygIll be there.17:56
sarob_Bldg e training room 817:56
sarob_Cool17:56
rockygOpenStack "hackathon"17:56
rockygrecruiting tool17:56
sarob_I run the sfbay Openstack user group17:56
davidlenwelloh cool17:56
davidlenwellis there a link to more info?17:57
rockygI can email you the reminder....17:57
sarob_#link meetup.com/Openstack17:57
davidlenwellawesome .. thanks17:57
rockygbetter17:57
sarob_That works too17:57
davidlenwellokay everyone.. good meeting .. thanks for showing up and participating :)17:57
rockygvery productive today.17:58
sarob_#link http://meetup.com/Openstack17:58
zehicle_at_dell+117:58
rockygttfn17:58
sarob_Thx17:58
davidlenwell#endmeeting17:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:58
openstackMeeting ended Thu May 29 17:58:20 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-29-16.57.html17:58
*** fcarpenter has left #openstack-meeting-317:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-29-16.57.txt17:58
catherine|2pls send info about fa2f17:58
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-05-29-16.57.log.html17:58
*** rockyg has quit IRC17:58
zehicle_at_dell#link https://etherpad.openstack.org/p/refstack.2014-06-1117:59
*** rkukura has joined #openstack-meeting-317:59
*** yamahata has quit IRC17:59
*** hemanthravi has joined #openstack-meeting-318:00
*** banix has quit IRC18:01
SumitNaiksatamhi Group Policy team!18:01
hemanthravihi18:01
*** sarob_ has quit IRC18:01
*** thinrichs has joined #openstack-meeting-318:01
SumitNaiksatamlets get started18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu May 29 18:01:39 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
rkukurahi18:01
*** openstack changes topic to " (Meeting topic: networking_policy)"18:01
openstackThe meeting name has been set to 'networking_policy'18:01
*** banix has joined #openstack-meeting-318:01
thinrichsHi all18:01
SumitNaiksatam#info agenda: https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy18:01
banixhi18:02
SumitNaiksatam#topic Gerrit Reviews18:02
*** openstack changes topic to "Gerrit Reviews (Meeting topic: networking_policy)"18:02
SumitNaiksatamper the discussion last week, and based on reviewer preferences, the patches have been restructured18:02
*** prasadv has joined #openstack-meeting-318:02
*** mandeep has joined #openstack-meeting-318:03
SumitNaiksatamso we have started with the EP, EPG, L2/3_Context resources at the head of the series18:03
SumitNaiksatamthe API, DB, and Plugin patches for these are already in18:03
SumitNaiksatam#link https://review.openstack.org/#/c/9590018:03
SumitNaiksatam#link https://review.openstack.org/#/c/9605018:03
SumitNaiksatam#link https://review.openstack.org/#/c/9639318:04
*** OSM has joined #openstack-meeting-318:04
SumitNaiksatamthese will be backed with the mapping driver patches, that rkukura is working on18:04
*** OSM is now known as songole18:04
SumitNaiksatamrkukura: ^^^18:04
rkukuraright, I expect that to be a series of 5 patches: API, DB, Plugin, Implicit Context Driver, Mapping Driver18:05
SumitNaiksatamrkukura: ok18:05
*** susaant has joined #openstack-meeting-318:05
SumitNaiksatamso for Juno, we will be going depth and breadth18:05
SumitNaiksatamin terms of the patch series18:05
SumitNaiksatam*Juno 118:06
SumitNaiksatamso rkukura mentioned above the depth series for EP, EPG, L2/3_Context18:06
SumitNaiksatamin parallel there will be a breadth series which will start introducing the other required resources in the model18:06
*** LouisF has joined #openstack-meeting-318:07
SumitNaiksatamthat way reviews can proceed in parallel on the model as well as the changes leading to the data path18:07
rkukuraSumitNaiksatam: Is our goal for Juno 1 to get the 1st 9 patches mentioned so far merged if possible?18:08
SumitNaiksatamalso, any dependencies on the model (like CLI, Heat, Horizon) can proceed in parallel with the model patches being in place18:08
rkukuras/9/8/18:08
SumitNaiksatamrkukura: definitely18:08
SumitNaiksatamwhat do others think about this?18:08
hemanthraviSumitNaiksatam: should we break CLI/Heat into different patches matching the model patches?18:09
armaxit's an ambitious goal, it really depends on the review churn18:09
SumitNaiksatamarmax: completely agree18:09
armaxbut it's doable18:09
SumitNaiksatamhoping for the best ;-)18:09
mandeephemanthravi: probably not, you can just depend on the most recent model patch18:09
banixhemanthravi: i would say no18:09
mandeephemanthravi: unless the size of patch becomes too large, that is18:09
hemanthraviok18:10
SumitNaiksatami guess we need to weigh the overhead18:10
SumitNaiksatamso while on the patches18:11
SumitNaiksatamwe had the older patches:18:11
rkukurahemanthravi: Is the question whether to break it horizonally, with the 1st four resrouces in one patch, other resources in followup patches? If so, I’d think that depends on the size.18:11
rkukuramandeep: That’s what I was trying to say :)18:11
mandeeprkukura: +1 ;-)18:11
SumitNaiksatamhemanthravi: did you get your answer?18:12
*** BrianB_ has quit IRC18:12
hemanthraviyes, will group them to make the patches manageable....cli/heat should be easy to review18:12
SumitNaiksatamhemanthravi: ok18:12
SumitNaiksatamso i was saying, we had older patches that were causing confusion18:13
SumitNaiksatamhttps://review.openstack.org/#/c/93853, https://review.openstack.org/#/c/9393518:13
SumitNaiksatamthe suggestion is to just abandon these18:13
SumitNaiksatamagree?18:13
rkukuraSumitNaiksatam: +1, with a comment referencing the new series18:13
SumitNaiksatamthe history will still remain18:13
banixSumitNaiksatam: yes keeping them around adds to confusion18:14
ivar-lazzaro+118:14
SumitNaiksatamrkukura: yes we will note that, and the review comments will be incorporated as well18:14
mandeepSumitNaiksatam: I agree, the PoC/prototype pieces there were creating confusion w.r.t to the final code that we expect to check-in and support18:14
banixSumitNaiksatam: marking as abandoned seems reasonable18:14
SumitNaiksatambanix ivar-lazzaro: ok18:14
SumitNaiksatammandeep: ok18:14
SumitNaiksatam#action rkukura SumitNaiksatam to abandon older patches18:14
SumitNaiksatamdo we need to discuss anything on the current patches18:15
SumitNaiksatamcurrent -> newer18:15
SumitNaiksatami know they landed recently18:15
SumitNaiksatamronak has feedback and i addressed them18:15
rkukuraSumitNaiksatam: They look great!18:15
SumitNaiksatami just saw rkukura’s comments and i havent addresed them18:15
SumitNaiksatamrkukura: ok18:15
*** pballand has joined #openstack-meeting-318:15
mandeepSumitNaiksatam: As armax identified, this is an big task for review. Can we get volunteers to start this review?18:16
hemanthravirkukura: yes, will break as your comment suggest18:16
SumitNaiksatammandeep: do you want me to volunteer people’s names? ;-P18:16
rkukuraIn reviewing, I started thinking about what our stance on IPv6 should be in these initial series18:16
mandeepSumitNaiksatam: I understand that we will need the datapath code to get some of these reviews forward, and that should be coming soon18:17
SumitNaiksatamrkukura: we have a separate agenda item to discuss that18:17
SumitNaiksatamrkukura: can we defer the ipv6 discussion to that?18:17
rkukuraSumitNaiksatam: Sure, but I’d like a clear decision on whether we are going to implement and test IPv6 during Juno18:18
*** zehicle_at_dell has quit IRC18:18
mandeeprkukura: My recommendation would be to ficus on IPv4 for Juno18:18
*** lenrow has quit IRC18:18
SumitNaiksatammandeep: that was my understanding18:18
mandeeprkukura: We can come to IPv6 post-Juno, as that will be significant task in itself18:18
SumitNaiksatamrkukura: is ipv6 support in neutron completely baked (i thought we are still implementing this)18:18
rkukuramandeep: I’m fine with that too, with the understanding that we are including IPv6 in the API, but raising exceptions if it is used18:19
SumitNaiksatamrkukura: that sounds like the way to go18:19
mandeeprkukura: Good idea18:19
rkukuraAs long as reviewers will be OK with that, for now.18:19
SumitNaiksatam#agreed No ipv6 support in GP will be beyond Juno, in Juno we will have it in the resource model but will raise exception18:20
SumitNaiksatamthat did not come out right18:20
SumitNaiksatam#undo18:21
openstackRemoving item from minutes: <ircmeeting.items.Agreed object at 0x23789d0>18:21
SumitNaiksatam#agreed ipv6 support in GP will be beyond Juno, in Juno we will have it in the resource model but will raise exception18:21
SumitNaiksatamok moving on18:21
SumitNaiksatam#topic PoC follow-up18:21
*** openstack changes topic to "PoC follow-up (Meeting topic: networking_policy)"18:21
SumitNaiksatamso last week we said that we are still working on the security groups mapping18:21
SumitNaiksatamrkukura: over to you18:22
rkukuraNow that we’ve switched to depth-first, I’ve been focusing on the 1st series of patches rather than on the PoC18:22
*** rguest has joined #openstack-meeting-318:22
SumitNaiksatamrkukura: ok18:23
rkukuraSo no new progress on the PoC18:23
rkukuraI’d like to get the 5 patches mentioned above into review as soon as possible, then switch to SG mapping18:23
SumitNaiksatamrkukura: so i would imagine the depth-first does not include the SG mapping yet18:23
mandeeprkukura: Agreed18:23
rkukuraAt that point, we can evaluate whether this makes more sense to do in the PoC repo, or based on the gerrit master + unmerged patches18:24
SumitNaiksatamrkukura: ok18:24
SumitNaiksatamthe other pending item from the PoC was the services’ integration18:24
SumitNaiksatamstephen was working on it18:24
SumitNaiksatambut he is on vacation and he provided an update18:24
rkukuraSumitNaiksatam: Correct, the SGs will come in when policy resources are added18:24
SumitNaiksatami will just paste it here18:24
SumitNaiksatamrkukura: ok18:24
SumitNaiksatamStephen’s update: For GP, I am still looking at moving the 'redirect' code to the right place (contract creation rather than action creation). However, since there will likely be changes on how mapping driver would/should work based on Armando's comments, and that the final implementation will depend on the ServiceBase work anyway, this will likely be pushed a bit later.18:24
SumitNaiksatami think he is more focussed on the advanced services stuff right now to align with this18:25
SumitNaiksatammoving on18:25
*** prasadv has quit IRC18:25
SumitNaiksatam#topic Mapping driver/data path patches18:26
*** openstack changes topic to "Mapping driver/data path patches (Meeting topic: networking_policy)"18:26
SumitNaiksatamwe covered a bit of this earlier18:26
SumitNaiksatambut there was some discussion on the mailing lists (and also from last week)18:26
SumitNaiksatammainly around accessing Neutron resources (Controller versus Client)18:26
SumitNaiksatamrkukura you have chosen an approach for this?18:26
rkukuraI think we’ve got concensus around starting out using python-neutronclient18:27
SumitNaiksatamrkukura: ok18:27
rkukuraI’ve got reservations about that regarding performance and failure modes it introduces, but it should allow rapid progress without having to come up with a better solution18:28
SumitNaiksatamrkukura: so the depth-first series will be implemented with the client?18:28
rkukuraThat’s the plan18:28
mandeepSumitNaiksatam: There was an action item from last week to meet with armax for an ad-hoc meeting. Since there was concensus on moving forward with client API, bot rkukura and armax felt that we did not need this meeeting anymore.18:28
LouisFis the BP updated with the python-neutronclient design?18:28
rkukuraFor calls to neutron resources. Calls to GP resources can probably be directly on the plugin18:28
armaxdon't we all have reservations about performance and failure modes?18:28
armax:)18:28
SumitNaiksatammandeep: ok18:28
armaxregardless of the approach?18:29
SumitNaiksatamarmax: true18:29
SumitNaiksatamarmax: are you comfortable with what mandeep mentions above ^^^ (and rkukura’s placn)?18:29
SumitNaiksatam*plan18:29
rkukuraarmax: I think using the client ensures keeping a loose coupling, enables progress, and can easily be revisited later18:29
armaxSumitNaiksatam: at this point I think that gerrit is best venue to take the discussion forward18:30
SumitNaiksatamarmax: ok, so we are not doing the ad hoc meeting any more18:30
*** emagana has quit IRC18:30
armaxhaving the code side by side with comments is very valuable18:30
SumitNaiksatamLouisF: i wil punt that question to hemanthravi18:30
*** lenrow has joined #openstack-meeting-318:30
SumitNaiksatamLouisF: btw, this discussion the client is different from the client for the GP model18:31
LouisFagree18:31
*** emagana has joined #openstack-meeting-318:31
SumitNaiksatamLouisF: out here we are talking about accessing the existing neutron resources from the GP mapping driver by using the neutronclient18:31
SumitNaiksatamLouisF: okay18:31
hemanthraviSumitNaiksatam: this will be using neutronclient to create the net/subnet/port resources and not the gp resources, rihgt?18:31
SumitNaiksatamhemanthravi: yes18:31
*** dkorn has joined #openstack-meeting-318:32
*** dlenrow has joined #openstack-meeting-318:32
SumitNaiksatamLouisF: does that answer your question, or were you asking the CLI design for the GP model?18:32
LouisFyes that answers my question18:33
SumitNaiksatamLouisF: good18:33
rkukuraSo is everyone OK with the ImplicitContextDriver making direct calls on the GP plugin to create L2Context and L3Context instances, at least for now?18:33
*** pcm_ has joined #openstack-meeting-318:33
*** pcm_ has left #openstack-meeting-318:33
SumitNaiksatamrkukura yes, that was also an item on the agenda18:33
SumitNaiksatamrkukura: we discussed this last week18:33
SumitNaiksatamrkukura: and good to get agreement18:33
*** emagana has quit IRC18:34
SumitNaiksatamrkukura: whats the alternate approach?18:34
*** emagana has joined #openstack-meeting-318:34
rkukuraEventually we may decide that quotas need to be enforced on the L2Context and L3Context that get created, which would be done if we used the python-neutronclient with GP support, or used the Controller. But this can come later.18:34
SumitNaiksatamrkukura: ah i see18:35
SumitNaiksatamrkukura: so similar issue as that with the other neutron resources18:35
*** lenrow has quit IRC18:35
rkukuraNot as critical as the DHCP and nova notifications for ports18:35
SumitNaiksatamrkukura: agree, so i am +1 for the approach you mentioned (making direct calls)18:36
rkukuraOK, this avoids introducing a dependency on an update python-neutronclient, which would prevent merging18:36
SumitNaiksatam#agreed calls to neutron networks, ports, subnets, routers from the mapping driver wil be made using the python-neutronclient18:37
SumitNaiksatam#agreed calls to GP resources from the mapping driver will be made directly18:37
SumitNaiksatamrkukura: sound okay ^^^ ?18:37
rkukurayes, at least for now18:37
SumitNaiksatamok18:37
*** ivar-lazzaro has quit IRC18:38
armaxthe two agreement statements seem to be in contradiction18:38
SumitNaiksatamso rkukura brought up a good point earlier on whether we need to support both v4 and v6 in the same EPG18:38
armaxSumitNaiksatam: could you clarify?18:38
SumitNaiksatamarmax: the first statement is per the earlier discussion (including email threads)18:39
rkukura1st is calls on existing neutron resources, 2nd is calls on GP resources18:39
SumitNaiksatamarmax: the second statement says, that for the GP resources that need to be created/updated from the mapping driver, the mapping driver will make direct calls on the GP plugin API18:39
*** catherine|2 has left #openstack-meeting-318:40
armaxSumitNaiksatam: gotcha, thanks18:40
armaxSumitNaiksatam: so long as back and forth of messages between objects is minimized we should be good18:40
SumitNaiksatamarmax: yeah, i agree18:41
SumitNaiksatamso back to the earlier point - rkukura brought up a good point earlier on whether we need to support both v4 and v6 in the same EPG18:41
SumitNaiksatami am guessing not for Juno18:41
SumitNaiksatamright?18:41
SumitNaiksatamif not, rkukura’s question is whether we will ever support18:42
rkukuraIf we aren’t doing IPv6 for Juno, we definitely won’t do both for Juno18:42
SumitNaiksatamrkukura: true, but i am not sure if we will ever need it18:43
SumitNaiksatamanyone has thoughts on this?18:43
*** csd has quit IRC18:43
rkukuraBut I’ve got no hands-on IPv6 experience, and was wondering if the model should allow an EPG to have multiple L2Cs and/or an L2C to have multiple L3Cs, either/both of which would allow a single EPG to have both IPv4 and IPv6 L3Cs18:43
mandeepSumitNaiksatam: We will probably need a longer design review for IPv6 and GP, I recommend a fuller review post-Juno deliverables and not make this decision without that background18:44
SumitNaiksatammandeep: so in the shorter term how do we make this future proof?18:44
rkukuraOne key question is whether these use cases would be IPv4 and IPv6 subnets on the same network, or on different networks, or both need to be supported18:45
SumitNaiksatamok lets take this offline18:45
rkukuraSure18:45
mandeeprkukura: SumitNaiksatam: OK18:45
SumitNaiksatam#action mandeep rkukura to discuss ipv6 implications18:45
SumitNaiksatamwe also discussed last week about the “implicit context driver"18:46
SumitNaiksatamjust want to make sure that we all agreed18:46
SumitNaiksatamso this is a dirver which defines the criteria for implicitly creating resources18:47
mandeepSumitNaiksatam: You mean the driver split into two parts, correct?18:47
rkukuraThis driver packages the code thats in the mapping_driver in the PoC that creates L2Context (BD) and L3Context (RD) objects when they are not explicity passed into the API18:47
SumitNaiksatamrkukura: thanks18:47
rkukuramandeep: correct18:47
mandeeprkukura: OK, got it. And I agree with that.18:48
SumitNaiksatamperhaps this will be more clear when people actually see this in the code18:48
SumitNaiksatamso as of now rkukura you are going with that approach, right?18:48
rkukurathats the plan18:48
SumitNaiksatamrkukura: ok18:48
SumitNaiksatammoving on18:48
SumitNaiksatam#topic Resource name changes (again!)18:48
*** openstack changes topic to "Resource name changes (again!) (Meeting topic: networking_policy)"18:48
SumitNaiksatamlast week the suggestiong was to rename BD, RD to l2/3_context resp18:49
SumitNaiksatambut we already have resource context objects used internally in the code18:49
SumitNaiksatamand we end up with names like L2ContextContext18:49
SumitNaiksatamrkukura already pointed out that last week18:50
SumitNaiksatamso the suggestion is to rename l2/3_context to l2/3_policy18:50
SumitNaiksatameveryone okay?18:50
mandeepSumitNaiksatam: Ok18:50
SumitNaiksatamor i should ask, anyone disagree or any better names?18:51
SumitNaiksatamok sold then!18:51
SumitNaiksatam#agreed BD, RD -> l2/3_context -> l2/3_policy18:51
SumitNaiksatam#topic API interception/Nova integration18:52
*** openstack changes topic to "API interception/Nova integration (Meeting topic: networking_policy)"18:52
rkukuraI don’t see a problem with that, but I’m not sure if “implicit policy driver” is better or worse than “implicit context driver”18:52
SumitNaiksatam#undo18:52
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x235d750>18:52
SumitNaiksatamrkukura: how about implicit mapping driver?18:52
rkukuraIts not really a mapping, its implicit resource management18:53
SumitNaiksatamagree18:53
mandeeprkukura: agreed18:53
SumitNaiksatamperhaps we can discuss offline, since that is not as critical as resource names18:53
rkukurawe could rename the Context objects passed to the driver API18:54
rkukuraMaybe L2CContext, L3CContext, EPGContext, EPContext, …?18:54
SumitNaiksatamrkukura: yeah thats a possibility18:54
SumitNaiksatambut more importantly, l2/3_policy seemed more natural to this context, than l2/3_context18:55
SumitNaiksatam#action rkukura to suggest renaming of implicit context driver18:56
SumitNaiksatam#topic API interception/Nova integration18:56
*** openstack changes topic to "API interception/Nova integration (Meeting topic: networking_policy)"18:56
SumitNaiksatamwe discussed this just a bit last weel18:56
SumitNaiksatam*week18:56
SumitNaiksatamhoping to get more time this week, but i think we are running behind again18:56
SumitNaiksatamso the issue here is that we need to intercept the port creation calls from nova18:57
SumitNaiksatamwe can revisit this next week18:57
SumitNaiksatam#topic Open Discussion18:57
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:57
SumitNaiksatamdid we miss anything?18:58
rkukuralets put testing on the agenda for next week18:58
SumitNaiksatamrkukura: yeah, i was just going to say, we wanted to discuss functional tests as well18:58
SumitNaiksatamperhaps people need to say a little more of the code to get a better context18:58
*** thinrichs has quit IRC18:58
SumitNaiksatami guess we should be in good shape on that front next week18:59
SumitNaiksatamanything else?18:59
rkukuraFor the mapping driver patches, I’d like to try to stick to pure unit tests, and do the testing we have in the PoC as functional tests18:59
SumitNaiksatamrkukura: +119:00
rkukuraSo these unit tests would mock the neutron-pythonclient calls19:00
mandeeprkukura: Let us review that with Maru as well19:00
rkukuraand neutron resources would not actually get created19:00
mandeeprkukura: He had some specific feedback on functional tests19:00
SumitNaiksatamok, on that happy note, lets wrap for today19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu May 29 19:00:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-29-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-29-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2014/networking_policy.2014-05-29-18.01.log.html19:01
rkukurabye everyone!19:01
SumitNaiksatambye all!19:01
*** mandeep has quit IRC19:02
*** rkukura has left #openstack-meeting-319:02
*** hemanthravi has quit IRC19:02
*** LouisF has quit IRC19:04
*** susaant has quit IRC19:09
*** rguest has quit IRC19:16
*** nati_ueno has quit IRC19:16
*** dhandy has left #openstack-meeting-319:18
*** pballand has quit IRC19:19
*** dlenrow has quit IRC19:21
*** eghobo has quit IRC19:23
*** eghobo has joined #openstack-meeting-319:23
*** nati_ueno has joined #openstack-meeting-319:28
*** jrist has quit IRC19:30
*** peristeri has quit IRC19:32
*** jackib has joined #openstack-meeting-319:35
*** nati_ueno has quit IRC19:36
*** nati_ueno has joined #openstack-meeting-319:36
*** jrist has joined #openstack-meeting-319:45
*** Swami has left #openstack-meeting-319:45
*** emagana has quit IRC19:47
*** emagana has joined #openstack-meeting-319:47
*** emagana has quit IRC19:50
*** emagana has joined #openstack-meeting-319:51
*** emagana has quit IRC19:52
*** tedchang has quit IRC19:52
*** nati_ueno has quit IRC19:54
*** emagana has joined #openstack-meeting-319:54
*** emagana has quit IRC19:55
*** nati_ueno has joined #openstack-meeting-319:57
*** nati_ueno has quit IRC20:01
*** nati_ueno has joined #openstack-meeting-320:03
*** nati_ueno has quit IRC20:15
*** lblanchard has quit IRC20:17
*** jtomasek has quit IRC20:18
-openstackstatus- NOTICE: Gerrit is going offline to correct an issue with a recent project rename. ETA 20:45 UTC.20:20
*** ChanServ changes topic to "Gerrit is going offline to correct an issue with a recent project rename. ETA 20:45 UTC."20:21
*** tedchang has joined #openstack-meeting-320:27
*** mwagner_lap has quit IRC20:38
*** ChanServ changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:39
-openstackstatus- NOTICE: Gerrit is back online20:39
*** chuckC has quit IRC20:44
*** dkorn has quit IRC20:44
*** shakamunyi has quit IRC20:51
*** shakamunyi has joined #openstack-meeting-320:52
*** thomasem has quit IRC20:58
*** sarob has joined #openstack-meeting-320:59
*** jackib has quit IRC21:01
*** shakamunyi has quit IRC21:14
*** julim has quit IRC21:24
*** eguz has joined #openstack-meeting-321:26
*** thomasem has joined #openstack-meeting-321:29
*** thomasem has quit IRC21:30
*** eghobo has quit IRC21:30
*** nati_ueno has joined #openstack-meeting-321:31
*** thomasem has joined #openstack-meeting-321:31
*** kinrui has joined #openstack-meeting-321:34
*** kinrui has quit IRC21:34
*** eghobo has joined #openstack-meeting-321:38
*** eguz_ has joined #openstack-meeting-321:39
*** eguz has quit IRC21:39
*** eghobo has quit IRC21:43
*** rockyg has joined #openstack-meeting-321:46
*** ivar-lazzaro has joined #openstack-meeting-321:48
*** mfer has quit IRC21:50
*** chuckC has joined #openstack-meeting-321:52
*** jamie_h has quit IRC21:53
*** banix has quit IRC22:02
*** jackib has joined #openstack-meeting-322:02
*** eguz_ has quit IRC22:03
*** eghobo has joined #openstack-meeting-322:03
*** shakamunyi has joined #openstack-meeting-322:11
*** shakamunyi has quit IRC22:22
*** shakayumi has joined #openstack-meeting-322:22
*** nati_ueno has quit IRC22:22
*** ivar-lazzaro has quit IRC22:23
*** yamahata has joined #openstack-meeting-322:28
*** jackib has quit IRC22:50
*** nati_ueno has joined #openstack-meeting-322:56
*** jackib has joined #openstack-meeting-322:56
*** jackib has quit IRC22:57
*** jackib has joined #openstack-meeting-323:05
*** tedchang has quit IRC23:12
*** tedchang has joined #openstack-meeting-323:14
*** david-lyle has quit IRC23:17
*** sarob has quit IRC23:18
*** sarob has joined #openstack-meeting-323:19
*** yamahata has quit IRC23:20
*** sarob has quit IRC23:23
*** mwagner_lap has joined #openstack-meeting-323:39
*** tedchang has quit IRC23:40
*** chuckC has quit IRC23:41
*** tedchang has joined #openstack-meeting-323:41
*** sarob has joined #openstack-meeting-323:44
*** sarob_ has joined #openstack-meeting-323:48
*** sarob has quit IRC23:48
*** sarob has joined #openstack-meeting-323:50
*** chuckC has joined #openstack-meeting-323:52
*** sarob_ has quit IRC23:53
*** sarob has quit IRC23:55

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