Thursday, 2017-05-25

*** claudiub has quit IRC00:00
*** diablo_rojo has joined #openstack-meeting-300:00
*** kzaitsev_mb has joined #openstack-meeting-300:01
*** anilvenkata has quit IRC00:07
*** zenirc369 has joined #openstack-meeting-300:09
*** yamahata has quit IRC00:11
*** bsilverman_14 has quit IRC00:11
*** bsilverman_ has joined #openstack-meeting-300:11
*** bobh has joined #openstack-meeting-300:12
*** SumitNaiksatam has quit IRC00:14
*** Sukhdev_ has quit IRC00:16
*** diablo_rojo has quit IRC00:17
*** wanghao_ has joined #openstack-meeting-300:21
*** armstrong has joined #openstack-meeting-300:22
*** zenirc369 has quit IRC00:23
*** sgrasley has joined #openstack-meeting-300:30
*** tuanluong has joined #openstack-meeting-300:36
*** dimtruck is now known as zz_dimtruck00:37
*** reedip_ has joined #openstack-meeting-300:38
*** armstrong has quit IRC00:38
*** bobh has quit IRC00:39
*** yamahata has joined #openstack-meeting-300:47
*** ducttape_ has joined #openstack-meeting-300:54
*** yamahata has quit IRC00:55
*** bobh has joined #openstack-meeting-301:00
*** zz_dimtruck is now known as dimtruck01:03
*** srobert has joined #openstack-meeting-301:05
*** pvaneck has quit IRC01:05
*** pvaneck has joined #openstack-meeting-301:06
*** srobert has quit IRC01:08
*** srobert has joined #openstack-meeting-301:08
*** pvaneck has quit IRC01:10
*** ducttape_ has quit IRC01:19
*** ducttape_ has joined #openstack-meeting-301:20
*** ducttap__ has joined #openstack-meeting-301:25
*** ducttap__ has quit IRC01:27
*** ducttap__ has joined #openstack-meeting-301:28
*** ducttap__ has quit IRC01:28
*** ducttape_ has quit IRC01:28
*** sgrasley has quit IRC01:33
*** bobh has quit IRC01:37
*** s3wong has quit IRC01:56
*** wanghao_ has quit IRC01:58
*** wanghao has joined #openstack-meeting-301:58
*** wanghao has quit IRC02:03
*** wanghao has joined #openstack-meeting-302:03
*** zhurong has joined #openstack-meeting-302:05
*** notmyname has quit IRC02:08
*** notmyname has joined #openstack-meeting-302:13
*** reedip_ has quit IRC02:30
*** SumitNaiksatam has joined #openstack-meeting-302:30
*** lucasxu has joined #openstack-meeting-302:33
*** donghao has joined #openstack-meeting-302:34
*** donghao has quit IRC02:38
*** galstrom_zzz is now known as galstrom02:47
*** tuanluong has quit IRC02:50
*** lucasxu has quit IRC03:06
*** lucasxu has joined #openstack-meeting-303:08
*** bobh has joined #openstack-meeting-303:10
*** ducttape_ has joined #openstack-meeting-303:16
*** ducttap__ has joined #openstack-meeting-303:17
*** ducttape_ has quit IRC03:17
*** lucasxu has quit IRC03:18
*** wanghao_ has joined #openstack-meeting-303:20
*** julim has quit IRC03:21
*** julim has joined #openstack-meeting-303:22
*** wanghao has quit IRC03:24
*** julim has quit IRC03:26
*** Sukhdev has joined #openstack-meeting-303:32
*** bobh has quit IRC03:33
*** tuanluong has joined #openstack-meeting-303:47
*** galstrom is now known as galstrom_zzz03:49
*** ducttap__ has quit IRC03:51
*** crushil has joined #openstack-meeting-303:54
*** gouthamr has quit IRC03:57
*** tuanluong has quit IRC03:59
*** benj_ has quit IRC04:03
*** benj_ has joined #openstack-meeting-304:04
*** psachin has joined #openstack-meeting-304:05
*** ducttape_ has joined #openstack-meeting-304:08
*** zhurong has quit IRC04:08
*** Sukhdev has quit IRC04:11
*** ducttape_ has quit IRC04:12
*** markvoelker has joined #openstack-meeting-304:13
*** yamamoto has quit IRC04:13
*** yamamoto has joined #openstack-meeting-304:13
*** zhurong has joined #openstack-meeting-304:16
*** yamamoto has quit IRC04:17
*** crushil has quit IRC04:38
*** kzaitsev_mb has quit IRC04:40
*** zenirc369 has joined #openstack-meeting-304:44
*** jtomasek has quit IRC04:46
*** crushil has joined #openstack-meeting-304:50
*** ltomasbo|away is now known as ltomasbo04:57
*** yamamoto has joined #openstack-meeting-305:01
*** mikal_ is now known as mikal05:06
*** markvoelker_ has joined #openstack-meeting-305:11
*** crushil has quit IRC05:13
*** markvoelker has quit IRC05:14
*** claudiub has joined #openstack-meeting-305:17
*** markvoelker has joined #openstack-meeting-305:17
*** markvoel_ has joined #openstack-meeting-305:19
*** markvoelker has quit IRC05:19
*** markvoelker_ has quit IRC05:21
*** pvaneck has joined #openstack-meeting-305:21
*** slaweq has joined #openstack-meeting-305:23
*** pvaneck has quit IRC05:25
*** SumitNaiksatam_ has joined #openstack-meeting-305:29
*** lyan has quit IRC05:29
*** SumitNaiksatam has quit IRC05:29
*** SumitNaiksatam_ is now known as SumitNaiksatam05:29
*** slaweq has quit IRC05:29
*** cshastri has joined #openstack-meeting-305:36
*** donghao has joined #openstack-meeting-305:37
*** donghao has quit IRC05:41
*** wanghao_ has quit IRC05:51
*** SumitNaiksatam has quit IRC05:51
*** SumitNaiksatam_ has joined #openstack-meeting-305:51
*** wanghao has joined #openstack-meeting-305:52
*** markvoel_ has quit IRC05:53
*** markvoelker has joined #openstack-meeting-305:53
*** markvoelker has quit IRC05:54
*** anilvenkata has joined #openstack-meeting-306:17
*** pcaruana has joined #openstack-meeting-306:20
*** anilvenkata has quit IRC06:22
*** jgu has left #openstack-meeting-306:22
*** markvoelker has joined #openstack-meeting-306:27
*** markvoelker has quit IRC06:32
*** anilvenkata has joined #openstack-meeting-306:35
*** pgadiya has joined #openstack-meeting-306:40
*** pgadiya has quit IRC06:41
*** ralonsoh has joined #openstack-meeting-306:55
*** markvoelker has joined #openstack-meeting-306:59
*** markvoelker has quit IRC07:03
*** markvoelker has joined #openstack-meeting-307:09
*** gcb has quit IRC07:10
*** dixiaoli has joined #openstack-meeting-307:13
*** gcb has joined #openstack-meeting-307:14
*** markvoelker has quit IRC07:14
*** markvoelker has joined #openstack-meeting-307:29
*** zhurong has quit IRC07:30
*** markvoelker has quit IRC07:37
*** donghao has joined #openstack-meeting-307:38
*** markvoelker has joined #openstack-meeting-307:42
*** donghao has quit IRC07:43
*** zhurong has joined #openstack-meeting-307:45
*** markvoelker has quit IRC07:49
*** wanghao_ has joined #openstack-meeting-307:51
*** wanghao has quit IRC07:53
*** mickeys has quit IRC07:55
*** wanghao_ has quit IRC08:07
*** wanghao has joined #openstack-meeting-308:08
*** markvoelker has joined #openstack-meeting-308:24
*** markvoelker has quit IRC08:30
*** markvoelker has joined #openstack-meeting-308:32
*** lpetrut has joined #openstack-meeting-308:37
*** markvoelker has quit IRC08:40
*** zhurong has quit IRC08:54
*** mickeys has joined #openstack-meeting-308:56
*** wanghao_ has joined #openstack-meeting-309:00
*** mickeys has quit IRC09:00
*** baoli has joined #openstack-meeting-309:02
*** racedo has joined #openstack-meeting-309:02
*** wanghao has quit IRC09:02
*** zhurong has joined #openstack-meeting-309:04
*** wanghao_ has quit IRC09:05
*** wanghao has joined #openstack-meeting-309:05
*** baoli has quit IRC09:06
*** wanghao_ has joined #openstack-meeting-309:15
*** markvoelker has joined #openstack-meeting-309:16
*** wanghao has quit IRC09:17
*** wanghao_ has quit IRC09:19
*** markvoelker has quit IRC09:21
*** zhurong has quit IRC09:35
*** sambetts|afk is now known as sambetts09:46
*** sdague has joined #openstack-meeting-309:46
*** markvoelker has joined #openstack-meeting-309:54
*** mickeys has joined #openstack-meeting-309:57
*** rmart04 has joined #openstack-meeting-309:58
*** markvoelker has quit IRC09:58
*** mickeys has quit IRC10:03
*** apetrich_ has quit IRC10:07
*** yamamoto has quit IRC10:11
*** ducttape_ has joined #openstack-meeting-310:13
*** ducttape_ has quit IRC10:18
*** dixiaoli has quit IRC10:39
*** markvoelker has joined #openstack-meeting-310:47
*** markvoelker has quit IRC10:52
*** tellesnobrega has quit IRC10:54
*** markvoelker has joined #openstack-meeting-310:55
*** yamamoto has joined #openstack-meeting-310:58
*** mickeys has joined #openstack-meeting-310:59
*** markvoelker has quit IRC10:59
*** mickeys has quit IRC11:03
*** markvoelker has joined #openstack-meeting-311:14
*** markvoelker has quit IRC11:19
*** dimtruck is now known as zz_dimtruck11:24
*** markvoelker has joined #openstack-meeting-311:29
*** markvoelker has quit IRC11:34
*** tellesnobrega has joined #openstack-meeting-311:35
*** pvaneck has joined #openstack-meeting-311:37
*** pvaneck has quit IRC11:42
*** jtomasek has joined #openstack-meeting-311:46
*** mickeys has joined #openstack-meeting-312:00
*** apetrich_ has joined #openstack-meeting-312:00
*** markvoelker has joined #openstack-meeting-312:00
*** sgrasley has joined #openstack-meeting-312:02
*** markvoelker has quit IRC12:04
*** mickeys has quit IRC12:04
*** tellesnobrega has quit IRC12:07
*** xavierr has joined #openstack-meeting-312:08
*** lyan has joined #openstack-meeting-312:09
*** markvoelker has joined #openstack-meeting-312:11
*** zz_dimtruck is now known as dimtruck12:11
*** markvoelker has quit IRC12:15
*** markvoelker has joined #openstack-meeting-312:17
*** markvoelker has quit IRC12:22
*** ducttape_ has joined #openstack-meeting-312:27
*** tellesnobrega has joined #openstack-meeting-312:28
*** srobert has quit IRC12:34
*** ducttape_ has quit IRC12:43
*** bobh has joined #openstack-meeting-312:48
*** lyan has quit IRC12:49
*** markvoelker has joined #openstack-meeting-312:56
*** yamamoto has quit IRC12:56
*** mickeys has joined #openstack-meeting-313:00
*** yamamoto has joined #openstack-meeting-313:02
*** gouthamr has joined #openstack-meeting-313:02
*** mickeys has quit IRC13:05
*** baoli has joined #openstack-meeting-313:05
*** psachin has quit IRC13:13
*** baoli has quit IRC13:13
*** baoli has joined #openstack-meeting-313:13
*** julim has joined #openstack-meeting-313:15
*** lucasxu has joined #openstack-meeting-313:16
*** iyamahat has joined #openstack-meeting-313:18
*** ccamacho|out has quit IRC13:18
*** lyan has joined #openstack-meeting-313:21
*** dixiaoli has joined #openstack-meeting-313:26
*** lucasxu has quit IRC13:27
*** lucasxu has joined #openstack-meeting-313:27
*** bfournie has joined #openstack-meeting-313:27
*** dixiaoli has quit IRC13:28
*** VW has joined #openstack-meeting-313:29
*** markvoelker has quit IRC13:33
*** lucasxu has quit IRC13:33
*** lucasxu has joined #openstack-meeting-313:34
*** VW has quit IRC13:36
*** VW has joined #openstack-meeting-313:36
*** spzala has joined #openstack-meeting-313:37
*** yamahata has joined #openstack-meeting-313:39
*** baoli_ has joined #openstack-meeting-313:40
*** baoli has quit IRC13:43
*** lucasxu has quit IRC13:43
*** lucasxu has joined #openstack-meeting-313:43
*** donghao has joined #openstack-meeting-313:46
*** donghao has quit IRC13:51
*** hjensas has joined #openstack-meeting-313:56
*** reedip_ has joined #openstack-meeting-313:57
*** iyamahat has quit IRC14:00
*** mickeys has joined #openstack-meeting-314:01
*** dimtruck is now known as zz_dimtruck14:02
*** yamahata has quit IRC14:02
*** mickeys has quit IRC14:05
*** apetrich_ has quit IRC14:06
*** apetrich has joined #openstack-meeting-314:06
*** ducttape_ has joined #openstack-meeting-314:07
*** ccamacho has joined #openstack-meeting-314:07
*** MarkBaker has quit IRC14:09
*** spzala has quit IRC14:14
*** markvoelker has joined #openstack-meeting-314:15
*** lhx__ has joined #openstack-meeting-314:15
*** jtomasek has quit IRC14:16
*** MarkBaker has joined #openstack-meeting-314:21
*** zenirc369 has quit IRC14:21
*** markvoelker has quit IRC14:23
*** yamamoto has quit IRC14:24
*** ducttape_ has quit IRC14:27
*** zz_dimtruck is now known as dimtruck14:29
*** Swami has joined #openstack-meeting-314:30
*** Swami has quit IRC14:31
*** claudiub has quit IRC14:33
*** ducttape_ has joined #openstack-meeting-314:34
*** ducttape_ has quit IRC14:35
*** dimtruck is now known as zz_dimtruck14:35
*** ducttape_ has joined #openstack-meeting-314:35
*** zz_dimtruck is now known as dimtruck14:37
*** galstrom_zzz is now known as galstrom14:38
*** lucasxu has quit IRC14:39
*** yamamoto has joined #openstack-meeting-314:39
*** ducttape_ has quit IRC14:39
*** anilvenkata has quit IRC14:41
*** yamamoto has quit IRC14:44
*** rhochmuth has joined #openstack-meeting-314:55
*** spzala has joined #openstack-meeting-314:55
*** lucasxu has joined #openstack-meeting-314:56
*** janzian has joined #openstack-meeting-314:56
*** tellesnobrega has quit IRC14:57
*** mlavalle has joined #openstack-meeting-314:58
*** haleyb has joined #openstack-meeting-314:58
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu May 25 15:00:08 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 haleyb15:00
openstackCurrent chairs: haleyb mlavalle15:00
haleybhi15:00
haleybSwami will not be attending today15:00
mlavalleswami pinged me earlier today. He won't make it to today's meeting15:00
mlavalleLOL15:00
haleybjinx15:01
*** claudiub has joined #openstack-meeting-315:01
*** markvoelker has joined #openstack-meeting-315:01
mlavalle#topic Announcements15:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:01
*** rossella__ has quit IRC15:01
mlavallePike 2 is almost here, June 5 - 9.15:02
mlavalleLess than 2 weeks from now15:02
*** mickeys has joined #openstack-meeting-315:02
mlavalle#link https://releases.openstack.org/pike/schedule.html15:02
mlavalleany other annoucements15:03
mlavalle?15:03
haleybnot from me15:03
mlavalleok.....15:03
mlavalle#topic Bugs15:03
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:03
*** ltomasbo is now known as ltomasbo|away15:04
mlavallehaleyb: do you have dvr bugs to discuss today?15:04
haleybthere are no new bugs, let me look quickly at older ones15:05
mlavallecool15:05
*** marst_ has joined #openstack-meeting-315:05
haleybno, just the RFE/bug swami is working on for centralized15:06
*** cshastri has quit IRC15:06
mlavalleok15:06
*** mickeys has quit IRC15:07
mlavalleon the l3-dhcp-ipam side:15:07
mlavallehttps://bugs.launchpad.net/neutron/+bug/168468215:07
openstackLaunchpad bug 1684682 in neutron "DHCP namespace doesn't have IPv6 default route" [High,In progress] - Assigned to Brian Haley (brian-haley)15:07
mlavalleI reviewed the patchset earlier this week15:07
mlavalleNice! I enjoyed reviewing it15:07
haleybmlavalle: yes, thanks for that, i will ping kevinbenton for review15:08
mlavallecool15:08
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/165556715:08
openstackLaunchpad bug 1655567 in neutron "DHCPv6 failures with "address already allocated in subnet" error" [High,Confirmed] - Assigned to Miguel Lavalle (minsel)15:08
mlavalleI made progress on this one15:09
mlavalleI found it is a race condition between two requests15:09
*** apetrich has quit IRC15:09
haleybtwo requests asking for the same IP?15:10
mlavallenot exactly15:10
mlavallefirst one attempts to create a dhcpv6-stateless subnet15:11
mlavallethe second one updates the dhcp port for this subnet and allocates an ip adress succesfully15:11
*** apetrich has joined #openstack-meeting-315:12
mlavalleso when the first one executes https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L44915:12
mlavalleit fails adding ip address to the DHCP port15:12
mlavallehaleyb: so, should the DHCP agent request be trying to add an ip address to the port on a dhcpv6-stateless subnet?15:14
haleybi was just looking at that code for another bug15:15
mlavalleisn't that an autoaddress that should be added by the method above^^^15:15
mlavalle?15:15
haleybit requests a port on all subnets where dhcp is enabled15:15
haleybso maybe there is a bug?15:15
mlavalleI am certain there is a bug15:16
mlavalleeither the agent shouldn't be requesting the ip address in the second request15:16
mlavalleor the method above should skip dhcp ports15:16
mlavalleright?15:17
mlavallesince this is an autoaddress subnet, I lean towards the bug being in the agent (the second request)15:17
*** rossella__ has joined #openstack-meeting-315:18
mlavalleThat is why we have the method above^^^ to allocate from autoaddress subnets15:18
haleybi'm thinking the agent should be the one to request it15:18
haleybin the ipv4 case it's the agent that does this15:19
mlavalleok, in that case, we should refine this query https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L46115:19
mlavalleto exclude dhcp owned ports15:19
*** yamamoto has joined #openstack-meeting-315:20
*** yamamoto has quit IRC15:20
haleybmlavalle: that's probably worth a try15:21
mlavallehaleyb: ok, let's follow that path15:21
haleybwe probably haven't thought of something which the tests should shake out15:21
mlavallehere's the plan: 1) I will spend some time in kibana with other ocurrences of the bug, to make sure I see the same thing15:22
haleybmlavalle: the other way is to have the agent look for the mode flags15:22
mlavalleyeah15:22
mlavalleand if the mode flag is dhcpv6-stateless, let the server take care of the address, right?15:23
*** ducttape_ has joined #openstack-meeting-315:24
haleybright, that might be more invasive and wouldn't cover other drivers that use the same logic as the linux one15:24
*** elmiko has joined #openstack-meeting-315:24
mlavallebut it is conceptually beter, IMO. since the subnet is dhcpv6-stateless, dhcp shouldn't be handing out addresses15:25
haleybthe linux driver should have tried to use an existing port, and only creates a new one if it doesn't exist, so guess that's the race15:25
haleybmlavalle: for dhcpv6-stateless the driver will hand-out addresses, but instance must learn other info from the router advertisement15:26
mlavalleah ok, that was my question above15:26
haleybi should have a link, but the code is in setup_dhcp_port()15:27
mlavalleso, as I said, i'll confirm in kibana with other instances of the bug, to make sure I see the same thing15:27
mlavalleand then I will propose a fix15:27
mlavallesounds like a plan?15:27
haleyb+115:28
mlavallecool15:28
mlavalleLast one I have today is https://bugs.launchpad.net/neutron/+bug/168322715:28
openstackLaunchpad bug 1683227 in neutron "test_connection_from_same_address_scope failed with: Cannot find device "qg-74372988-7f"" [High,Confirmed]15:28
mlavalleThis one is still searching for an owner15:29
mlavalleif one doesn't show up, I'll take it next and give it some TLC15:29
*** apetrich has quit IRC15:29
mlavalleany other bugs we should discuss today?15:30
haleybok, thanks.  i will try and look as well15:30
mlavalletake that as a no15:32
haleybsorry, no more bugs15:32
mlavalle#topic DNS extension15:32
*** openstack changes topic to "DNS extension (Meeting topic: neutron_l3)"15:33
mlavalleI've been working on implementing https://bugs.launchpad.net/neutron/+bug/165067815:33
openstackLaunchpad bug 1650678 in neutron "[RFE] Allow specifying dns_domain when creating a port" [Wishlist,In progress] - Assigned to Miguel Lavalle (minsel)15:33
mlavalleI have already 3 patchsets in gerrit15:34
mlavalleand I just finished implementing the logic. I will push that patchset over the next few days15:34
mlavallethe logic is working fine15:34
haleyb:) i'll add myself if i haven't already15:35
mlavalleit doesn't break any current tests15:35
mlavalleI need to add tests for the new functionality, though15:35
*** VW has quit IRC15:35
*** VW has joined #openstack-meeting-315:35
mlavallehaleyb: no need to review just yet. I'll let you know when the entire series is ready15:35
haleybmlavalle: ok, i just like getting gerrit emails :)15:36
mlavallehaleyb: should we add this to the team's charter for Pike?15:36
haleybmlavalle: yes, think we can add if it's this far along already15:37
mlavalleok, i'll do it15:37
mlavalle#topic Open Agenda15:38
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_l3)"15:38
*** pcaruana has quit IRC15:38
mlavalleany other topics we should discuss today?15:38
haleybmlavalle: i know you answered a few questions for hjensas15:39
*** pcaruana has joined #openstack-meeting-315:39
*** ltomasbo|away is now known as ltomasbo15:39
haleybbut i think he got some good answers from you and kevin15:39
mlavalleyeah, I intend to follow up with him and I have the bug he filed in my radar screen15:39
haleybmlavalle: great, thanks.  i had asked him to add an agenda item if there were more questions, but think kevin answered them last night15:40
*** iyamahat has joined #openstack-meeting-315:40
*** armstrong has joined #openstack-meeting-315:41
mlavalleany other topics?15:41
*** racedo has quit IRC15:44
mlavalleok, have a nice rest of your week15:44
mlavalle#endmeeting15:44
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:44
openstackMeeting ended Thu May 25 15:44:42 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:44
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-05-25-15.00.html15:44
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-05-25-15.00.txt15:44
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-05-25-15.00.log.html15:44
*** bfournie has left #openstack-meeting-315:44
*** janzian has left #openstack-meeting-315:48
*** armstrong has quit IRC15:53
*** cdent has joined #openstack-meeting-315:58
*** rhochmuth has quit IRC15:59
cdentedleafe: you start16:00
elmiko#startmeeting api-wg16:00
openstackMeeting started Thu May 25 16:00:15 2017 UTC and is due to finish in 60 minutes.  The chair is elmiko. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
elmikoha16:00
cdentor elmiko16:00
*** openstack changes topic to " (Meeting topic: api-wg)"16:00
openstackThe meeting name has been set to 'api_wg'16:00
cdentwin16:00
cdento/16:00
*** VW has quit IRC16:00
elmiko#chair cdent edleafe16:00
openstackCurrent chairs: cdent edleafe elmiko16:00
*** iyamahat has quit IRC16:00
elmikook, how does this thing work again16:00
* elmiko cracks fingers16:00
edleafesorry, was busy in -nova16:00
*** VW has joined #openstack-meeting-316:00
edleafes/was/am16:00
elmiko#link https://wiki.openstack.org/wiki/Meetings/API-WG#Agenda16:01
elmiko#topic previous meeting action items16:01
*** openstack changes topic to "previous meeting action items (Meeting topic: api-wg)"16:01
elmikoi think the main one was reading mordred's prs16:01
*** dtantsur has joined #openstack-meeting-316:02
dtantsuro/16:02
*** pvaneck has joined #openstack-meeting-316:02
*** mickeys has joined #openstack-meeting-316:03
elmikohas everyone had a chance to read the prs starting with https://review.openstack.org/#/c/45940516:03
*** lucasxu has quit IRC16:03
elmiko#link https://review.openstack.org/#/c/45940516:03
* mordred hopes everyone enjoys long novels16:03
cdentnew versions were just posted, so I'm not up to date with today16:03
*** lucasxu has joined #openstack-meeting-316:03
mordredcdent: mostly tiny changes from last versions16:03
elmikoon the whole they look good to me16:03
cdent1% of very big is big16:03
edleafeyeah, I'm behind in my reading due to PyCon travel16:03
mordredcdent: I fixed a typo you pointed out and changed the URL suggetsed for service-types publication16:03
elmikothere were some minor questions, but it seems like a win for me16:04
* dtantsur is half way through the novel16:04
mordreddtantsur made a good suggestion on the first one based on the recent ironic thread, so I'm going to try to incorporate that today16:04
elmikosweet, i think that was one of the main questions16:04
dtantsurcool16:04
mordredbut I'll wait a bit to see if there are any other feedbacks on the stack so we can take care of them all in one pass16:04
elmikomordred: +116:05
mordredalso - related but not related - I pushed up a patch to system-config for the creation of a new mailing list for SDK authors and API consumers:16:06
mordredhttps://review.openstack.org/#/c/468046/16:06
elmikointeresting...16:06
mordredthis stems from the fact that David Flanders and I have an email chain going with a bunch of the SDK authors ... and maybe getting that intoa mailng list is better than private emails16:06
cdentthat's a good idea16:06
dtantsurnice16:06
cdenti'm glad to see that "everyone has to be on os-dev or not at all" is finally dying16:07
dtantsurespecially to cover less-known SDK authors16:07
mordredthey're all, so far, excited about us reaching out and interested in working more closely16:07
elmikohuge +1 to get that activity on a list somewhere16:07
mordreddtantsur: ++ exactly16:07
mordreddid anyone know there are 2 active java sdks?16:07
*** mickeys has quit IRC16:07
elmikoi didn't16:07
* dtantsur did not16:07
mordredor that the php sdk is actuall pretty solid?16:07
mordredme either16:07
* dtantsur is interested what kind of applications people create with the PHP SDK. hopefully, some additions to Nextcloud or something like that.16:08
cdentmordred: I left a comment: the name of the list is no good16:08
mordredcdent: awesome16:09
cdentwith that name the audience is huge, and that appears contrary to what you're going for16:09
edleafedtantsur: I was on the SDK team at Rackspace years ago. The PHP SDK was pretty popular16:09
dtantsurinteresting16:09
elmikocdent: openstack-api-abusers?16:09
mordreddtantsur: I believe owncloud is using it as well16:09
mordredcdent: well - so definitely some help on name/description is needed here ...16:10
dtantsur\o/16:10
elmikoi'm both scared and impressed about the php sdk16:10
* cdent will think16:10
mordredI think the target audience is "anyone interacting with the REST API directly rather than via an SDK - mostly relevant for SDK authors"16:10
dtantsuropenstack-not-only-in-python@lists.o.o (though it will attract swift folks too)16:11
mordredor "SDK authors - but people with a deep interest in consuming the REST API directly may be interested"16:11
elmikodtantsur: LOL yes!16:11
dtantsursome people consume API directly, they should be included too16:11
mordredmaybe just openstack-sdk-authors? and if you're a power-REST consumer you can join too16:11
cdenti think that's reasonable16:12
dtantsuropenstack-sdk-authors++16:12
cdentif you consume the api raw, you are your own sdk-author16:12
edleafeif you write an app that consumes the API directly, you're writing an SDK with a user count of 116:12
cdentjinx16:12
cdentish16:12
elmikohaha16:12
edleafe:)16:12
dtantsurheh16:12
elmikoopenstack-sdk-authors seems reasonable to send up the flag pole16:12
*** pvaneck_ has joined #openstack-meeting-316:13
elmikook, moving along16:13
elmiko#topic open mic and new biz16:13
*** openstack changes topic to "open mic and new biz (Meeting topic: api-wg)"16:13
elmikoi think we just talked about mordred's changes, anything more on that?16:14
cdentmore reviewing to happen, but seems we are getting close16:14
cdentso16:14
cdentyay16:14
elmiko#action everyone re-review mordred's changes begining with https://review.openstack.org/#/c/45940516:14
elmiko#undo16:14
openstackRemoving item from minutes: #action everyone re-review mordred's changes begining with https://review.openstack.org/#/c/45940516:14
elmiko#action everyone re-review mordred's changes beginning with https://review.openstack.org/#/c/45940516:14
mordredthank you all again for reviewing such long and involved things. I really appreciate it and recognize just how much content it is16:15
elmikono no, thanks to you. that's a boat load of work =)16:15
elmikois there any other new business folks would like to bring up?16:15
cdentare people aware of the request-id changes that sdague has in progress?16:16
* dtantsur is not16:16
elmikoneither am i16:16
edleafevaguely16:16
elmikoi assume this is a result of the logging discussions from summit?16:16
sdaguettps://gist.github.com/sdague/eb91caee9ce27c4d0ae913e5743b441616:16
cdentit's going to make it possible and easy to pass a request id from one service to another so that logs have both a global and local request id16:16
elmikoneat16:16
cdentthanks sdague16:16
*** pvaneck has quit IRC16:16
elmiko++16:17
sdaguealso http://lists.openstack.org/pipermail/openstack-dev/2017-May/117367.html16:17
mordredsdague: this might be off topic - or not relevant ...16:18
*** MarkBaker has quit IRC16:18
sdaguemordred: go for it16:18
mordredsdague: but in putting that together did you happen to look at the opentracing/openzipkin work out there?16:18
sdagueno16:18
*** reedip_ has quit IRC16:19
mordredit seems very close at least problem-space-wise - but it's also possible that impl details make it irrelevant16:19
sdaguethere is already osprofiler if you are going that deep16:19
sdaguethis is litterally make grep and ELK work16:19
mordredtotally16:19
mordredI was mostly thinking on the terminology/concepts front - not code16:20
sdaguesure16:20
mordredbut like I said - maybe not relevant - just wanted t bring it up in case it was16:20
sdaguewell, the ship has sailed on all of those parts as it's half landed16:20
mordredkk16:20
sdaguethe oslo infrastructure is done, it's just consumption, which is a bunch of small patches16:20
cdentwhat's been done is really nicely simple and hugely valuable16:20
mordredsweet16:21
*** yamamoto has joined #openstack-meeting-316:21
*** mickeys has joined #openstack-meeting-316:21
cdentelmiko, edleafe: i have to go, let me know if I end up needing to do something16:22
sdagueit's all mostly a project management task actually, which is why I've got the big list of steps16:22
*** cdent has quit IRC16:22
elmikoanymore on this ?16:23
elmikook, then16:24
elmiko#topic guidelines16:24
*** openstack changes topic to "guidelines (Meeting topic: api-wg)"16:24
elmiko#link https://review.openstack.org/#/q/status:open+project:openstack/api-wg,n,z16:24
elmikoi think the only new stuff are mordred's changes16:24
elmikois there anything else we need to address?16:24
edleafenot from me16:25
elmiko#topic bug review16:25
*** openstack changes topic to "bug review (Meeting topic: api-wg)"16:25
elmiko#link https://bugs.launchpad.net/openstack-api-wg16:25
elmikodoesn't seem like anything new there either16:26
elmikowe should probably do a triage at some point16:26
elmikoif there is nothing else, i guess we'll move on to the wrap16:27
elmiko#topic weekly newsletter16:27
*** openstack changes topic to "weekly newsletter (Meeting topic: api-wg)"16:27
elmiko#link https://etherpad.openstack.org/p/api-wg-newsletter16:27
elmikoedleafe: are you still available for the newsletter?16:28
edleafeI'm running out for a couple of hours. If it can wait, I'll do it when I return16:28
elmikoi can do it, i'll ping on -sdks when i've got it ready16:29
edleafegreat. I won't be able to review it for a while (see above) :)16:29
elmikonp16:29
*** pcaruana has quit IRC16:30
elmikolast call...16:30
elmikothanks everyone for attending!16:30
*** pcaruana has joined #openstack-meeting-316:30
elmiko#endmeeting16:30
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:30
openstackMeeting ended Thu May 25 16:30:59 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-05-25-16.00.html16:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-05-25-16.00.txt16:31
openstackLog:            http://eavesdrop.openstack.org/meetings/api_wg/2017/api_wg.2017-05-25-16.00.log.html16:31
*** dtantsur has left #openstack-meeting-316:31
*** MarkBaker has joined #openstack-meeting-316:31
*** yamamoto has quit IRC16:32
*** iyamahat has joined #openstack-meeting-316:44
*** iyamahat has quit IRC16:45
*** iyamahat has joined #openstack-meeting-316:45
*** ppiela_ has joined #openstack-meeting-316:48
*** ltomasbo is now known as ltomasbo|away16:48
*** lhx__ has quit IRC16:50
*** iyamahat has quit IRC16:53
*** jtomasek has joined #openstack-meeting-316:53
*** Swami has joined #openstack-meeting-316:58
*** baoli_ has quit IRC16:59
*** mlavalle has left #openstack-meeting-317:00
*** ralonsoh has quit IRC17:01
*** baoli has joined #openstack-meeting-317:04
*** yamamoto has joined #openstack-meeting-317:06
*** rhochmuth has joined #openstack-meeting-317:07
*** yamamoto has quit IRC17:10
*** SumitNaiksatam_ has quit IRC17:11
*** rmart04 has quit IRC17:16
*** tellesnobrega has joined #openstack-meeting-317:17
*** sambetts is now known as sambetts|afk17:18
*** spzala has quit IRC17:20
*** lucasxu has quit IRC17:20
*** iyamahat has joined #openstack-meeting-317:27
*** armstrong has joined #openstack-meeting-317:38
*** armstrong has quit IRC17:40
*** SumitNaiksatam has joined #openstack-meeting-317:41
*** diablo_rojo has joined #openstack-meeting-317:43
*** iyamahat has quit IRC17:43
*** tbachman has joined #openstack-meeting-317:50
*** s3wong has joined #openstack-meeting-317:53
*** rmart04 has joined #openstack-meeting-317:54
*** lpetrut has quit IRC17:54
*** racedo has joined #openstack-meeting-317:55
*** jeremyfreudberg has joined #openstack-meeting-317:55
*** jeremyfreudberg has left #openstack-meeting-317:56
*** claudiub has quit IRC17:56
*** rkukura has joined #openstack-meeting-317:56
*** annak has joined #openstack-meeting-317:58
SumitNaiksatamrkukura: tbachman annak: hi18:00
tbachmanSumitNaiksatam: hi!18:00
rkukurahi18:00
*** ducttape_ has quit IRC18:00
SumitNaiksatam#startmeeting networking_policy18:00
openstackMeeting started Thu May 25 18:00:46 2017 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at http://wiki.debian.org/MeetBot.18:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:00
*** openstack changes topic to " (Meeting topic: networking_policy)"18:00
openstackThe meeting name has been set to 'networking_policy'18:00
SumitNaiksatam#info agenda https://wiki.openstack.org/wiki/Meetings/GroupBasedPolicy#May_25th.2C_18th_201718:01
annakhi!18:01
SumitNaiksatami think we are still dealing with the issues from last week (at least i am)18:01
SumitNaiksatam#topic IP v4, v6 dual-stack support18:01
*** openstack changes topic to "IP v4, v6 dual-stack support (Meeting topic: networking_policy)"18:01
SumitNaiksatam#link https://review.openstack.org/#/c/459823/18:01
tbachman:|18:02
SumitNaiksatamtbachman: :-) thanks for continuing to work on this18:02
tbachmanSumitNaiksatam: there’s at least one fix to make to that patch18:02
SumitNaiksatamtbachman: oh18:02
tbachmanI need to change the defaults to use SLAAC18:02
SumitNaiksatamah okay18:02
SumitNaiksatamtbachman: thats the neutron default?18:02
tbachmanI can resubmit that, but I was hoping to be further along than I am with functional/integration testing18:02
tbachmanAlas no18:03
rkukuratbachman: Should that be configurable in GBP?18:03
tbachmanrkukura: good question18:03
SumitNaiksatamrkukura: good point18:03
tbachmanwe could add a config option18:03
tbachmanbut I worry about endless config18:03
rkukuraThis seems similate to default_prefix_len, etc.18:03
SumitNaiksatamtbachman: only for those who need it18:03
tbachmantrue18:03
tbachmanit’s easily added18:04
SumitNaiksatamtbachman: is it the neutron default?18:04
tbachmanI don’t believe so18:04
tbachmanI believe the neutron default is none18:04
* tbachman goes to check18:04
*** rossella__ has quit IRC18:06
SumitNaiksatamrkukura: are you good with the patch otherwise?18:06
SumitNaiksatamannak: how about you, in case you got a chance to look at the lastest patchset?18:06
rkukurayes, although I want to take a quick look at the changes since the last version I reviewed18:07
SumitNaiksatamrkukura: sure18:07
annakSumitNaiksatam: not the latest, but it looked good. I'll look at latest18:07
SumitNaiksatamannak: thanks18:07
*** donghao has joined #openstack-meeting-318:08
SumitNaiksatamgiven that we are heading into the long weekend, i would hope that we can attempt to merge this sooner than later18:08
*** baoli has quit IRC18:08
SumitNaiksatamwe have to merge the backports as well18:08
tbachmanSumitNaiksatam: ack18:08
rkukuraSumitNaiksatam: I have 4 or 5 of those to do to stable/mitaka18:08
tbachmanI can’t find reference, but I’m pretty sure the default is None18:08
SumitNaiksatamyou can expect some maintenance activity and downtime over the weekend18:08
SumitNaiksatamrkukura: yes, we will come to that in a min18:09
tbachmanSumitNaiksatam: I also noticed that igordcard’s QoS patch wasn’t backported. Is that b/c it’s a new feature?18:09
SumitNaiksatamtbachman: np18:09
tbachmanOr should that be backported as well?18:09
SumitNaiksatamtbachman: we decided that we will not backport the QoS patch to newton18:09
tbachmank18:09
SumitNaiksatamit will be available starting Ocata18:09
tbachmanSumitNaiksatam: got it. thx18:09
SumitNaiksatamactually we attempted to backport18:09
SumitNaiksatambut ran into some issues, and decided it was best to leave it out18:10
tbachmanSumitNaiksatam: got it18:10
SumitNaiksatamif someone has a real need for this in mitaka, we can definitely reconsider the decision18:10
tbachmanrkukura: SumitNaiksatam: should I add a config var for IPv6 RA mode, etc. for GBP?18:10
rkukuratbachman: both ra_mode and address_mode?18:11
*** songole has joined #openstack-meeting-318:11
SumitNaiksatamsongole: hi18:11
songoleSumitNaiksatam: hello18:11
tbachmanrkukura: ack18:11
tbachmanSumitNaiksatam: since songole is here, we could talk about the policy ip_pool18:11
SumitNaiksatamtbachman: these will be used as defaults for implicit creation, right?18:11
tbachmanSumitNaiksatam: ack18:11
tbachmanmy thinking is that our default would be SLAAC18:11
SumitNaiksatamtbachman: you mean proxy ip_pool18:11
tbachmanunless we want our defaults to be the neutron defaults18:12
*** david-lyle has joined #openstack-meeting-318:12
tbachman(with “our” meaning GBP)18:12
tbachmanSumitNaiksatam: ack on proxy ip_pool18:12
SumitNaiksatamtbachman: yeah, i wanted to dig a little more on that18:12
SumitNaiksatamtbachman: why SLAAC?18:12
tbachmanIt seems to be a preferred mode, from what I can tell18:12
tbachmanbut it doesn’t have to be18:12
tbachmanit may make more sense for our default to be the same as neutron's18:12
rkukuratbachman: Are the neutron defaults usable for IPv6, or its it always necessary to specify something?18:12
SumitNaiksatamtbachman: yeah thats what i wanted to clarify18:13
tbachmanrkukura: define usable ;)18:13
*** donghao has quit IRC18:13
tbachmanI think their defaults mean that neutron doesn’t take any responsibility for that behavior18:13
rkukuratbachman: You create an IPv6 subnet, attach it to a router, and you get connectivity over IPv618:13
tbachmanthe documentation actually does a good job of explaining this, if I remember correctly18:13
tbachmanlet me go find that link18:13
tbachmanThis link has a helpful table:18:14
*** baoli has joined #openstack-meeting-318:14
tbachman#link https://docs.openstack.org/liberty/networking-guide/adv-config-ipv6.html <== this link has a helpful table18:15
rkukuraMy argument would be that the GBP defaults used in implicit workflows should result in usable IPv6 connectivity when ip_version == 46 or 618:15
tbachmannote the first entry in the table18:15
tbachman“Backwards compatibility with pre-Juno IPv6 behavior.”18:15
*** baoli has quit IRC18:15
tbachmanThis is the part titled “ipv6_ra_mode and ipv6_address_mode combinations"18:15
rkukuraN/SN/SOffNot DefinedBackwards compatibility with pre-Juno IPv6 behavior.18:15
rkukuraLooks like the defaults are for backwards compatibility rather than usability18:16
SumitNaiksatamrkukura: agree, assuming neutron is not usable without that configuration18:16
tbachmanrkukura: ack on the backwards-compatibility18:16
tbachmanthere’s also SLAAC from an openstack router, and SLAAC form a non-openstack router18:17
tbachmanbut I’ve found that openstack doesn’t let you attach subnets to a router if you’ve elected SLAAC from a non-openstack router18:17
tbachmanso, I’d say it should be the SLAAC from an openstack router :)18:17
tbachman(note: that’s for internal interfaces, and not the gateway)18:18
*** anilvenkata has joined #openstack-meeting-318:18
rkukuratbachman: agree18:18
rkukurabut with pure-SLAAC, VMs don’t get a default gateway, right?18:18
tbachmanalso note that most of these are “not implemented” by the reference implementation18:19
tbachmanSLAAC is just for address assignemnt18:19
tbachmanthe router advertisements provide the default GW18:19
*** david-lyle has quit IRC18:19
rkukuraSo dhcpv6-stateless is what uses SLAAC and has RAs for the GW, right?18:19
*** lyan has quit IRC18:19
*** slaweq has joined #openstack-meeting-318:19
SumitNaiksatamtbachman: rkukura: i still think the defaults should be what neutron does, a specific driver can override the defaults18:20
rkukuraSumitNaiksatam: I could go along with that, as long as its configurable for the deployment18:20
tbachmanSumitNaiksatam: I’m fine with that. I’ll amend my patch to include these config vars18:20
SumitNaiksatamand by driver, i mean the GBP policy driver18:20
tbachmanSumitNaiksatam: should these be provided in the resource mapping driver then?18:21
SumitNaiksatamokay, we can follow up on this discusion on the gerrit review18:21
rkukuraDo we need config at the PD level? What do we do for default_prefix_len?18:21
tbachmanFor IPv6, we’ve agreed it’s 6418:21
SumitNaiksatamrkukura: i meant the PD can override it18:21
rkukuratbachman: I meant for IPv418:22
tbachmanah — that’s part of the L3 config now, right?18:22
rkukuraI think its best of these sorts of config variables all work similarly18:22
tbachmanhmmm18:22
*** dgonzalez has quit IRC18:22
tbachmanrkukura: are you referring to implicit workflow (i.e. where L3P is created implicitly)?18:22
*** dgonzalez has joined #openstack-meeting-318:22
SumitNaiksatamrkukura: default_prefix_len is part of GBP API18:23
rkukuraBoth implicit L3P creation, and explicit where the value is not passed18:23
rkukuraI guess the explicit creation uses API default values18:24
tbachmanrkukura: your point is just that the defaults should all be consistent then, right?18:24
rkukuraSo do these need to be added as L3P API attributes?18:24
tbachman(and if so, I should double-check that’s the case)18:24
*** ducttape_ has joined #openstack-meeting-318:25
SumitNaiksatamrkukura: i was hoping you would not bring that up! :-(18:25
tbachmanlol18:25
*** lucasxu has joined #openstack-meeting-318:25
rkukuraMy point is more about how a deployment sets defaults (via config) and how a user overrides those defaults than about whether the specific values are consistent between Neutron and GBP18:25
*** slaweq has quit IRC18:26
SumitNaiksatamwell without representation in the API there is no way the user can override it18:26
*** racedo has quit IRC18:27
tbachmanbut — we don’t provide all the information about subnets when we create an L3P18:27
SumitNaiksatamthe only way to override it is to create a neutron object with those overrides and associate it with a GBP object (i am glossing over the defails here)18:27
tbachmanfor example, default GW18:27
*** baoli has joined #openstack-meeting-318:27
tbachmanI guess it’s a question of whether this level of detail is warranted in the API18:28
tbachmanduring L3P creation18:28
rkukuraright18:28
SumitNaiksatamtbachman: true, in such cases, where neutron models that detail, we expect the neutron object to be creted directly18:28
tbachmanand is this something someone would want to change during deployment, w/o having to restart neutron18:28
SumitNaiksatamand then be assocaited with the relevant GBP resource18:28
tbachmanI would think this would be consistent across a deployment18:29
tbachman(meaning the same mode is used throughout)18:29
SumitNaiksatamtbachman: good point18:29
tbachmanSumitNaiksatam: but with L3P’s, we still create the subnets, even if the user just provided a prefix18:29
tbachmanand we don’t create them during L3P creation18:30
tbachmanI can see an argument for exposing this18:30
SumitNaiksatamtbachman: the resource_mapping driver would allow you to associate subnets with a PTG18:30
tbachmanb/c it’s kind of a “mode” for deployment18:30
*** baoli has quit IRC18:30
SumitNaiksatamand you can create the subnets in Neutron the way you want it18:31
tbachmanSumitNaiksatam: true18:31
tbachmanbut in our subnetpools model, we have no way of providing this18:31
tbachmanit’s only specified during subnet creation18:31
SumitNaiksatamtbachman: we will perhaps need to revisit that in the resource_mapping context :-)18:32
tbachman:)18:32
tbachmanso, I just add a default in my driver for now, and we revisit later?18:32
*** baoli has joined #openstack-meeting-318:32
tbachmanI’m just worried about changing a behavior/default at some later point18:32
tbachmanAt the very least, I say we add config vars, and then we can examine later if we want to specify this in the REST18:33
tbachmanand if we expose it via REST, the defaults should be what’s in the config18:33
tbachman(and not defined in the REST itself)18:33
SumitNaiksatamtbachman: would it not be a matter of promoting this configuration in the future (as opposed to changing behavior)?18:33
rkukuraadding config now and API later is fine with me18:33
SumitNaiksatamokay good, so we have agreement :-)18:33
tbachman:)18:33
tbachmancool — I’ll add that to my respin as well18:34
SumitNaiksatamassuming annak is on board too :-)18:34
tbachmanand thanks to everyone for reviewing and approving the spec, too!18:34
SumitNaiksatami think rkukura deserves special pat on the back for that!18:34
annaktbachman: i need to catch up a bit :) i understood subnets are always created implicitly for all drivers using subnetpools?18:34
tbachmanSumitNaiksatam: ack18:34
tbachmanannak: only in the implicit workflows :)18:35
tbachmanah18:35
tbachmanannak: my bad18:35
tbachmanyes — subnets are created implicitly when needed, and not when the L3P is created18:35
tbachman(from the subnetpools)18:35
tbachmanSumitNaiksatam: now that I’ve taken up 1/2 of our IRC meeting, do we want to cover the proxy ip_pool still?18:35
SumitNaiksatamtbachman: yes18:36
SumitNaiksatamsongole: still there?18:36
songoleyes18:36
SumitNaiksatamtbachman: go ahead, we should try to close this18:36
tbachmansongole: not sure if you’ve followed the dual-stack development, but we’ve expanded the use of the ip_pool parameter18:36
tbachmanas you’re well aware, there’s also a proxy ip_pool parameter18:37
songoletbachman: I need to catch up on the spec..18:37
tbachmanour expansion of this parameter is to instead of it being just a single subnet prefix, it’s now a string, which we can interpret as a comma-separated list of prefixes18:37
tbachmanand the prefixes can be a mix of IPv4 and IPv618:37
tbachmanright now, we haven’t changed any behavior for proxy ip_pool18:37
tbachmanbut if you want to take advantage of dual-stack, there is a change we should probably make18:38
SumitNaiksatamsongole: so the summary is, whether we need to do the same thing for proxy_ip_pool, what we did for the ip_pool of the L3P?18:38
tbachmanright now, there is no ip_version provided with the proxy workflow18:38
tbachmanthe ip_version is implied as IPv418:38
tbachmanwe should consider adding an ip_version config var, and allow it to use the same values as is used with the L3P18:39
tbachman(4, 6, and now 46 to mean “dual-stack”)18:39
songoleSumitNaiksatam: I would think it is required18:39
SumitNaiksatamsongole: okay, tbachman’s current spec and implementation does not address this18:39
SumitNaiksatamsongole: we would need some follow up work to get to that18:39
tbachmanSumitNaiksatam: it wouldn’t take much, I think18:39
SumitNaiksatamsongole: until then, when using NFP and service chains, perhaps only ipv4 is going to work18:40
SumitNaiksatamtbachman: okay18:40
tbachmanI think it would just be adding the ip_version config var18:40
songolethe proposal to make it a string - is it part of the spec?18:40
SumitNaiksatamsongole: yes18:40
tbachmansongole: it is — for L3P18:40
tbachmanbut not the proxy ip_pool18:40
songoletbachman: ah, got it18:40
* tbachman has a terrible memory — we may have also changed the type for proxy ip_pool to be a string18:41
SumitNaiksatamtbachman: could we potentially consider using the same ip_version for both ip_pool and proxy_ip_pool?18:41
tbachmanSumitNaiksatam: we could18:41
tbachmansongole: it is a string in the proxy ip_pool as well18:41
tbachman(that’s in my patch)18:41
tbachmanI did that to keep things consistent18:42
SumitNaiksatamtbachman: ah good, so that change is already done18:42
songoletbachman: ok. cool18:42
tbachmanSumitNaiksatam: ack. But we still need ip_version18:42
tbachmanthe question is whether we would want a separate one for proxy ip_pool18:42
*** rmart04 has quit IRC18:42
tbachmanI can see the argument for a separate config file var18:42
songolewe could use the same version param with proxy ip_pool as well18:42
tbachmansince there is a separate ip_pool18:42
SumitNaiksatamtbachman: yeah, i meant the ip_version stands for both pools18:42
*** Sukhdev has joined #openstack-meeting-318:42
tbachmanIn any case, this is something we can address in a follow-on patch, if needed18:43
tbachmanwe already have to do one for the DB schema change18:43
tbachman(in order to increase the ip_pool string from 64 to 256 characters)18:43
SumitNaiksatamif we use the same ip_version, then perhaps only additional changes are required in the plumber18:44
SumitNaiksatamtbachman: ack18:44
rkukuratbachman: So if ip_version enables IPv6 but proxy_ip_pool does not have any IPv6 prefixes, does this disable IPv6 for proxies?18:44
songoletbachman: would nfp break with this change unless we handle v6 addressing changes?18:44
tbachmanrkukura: right now, there is no checking of ip_version against proxy ip_pool vaues18:44
SumitNaiksatamsongole: it depends on how its being used18:44
tbachmansongole: IPv4 works as-is18:45
tbachmanthe goal was to not break existing workflows18:45
tbachmanso — you don’t get anything new, but nothing should be broken18:45
SumitNaiksatamtbachman: nice thanks for confirming that18:45
* tbachman admits he has a limited grasp of the proxy workflows18:45
SumitNaiksatamsongole: hopefullly our gate jobs will catch if anything breaks18:46
SumitNaiksatamsongole: the NFP gate jobs that is18:46
songoleSumitNaiksatam: ok18:46
rkukuratbachman: right, so it should be possible to have ip_version=46, and proxy_ip_pool to contain v4 and/or v6 prefixes, providing control over which IP versions are available to proxy18:46
* tbachman notes that those passed in his current iteration of his patch18:46
SumitNaiksatamtbachman: nuce18:46
tbachmanrkukura: I’m not sure what happens if there is an IPv6 prefix in proxy_ip_pool18:46
tbachmanwe don’t have a test for that18:46
tbachmanbut IPv4 is currently tested, of course18:47
tbachman(and still works)18:47
*** annak_ has joined #openstack-meeting-318:47
SumitNaiksatamokay, perhaps we can switch to the other two topics on the agenda18:47
rkukuraok18:47
SumitNaiksatamsongole: perhaps you can look at the spec: #link https://review.openstack.org/#/c/459823/18:48
* tbachman notes he probably should have an exception to catch that for now18:48
tbachmanSumitNaiksatam: thanks for linking that!18:48
SumitNaiksatamand we can follow up if you have concerns18:48
SumitNaiksatamtbachman: thanks again for being on top of this!18:48
SumitNaiksatam#topic stable/mitaka timeout issues18:48
*** openstack changes topic to "stable/mitaka timeout issues (Meeting topic: networking_policy)"18:48
*** annak has quit IRC18:48
tbachmanSumitNaiksatam: np!18:49
SumitNaiksatamthe summary here is that the stable/mitaka py27 timesout more often than not18:49
songoleSumitNaiksatam: will do.18:49
SumitNaiksatamand i have been trying to get to the bottom of it18:49
SumitNaiksatamso far with limited success18:49
SumitNaiksatami identified a couple of places where we were trying to connect to external servers/processes18:50
SumitNaiksatamand waiting for it to timeout18:50
SumitNaiksatamon both occassions we could just get rid of the tests since these are legacy18:50
SumitNaiksatamunfortunately the problem is still not solved18:50
SumitNaiksatami have this patch: #link https://review.openstack.org/#/c/467391/18:51
SumitNaiksatamit also cleans up a lot of the logging18:51
SumitNaiksatamso if you see this:18:52
SumitNaiksatamhttp://logs.openstack.org/26/463626/19/check/gate-group-based-policy-python27-ubuntu-trusty/6dc1861/console.html18:52
SumitNaiksatama lot of the redundant noisy logging is gone18:52
SumitNaiksatammakes it easier to narrow down the problems18:52
SumitNaiksatami think we should try to merge this patch and couple of others in the queue:18:53
SumitNaiksatam#link https://review.openstack.org/#/q/status:open+project:openstack/group-based-policy+branch:stable/mitaka18:53
SumitNaiksatamrkukura: your patches can also be posted18:53
SumitNaiksatamthats it from me, unless there are questions/comments18:54
rkukuraSumitNaiksatam: Which patches of mine? I haven’t done any of the backlogged stable/mitaka back-ports yet18:54
SumitNaiksatamrkukura: yes, i meant you can post them18:54
SumitNaiksatamrkukura: i feel more confident that they will not perpetually timeout18:55
SumitNaiksatameven while i try to fix the situation further18:55
rkukuraSumitNaiksatam: I haven’t been waiting for the timeout fix - I’ve been trying to finish the data migration patch for apic_aim18:55
rkukuraI will review the patches mentioned.18:55
SumitNaiksatamrkukura: i know that, but the reality is taht we wouldnt have been able to merge them18:55
SumitNaiksatameven if you had posted them18:55
rkukuraSumitNaiksatam: understood18:56
rkukuraI guess that is important for manual backports18:56
SumitNaiksatami feel a little more optimistic now (rechecks will probably be needed)18:56
rkukurafor these timeout work-arounds, I’d rather see fixes merged to master, then newton, then mitaka when possible18:56
SumitNaiksatamrkukura: yes, but these might be branch specific18:57
rkukuraunless the code causing the issue is already gone/changed/fixed on the newer branches18:57
SumitNaiksatamthe log clean up which i am doing here will definitely be helpful in the other branches as well18:57
rkukuraright18:57
SumitNaiksatami will post the relevant patches separately18:57
SumitNaiksatamsome of the patching might be different for those branches18:58
SumitNaiksatamokay switching topics18:58
rkukuraok18:58
SumitNaiksatam#topic Ocata sync18:58
*** openstack changes topic to "Ocata sync (Meeting topic: networking_policy)"18:58
SumitNaiksatamannak_: still there?18:58
annak_yep18:58
tbachmanSumitNaiksatam: 1 min18:59
SumitNaiksatamsorry got delayed to get to this18:59
annak_np18:59
SumitNaiksatamso i was hoping to have started merging the patches this week18:59
*** claudiub has joined #openstack-meeting-318:59
SumitNaiksatambut might take a little longer since there is still some backlog18:59
SumitNaiksatammeanwhile annak_ thanks for keeping up the work on this18:59
SumitNaiksatamand let us know if you are hitting any issues19:00
annak_np, sure19:00
SumitNaiksatamwe can discuss on GBP IRC channel or over emails19:00
SumitNaiksatamannak_: thanks!19:00
SumitNaiksatamalrighty, thanks all for joining!19:00
SumitNaiksatambye19:00
tbachmanSumitNaiksatam: thanks!19:00
annak_I had a few qs - I'll ask you offline19:00
SumitNaiksatam#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu May 25 19:00:38 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-05-25-18.00.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-05-25-18.00.txt19:00
annak_bye!19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_policy/2017/networking_policy.2017-05-25-18.00.log.html19:00
*** tbachman has left #openstack-meeting-319:00
SumitNaiksatamannak_: definitely19:00
*** songole has left #openstack-meeting-319:00
rkukurabye19:01
*** rkukura has left #openstack-meeting-319:02
*** annak_ has quit IRC19:05
*** yamamoto has joined #openstack-meeting-319:08
*** anilvenkata has quit IRC19:08
*** pcaruana has quit IRC19:09
*** ppiela_ has quit IRC19:10
*** yamamoto has quit IRC19:13
*** jtomasek_ has joined #openstack-meeting-319:17
*** baoli has quit IRC19:23
*** baoli has joined #openstack-meeting-319:25
*** apetrich has joined #openstack-meeting-319:33
*** apetrich has quit IRC19:42
*** ppiela has joined #openstack-meeting-319:45
*** bobh has quit IRC19:50
*** annegentle has joined #openstack-meeting-319:53
*** haleyb has quit IRC19:54
*** apetrich has joined #openstack-meeting-319:55
*** Sukhdev has quit IRC19:57
*** amotoki is now known as amotoki_away19:58
*** amotoki_away is now known as amotoki19:59
*** amotoki is now known as amotoki_away19:59
*** yamahata has joined #openstack-meeting-320:10
*** david-lyle has joined #openstack-meeting-320:12
*** julim has quit IRC20:15
*** david-lyle has quit IRC20:17
*** lucasxu has quit IRC20:21
*** lucasxu has joined #openstack-meeting-320:22
*** lyan has joined #openstack-meeting-320:33
*** kbyrne has quit IRC20:38
*** markvoelker has quit IRC20:42
*** slaweq has joined #openstack-meeting-320:44
*** yamahata has quit IRC20:45
*** VW has quit IRC20:48
*** VW has joined #openstack-meeting-320:48
*** yamahata has joined #openstack-meeting-320:51
*** tellesnobrega has quit IRC20:51
*** markvoelker has joined #openstack-meeting-320:56
*** markvoelker has quit IRC21:00
*** xavierr has quit IRC21:01
*** jtomasek_ has quit IRC21:04
*** ducttape_ has quit IRC21:06
*** donghao has joined #openstack-meeting-321:11
*** donghao has quit IRC21:15
*** dimtruck is now known as zz_dimtruck21:16
*** yamahata has quit IRC21:18
*** lyan has quit IRC21:22
*** lyan has joined #openstack-meeting-321:24
*** sdague has quit IRC21:24
*** marst_ has quit IRC21:30
*** tellesnobrega has joined #openstack-meeting-321:30
*** crushil has joined #openstack-meeting-321:30
*** s3wong has quit IRC21:33
*** crushil has quit IRC21:37
*** lucasxu has quit IRC21:39
*** bobh has joined #openstack-meeting-321:50
*** zz_dimtruck is now known as dimtruck21:54
*** bobh has quit IRC21:55
*** bzhao_ has joined #openstack-meeting-321:59
*** slaweq has quit IRC22:05
*** markvoelker has joined #openstack-meeting-322:05
*** annegentle has quit IRC22:06
*** slaweq has joined #openstack-meeting-322:07
*** slaweq has quit IRC22:08
*** slaweq has joined #openstack-meeting-322:08
*** julim has joined #openstack-meeting-322:10
*** julim has quit IRC22:11
*** slaweq has quit IRC22:13
*** galstrom is now known as galstrom_zzz22:14
*** markvoelker has quit IRC22:15
*** julim has joined #openstack-meeting-322:16
*** markvoelker has joined #openstack-meeting-322:16
*** julim has quit IRC22:16
*** julim has joined #openstack-meeting-322:25
*** ttrifonov has quit IRC22:28
*** ttrifonov has joined #openstack-meeting-322:29
*** baoli has quit IRC22:29
*** gouthamr has quit IRC22:29
*** lyan has quit IRC22:44
*** ducttape_ has joined #openstack-meeting-322:48
*** claudiub has quit IRC22:49
*** jamespd has left #openstack-meeting-322:52
*** VW has quit IRC22:54
*** VW_ has joined #openstack-meeting-322:55
*** gouthamr has joined #openstack-meeting-323:05
*** markvoelker has quit IRC23:11
*** ducttape_ has quit IRC23:15
*** ducttape_ has joined #openstack-meeting-323:16
*** lyan has joined #openstack-meeting-323:16
*** pvaneck_ has quit IRC23:19
*** dimtruck is now known as zz_dimtruck23:19
*** rhochmuth has quit IRC23:23
*** rhochmuth has joined #openstack-meeting-323:23
*** rhochmuth has quit IRC23:28
*** iyamahat has joined #openstack-meeting-323:29
*** ducttape_ has quit IRC23:30
*** diablo_rojo has quit IRC23:40
*** markvoelker has joined #openstack-meeting-323:44
*** markvoelker has quit IRC23:45
*** lyan has quit IRC23:46
*** Swami has quit IRC23:49
*** lyan has joined #openstack-meeting-323:52
*** SumitNaiksatam has quit IRC23:57
*** zz_dimtruck is now known as dimtruck23:58
*** lyan has quit IRC23:59
*** iyamahat has quit IRC23:59

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