Thursday, 2017-06-15

*** dimtruck is now known as zz_dimtruck00:05
*** zz_dimtruck is now known as dimtruck00:06
*** dimtruck is now known as zz_dimtruck00:13
*** lyan has quit IRC00:28
*** ducttape_ has joined #openstack-meeting-300:33
*** zhurong has joined #openstack-meeting-300:39
*** tuanluong has joined #openstack-meeting-300:42
*** mickeys has joined #openstack-meeting-300:44
*** wanghao has joined #openstack-meeting-300:46
*** mickeys has quit IRC00:48
*** zz_dimtruck is now known as dimtruck00:52
*** abramley has joined #openstack-meeting-300:54
*** shuyingya has joined #openstack-meeting-300:56
*** amotoki_away is now known as amotoki01:10
*** mfedosin has quit IRC01:13
*** lucasxu has joined #openstack-meeting-301:19
*** lucasxu has quit IRC01:21
*** gcb has joined #openstack-meeting-301:30
*** yamahata has quit IRC01:39
*** iyamahat has quit IRC01:39
*** mickeys has joined #openstack-meeting-301:45
*** mickeys has quit IRC01:49
wanghaohi02:00
*** VW has quit IRC02:02
*** VW has joined #openstack-meeting-302:02
*** tenobreg has joined #openstack-meeting-302:04
*** ducttape_ has quit IRC02:06
*** ducttape_ has joined #openstack-meeting-302:07
*** ducttape_ has quit IRC02:08
*** tellesnobrega has quit IRC02:08
*** baoli has joined #openstack-meeting-302:10
*** markvoelker has quit IRC02:32
*** markvoelker has joined #openstack-meeting-302:33
*** shu-mutou-AWAY is now known as shu-mutou02:34
*** markvoelker has quit IRC02:37
*** mickeys has joined #openstack-meeting-302:46
*** dimtruck is now known as zz_dimtruck02:46
*** baoli has quit IRC02:47
*** mickeys has quit IRC02:50
*** rossella_s has joined #openstack-meeting-302:57
*** dklyle has joined #openstack-meeting-303:01
*** david-lyle has quit IRC03:04
*** ducttape_ has joined #openstack-meeting-303:08
*** yamahata has joined #openstack-meeting-303:12
*** rossella_s has quit IRC03:23
*** mickeys has joined #openstack-meeting-303:46
*** mickeys has quit IRC03:51
*** iyamahat has joined #openstack-meeting-303:55
*** wanghao_ has joined #openstack-meeting-303:57
*** wanghao has quit IRC03:58
*** iyamahat has quit IRC04:03
*** tobberydberg has joined #openstack-meeting-304:09
*** tobberydberg has quit IRC04:13
*** anilvenkata has joined #openstack-meeting-304:15
*** salv-orlando has joined #openstack-meeting-304:16
*** salv-orlando has quit IRC04:21
*** psachin has joined #openstack-meeting-304:22
*** gouthamr has quit IRC04:24
*** zhurong has quit IRC04:28
*** salv-orlando has joined #openstack-meeting-304:28
*** markvoelker has joined #openstack-meeting-304:33
*** zhurong has joined #openstack-meeting-304:40
*** pgadiya has joined #openstack-meeting-304:42
*** mickeys has joined #openstack-meeting-304:47
*** mickeys has quit IRC04:52
*** salv-orl_ has joined #openstack-meeting-305:05
*** markvoelker has quit IRC05:07
*** salv-orlando has quit IRC05:08
*** claudiub has joined #openstack-meeting-305:08
*** haleyb_ has quit IRC05:12
*** abramley has quit IRC05:13
*** haleyb_ has joined #openstack-meeting-305:26
*** cshastri has joined #openstack-meeting-305:43
*** zenirc369 has joined #openstack-meeting-305:44
*** diablo_rojo has joined #openstack-meeting-305:45
*** rossella_s has joined #openstack-meeting-305:48
*** mickeys has joined #openstack-meeting-305:48
*** MarkBaker has joined #openstack-meeting-305:48
*** tobberydberg has joined #openstack-meeting-305:50
*** pgadiya has quit IRC05:51
*** mickeys has quit IRC05:53
*** makowals has joined #openstack-meeting-305:58
*** calbers has quit IRC06:02
*** salv-orl_ has quit IRC06:02
*** mickeys has joined #openstack-meeting-306:02
*** makowals has quit IRC06:03
*** pgadiya has joined #openstack-meeting-306:04
*** markvoelker has joined #openstack-meeting-306:04
*** galstrom_zzz is now known as galstrom06:10
*** ltomasbo|away is now known as ltomasbo06:13
*** gcb has quit IRC06:17
*** calbers has joined #openstack-meeting-306:18
*** rossella_s has quit IRC06:24
*** gcb has joined #openstack-meeting-306:28
*** markvoelker has quit IRC06:37
*** makowals has joined #openstack-meeting-306:40
*** dims has quit IRC06:44
*** dims has joined #openstack-meeting-306:46
*** pcaruana has joined #openstack-meeting-306:58
*** iyamahat has joined #openstack-meeting-307:01
*** ccamacho|brb has quit IRC07:12
*** salv-orlando has joined #openstack-meeting-307:12
*** iyamahat has quit IRC07:15
*** mickeys has quit IRC07:15
*** ccamacho has joined #openstack-meeting-307:16
*** shuyingya has quit IRC07:19
*** shuyingya has joined #openstack-meeting-307:19
*** ralonsoh has joined #openstack-meeting-307:21
*** shuyingya has quit IRC07:22
*** shuyingya has joined #openstack-meeting-307:23
*** rossella_s has joined #openstack-meeting-307:26
*** neiljerram has joined #openstack-meeting-307:30
*** ltomasbo is now known as ltomasbo|away07:32
*** markvoelker has joined #openstack-meeting-307:34
*** bsilverman_ has quit IRC07:35
*** bsilverman_ has joined #openstack-meeting-307:35
*** rossella_s has quit IRC07:38
*** neiljerram has quit IRC07:57
*** rossella_s has joined #openstack-meeting-308:00
*** mickeys has joined #openstack-meeting-308:00
*** neiljerram has joined #openstack-meeting-308:01
*** abalutoiu has joined #openstack-meeting-308:04
*** rossella_s has quit IRC08:05
*** markvoelker has quit IRC08:08
*** shuyingy_ has joined #openstack-meeting-308:10
*** diablo_rojo has quit IRC08:11
*** dosaboy has quit IRC08:11
*** shuyingya has quit IRC08:14
*** ltomasbo|away is now known as ltomasbo08:17
*** dosaboy has joined #openstack-meeting-308:19
*** rossella_s has joined #openstack-meeting-308:22
*** yamahata has quit IRC08:23
*** lpetrut has joined #openstack-meeting-308:32
*** shuyingy_ has quit IRC08:34
*** shuyingya has joined #openstack-meeting-308:34
*** rstarmer_ has joined #openstack-meeting-308:34
*** rossella_s has quit IRC08:36
*** psachin has quit IRC08:40
*** mfedosin has joined #openstack-meeting-308:41
*** rstarmer_ has quit IRC08:41
*** psachin has joined #openstack-meeting-308:41
*** rstarmer_ has joined #openstack-meeting-308:42
*** psachin has quit IRC08:43
*** psachin has joined #openstack-meeting-308:43
*** dosaboy has quit IRC08:50
*** dosaboy has joined #openstack-meeting-308:51
*** dosaboy has quit IRC08:53
*** mickeys has quit IRC09:04
*** markvoelker has joined #openstack-meeting-309:05
*** dosaboy has joined #openstack-meeting-309:08
*** rstarmer_ has quit IRC09:19
*** rstarmer_ has joined #openstack-meeting-309:21
*** shuyingya has quit IRC09:22
*** shuyingya has joined #openstack-meeting-309:23
*** psachin has quit IRC09:29
*** shuyingy_ has joined #openstack-meeting-309:31
*** shuyingya has quit IRC09:34
*** markvoelker has quit IRC09:38
*** shu-mutou is now known as shu-mutou-AWAY09:47
*** d0ugal has quit IRC09:48
*** d0ugal has joined #openstack-meeting-309:49
*** galstrom is now known as galstrom_zzz09:52
*** wanghao_ has quit IRC09:54
*** mickeys has joined #openstack-meeting-310:05
*** mickeys has quit IRC10:09
*** rstarmer_ has quit IRC10:12
*** rstarmer_ has joined #openstack-meeting-310:16
*** sambetts|afk is now known as sambetts10:23
*** markvoelker has joined #openstack-meeting-310:34
*** abramley has joined #openstack-meeting-310:36
*** sdague has joined #openstack-meeting-310:48
*** rstarmer_ has quit IRC10:55
*** salv-orlando has quit IRC10:56
*** jpich has joined #openstack-meeting-310:56
*** shuyingy_ has quit IRC10:56
*** shuyingya has joined #openstack-meeting-310:56
*** shuyingy_ has joined #openstack-meeting-310:57
*** shuyingya has quit IRC10:57
*** shuyingy_ has quit IRC10:59
*** shuyingya has joined #openstack-meeting-311:00
*** julim has joined #openstack-meeting-311:04
*** mickeys has joined #openstack-meeting-311:05
*** tobberyd_ has joined #openstack-meeting-311:06
*** tobberyd_ has quit IRC11:07
*** tobberyd_ has joined #openstack-meeting-311:07
*** markvoelker has quit IRC11:08
*** tobberydberg has quit IRC11:09
*** mickeys has quit IRC11:10
*** ralonsoh has quit IRC11:10
*** ralonsoh has joined #openstack-meeting-311:10
*** tobberyd_ has quit IRC11:10
*** tobberydberg has joined #openstack-meeting-311:11
*** tobberyd_ has joined #openstack-meeting-311:31
*** salv-orlando has joined #openstack-meeting-311:34
*** tobberydberg has quit IRC11:34
*** tobberyd_ has quit IRC11:49
*** markvoelker has joined #openstack-meeting-311:51
*** tobberydberg has joined #openstack-meeting-311:52
*** abramley has quit IRC11:54
*** julim has quit IRC12:00
*** mickeys has joined #openstack-meeting-312:06
*** tuanluong has quit IRC12:10
*** mickeys has quit IRC12:12
*** shuyingya has quit IRC12:13
*** ccamacho is now known as ccamacho|lunch12:15
*** shuyingya has joined #openstack-meeting-312:23
*** zhurong has quit IRC12:26
*** shuyingya has quit IRC12:27
*** zhurong has joined #openstack-meeting-312:28
*** shuyingya has joined #openstack-meeting-312:28
*** baoli has joined #openstack-meeting-312:31
*** donghao has joined #openstack-meeting-312:35
*** donghao has quit IRC12:35
*** zhurong has quit IRC12:36
*** donghao has joined #openstack-meeting-312:37
*** shuyingy_ has joined #openstack-meeting-312:43
*** shuyingya has quit IRC12:46
*** lyan has joined #openstack-meeting-312:48
*** zenirc369 has quit IRC12:55
*** julim has joined #openstack-meeting-312:58
*** armstrong has joined #openstack-meeting-313:00
*** haleyb_ has quit IRC13:08
*** mickeys has joined #openstack-meeting-313:08
*** gouthamr has joined #openstack-meeting-313:11
*** mickeys has quit IRC13:13
*** shuyingy_ has quit IRC13:19
*** shuyingya has joined #openstack-meeting-313:20
*** lucasxu has joined #openstack-meeting-313:26
*** ccamacho|lunch is now known as ccamacho13:30
*** shuyingya has quit IRC13:30
*** jeremyfreudberg has joined #openstack-meeting-313:34
*** jeremyfreudberg has quit IRC13:39
*** bobh has joined #openstack-meeting-313:43
*** tenobreg has quit IRC13:45
*** jeremyfreudberg has joined #openstack-meeting-313:45
*** tellesnobrega has joined #openstack-meeting-313:46
*** bobh has quit IRC13:46
*** tosky has joined #openstack-meeting-313:47
*** zhurong has joined #openstack-meeting-313:48
*** bobh has joined #openstack-meeting-313:49
*** VW has quit IRC13:56
*** lhx__ has joined #openstack-meeting-313:57
*** VW has joined #openstack-meeting-313:57
*** esikachev has joined #openstack-meeting-313:58
*** vgridnev has joined #openstack-meeting-314:00
*** shuyingya_m has joined #openstack-meeting-314:00
*** mlavalle has joined #openstack-meeting-314:00
tellesnobrega#startmeeting sahara14:01
openstackMeeting started Thu Jun 15 14:01:20 2017 UTC and is due to finish in 60 minutes.  The chair is tellesnobrega. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
*** spzala has joined #openstack-meeting-314:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: sahara)"14:01
openstackThe meeting name has been set to 'sahara'14:01
vgridnevO/14:01
jeremyfreudbergo/14:01
shuyingya_mo/ hi all, long time no see :)14:01
*** bnemec has joined #openstack-meeting-314:01
esikachevhi14:01
tellesnobregashuyingya_m, its been a while14:01
jeremyfreudbergshuyingya_m, welcome back!14:02
*** jpich has left #openstack-meeting-314:02
*** iwonka has joined #openstack-meeting-314:02
tellesnobregais tosky around already?14:02
shuyingya_mYep, have a business travel recently to improve our product14:02
*** rbak has joined #openstack-meeting-314:02
toskyhi14:03
tellesnobregaturns out today is one of our most attended meetings lately14:03
*** zemuvier has joined #openstack-meeting-314:03
zemuviero/14:03
*** spzala has quit IRC14:03
tellesnobrega#topic News/Updates14:03
*** openstack changes topic to "News/Updates (Meeting topic: sahara)"14:03
tellesnobregaI'm still working on images, got a new patch for CDH and will put a new up for ambari today14:04
tellesnobrega#link https://review.openstack.org/#/c/448712/914:04
tellesnobregaplease take some time to review it if you can14:04
toskyno much news, but I'm planning to test Pike soon; maybe you don't know, but TripleO added the support for deploying services in containers, and the patch which containerize Sahara just landed14:04
toskytellesnobrega: already commented :)14:04
tellesnobregaother than that, I'm trying to find resources so we can deploy our CI again14:05
jeremyfreudbergtellesnobrega, bonus points if those new resources can also be used for ironic integration tests14:05
toskyyou like challenges14:06
vgridnevNothing new from me14:06
tellesnobregajeremyfreudberg, that is kinda hard, we have been struggling to get resources to test ironic integration for a while, but let's see14:06
esikachevno updates from me14:06
tellesnobregaesikachev, once we get the resources I will let you know and we can work on deploying it14:07
esikachevok14:07
jeremyfreudbergtellesnobrega, that's why it's bonus points :) anyway, not much new from me either, just trying to prioritize what can be done before pike-3 / feature freeze sneaks up on us14:07
tellesnobregaI have another update, I would like to present to you all iwonka, she is our outreachy intern and will be working with us for the next 3 months14:08
tellesnobregaiwonka, care to introduce yourself?14:08
shuyingya_mWorking on add hbase to vanilla in my product,it works now14:08
jeremyfreudbergshuyingya_m, woah! awesome o__o14:08
iwonkahi everyone :)14:09
tellesnobregathat is awesome14:09
*** mickeys has joined #openstack-meeting-314:09
jeremyfreudberg(shuyingya_m, would it go upstream too?)14:09
*** mrmartin has joined #openstack-meeting-314:09
tellesnobregajeremyfreudberg, my next question exactly14:09
shuyingya_mI need further test,and will post to upstream later14:09
shuyingya_mOf course14:10
tellesnobregashuyingya_m, awesome :) thanks for that14:10
*** zz_dimtruck is now known as dimtruck14:10
iwonkaas tellesnobrega wrote, i'm an intern now and i'm working on adding portable ode group templates and data sources to sahara14:11
tellesnobregaiwonka, you have to floor, just tell us a bit of your background and what you are going to be doing14:11
shuyingya_mAnd a new intern has posted some unit test to vanilla14:11
tellesnobregashuyingya_m, rocky?14:11
shuyingya_mYep.14:11
tellesnobregacool14:11
iwonkatellesnobrega: project ^14:11
iwonkaand i think that's all, haven't done much yet14:12
tellesnobregaiwonka, great14:12
tellesnobrega#topic Denver PTG14:13
*** openstack changes topic to "Denver PTG (Meeting topic: sahara)"14:13
shuyingya_miwonka: feel free to ask us in sahara channel if you need help14:13
*** mickeys has quit IRC14:14
tellesnobregaSotK, in september 11-15th OpenStack is having the next PTG in Denver USA, who here is planning on attending?14:14
toskyuh, good question, I didn't have news from my manager yet14:14
jeremyfreudbergmy organization will send me if there's something happening14:14
shuyingya_mI have applied for the travel support. My leader has no plan yet14:15
tellesnobregajeremyfreudberg, awesome... basically I need to know if it will make sense to have PTG. I really think we should, let's try to take as much people as we can14:15
esikachevdepend on TSP14:16
vgridnevI think that I will not be able to attend, : (14:16
jeremyfreudbergvgridnev :(14:17
tellesnobregaI was talking with jeremyfreudberg and tosky and we thought about after the meetings working on bugs or documentation, so it would be good to get people there so we can both make important decisions and also if we have time to work alongside14:17
*** pgadiya has quit IRC14:18
vgridnevsince there is no so much slots for TSP , so I think that it's not correct for me use this slot, so I will let new stackers to attend14:19
tellesnobregavgridnev, you will be missed14:19
tellesnobregavgridnev, did you start your new job already?14:19
vgridnevI'll start next week, now I have some free time to rest a little14:20
tellesnobregavgridnev, enjoy14:20
tellesnobrega#topic Open Discussion14:21
*** openstack changes topic to "Open Discussion (Meeting topic: sahara)"14:22
*** zhurong has quit IRC14:22
toskyI missed last week's meeting, so: thanks for all the work vgridnev!14:22
*** abramley has joined #openstack-meeting-314:22
*** ccamacho has quit IRC14:22
jeremyfreudbergsome good news on my end actually, red hat in boston has agreed to donate some office space to my organization. i'll be working there for the rest of the summer14:22
*** ccamacho has joined #openstack-meeting-314:22
tellesnobregajeremyfreudberg, that is awesome14:22
esikachevcool14:23
tellesnobregaon the new office?14:23
jeremyfreudbergyeah, tellesnobrega, the new one14:23
tellesnobregajeremyfreudberg, cool14:23
shuyingya_mjeremyfreudberg: cool14:23
tellesnobregaiwonka is facing some issues with oslo.messaging on devstack14:24
tellesnobregabasically she has to update to 5.24.2 (I think)14:25
tellesnobregaanyone has done that? can help her out?14:26
tellesnobregawe suggested uninstalling oslo.messaging, unstacking and cleaning, installing new version and start stack again14:26
jeremyfreudbergi'm surprised unstack-restack didn't pull in fresh requirements14:26
jeremyfreudbergbut it's not my expertise14:27
vgridnevYou can try to pull new version of requirements repository14:28
*** haleyb_ has joined #openstack-meeting-314:28
tellesnobregavgridnev, can you explain to her how to do that?14:29
vgridnevcd requirements ; git pull origin master14:29
*** ducttape_ has quit IRC14:29
tellesnobregaiwonka, ^14:29
*** ducttape_ has joined #openstack-meeting-314:30
shuyingya_miwonka: what kind of system you use? Ubuntu 16 installed many times,didn't meet such issues14:30
vgridnevOr you can just add RECLONE=True in local.conf14:30
vgridnevThat will reclone latests versions of all repos14:31
tellesnobregavgridnev, true, forgot about reclone14:31
shuyingya_mPip-upgrade=true14:31
*** julim has quit IRC14:31
shuyingya_mMay also help14:31
iwonkashuyingya_m: yes, ubuntu14:33
iwonkadesktop14:33
shuyingya_mPIP_UPGRADE=True14:33
*** emagana has joined #openstack-meeting-314:33
iwonkawhere?14:33
iwonkai mean which file?14:33
tellesnobregalocal.conf14:33
shuyingya_mIn local.conf14:33
toskyand I guess that oslo.messaging is not installed from debian packages, right?14:34
toskydeb packages*14:34
iwonkanow it was installes with pip install14:35
iwonka*installed14:35
tellesnobregaiwonka, hopefully we can fix the issues with the ideas here14:37
tellesnobregado we have anything else to discuss?14:37
jeremyfreudbergi'm done14:38
iwonkatellesnobrega: unstacked, did what vgridnev suggested and now waiting for stack to run again14:38
tellesnobregaiwonka, awesome, let us know on #openstack-sahara14:38
iwonkasure14:38
tellesnobregaI guess we can end the meeting now, thanks all for coming, lets keep up the good work14:39
tellesnobregaand let me know about PTG14:39
tellesnobrega#endmeeting14:40
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:40
openstackMeeting ended Thu Jun 15 14:40:18 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:40
openstackMinutes:        http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-06-15-14.01.html14:40
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-06-15-14.01.txt14:40
openstackLog:            http://eavesdrop.openstack.org/meetings/sahara/2017/sahara.2017-06-15-14.01.log.html14:40
*** tosky has left #openstack-meeting-314:40
*** jeremyfreudberg has left #openstack-meeting-314:41
*** iwonka has left #openstack-meeting-314:43
*** shuyingya_m has quit IRC14:44
*** zenirc369 has joined #openstack-meeting-314:46
*** makowals has quit IRC14:47
*** esikachev has quit IRC14:48
*** Swami has joined #openstack-meeting-314:51
*** cshastri has quit IRC14:51
*** makowals has joined #openstack-meeting-314:53
*** reedip_ has joined #openstack-meeting-314:54
*** janzian has joined #openstack-meeting-314:59
*** rstarmer has joined #openstack-meeting-314:59
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Jun 15 15:00:07 2017 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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
mlavalle#chair haleyb Swami15:00
openstackCurrent chairs: Swami haleyb mlavalle15:00
Swamihi15:00
haleybhi15:00
*** julim has joined #openstack-meeting-315:00
mlavallein case somebody disconnects, we have redundant charis :-)15:01
mlavallechairs^^^^15:01
mlavalle#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** vkmc_ has joined #openstack-meeting-315:01
SwamiI need to leave early today. Just for your info.15:01
*** davidsha_ has joined #openstack-meeting-315:02
mlavalleok15:02
mlavalleWe are well on our way to Pike-315:02
mlavalle#link https://releases.openstack.org/pike/schedule.html15:02
mlavalleany other announcements?15:02
mlavalleok15:03
mlavalle#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
mlavallelet's start with dvr bugs, so Swami can leave early....15:03
Swamimlavalle: thanks15:04
SwamiNew bug this week.15:05
Swami#link https://bugs.launchpad.net/neutron/+bug/169514015:05
openstackLaunchpad bug 1695140 in neutron "SRC without FIP,DEST with FIP case is broken for dvr-multinode" [Undecided,New] - Assigned to Brian Haley (brian-haley)15:05
*** vgridnev has quit IRC15:05
*** lyan has quit IRC15:06
SwamiI saw the comment in there from brian and it seems that it might be due to the regression. I will monitor that in the coming week.15:06
haleybSwami: now that we re-merged https://review.openstack.org/#/c/470063/ we should re-check15:06
haleyber, just merged15:06
SwamiThere is one issue that I found with this patch. The functional test is failing with the ha combination.15:07
SwamiI will try to push a patch to fix that test case.15:07
mlavalleis it a problem with the test or the code?15:07
SwamiIt is the problem with the test.15:08
SwamiIn the case of ha, there are two snat nodes and the host binding is not matching.15:08
SwamiI will push in a patch that fixes the test case.15:08
SwamiI just tested it and it is running fine.15:09
*** rstarmer has quit IRC15:09
Swamihttp://logs.openstack.org/07/474007/2/check/gate-neutron-dsvm-functional-ubuntu-xenial/4eee227/testr_results.html.gz15:10
*** dklyle is now known as david-lyle15:10
*** mickeys has joined #openstack-meeting-315:10
Swamihere is the info about that test failure in gate.15:10
SwamiThe next one in the list is15:11
Swami#link https://bugs.launchpad.net/neutron/+bug/169698315:11
openstackLaunchpad bug 1696983 in neutron "ovs-fw: flows on br-int are overlapping with dvr flows" [Undecided,In progress] - Assigned to Jakub Libosvar (libosvar)15:11
*** lyan has joined #openstack-meeting-315:11
Swamilibosvar has already pushed in patch to address this issue.15:12
Swami#link https://review.openstack.org/#/c/472691/15:12
SwamiI will review it. I have not reviewed it yet and I do see brian had already reviewed it.15:12
mlavalleI recently reviewed a spec that is going to help with this kind of problems15:13
haleybyes, it looked ok to me15:13
mlavalle#link https://review.openstack.org/#/c/320439/15:13
mlavallefor the time, though, we need libosvar's patchset15:13
mlavalletime being^^^15:13
Swamimlavalle: makes sense15:14
*** mickeys has quit IRC15:14
SwamiThose are the only new bugs this week.15:15
haleybthere is also https://bugs.launchpad.net/neutron/+bug/169679615:15
openstackLaunchpad bug 1696796 in neutron "No fip connectivity after switch to legacy mode from dvr_snat" [Undecided,Incomplete]15:15
mlavalleI was about to ask about that15:15
haleybthat seems like an invalid config to me15:15
Swamihaleyb: yes I saw that and it seems to be an operation error.15:15
haleybi will put a note and close as invalid, can't run a dvr router on a legacy node15:15
SwamiThe user just changed the agent mode and did not convert the dvr router.15:15
haleybthey need to convert first15:16
Swamihaleyb: yes15:16
Swamimlavalle: haleyb: This patch is up for review again. #link https://review.openstack.org/#/c/474007/15:16
SwamiThis was reverted recently for the error log. This was partially caused by the regression on the snat namespace.15:17
haleybSwami: yes, saw that.  Is the error gone?15:17
mlavalleis that Jenkins failure something you need to fix or just re-check?15:17
SwamiAlso I found another issue where the check_for_address_scopes were not checking for 'None'.15:18
Swamihaleyb: yes I don't see the error anymore in my environment. But I will check again in the gate tests.15:18
Swamimlavalle: That jenkins failure is the one that I will fix, and it is due to the test case failure that I spoke above in combination with ha and dvr.15:19
mlavalleLOL15:19
mlavalletripping ourselves15:19
Swamimlavalle: :)15:19
SwamiThat's all I have for the DVR bugs, there are still the monitoring bug related to DVR and I have not started my work on it, since I was focussing on the regression.15:20
Swamis/monitoring/metering15:21
mlavalleThanks Swami. how did the move go?15:21
SwamiAll big items have moved. Just some items here and there.15:21
SwamiBut it was hard after 11 years.15:21
haleybSwami: let me know if you want me to pick-up a patch, there are a few in progress that might need updates and it would be good to get them in15:21
haleybthink i had started one and ran into a rebase15:22
Swamihaleyb: no problem, I will reach out to you.15:22
*** tobberyd_ has joined #openstack-meeting-315:22
mlavalleok15:22
mlavallemoving on15:22
mlavallehttps://bugs.launchpad.net/neutron/+bug/165556715:23
openstackLaunchpad bug 1655567 in neutron "DHCPv6 failures with "address already allocated in subnet" error" [High,In progress] - Assigned to Miguel Lavalle (minsel)15:23
SwamiI need to leave now. I will catch up later on the neutron channel.15:23
mlavalleSwami: Thanks for the update15:23
mlavalleThis bug has a fix proposed:15:24
mlavalle#link https://review.openstack.org/#/c/469669/15:24
mlavalleI think it is good to go, so please review when you have a chance15:24
haleybmlavalle: it looks good to me, but ihar had one question - "is solution working for agentless dhcp drivers?"15:24
mlavallehaleyb: that question was based on the previous approach15:25
*** tobberydberg has quit IRC15:25
*** claudiub has quit IRC15:25
haleyboh, i just never saw an answer, or a +2 from him so was waiting15:25
mlavalleto skip assigment of auto addr for dhcp ports, on the assumption that the agent was going to assign it15:26
*** lpetrut has quit IRC15:26
mlavalleafter he made that comment, I had an irc conversation with him15:26
mlavalleand adopted the current approach15:26
haleybok, great15:27
mlavallenamely, if the address has been assigned and it is a DHCP port, assume the agent already took care of it15:27
mlavallemakes sense?15:27
haleybyes, makes sense15:27
mlavallethat way we don't run the risk of breaking agentless plugins15:28
*** tobberyd_ has quit IRC15:28
mlavalleNext is a new one https://bugs.launchpad.net/neutron/+bug/169792515:29
openstackLaunchpad bug 1697925 in neutron "as a tenant user not able to create a subnetpool associating with a shared address scope" [High,In progress] - Assigned to Roey Chen (roeyc)15:29
*** egallen has joined #openstack-meeting-315:29
mlavallehaleyb: have you seen it before?15:29
haleybmlavalle: no, haven't seen it.  there's a review up now15:30
mlavalleI spent time with it this morning15:30
mlavallein the bug, it is somewhat suggested that this might be a regresion15:31
mlavallethat in the past, this was possible15:31
mlavalleI dug out the original patchset that implemented address scopes, and it is always been like it is today:15:32
*** yamahata has joined #openstack-meeting-315:32
mlavalle#link https://review.openstack.org/#/c/197552/15/neutron/db/db_base_plugin_v2.py@70715:32
haleybso do you consider it a bug?15:34
mlavallehaleyb: based on this, I want to take this with caution. There may be a good reason we are enforcing this15:34
mlavalleit seems more a rfe to me as of now15:34
amotokiI commented in the bug, but I am not sure it is design decision or a bug. I wonder what is the purpose of 'shared' flag of address scope.15:35
mlavalleamotoki: yeah I saw you comments. It was implemented like that originally: https://review.openstack.org/#/c/197552/15/neutron/db/db_base_plugin_v2.py@70715:35
amotokibased on the concept of address scope, it looks like a valid use case but I might be missing somethign15:35
mlavalleit seems also to me like a reasonable use case15:36
mlavallebut the fact that it was implmented like that since the beginning moves me to be cuatious15:36
mlavallecautious15:36
amotokime too15:37
mlavalleit's not that it was possible to do this in a previous release and now we have a regression15:37
mlavalleit is a new use case. I lean towards treating this as a rfe15:38
amotokiagree. perhaps is is a new use case. as you say, it was impossible in the past releases.15:39
mlavalleI will go through the original patchset and try to glean out from the comments if something was said about this15:39
mlavallehaleyb: do you have any recollections from this review?^^^15:39
haleybmlavalle: not down to that level of detail, no15:40
*** donghao has quit IRC15:41
mlavallecool, I'll comment in the bug that we are open to discuss this, but that we are going to move with caution given what we just discussed15:41
mlavallehaleyb, amotoki: is that ok?15:41
amotokimlavalle: agree15:42
haleybmlavalle: i don't believe the current patch removing the check is correct at least15:42
mlavallebtw, I went through the chapter in the networking guide and it doesn't provides any specific guidance15:42
mlavallehaleyb: yeah, seems a bit rash15:43
haleybat best we check for shared as well, but like you said, be cautious15:43
mlavalleamotoki: thanks for your comments15:44
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/168322715:45
openstackLaunchpad bug 1683227 in neutron "test_connection_from_same_address_scope failed with: Cannot find device "qg-74372988-7f"" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:45
*** cshastri has joined #openstack-meeting-315:45
mlavalleI intended to work on this one, but got distracted by the previous one. I will get back to it15:46
mlavalleFinally, for today, we have https://bugs.launchpad.net/neutron/+bug/169476415:47
openstackLaunchpad bug 1694764 in neutron "test_metadata_proxy_respawned failed to spawn metadata proxy" [High,Confirmed]15:47
mlavalleThis one has no owner yet15:47
mlavalleany other bugs we should discuss today?15:48
haleybi had none15:48
mlavalleok, moving on15:49
mlavalle#topic DNS15:49
*** openstack changes topic to "DNS (Meeting topic: neutron_l3)"15:49
mlavallehaleyb: here I want to say that I have finish coding this, including unit tests15:49
mlavalleI hit a weird python 3.5 unit test failure15:50
mlavallethe test case passes python 2.715:50
mlavallebut if fails in 3.515:50
mlavalleso as soon as I fix that, I'll bug you for reviews :-)15:50
davidsha_do you have a link to it or is this local?15:51
haleybusually it's the other way around, fails on 3.515:51
mlavalleyeah, failed in 3.515:51
haleyboh, i must be dyslexic :)15:51
mlavalledavidsha_: it is the failure here: https://review.openstack.org/#/c/468697/15:52
mlavalleThe patchset adds the test case that fails in the 3.5 job15:52
*** tobberydberg has joined #openstack-meeting-315:53
davidsha_but passes in 2.7, that's weird, was expecting an attribute error or something.15:53
mlavalle#topic Open Agenda15:53
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_l3)"15:53
davidsha_Just on the reason why there was a lock on tenants earlier: https://review.openstack.org/#/c/197552/3/neutron/db/db_base_plugin_v2.py@74315:54
davidsha_It seems the spec will be the place to find out.15:55
mlavalledavidsha_: yeah, I was looking for something like that15:55
mlavalleThanks!15:55
mlavalledavidsha_: I still have to take time to look at your PoC15:56
*** reedip_ has quit IRC15:56
mlavalleI will do my best over the next few days :-)15:57
*** tobberydberg has quit IRC15:57
davidsha_mlavalle: No problem, working on a follow on, there are a few issues with ipv6 so I'll try to have those fixed asap.15:57
mlavallecool15:57
mlavalleany other topics?15:57
davidsha_the spec mentioned in the comment: https://review.openstack.org/#/c/180267/15:58
*** dtantsur has joined #openstack-meeting-315:58
mlavalleperfect, thanks!15:58
mlavallelet's call it a day, then15:58
mlavalleTnanks for attending15:58
mlavalle#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Thu Jun 15 15:59:03 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-06-15-15.00.html15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-06-15-15.00.txt15:59
*** cdent has joined #openstack-meeting-315:59
davidsha_Thanks, cya!15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-06-15-15.00.log.html15:59
amotokithanks15:59
haleybbye15:59
*** janzian has quit IRC16:00
cdent#startmeeting api-wg16:00
openstackMeeting started Thu Jun 15 16:00:11 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: api-wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
cdent#chair edleafe cdent elmiko16:00
openstackWarning: Nick not in channel: elmiko16:00
openstackCurrent chairs: cdent edleafe elmiko16:00
cdent#link agenda https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:00
cdentwho is here for some api-wg joy?16:00
cdentthere's nothing new on the agenda16:01
edleafe\0/16:01
cdentthere were no action items from last week16:01
dtantsuro/16:02
cdentoh hey dtantsur thank for joining in16:02
cdentdo you have anything to bring up this week?16:02
* dtantsur does not16:03
*** mlavalle has left #openstack-meeting-316:03
edleafeThere are now a whopping 6 votes in the naming survey16:03
cdentany clear winner?16:04
edleafeSo far 'not_before' is narrowly edging out 'earliest_min_raise_date'16:04
edleafewith '16:04
edleafemin_raise_not_before' trailing a bit further behind16:05
*** haleyb_ has quit IRC16:05
cdentso if we went with that, then we'd be reverting back to the original and all this flim flam was for nothing and I should sit on a step and think about what I did16:06
edleafeWell, if you question a choice, put it up for a vote, and that choice wins, is that a bad thing?16:06
edleafeAt least if there were strong feelings, they had a chance to be heard16:07
cdenttrue16:08
*** lyan has quit IRC16:09
cdentI was mostly just trying to inject the usual sarcasm into today's meeting, but I think the big tent is weighing me down.16:09
*** slaweq has joined #openstack-meeting-316:09
edleafeSo I'll move ahead with that change? And maybe freeze next week?16:09
cdentyes, that sounds great16:09
cdent#action edleafe to update microversion to not_before16:09
edleafeyeah, I was thinking about tossing a molotov cocktail into that discussion16:09
edleafeand stop using "big tent"!16:09
*** armstrong has quit IRC16:10
*** mickeys has joined #openstack-meeting-316:10
cdentthat's agreed16:10
*** julim has quit IRC16:11
cdentbut the rest of it, not so much16:11
cdent#topic guidelines16:11
*** openstack changes topic to "guidelines (Meeting topic: api-wg)"16:11
cdent#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:11
cdentnobody minused the frozen things16:12
edleafemerge 'em!!16:12
* cdent does so16:12
*** julim has joined #openstack-meeting-316:13
* edleafe cheers16:13
cdentanything from here and above ready? https://review.openstack.org/#/c/459405/16:14
edleafeHaven't looked in a few days16:14
dtantsurI haven't read it yet16:14
*** SumitNaiksatam has joined #openstack-meeting-316:15
*** mickeys has quit IRC16:15
cdentthen I reckon they can safely sit, yeah?16:15
edleafeSo let's all read it, and maybe see about freezing next week?16:15
edleafeSpeaking of next week, need me to run the meeting, cdent?16:15
cdentyes and yes16:16
cdentand the week after that16:16
edleafe...and the week after that, no? When do you officially return?16:16
cdentthe 5th, so I'll be around for the 6th and I'd like to set the precedent that this is one of the regular inviolable times16:17
edleafecool16:18
cdent#topic bugs16:19
*** openstack changes topic to "bugs (Meeting topic: api-wg)"16:19
cdentno changes16:19
cdentObviously during those two weeks where I'm away dtantsur should fix all the bugs, right?16:19
dtantsur\o/16:20
dtantsur$ cd api-wg && git rm . && git commit -am "boo" && git push -f16:20
cdentharsh16:20
dtantsurdifficult times - difficult decisions!16:21
cdenttrue16:21
*** yamahata has quit IRC16:21
edleafeThat's stolen from my inbox-zero method16:21
cdentany other concerns to think about before we declare it newsletter time?16:22
cdentif it was important they'll mail again16:22
dtantsur++16:22
cdent#topic weekly newsletter16:23
*** openstack changes topic to "weekly newsletter (Meeting topic: api-wg)"16:23
cdent#link https://etherpad.openstack.org/p/api-wg-newsletter16:23
cdentany takers, or shall I?16:23
*** lyan has joined #openstack-meeting-316:23
edleafego for it16:24
cdentI'll ping when I want a proof16:24
*** slaweq has quit IRC16:25
cdentThanks for your attention and attendance. If I show up next week it is only because I miss you and not because I'm obsessed.16:25
cdent#endmeeting16:25
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:25
openstackMeeting ended Thu Jun 15 16:25:41 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-06-15-16.00.html16:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-06-15-16.00.txt16:25
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-06-15-16.00.log.html16:25
*** dtantsur has left #openstack-meeting-316:25
*** julim has quit IRC16:30
*** slaweq has joined #openstack-meeting-316:32
*** abramley has quit IRC16:32
*** iyamahat has joined #openstack-meeting-316:37
*** mickeys has joined #openstack-meeting-316:40
*** lhx__ has quit IRC16:43
*** slaweq has quit IRC16:43
*** Neptu has quit IRC16:43
*** bobh has quit IRC16:45
*** mickeys has quit IRC16:45
*** Neptu has joined #openstack-meeting-316:51
*** pasquier-s_ has quit IRC16:55
*** ltomasbo is now known as ltomasbo|away16:56
*** yamahata has joined #openstack-meeting-316:57
*** Neptu has quit IRC16:58
*** Swami has quit IRC16:59
*** yamahata has quit IRC17:00
*** cdent has left #openstack-meeting-317:00
*** yamahata_ has joined #openstack-meeting-317:01
*** ralonsoh has quit IRC17:01
*** neiljerram has quit IRC17:03
*** abramley has joined #openstack-meeting-317:07
*** sambetts is now known as sambetts|afk17:08
*** abramley has quit IRC17:09
*** jtomasek has quit IRC17:13
*** bobh has joined #openstack-meeting-317:14
*** salv-orl_ has joined #openstack-meeting-317:14
*** pcaruana has quit IRC17:16
*** salv-orlando has quit IRC17:17
*** Neptu has joined #openstack-meeting-317:18
*** SumitNaiksatam has quit IRC17:23
*** SumitNaiksatam has joined #openstack-meeting-317:25
*** Swami has joined #openstack-meeting-317:30
*** vkmc_ has quit IRC17:31
*** SumitNaiksatam has quit IRC17:31
*** SumitNaiksatam has joined #openstack-meeting-317:35
*** cshastri has quit IRC17:35
*** mickeys has joined #openstack-meeting-317:46
*** tbachman has joined #openstack-meeting-317:48
*** mickeys has quit IRC17:50
*** davidsha_ has quit IRC17:57
SumitNaiksatamtbachman: hi18:00
tbachmanSumitNaiksatam: hi!18:00
*** annak has joined #openstack-meeting-318:00
SumitNaiksatamannak: hi18:00
*** rkukura has joined #openstack-meeting-318:00
tbachmanthey18:00
tbachmankeep18:00
tbachmanrolling18:00
tbachmanin18:00
SumitNaiksatamrkukura: hi18:00
rkukurahi18:01
SumitNaiksatamtbachman: :-)18:01
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Jun 15 18:01:05 2017 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
annakhi18:01
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#June_15th_201718:01
SumitNaiksatam#topic Subnetpools in resource_mapping driver18:01
*** openstack changes topic to "Subnetpools in resource_mapping driver (Meeting topic: networking_policy)"18:01
SumitNaiksatam#link https://review.openstack.org/46968118:01
* tbachman runs and hides18:01
SumitNaiksatamwe have been discussing this offline18:01
*** cshastri has joined #openstack-meeting-318:02
SumitNaiksatamtbachman: lol18:02
SumitNaiksatamannak: any new updates beyind what you mentioned in the emails?18:02
annakNo18:03
SumitNaiksatamannak: ok18:03
annakCurrently the patch implements the "ugly" solution18:03
annakwith delete issue unsolved18:03
SumitNaiksatamrkukura: any new ideas besides what we discussed, since you mentioned that relaxing that the one subnetpool per netwok constraint is required18:03
SumitNaiksatamannak: right, come to that delete issue in a minute18:04
*** haleyb_ has joined #openstack-meeting-318:04
rkukuraso why can’t proxy groups use subnets from the same subnetpool as the PTG?18:04
SumitNaiksatamrkukura: they can, and that is what we are doing, but we need to carve out dedicated prefix for them18:04
rkukurado we definitely need a dedicated prefix?18:05
SumitNaiksatamseems like18:05
SumitNaiksatambecause that assignments from that prefix are only significant in the traffic stitched path18:06
SumitNaiksatamits not meant to eat into the “ip_pool” that the user may desire and has set for the l3p18:06
annakis there any significance in separating the two address spaces - ip pool and proxy ip pool?18:07
SumitNaiksatambesides there might be routing/connectivity implications which i am probably forgetting here18:08
rkukuraannak: That is what I’m asking - after the proxy subnet is allocated, is it treated any differently?18:08
SumitNaiksatamannak: rkukura: i think routes might be set in the stitched path18:08
rkukuraLike is some routing based on the proxy prefix?18:08
SumitNaiksatamyeah, which is easier to do with a completely separate prefix18:09
SumitNaiksatamand is how its most likely currently implemented18:09
*** songole has joined #openstack-meeting-318:10
SumitNaiksatamsongole: hi18:10
songoleHi SumitNaiksatam18:10
SumitNaiksatamsongole: discussing proxy_pool again :-)18:10
songoleok. goog timing18:10
SumitNaiksatamannak: rkukura: one thing came up while discussing with tbachman yesterday, i was thinking if GBP can extend the subnetpool API to take the list of prefixes for assignment18:11
tbachmanSumitNaiksatam: should we bring songole up to speed?18:11
SumitNaiksatam(as opposed to the current API of a single prefix or everything)18:12
SumitNaiksatamtbachman: yes sure18:12
rkukuraSo do you mean we’d have a single subnetpool, but be able to allocate from different sets of prefixes for normal vs. proxy PTGs?18:12
SumitNaiksatamrkukura: yeah18:12
tbachmansongole: we’re struggling a bit with the prefixes for the proxy18:12
tbachmanright now, the implicit workflow allows the user to provide a prefix via the .ini file (or just use a default) to use for the proxy_ip_pool18:13
songoletbachman: ipv4 & ipv6 - separate prefixes?18:13
annakSumitNaiksatam: I think the problem with passing a cidr to subnetpool is that it has to be a complete cidr with prefix len, not just "give me something 192.168-ish"18:13
tbachmansongole: yes, but I think we have this issue even with single staack18:13
rkukuraI think the fundemental question is whether we really need the proxy subnets under a single distinct prefix, or if we could simply allocate them from the same subnetpool as regular PTGs use?18:13
tbachmanwhen subnetpools are used to allocate subnets to a network, neutron requires that all subnets on that network also be allocated from that specific subnetpool18:14
SumitNaiksatamrkukura: to the extent i recall it needs to be distinct at least in the current implementation, thats the whole reason we defined this extention18:14
* tbachman quiets down to minimize thread switching18:14
SumitNaiksatamtbachman: sorry, for talking over18:15
tbachmanSumitNaiksatam: I think it was the other way around ;)18:15
tbachmanSumitNaiksatam: please continue18:15
songolerkukura: the subnet size for proxy pool is very small. that is a reason why it is a separate pool18:15
SumitNaiksatamsongole: yes, definitely one of the reasons, we did not want IPs to be wasted18:15
rkukuraOK, but we I think decided not to use the default_prefix_len of the subnetpool anyway18:16
rkukuradiifferent sized subnets can easily be allocated from the same subnetpool18:16
annakyes, we can respect the proxy prefix length parameter and still allocate from regular pool18:17
rkukuraIs there a difference in need for public IPs? For example, might publicly routable IPs be needed for regular subnets but not for proxy subnets?18:17
songoleSumitNaiksatam: the other reason being it to be quite distinct from the regular subnet.. doesn't have to be18:17
songolemakes it easy to distinguish18:17
SumitNaiksatamsongole: the “doesnt have to be” part is what we are debating about18:17
songoleannak, rkukura: if we can allocate different sized subnets, I suppose it should be ok.18:18
SumitNaiksatamsongole: i was also mentioning earlier, that it was indentified at that time we dont want to waste the “ip_pool” addresses for internal assignment18:19
rkukuraSumitNaiksatam: Does “internal assignment” mean the proxy subnets don’t need to be publicly routable even when the regular subnets are (i.e. no-NAT)?18:20
SumitNaiksatamsongole: this, along with the complexity of  assigning routes, was the major motivating factor separating the two18:20
SumitNaiksatamrkukura: yes18:20
annakrkukura: "dont need to be" or "must not be" publicly routable?18:21
rkukuraannak: I’d like to understand whether its “don’t need to be”, “must not be”, or “must be”.18:21
songoleI believe we assign fips to proxy ips in the case of vpn18:22
SumitNaiksatamsongole: no18:22
rkukurasongole: That would mean “must be”, right?18:22
annaki understood proxy ip are only internal, is that wrong?18:23
songoleSumitNaiksatam: I will get back on that.18:23
SumitNaiksatamsongole: proxy_pool is only for interal stitching assignment18:23
rkukuraor maybe not, since fips imply NAT18:23
SumitNaiksatamonly IPs from “ip_pool” are NAT'ed18:23
songolewhen fw is inserted, traffic is routed to stitching ip18:24
songolewhich is allocated from proxy pool18:24
rkukuraSumitNaiksatam: thanks - I guess one argument would be to not waste public IP space for proxy subnets when normal subnets are public (no-NAT)18:24
*** rstarmer has joined #openstack-meeting-318:25
SumitNaiksatamrkukura: it might not just be a public space issue18:25
SumitNaiksatamrkukura: even withing the organization, they might not want IPs to be wasted for internal assignment18:26
*** abramley has joined #openstack-meeting-318:26
SumitNaiksatamwhen its possible to us a locally scoped space18:26
SumitNaiksatamsongole: routing to proxy_ips only happens within the stitched path18:28
SumitNaiksatamsongole: no entity outside the stitched patch is aware of the proxy_ip assignments18:28
annaksounds like the intuitive thing would be to configure two subnetpools.18:29
SumitNaiksatamsongole: the proxy_group takes over the original PTG’s identitiy on one side, and connects to the original PTG via the proxy IPs and the stiched path (with the inserted service) on the other side18:29
rkukuraannak, even if we did configure two subnetpools, these would need to reference the same address_scope, right, to ensure no overlap18:30
annakrkukura: yes18:30
songoleSumitNaiksatam: right. vpn gets terminated on the fw. The only way you can reach vpn from outside would be by way of attaching a fip18:30
songoleAgain, I will get back on the fip part18:31
SumitNaiksatamsongole: but the FIP would be associated with a PT’s IP, not an IP from the proxy_pool, right?18:31
SumitNaiksatamsongole: okay18:31
rkukuraAnd, assuming we need the proxy and normal subnets on the same L2 network, using separate subnetpool would require relaxing neutron’s restriction.18:31
SumitNaiksatambecause no one else knows about that IP from proxy_pool18:32
annakrkukura: yes18:32
SumitNaiksatami guess they could belong to separate address spaces and we can enforce that they dont overlap, but they would have to map to same backend VRF18:33
SumitNaiksatamso that they are all reachable18:33
annakrkukura: I asked salvatore about the limitation and he thinks its  because subnet pools were introduced before address scopes.18:33
rkukuraI’m not fundementally opposed to relaxing that restriction (as long as same address_scope is required for all subnetpools on a network), but I think it would be difficult to change in Neutron. The subnetpool’s address_scope_id attribute is mutable, and there would be no way to atomically associate a set of subnetpools with a new address_scope.18:34
*** cshastri has quit IRC18:34
annakrkukura: we can try to relax the limitation only for subnetpools that are already within same address scope18:35
*** armstrong has joined #openstack-meeting-318:35
rkukuraannak: That might make sense on its own, but what if one of those subnetpool’s addres_scope_id value is changed?18:35
*** rstarmer has quit IRC18:36
rkukuraOur mechanism driver currently blocks changing the address_scope_id of subnetpool, but there may be valid use cases for changing this.18:36
SumitNaiksatamrkukura: in the apic_mapping mechanism driver, is it possible to associate mutliple address_scopes with the same VRF?18:37
SumitNaiksatamaddress_scopes of the same family that is18:37
annakrkukura: i guess we should disallow such change if subnets are already allocated.. maybe similar checks are already in place, i can investigate that18:38
rkukuraSumitNaiksatam: In the aim_mapping MD, at most one v4 and at most one v6 scope can reference the same VRF18:38
SumitNaiksatamannak: that validation would have to be in whichever Neutron mechanism driver or monolithin plugin is deployed18:38
SumitNaiksatamrkukura: okay, so i guess multiple address_scopes is a non-starter (even as a hack)18:39
rkukuraI think the current one-subnetpool-per-family-per-network validation is done in neutron code, not in plugin or driver code, but I could be wrong.18:39
SumitNaiksatamrkukura: ah you mean the DB level code?18:40
tbachmanI think there are two thigns here18:40
*** rstarmer has joined #openstack-meeting-318:40
tbachmanone is a mapping to VRFs, which is ACI specific18:40
annakrkukura: you're right, in neutron18:40
tbachmanthe other is mapping of subnets belonging to address scopes to networks18:40
annak(NetworkSubnetPoolAffinityError)18:40
rkukuraSumitNaiksatam: yes, plus the code that populates network dicts with subnetpool and address scope IDs.18:41
SumitNaiksatamrkukura: annak: but that is something that is something that can be overridden at the plugin level (in theory)18:41
annakI think the scenario we're struggling with is not unique to GBP18:41
SumitNaiksatamtbachman: i agree, but I brought VRFs, because I am sure the same/similar concepts apply for other backends as well18:42
SumitNaiksatamannak: agree18:42
SumitNaiksatam*brought up18:42
SumitNaiksatamjust a quick time check, we are 42 mins into the meeting :-)18:43
tbachman:)18:43
tbachmanSumitNaiksatam: it’s a tough problem18:43
SumitNaiksatamcouple of other topics to quickly touch up on18:43
SumitNaiksatamtbachman: yes definitely18:43
rkukuraok18:43
SumitNaiksatamshould we quickly bring up those topics and revert to this discussion in the open discussion section?18:43
annaksorry I'll need to leave 5 min yearly18:44
rkukurasure18:44
SumitNaiksatamannak: oops18:44
SumitNaiksatam#topic Ocata sync18:44
*** openstack changes topic to "Ocata sync (Meeting topic: networking_policy)"18:44
SumitNaiksatam#link https://review.openstack.org/#/q/topic:ocata_sync18:44
SumitNaiksatamannak: we will try to do this quickly18:44
SumitNaiksatamannak: i know you are blocked on the dependent repos18:44
annak(I mean, 11:55)18:44
SumitNaiksatamannak: ah okay18:45
SumitNaiksatamannak: i am working on those18:45
annakSumitNaiksatam: thanks!18:45
SumitNaiksatami finished the python-opflex-agent18:45
SumitNaiksatamwhich was fairly straightforward18:45
SumitNaiksatambut i am having trouble with the apic-ml2 repo18:45
SumitNaiksatamin trying to get the tests to be aligned with the refactored code18:46
tbachmanSumitNaiksatam: anything I can help with?18:46
SumitNaiksatamtbachman: yes i will let you, thanks18:46
tbachmanSumitNaiksatam: np!18:46
tbachmanSumitNaiksatam: are you doing these under a topic?18:46
* tbachman goes to gerrit18:46
SumitNaiksatamannak: i will keep you updated, i was hoping that i would have been long done with this18:46
SumitNaiksatamtbachman: no actually its a github repo18:46
tbachmanah, right18:47
*** mickeys has joined #openstack-meeting-318:47
SumitNaiksatamand i have not posted a new branch18:47
SumitNaiksatambut will do so18:47
SumitNaiksatami thought i would fix the issue and do it18:47
SumitNaiksatami did some whole sale changes, and i cant figure out what is causing a wierd failure18:47
SumitNaiksatami think i got some mocking wrong somewhere18:47
SumitNaiksatamanyway18:48
tbachmanSumitNaiksatam: which branch ?18:48
SumitNaiksatamtbachman: not posted yet18:48
SumitNaiksatamannak: anything else you wanted to bring up on this?18:48
annakSumitNaiksatam: no, I don't think so18:48
SumitNaiksatamannak: one question we had for you was whether the two patches which have been merged today, should be backported to stable/newton18:48
SumitNaiksatami guess not required to be18:49
rkukuraSumitNaiksatam: Do either of annak’s patches that merged to master today need to be back-ported to stable/newton?18:49
SumitNaiksatamrkukura: yeah, just asking18:49
rkukurashould read as I type ;)18:49
annaki think we wanted this for the ease of merging? I can backport them18:49
SumitNaiksatamannak: ok cool18:49
rkukuramakes sense to me18:49
annaknp, will do18:49
SumitNaiksatamrkukura: i was just about to type “makes sense” :-)18:50
SumitNaiksatam#topic NFP patches18:50
*** openstack changes topic to "NFP patches (Meeting topic: networking_policy)"18:50
SumitNaiksatamsongole: hi, we can merge the patches now, my only probably was that the NFP gate job keeps failing18:50
SumitNaiksatamsongole: is it because its something wrong with the job or is it the patches that are breaking the job?18:50
songoleSumitNaiksatam: I believe it is the test issue.18:51
songoleI will check18:51
songoleagain18:51
*** mickeys has quit IRC18:51
SumitNaiksatamsongole: so pleaese +2 the patches that are comfortable with, and the rest of the reviewers will check accordingly18:51
SumitNaiksatamsongole: thanks18:52
SumitNaiksatam#topic Open Discussion18:52
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:52
SumitNaiksatamreverting back to the subnetpools discussion18:52
SumitNaiksatamin my mind one of the priorities is to unblock annak with respect to the patch18:53
rkukuraFor that purpose, I don’t think we can really consider any changes to neutron itself, right?18:53
SumitNaiksatamrkukura: we could patch neutron in GBP, no?18:54
rkukuraEven if apic_aim or vmware drivers/plugins want to change Neutron, don’t we need the RMD to work with arbitrary neutron back-ends?18:54
SumitNaiksatamrkukura: overriding by18:55
SumitNaiksatamsorry, hit enter too soon18:55
SumitNaiksatamannak: i guess its time for you to take off18:55
annaksorry i have to leave, will read the discussion afterwards, thanks everyone!18:55
tbachmanLet’s presume we aren’t patching neutron — is there another solution other than either using the exisgint pool or adding the prefix to it?18:55
*** annak has quit IRC18:55
tbachmancan we have a separate network, as annak was asking?18:56
rkukuraMy point was simply that if GBP were to monkey-patch neutron to relax the restricition, that could break neutron plugins or drivers that expect that restriction to be enforced.18:56
SumitNaiksatamtbachman: i dont think so18:56
tbachmanand can we entertain other options for services and/or the proxy?18:56
tbachman(i.e. how much are we open to changing here)18:57
SumitNaiksatamrkukura: yes I agree, although in this case, GBP is being less restrictive18:57
SumitNaiksatamtbachman: that becomes a longer discussion, and to my earlier point, it does not allow annak to make progres in the near term18:57
SumitNaiksatamhence i was suggesting that we add an additional API option to the subnetpools18:58
SumitNaiksatamone we implement in GBP and extend subnetpools18:58
SumitNaiksatamand that allows taking in a one or more prefixes for assignment18:58
SumitNaiksatamin the easiest implementation, it would just iterate throught the prefixes until an allocation is successful18:59
SumitNaiksatamthis would most likely be less optimal than allowing neutron subnetpool implementation to handle the choosing of the prefix18:59
* tbachman notes the time19:00
SumitNaiksatamtbachman: thanks19:00
SumitNaiksatamyes we got to end it there for today19:00
rkukuraIs it worth looking at just using the same subnetpool and a different prefix_len? Do we know what other code would need to change (setting up routes, etc.)?19:00
SumitNaiksatamback to the offline discussion on this19:00
rkukurathanks SumitNaiksatam!19:00
tbachmanSumitNaiksatam: thanks for leading this!19:00
SumitNaiksatamrkukura: yes, i believe that would required rewriting the traffic stitching implementation19:00
SumitNaiksatamthanks all for attending19:00
SumitNaiksatambye!19:00
rkukurabye19:01
tbachmanSumitNaiksatam: bye!19:01
SumitNaiksatam#endmeeting19:01
songolebye19:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:01
openstackMeeting ended Thu Jun 15 19:01:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-06-15-18.01.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-06-15-18.01.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-06-15-18.01.log.html19:01
*** tbachman has left #openstack-meeting-319:01
*** rkukura has left #openstack-meeting-319:01
*** lucasxu has quit IRC19:10
*** slaweq has joined #openstack-meeting-319:11
*** lucasxu has joined #openstack-meeting-319:11
*** abramley has quit IRC19:17
*** anilvenkata has quit IRC19:20
*** ducttap__ has joined #openstack-meeting-319:21
*** ducttape_ has quit IRC19:24
*** Sukhdev has joined #openstack-meeting-319:26
*** ducttape_ has joined #openstack-meeting-319:27
*** songole has quit IRC19:28
*** ducttap__ has quit IRC19:29
*** slaweq has quit IRC19:34
*** julim has joined #openstack-meeting-319:34
*** tobberydberg has joined #openstack-meeting-319:37
*** slaweq has joined #openstack-meeting-319:38
*** mickeys has joined #openstack-meeting-319:47
*** mickeys has quit IRC19:53
*** mfedosin has quit IRC19:53
*** abramley has joined #openstack-meeting-319:56
*** Guest11 has joined #openstack-meeting-320:00
*** neiljerram has joined #openstack-meeting-320:23
*** zenirc369 has quit IRC20:25
*** rstarmer has quit IRC20:31
*** rbak has quit IRC20:31
*** slaweq has quit IRC20:44
*** armstrong has quit IRC20:45
*** mickeys has joined #openstack-meeting-320:49
*** baoli has quit IRC20:50
*** mickeys has quit IRC20:54
*** lucasxu has quit IRC20:55
*** ducttape_ has quit IRC21:09
*** tobberydberg has quit IRC21:10
*** tobberydberg has joined #openstack-meeting-321:10
*** Guest11 has quit IRC21:13
*** tobberydberg has quit IRC21:15
*** gouthamr has quit IRC21:23
*** dimtruck is now known as zz_dimtruck21:25
*** ducttape_ has joined #openstack-meeting-321:34
*** slaweq has joined #openstack-meeting-321:36
*** ducttape_ has quit IRC21:38
*** slaweq has quit IRC21:40
*** ducttape_ has joined #openstack-meeting-321:41
*** gouthamr has joined #openstack-meeting-321:43
*** mickeys has joined #openstack-meeting-321:50
*** ducttape_ has quit IRC21:54
*** mickeys has quit IRC21:54
*** ducttape_ has joined #openstack-meeting-321:55
*** armstrong has joined #openstack-meeting-321:56
*** bobh has quit IRC22:05
*** ducttape_ has quit IRC22:14
*** ducttape_ has joined #openstack-meeting-322:17
*** ducttape_ has joined #openstack-meeting-322:17
*** rbak has joined #openstack-meeting-322:22
*** zz_dimtruck is now known as dimtruck22:31
*** ducttape_ has quit IRC22:33
*** ducttape_ has joined #openstack-meeting-322:34
*** salv-orl_ has quit IRC22:39
*** Swami has quit IRC22:40
*** neiljerram has quit IRC22:47
*** mickeys has joined #openstack-meeting-322:51
*** mickeys has quit IRC22:56
*** dimtruck is now known as zz_dimtruck22:59
*** slaweq has joined #openstack-meeting-323:06
*** neiljerram has joined #openstack-meeting-323:06
*** slaweq has quit IRC23:10
*** ducttape_ has quit IRC23:16
*** ducttape_ has joined #openstack-meeting-323:18
*** ducttape_ has quit IRC23:21
*** ducttape_ has joined #openstack-meeting-323:22
*** ducttape_ has quit IRC23:26
*** sdague has quit IRC23:28
*** ducttape_ has joined #openstack-meeting-323:32
*** ducttape_ has quit IRC23:37
*** mickeys has joined #openstack-meeting-323:52
*** zhipeng has joined #openstack-meeting-323:53
*** mickeys has quit IRC23:56

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