Thursday, 2017-04-27

*** d0ugal has quit IRC00:04
*** diablo_rojo has joined #openstack-meeting-300:04
*** palexster has joined #openstack-meeting-300:19
*** mickeys has quit IRC00:32
*** Sukhdev has quit IRC00:35
*** annegentle has joined #openstack-meeting-300:36
*** gouthamr has joined #openstack-meeting-300:46
*** wanghao has joined #openstack-meeting-300:48
*** shuyingya has joined #openstack-meeting-300:54
*** sdague has quit IRC00:58
*** shuyingya has quit IRC01:01
*** dixiaoli has joined #openstack-meeting-301:01
*** wanghao_ has joined #openstack-meeting-301:02
*** wanghao has quit IRC01:02
*** baoli has joined #openstack-meeting-301:09
*** baoli has quit IRC01:14
*** annegentle has quit IRC01:14
*** annegentle has joined #openstack-meeting-301:19
*** zhenguo has joined #openstack-meeting-301:19
*** shuyingya has joined #openstack-meeting-301:24
*** shuyingya has quit IRC01:24
*** diablo_rojo has quit IRC01:30
*** baoli has joined #openstack-meeting-301:32
*** iyamahat has quit IRC01:32
*** mickeys has joined #openstack-meeting-301:33
*** yamahata_ has quit IRC01:33
*** Sukhdev has joined #openstack-meeting-301:34
*** lyan has quit IRC01:37
*** mickeys has quit IRC01:37
*** baoli has quit IRC01:38
*** gcb has joined #openstack-meeting-301:38
*** donghao has joined #openstack-meeting-301:40
*** gouthamr has quit IRC01:42
*** rbak has joined #openstack-meeting-301:44
*** donghao has quit IRC01:45
*** rbak has quit IRC01:58
*** zhurong has joined #openstack-meeting-302:02
*** annegentle has quit IRC02:06
*** huanxuan has joined #openstack-meeting-302:07
*** wxy has joined #openstack-meeting-302:14
*** zhurong has quit IRC02:18
*** baoli has joined #openstack-meeting-302:18
*** baoli has quit IRC02:23
*** mickeys has joined #openstack-meeting-302:32
*** reedip has joined #openstack-meeting-302:34
*** zhurong has joined #openstack-meeting-302:44
*** reedip has quit IRC02:50
*** gouthamr has joined #openstack-meeting-302:51
*** reedip has joined #openstack-meeting-303:03
*** baoli has joined #openstack-meeting-303:19
*** huanxuan_ has joined #openstack-meeting-303:20
*** huanxuan has quit IRC03:23
*** baoli has quit IRC03:24
*** reedip has quit IRC03:26
*** psachin has joined #openstack-meeting-303:32
*** reedip has joined #openstack-meeting-303:32
*** tuanluong has joined #openstack-meeting-303:36
*** dimtruck is now known as zz_dimtruck03:37
*** donghao has joined #openstack-meeting-303:42
*** zhurong has quit IRC03:42
*** donghao has quit IRC03:46
*** iurygregory has quit IRC03:56
*** reedip has quit IRC04:01
*** gouthamr has quit IRC04:01
*** iurygregory has joined #openstack-meeting-304:02
*** warface has joined #openstack-meeting-304:09
*** baoli has joined #openstack-meeting-304:20
*** reedip has joined #openstack-meeting-304:23
*** baoli has quit IRC04:25
*** iyamahat has joined #openstack-meeting-304:28
*** anilvenkata has joined #openstack-meeting-304:30
*** Sukhdev has quit IRC04:32
*** warface has quit IRC04:43
*** yamahata_ has joined #openstack-meeting-304:45
*** Sukhdev has joined #openstack-meeting-304:48
*** Sukhdev has quit IRC04:49
*** salv-orlando has joined #openstack-meeting-304:51
*** Sukhdev has joined #openstack-meeting-304:53
*** warface has joined #openstack-meeting-304:53
*** pgadiya has joined #openstack-meeting-304:58
*** galstrom_zzz is now known as galstrom05:09
*** tobberydberg has joined #openstack-meeting-305:11
*** baoli has joined #openstack-meeting-305:21
*** claudiub|3 has joined #openstack-meeting-305:24
*** baoli has quit IRC05:25
*** warface has quit IRC05:42
*** cshastri has joined #openstack-meeting-305:43
*** warface has joined #openstack-meeting-305:43
*** donghao has joined #openstack-meeting-305:44
*** donghao has quit IRC05:48
*** ltomasbo|away is now known as ltomasbo06:04
*** reedip has quit IRC06:07
*** zhurong has joined #openstack-meeting-306:12
*** amotoki has quit IRC06:19
*** andreas_s has joined #openstack-meeting-306:19
*** ccamacho has quit IRC06:19
*** amotoki has joined #openstack-meeting-306:20
*** baoli has joined #openstack-meeting-306:22
*** baoli has quit IRC06:26
*** galstrom is now known as galstrom_zzz06:31
*** galstrom_zzz is now known as galstrom06:32
*** matrohon has joined #openstack-meeting-306:35
*** shuyingya has joined #openstack-meeting-306:36
*** Sukhdev has quit IRC06:39
*** bobmel has quit IRC06:43
*** d0ugal has joined #openstack-meeting-306:44
*** pcaruana has joined #openstack-meeting-306:44
*** salv-orlando has quit IRC06:48
*** zhurong has quit IRC07:02
*** MarkBaker has quit IRC07:03
*** iyamahat has quit IRC07:06
*** zhurong has joined #openstack-meeting-307:06
*** salv-orlando has joined #openstack-meeting-307:07
*** ltomasbo is now known as ltomasbo|away07:18
*** abalutoiu__ has quit IRC07:21
*** baoli has joined #openstack-meeting-307:22
*** baoli has quit IRC07:27
*** ralonsoh has joined #openstack-meeting-307:34
*** zhurong has quit IRC07:37
*** rmart04 has joined #openstack-meeting-307:39
*** egallen has joined #openstack-meeting-307:40
*** abalutoiu has joined #openstack-meeting-307:42
*** matrohon has quit IRC07:46
*** tuanluong has quit IRC07:51
*** abalutoiu has quit IRC07:51
*** mickeys has quit IRC08:06
*** abalutoiu has joined #openstack-meeting-308:07
*** kzaitsev_ws has joined #openstack-meeting-308:08
*** iyamahat has joined #openstack-meeting-308:11
*** tuanluong has joined #openstack-meeting-308:12
*** MarkBaker has joined #openstack-meeting-308:14
*** zhurong has joined #openstack-meeting-308:20
*** amotoki has quit IRC08:22
*** iyamahat has quit IRC08:23
*** sheeprine has quit IRC08:23
*** baoli has joined #openstack-meeting-308:23
*** pgadiya has quit IRC08:26
*** rossella_s has joined #openstack-meeting-308:26
*** sheeprine has joined #openstack-meeting-308:27
*** baoli has quit IRC08:28
*** andreas_s has quit IRC08:30
*** amotoki has joined #openstack-meeting-308:32
*** galstrom is now known as galstrom_zzz08:37
*** makowals_ has quit IRC08:39
*** reedip has joined #openstack-meeting-308:40
*** tuanluong has quit IRC08:42
*** ltomasbo|away is now known as ltomasbo08:43
*** d0ugal has quit IRC08:45
*** andreas_s has joined #openstack-meeting-308:46
*** ccamacho has joined #openstack-meeting-308:47
*** lpetrut has joined #openstack-meeting-308:50
*** mfedosin has joined #openstack-meeting-308:52
*** makowals has joined #openstack-meeting-308:52
*** reedip has quit IRC09:02
*** makowals has quit IRC09:04
*** d0ugal has joined #openstack-meeting-309:04
*** d0ugal has quit IRC09:04
*** d0ugal has joined #openstack-meeting-309:04
*** mickeys has joined #openstack-meeting-309:07
*** mickeys has quit IRC09:12
*** aarefiev_afk is now known as aarefiev09:16
*** MarkBaker has quit IRC09:16
*** amotoki has quit IRC09:21
*** sambetts|afk is now known as sambetts09:21
*** amotoki has joined #openstack-meeting-309:22
*** amotoki has quit IRC09:23
*** baoli has joined #openstack-meeting-309:24
*** baoli has quit IRC09:29
*** amotoki has joined #openstack-meeting-309:41
*** andreas_s has quit IRC09:46
*** salv-orl_ has joined #openstack-meeting-309:49
*** salv-orlando has quit IRC09:52
*** dixiaoli has quit IRC09:57
*** lpetrut_ has joined #openstack-meeting-309:58
*** ociuhandu has quit IRC09:59
*** lpetrut has quit IRC10:00
*** d0ugal has quit IRC10:01
*** d0ugal has joined #openstack-meeting-310:07
*** mickeys has joined #openstack-meeting-310:08
*** andreas_s has joined #openstack-meeting-310:13
*** mickeys has quit IRC10:15
*** zhurong has quit IRC10:20
*** d0ugal has quit IRC10:21
*** baoli has joined #openstack-meeting-310:25
*** d0ugal has joined #openstack-meeting-310:26
*** huanxuan_ has quit IRC10:27
*** zhurong has joined #openstack-meeting-310:27
*** amotoki has quit IRC10:28
*** baoli has quit IRC10:30
*** psachin has quit IRC10:30
*** psachin has joined #openstack-meeting-310:34
*** salv-orl_ has quit IRC10:38
*** d0ugal has quit IRC10:45
*** MarkBaker has joined #openstack-meeting-310:47
*** sdague has joined #openstack-meeting-311:04
*** xavierr has joined #openstack-meeting-311:04
*** d0ugal has joined #openstack-meeting-311:05
*** markvoelker_ has joined #openstack-meeting-311:11
*** markvoelker has quit IRC11:12
*** makowals has joined #openstack-meeting-311:16
*** anilvenkata has quit IRC11:34
*** MarkBaker has quit IRC11:37
*** markvoelker_ has quit IRC11:38
*** MarkBaker has joined #openstack-meeting-311:39
*** mfedosin has quit IRC11:42
*** mfedosin has joined #openstack-meeting-311:42
*** donghao has joined #openstack-meeting-311:42
*** amotoki has joined #openstack-meeting-311:45
*** donghao has quit IRC11:47
*** andreas_s has quit IRC11:51
*** mariannelm has joined #openstack-meeting-311:52
*** shuyingya has quit IRC11:55
*** shuyingya has joined #openstack-meeting-311:55
*** amotoki has quit IRC11:58
*** julim has quit IRC12:00
*** amotoki has joined #openstack-meeting-312:01
*** dgonzalez has quit IRC12:02
*** MarkBaker has quit IRC12:04
*** dgonzalez has joined #openstack-meeting-312:07
*** shuyingy_ has joined #openstack-meeting-312:08
*** shuyingya has quit IRC12:11
*** annegentle has joined #openstack-meeting-312:13
*** jayahn has joined #openstack-meeting-312:17
*** amotoki has quit IRC12:19
*** jayahn has quit IRC12:24
*** zhurong has quit IRC12:25
*** ociuhandu has joined #openstack-meeting-312:25
*** amotoki has joined #openstack-meeting-312:25
*** MarkBaker has joined #openstack-meeting-312:26
*** matrohon has joined #openstack-meeting-312:29
*** amotoki has quit IRC12:34
*** markvoelker has joined #openstack-meeting-312:35
*** shuyingy_ has quit IRC12:35
*** annegentle has quit IRC12:41
*** mickeys has joined #openstack-meeting-312:47
*** tobberyd_ has joined #openstack-meeting-312:48
*** mickeys has quit IRC12:51
*** tobberydberg has quit IRC12:52
*** bobh has joined #openstack-meeting-312:52
*** amotoki has joined #openstack-meeting-312:55
*** shuyingya has joined #openstack-meeting-312:58
*** zhurong has joined #openstack-meeting-312:58
*** tobberyd_ has quit IRC13:03
*** d0ugal has quit IRC13:04
*** wanghao has joined #openstack-meeting-313:04
*** tobberydberg has joined #openstack-meeting-313:04
*** wanghao has quit IRC13:05
*** lyan has joined #openstack-meeting-313:05
*** julim has joined #openstack-meeting-313:06
*** tobberydberg has quit IRC13:07
*** wanghao_ has quit IRC13:07
*** tobberydberg has joined #openstack-meeting-313:07
*** julim has quit IRC13:09
*** julim has joined #openstack-meeting-313:10
*** Guest94155 has quit IRC13:10
*** VW has joined #openstack-meeting-313:12
*** salv-orlando has joined #openstack-meeting-313:12
*** anilvenkata has joined #openstack-meeting-313:14
*** stanzgy has quit IRC13:19
*** bswartz has joined #openstack-meeting-313:19
*** d0ugal has joined #openstack-meeting-313:20
*** spzala has joined #openstack-meeting-313:22
*** baoli has joined #openstack-meeting-313:22
*** baoli has quit IRC13:23
*** baoli has joined #openstack-meeting-313:26
*** VW has quit IRC13:33
*** VW has joined #openstack-meeting-313:34
*** VW has quit IRC13:38
*** diablo_rojo has joined #openstack-meeting-313:46
*** lamt has joined #openstack-meeting-313:49
*** warface has quit IRC13:51
*** psachin has quit IRC13:56
*** annegentle has joined #openstack-meeting-314:03
*** warface has joined #openstack-meeting-314:07
*** rbak has joined #openstack-meeting-314:07
*** zz_dimtruck is now known as dimtruck14:13
*** claudiub|3 has quit IRC14:19
*** salv-orlando has quit IRC14:23
*** shuyingy_ has joined #openstack-meeting-314:24
*** shuyingya has quit IRC14:24
*** jayahn has joined #openstack-meeting-314:26
*** diablo_rojo has quit IRC14:27
*** d0ugal has quit IRC14:28
*** gouthamr has joined #openstack-meeting-314:31
*** d0ugal has joined #openstack-meeting-314:32
*** anilvenkata has quit IRC14:37
*** zenirc369 has joined #openstack-meeting-314:37
*** salv-orlando has joined #openstack-meeting-314:38
*** zhurong has quit IRC14:39
*** d0ugal has quit IRC14:39
*** lpetrut_ has quit IRC14:40
*** lhx_ has joined #openstack-meeting-314:42
*** ltomasbo is now known as ltomasbo|away14:42
*** donghao has joined #openstack-meeting-314:42
*** darrenc has quit IRC14:43
*** cshastri has quit IRC14:44
*** srobert has joined #openstack-meeting-314:44
*** tobberyd_ has joined #openstack-meeting-314:47
*** d0ugal has joined #openstack-meeting-314:47
*** tobberydberg has quit IRC14:51
*** tobberyd_ has quit IRC14:52
*** MarkBaker has quit IRC14:54
*** ralonsoh_ has joined #openstack-meeting-314:55
*** john-dav_ has joined #openstack-meeting-314:55
*** d0ugal has quit IRC14:56
*** ralonsoh has quit IRC14:57
*** janzian has joined #openstack-meeting-314:57
*** zenirc369 has quit IRC14:57
*** mlavalle has joined #openstack-meeting-314:59
mlavalle#startmeeting neutron_l315:00
openstackMeeting started Thu Apr 27 15:00:13 2017 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at
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
mlavalle#topic Announcements15:02
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"15:02
*** ralonsoh has joined #openstack-meeting-315:02
mlavalleThe Pike 2 milestone is next15:02
*** ralonsoh_ has quit IRC15:02
mlavalleScheduled for June 5 - 915:02
mlavalleBoston Summit is a little more that a week away15:04
mlavalleMay 8 - 1115:04
*** john-dav_ is now known as john-davidge15:04
*** jayahn has quit IRC15:04
* mlavalle looking forward to sharing some frosty beverages with haleyb and sending the bill to john-davidge15:05
haleybthat joke will never get old :)15:05
*** pcaruana has quit IRC15:05
mlavalleAny other announcements?15:06
*** MarkBaker has joined #openstack-meeting-315:06
mlavalle#topic Bugs15:07
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"15:07
*** iyamahat has joined #openstack-meeting-315:07
mlavalleFirst one up is
openstackLaunchpad bug 1627424 in neutron "FlushError on IPAllocation" [Medium,Fix committed] - Assigned to Miguel Lavalle (minsel)15:07
mlavalleWe don't have any hits for this bug producing any build failures over the past 7 days15:08
mlavalleremoving the "with build failures" requirement, I can see 7 hits over the past 7 days15:09
mlavalle5 of them are with branches ocata or newton, which don't have this fix:
mlavalleThe other 2 were in Tempest, which doesn't run Neutron master for the failed tests15:10
*** tellesnobrega has quit IRC15:10
mlavalleSo, I closed this bug a few minutes ago15:10
mlavalleIt took some effort but we squashed this sucker \o/15:11
*** mickeys has joined #openstack-meeting-315:11
mlavalleI don't think that final patchset was the entire solution. It was just the final nail in the coffin of this bug15:12
mlavalleThe re-factoring of the delete_network and delete_subnet methods in the ML2 and DB plugins by kevinbenton had a lot to do with it15:12
mlavalleNext up is
openstackLaunchpad bug 1683227 in neutron "test_connection_from_same_address_scope failed with: Cannot find device "qg-74372988-7f"" [High,Confirmed]15:14
mlavalleI didn't have time to spend with this one15:15
mlavalleSince the Flusherror is gone, I'll give this one some TLC soon15:16
haleybwe should add a logstash query to the bug to make sure it wasn't a one-time thing15:17
*** zigo has quit IRC15:17
mlavallehaleyb: yeah, that is my very next step15:17
mlavalleI don't want to be chasing any ghosts15:17
*** ltomasbo|away is now known as ltomasbo15:18
mlavalleThose are all the bugs we have today15:18
mlavalleAny other bugs from the team?15:19
haleybnot from me15:20
mlavallecool, moving on15:20
mlavalle#topic DNS15:20
*** openstack changes topic to "DNS (Meeting topic: neutron_l3)"15:20
*** d0ugal has joined #openstack-meeting-315:21
mlavalleI have been adding patchsets to add the dns_domain attribute to ports15:21
mlavalleI have 3 patchsets under review and a fourth one on its way15:22
mlavalleI will put all of them under the same gerrit topic so they are easy to find15:22
*** shuyingy_ has quit IRC15:22
mlavalle#topic Routed Networks15:23
*** openstack changes topic to "Routed Networks (Meeting topic: neutron_l3)"15:23
haleybmlavalle: can you put info on the DNS reviews on the etherpad?  i didn't see alink there15:24
mlavallehaleyb: I will do that15:24
mlavalleon the Routed networks stuff, I will start working on a spec to add floating ips support15:25
mlavalleAs soon as I push the first version, I will post it in the etherpad15:25
*** chyka has joined #openstack-meeting-315:26
mlavalle#topic Open Agenda15:27
*** openstack changes topic to "Open Agenda (Meeting topic: neutron_l3)"15:27
mlavalleI will submit a patchset to infra to add haleyb to the chairs of this meeting15:27
mlavalleAny toher topics?15:28
haleybnot from me15:28
mlavalleCool, we are done for today15:28
mlavalleEnjoy the rest of the week15:28
*** openstack changes topic to "OpenStack Meetings ||"15:29
openstackMeeting ended Thu Apr 27 15:29:03 2017 UTC.  Information about MeetBot at . (v 0.1.4)15:29
openstackMinutes (text):
*** john-davidge has left #openstack-meeting-315:29
*** janzian has left #openstack-meeting-315:30
*** markvoelker has quit IRC15:30
*** markvoelker has joined #openstack-meeting-315:31
*** aarefiev is now known as aarefiev_afk15:35
*** mlavalle has left #openstack-meeting-315:36
*** VW has joined #openstack-meeting-315:39
*** ccamacho has quit IRC15:41
*** yamahata_ has quit IRC15:48
*** iyamahat has quit IRC15:49
*** salv-orl_ has joined #openstack-meeting-315:50
*** elmiko has joined #openstack-meeting-315:50
*** makowals has quit IRC15:50
*** salv-orlando has quit IRC15:52
*** cdent has joined #openstack-meeting-315:56
cdent#startmeeting api-wg16:00
openstackMeeting started Thu Apr 27 16:00:01 2017 UTC and is due to finish in 60 minutes.  The chair is cdent. Information about MeetBot at
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 elmiko16:00
openstackCurrent chairs: cdent edleafe elmiko16:00
cdentanyone else joining us today?16:00
*** mordred has joined #openstack-meeting-316:00
cdentah, there we go16:01
* mordred waves at the nice people16:01
* edleafe is sad that mordred didn't wave at him, too16:01
cdent#topoic previous meeting actions16:01
*** rmart04 has quit IRC16:01
cdent#topic previous meeting actions16:01
*** openstack changes topic to "previous meeting actions (Meeting topic: api-wg)"16:01
edleafeyou misspelled 'tapioca'16:01
cdentelmiko and I are supposed to be preparing for the forum16:01
* cdent looks at elmiko sheepishly16:01
* elmiko is preparing furiously16:02
cdentwell done16:02
cdentedleafe was to ping liaisons16:02
cdentthere was email, anything after that edleafe ?16:02
*** Patifa has joined #openstack-meeting-316:02
edleafeI got a few responses, but not much16:02
*** lamt has quit IRC16:03
edleafeHeat will have to find a new liaison16:03
edleafeManilla too16:03
cdentthe usual rule for cross project liaisons is that it is the PTL in the absence of them designating someone else16:03
*** iyamahat has joined #openstack-meeting-316:04
cdentso one option would be to set missing people or projects to the ptl?16:04
edleafeI also asked for email addresses so that we can reach them outside of Gerrit reviews16:04
edleafeWe could set to PTL, but we don't know how many of the liaisons are no longer able to do the role, or how many didn't respond16:05
* edleafe thinks that's sort of the same thing :)16:05
cdenti just meant set to ptl for the missing projects and the people we know are missing16:05
elmikoi like adding the ptls then making ridiculous demands16:05
*** makowals has joined #openstack-meeting-316:05
cdentand leave the rest to rust16:05
edleafeSure, but that does nothing to address our concern about "silence is consent"16:06
cdentbut it may be better than the current situation16:06
*** galstrom_zzz is now known as galstrom16:07
* cdent doesn't have any ideas16:07
cdentmaybe silence is just gonna mean approval and that's the way it goes16:07
elmikoit seemed like we were using our best idea16:07
cdentelmiko I guess you and I can farm people at the BOF for ideas, but usual the attendees are not PTLs and CPLs16:09
cdentso besides that, that leaves wait and see. edleafe ?16:09
mordredI like silence is assent until it becomes a problem16:09
elmikogiven the nature of the openstack community, i'm not sure there is anything more substantial we can do16:09
mordredI mean, I don't "like" it - but I don't see a better choice atm16:09
edleafeI'm out of ideas. If there isn't that much interest...16:09
cdentmordred: you like that because you've written a lot of things that you want people to assent to ;)16:10
mordredcdent: yup16:10
elmikoedleafe: right, we can't "force" pppl to participate16:10
* edleafe posts a review that obligates CPLs to pay me $10016:10
mordredcdent: but seriously, we easily get hamstrung in openstack waiting for active consensus from people who have decided to not respond16:10
*** kzaitsev_ws has quit IRC16:10
mordredand that's not great either16:10
elmikoedleafe: +116:10
cdentmordred: true16:10
cdentit's just...a bummer16:10
elmikocdent: too true16:11
cdentwe've made an effort, so I guess we move on16:11
mordredeventually something will happen that will piss someone off and they'll start paying attention16:11
edleafemordred: that's "as good as it's gonna get" :)16:11
mordrededleafe: ++16:11
cdentalright, move on to next topic?16:11
elmikoi like the idea that we are as transparent as possible, give folks ample time to raise issues, and then make the guidelines published16:11
elmikoif it becomes an issue, then yeah, folks will complain and, ideally,they will get more involved16:12
mordredyah - and making a best-effort to ping any peope we can happen to know are specifically impacted when reasonable16:12
elmikonot like we are hiding16:12
cdentthe agenda is a bit out of date, we've just covered what's listed as the one new biz16:12
elmikomordred: absolutely16:12
cdent#topic new biz16:12
*** openstack changes topic to "new biz (Meeting topic: api-wg)"16:12
cdentbut edleafe pointed out a good point in his last comment on:
cdenti accidently implicitly approved a not yet approved guideline16:13
*** makowals has quit IRC16:14
elmikoseems like we need to get the dependent one merged to then16:14
cdentor leave out that bit16:14
elmikoman, i never imagined we'd need a dep graph for guidelines lol16:14
cdentor not care and assume the other wil merge16:14
edleafeSince jroll is not in a position to continue on the signaling patch, I can pick it up16:15
cdentedleafe: I had the same thing, but if you want it, have at16:15
cdents/had/had said/16:15
jrolledleafe: thanks for that16:15
edleafeWe can hold off on the stability guideline until that is merged. If it is killed, then we can update the stability patch16:15
mordredcdent: I think maybe just leaving that bit out, then putting in a patch that depends on the next_min_version patch that updates the api_interop doc with the next_min_version stuff?16:15
jrollI still consider it done, just need to get people to agree16:15
*** makowals has joined #openstack-meeting-316:15
edleafejroll: zactly16:16
edleafethat's why I figure let's not muck with the stability patch16:16
elmikoyeah, i kinda agree with mordred here. maybe best to leave out the dependent bit and then update when the other merges16:16
cdentedleafe: there's some desire to get the stability thing merged so the tc proposal that wants it can move16:16
mordredor maybe even add the next_min_version bits to jroll's patch so that it can be seen in the context of how it changes the api_interop doc?16:16
edleafejust hold off merging for now16:16
*** makowals has quit IRC16:17
edleafeThe one contentious part left is the time aspect16:17
edleafeIOW, the guarantee that it won't change before $date16:18
cdent#link next_min_version:
edleafeBut thinking about that now, that could take a while to resolve16:18
* cdent nods16:19
edleafeSo maybe just drop the wording from stability, re-freeze, and merge it next week?16:19
elmikoyeah, that seems like it will need some time in the oven16:19
cdentworks for me16:19
mordrededleafe: ++16:19
elmikoi'm +1 for rewording16:19
cdenti've push a new version which s/,.*/\./16:21
cdenti figured simple was best16:21
cdentelmiko, edleafe can one of you glance and refreeze if it is sufficient?16:21
*** matrohon has quit IRC16:22
cdentI'd be somewhat inclined to think that was a small enough change to be a typo16:22
cdentand thus we can just merge it16:22
cdentbut I'm probably violating protocol somehow16:22
*** tobberydberg has joined #openstack-meeting-316:22
elmikoyou, violate a protocol, i'm shocked i tell you, shocked!16:22
* cdent has infectious PTSD from mordred 16:23
*** donghao has quit IRC16:23
elmikoyeah, that change lgtm16:24
* edleafe is super-conservative, as everyone who knows me will attest to16:24
* cdent guffaws16:24
* elmiko sarcasm meter goes off16:24
cdentAnyone else have any other new business? mordred did you want to chat about your novels?16:25
elmikoomg, remember a few weeks ago we joked about sarcasm aaS?16:25
elmikomy group dug up all these machine learning articles about sarcasm detection16:25
*** lhx_ has quit IRC16:25
mordredI mean, I have written several very large and mind-hurting new documents16:25
elmikouh oh16:25
mordredI will apologize in advance for the one on consuming discovery - it definitely hurts16:26
cdent#link discovery-related proposed guidelines:
cdentyeah don't let that one put you off. the rest of them pay out16:26
edleafeNo exaggeration - it took me almost 3 hours to digest the first one16:26
mordredit might be worth a couple of seconds of background of how we even got here real quick ...16:26
*** galstrom is now known as galstrom_zzz16:26
*** abalutoiu has quit IRC16:26
edleafeelmiko: the later versions had better examples that made things a bit clearer16:27
*** tobberydberg has quit IRC16:27
elmikoahh, gotcha16:27
edleafemordred: go for it!16:27
elmikoand yeah, background++16:27
mordredover in shade-land we're currently working on swiching from client libs to direct REST - which has been quite pleasant overall16:27
mordredbut we got to the point where we needed to do version discovery for the third time, and it seemed like we should maybe write a general function16:27
mordredthat's when we learned that keystoneauth already has a general function to do version discovery16:27
mordredbut it didn't quite do all the things we needed16:28
mordrednext step - add them!16:28
mordredbut ... ksa has some nice logic, and we wanted ot add some new cases - and it quickly became clear that there was not a general understanding of what the 'right' thing to do was16:28
mordredother than just waht the existing libs happened to have already been doing16:28
*** warface has quit IRC16:29
mordredso I have _no_idea_ how people in non-python land could hope to navigate that, if it's even hard for those of us with the libs16:29
mordredanywho - I wrote up what I have come to understand as the complete process that covers all of the edge cases and is forwards compatible with how we'd LIKE  it to work in the future16:30
*** warface has joined #openstack-meeting-316:30
mordredthat, then,led to writing down what we'd like it to be the in future )16:30
elmikodoes this tie in at all to the early proposals we had for adding api discoverability to the guidelines?16:30
elmikoi think we have some json-home stuff in there16:31
edleafeThe biggest problem with reviewing is that (aside from grammar and the like) none of us have the domain knowledge that mordred does16:31
*** gouthamr has quit IRC16:31
mordredI've been pulling catalogs and version discovery docs from various clouds and just walking through them by hand - which isn't super pleasant - but yah, we need to come up with a better way to vett the actual logic itself16:32
mordredelmiko: the version discovery stuff doesn't change much realted to api-discoverability as much as just capture current state and what folks have been generally saying at summits and ptgs16:33
elmikomordred: ah, gotcha. i hesitate to ask, but does this approach the HATEOS kinda stuff?16:33
mordredelmiko: it's definitely based around the version document that's in the microversions document being the "right" way for those to look- but it should hande all of the versoin documents you just linked16:34
mordredelmiko: not that I'm aware of16:34
cdentelmiko: your question reminds me of something that came up while I was reading mordred's stuff: we need, fairly regularly, to read the guidelines as a body of work and make sure we rationalize it for modern times and added docs and the like16:34
elmikocdent: +1 i like that intention16:34
edleafecdent: oh, so you're handing out homework now? :)16:35
elmikowell, i'll need to read up on morded's proposals before i could comment (semi-)intelligently ;)16:35
elmikoit seems like a great direction to go though16:35
*** matrohon has joined #openstack-meeting-316:35
*** salv-orl_ has quit IRC16:36
mordredelmiko: the most contentious one is likely to be the third one in the stack, where I propose a completely new thing for clouds to deploy :)16:36
elmikobecause that *always* goes over well16:37
mordredthe first two should be fairly uncontroversial pending validation of their correctness16:37
elmikoack, are the other 2 linked from the first?16:37
mordredit's a stack16:37
elmikocool, i will read it before the forum16:37
cdentof 5!16:37
mordredoh - actually, api-wg owns service-types-authority too, right?16:37
elmikoi'll have plenty of airplane time and conference time next week ;)16:38
cdentedleafe: yes, I'm handing out homework for all of us, because clearly none of us have enough to do16:38
cdentmordred: sort of16:38
cdentthere's overlap16:38
cdentbut not concurrency16:38
mordredcause this morning, based on a question from dtroyer, I added:
mordred(which cdent asked some excellent questions on)16:38
cdentthey can probably be translated as "what was dtroyer's question?"16:39
mordred"how do we describe to people what to do about volumev2"16:39
elmikohuh, apparently i'm still core reviewer on service-types-authority16:39
* cdent apologizes for his outburst16:39
mordred is the consuming-version-discovery-process impact of that change16:39
mordredcdent: yah. so much agreement16:40
*** gouthamr has joined #openstack-meeting-316:40
mordredbut it's again a thing that we have encoded in a few libraries, which makes it tribal-knowledge16:40
mordredand if we cna put it somewhere in something akin to official guidance of how to consume some of these resources16:40
elmikoi'm curious, how come you're moving away from libs in favor of rest?16:41
mordredit might be reasonable to expect peopel outside of our bubble to havea chance of navigating it properly16:41
mordredelmiko: the libs provide negative value16:41
mordredelmiko: basically, they are thin verneers over REST, and hide some of the nicenes from the REST16:41
elmikocdent: i would so wear that16:42
mordredbut they introduce a giant pile of dependency issues16:42
elmikoright, that makes sense. i was just curious16:42
mordredso it's a huge amount of pain for no benefit16:42
mordredelmiko: it's a great question! I have learned from the process that the openstack rest apis are actually much better than I thought they were16:42
elmikomordred: that's very cool and encouraging16:42
mordredand the things I was frustrated with were actually their representation in our python libs16:42
elmikowow, that's really interesting16:43
mordredyah. it's _way_ clearer to consume the thing the devs actually expose :)16:43
* cdent has been saying that from the start...16:43
*** seanatcisco has joined #openstack-meeting-316:43
elmikoalthough this does make me wistful that openapi doesn't fit the openstack world16:43
cdent~15 minute warning16:44
cdentI think this week it is mordred that is passing out the homework, not me16:44
elmikotoo true16:44
edleafecdent: you're just piling on :)16:44
elmikoalthough, on the topic of re-reading the docs from time to time. it seems like a great activity to plan for the api-wg "bug week"16:45
mordredwell - honestly, I REALLY appreciate people reading these- the responses so far have been super helpful and we've made several improvements in them already16:45
mordredI do apologize for how complex the first one it - but also, that's the current state of the wrld16:45
mordredso - yay!16:45
elmikono worries, i'll definitely take a gander16:46
cdentI think it's great stuff to have16:46
edleafemordred: they are a royal pain to read, so I wouldn't read them if they weren't also really important16:46
edleafeso thanks for putting them together16:46
cdentIs there any additional business before we move on to managing the guidelines?16:46
edleafemove ahead!16:47
elmikonothing from me16:47
*** rossella_s has quit IRC16:47
cdentone frozen thing was defrosted and then refrozen, so that will make us ill, so don't eat it16:47
cdentthe other two frozen things are good to merge, so I will, now16:47
cdentedleafe wins at stackalytics16:48
*** lamt has joined #openstack-meeting-316:48
*** ltomasbo is now known as ltomasbo|away16:48
edleafecdent gets paid by LOC16:48
cdentnothing is ready to be frozen16:48
*** ociuhandu has quit IRC16:48
cdentI get paid?16:49
cdentmonty's new stuff is grand, and will be announced in the newsletter16:49
cdentjroll's thing will be taken over by edleafe16:49
cdentsdague's microversion architecture thing is a long term wip16:50
cdentcapabilities needs a new owner, but also might make more sense to abandon because we kind of killed it at the PTG16:50
edleafe#action edleafe to adopt jroll's patch16:50
cdentthoughts on what to do about capabilities?16:50
edleafecdent: +1 on abandoning capabilities16:51
cdentroger that16:51
* cdent does it16:51
*** ralonsoh has quit IRC16:51
cdentanything else about guidelines?16:52
cdent(note that I've been sloppy about #links through here because the newsletter will cover all that)16:53
edleafeyay sloppy!16:53
cdent#topic bug review16:53
*** openstack changes topic to "bug review (Meeting topic: api-wg)"16:53
cdentnothing new16:54
cdentbut also no progress on the existing bug. we should probably have a bug squash like elmiko said above16:54
cdent#topic weekly newsletter16:55
*** openstack changes topic to "weekly newsletter (Meeting topic: api-wg)"16:55
edleafeMost are TODOs, so we can probably each take one16:55
cdentyes, it's really just a matter of doing them, not any real complexity16:55
cdentI guess i is proabably about my turn for the newsletter?16:55
edleafeI have to run right after the meeting, so would you mind doing the newsletter, cdent?16:55
edleafejinx ** 216:56
* cdent explodes16:56
cdentelmiko: will you be around in a bit for proofing ping?16:56
cdentcool, will do so16:57
elmikoheads up, i'm out next week. i'll try to make the meeting, but i will be at a conference so...16:57
cdentthanks for coming mordred and thanks for huge contributions, you are this weeks golden cookie recipient16:57
elmikothanks mordred !16:58
cdentand with that16:58
*** openstack changes topic to "OpenStack Meetings ||"16:58
openstackMeeting ended Thu Apr 27 16:58:23 2017 UTC.  Information about MeetBot at . (v 0.1.4)16:58
openstackMinutes (text):
*** baoli has quit IRC16:58
elmikothanks cdent !16:59
*** elmiko has left #openstack-meeting-316:59
*** salv-orlando has joined #openstack-meeting-317:01
*** warface has quit IRC17:06
*** harlowja has quit IRC17:08
*** baoli has joined #openstack-meeting-317:09
*** tellesnobrega has joined #openstack-meeting-317:15
*** abalutoiu has joined #openstack-meeting-317:16
*** MarkBaker has quit IRC17:21
*** cdent has quit IRC17:24
*** donghao has joined #openstack-meeting-317:24
*** donghao has quit IRC17:29
*** baoli_ has joined #openstack-meeting-317:31
*** amotoki has quit IRC17:32
*** baoli has quit IRC17:33
*** tongli has joined #openstack-meeting-317:41
*** rbak has quit IRC17:42
*** baoli_ has quit IRC17:42
*** baoli has joined #openstack-meeting-317:45
*** seanatcisco has quit IRC17:46
*** seanatcisco has joined #openstack-meeting-317:46
*** tellesnobrega has quit IRC17:49
*** rkukura has joined #openstack-meeting-317:50
*** harlowja has joined #openstack-meeting-317:51
*** tbachman has joined #openstack-meeting-317:51
*** seanatcisco has quit IRC17:58
*** seanatcisco has joined #openstack-meeting-317:58
*** tellesnobrega has joined #openstack-meeting-317:59
*** annak has joined #openstack-meeting-317:59
*** SumitNaiksatam has joined #openstack-meeting-318:00
SumitNaiksatamrkukura: tbachman annak igordcard: hi there18:00
tbachmanSumitNaiksatam: hi!18:00
SumitNaiksatam#startmeeting networking_policy18:01
openstackMeeting started Thu Apr 27 18:01:02 2017 UTC and is due to finish in 60 minutes.  The chair is SumitNaiksatam. Information about MeetBot at
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
SumitNaiksatammain agenda today is thomas’ dual stack spec18:01
SumitNaiksatam#topic IP v4, v6 dual-stack support proposal18:01
*** openstack changes topic to "IP v4, v6 dual-stack support proposal (Meeting topic: networking_policy)"18:01
tbachmanannak: rkukura: SumitNaiksatam; thanks for the comments!18:01
SumitNaiksatamtbachman: np, rkukura deserves the majority :-)18:02
tbachmanSumitNaiksatam: ack!18:02
tbachmanFWIW, I’ve posted an updated version, based on the feedback/reviews18:02
SumitNaiksatamtbachman: so you had rightly brought up the external segment18:02
rkukuramore on there way ;)18:02
SumitNaiksatamrkukura: oh okay18:02
tbachmanrkukura: lol18:02
SumitNaiksatamrkukura: i thought you were done,  i mean...18:03
tbachmanSumitNaiksatam: yeah — I wasn’t sure whether or not to address that in this spec18:03
SumitNaiksatamtbachman: i was thinking it shoud be a part of this18:03
tbachmanSumitNaiksatam: okay. I’ll add that in then18:03
rkukurajust a couple nits, and maybe one needing fixing (so far)18:03
SumitNaiksatamtbachman: i dont mean to prolong this, but i think it goes with this18:03
tbachmanSumitNaiksatam: agreed18:03
tbachmansounds like I’ll need another iteration in any case ;)18:03
SumitNaiksatamrkukura: just kidding :-) thanks for the thorough review18:03
SumitNaiksatamannak: do you feel comfortable with this?18:04
SumitNaiksatami mean the current iteration18:04
annakSumitNaiksatam: sure, i was just giving a different perspective18:05
tbachmanannak: your point was very valid18:05
SumitNaiksatamtbachman: +118:05
annakperhaps we can keep it in mind for future18:05
tbachmanannak: definitely18:05
*** tongli has quit IRC18:06
rkukuraI have one open issue with the proposed spec that maybe we could get consensus on here18:06
SumitNaiksatamannak: with the proposed changes, do you feel you will be able to incorporate them in your driver?18:06
SumitNaiksatamrkukura: okay go ahead, you first18:07
annakSumitNaiksatam: I think so18:07
SumitNaiksatamannak: nice18:07
*** MarkBaker has joined #openstack-meeting-318:07
rkukuraafter annak18:07
SumitNaiksatamannak: the point of this exercise is to make sure that all drivers can support this18:07
annakI'm done :)18:07
SumitNaiksatamannak: otherwise we need to rethink18:07
SumitNaiksatamrkukura: go ahead18:08
rkukuraSo I’ve been arguiing that IPv4 subnets should always be allocated with the L3P’s subnet_prefix_length, even if that is different than the default_prefixlen of the IPv4 subnetpool from which it is being allocated.18:08
rkukuraI think this is important to allow the subnetpool (particularly for public addresses) to be widely shared - not everyone needs the same size subnets18:09
SumitNaiksatamrkukura: okay, i know we had a bit of discussion on this18:10
rkukuraSo my thinking is that subnet_prefix_length should be used if it is between the subnetpool’s min_prefixlen and max_prefixlen.18:10
rkukuraIt doesn’t seem this has been incorporated into the current draft, and some of the places where it says “subnet_prefix_length is ignored” would need updating.18:11
tbachmanrkukura: what did you think of my change for the L3P’s subnet_prefix_length is None?18:11
rkukuraIs that in the current draft tbachman ?18:11
SumitNaiksatamrkukura: i do still maintain that that model is but complicated for the user to understand18:11
* tbachman thinks18:11
SumitNaiksatamrkukura: however, if you thnk that it satisfies a use case which we cannot otherwise support, we can go with that18:12
rkukuraSumitNaiksatam: I’m not trying to add complexity, and it might even make the model a bit more consistent18:12
SumitNaiksatamrkukura: okay, how so?18:12
rkukuraEspecially with the resource_mapping driver, tuning the subnet size may be important18:13
tbachmanrkukura: looks like I left my addition out :(18:14
tbachmanI’ll have to add that in18:14
rkukuraIt can be argued it would be more consistent if subnet_prefix_length is always used (if not None) when allocating IPv4 subnets is more consistent than sometimes using it during L3P creation, and sometimes completely ignoring it for IPv418:14
SumitNaiksatamrkukura: okay18:15
rkukuraI do like the idea of None meaning “ignore it”18:15
tbachmanshould there instead be an exception if the user’s provided a length that is outside the min/max ?18:15
SumitNaiksatamrkukura: and why is it more important for the resource_mapping driver?18:15
SumitNaiksatamtbachman: yes18:15
*** spzala has quit IRC18:15
rkukuraI’m OK with either an exception when creating the L3P, or simply constraining the length by the subnetpool’s min and max when allocating from that pool. I think these subnetpool attributes are mutable.18:16
annakrkukura: could you perhaps give some concrete example of the use case where this is important? with examples of subnets18:17
tbachmanrkukura: ack. That’s where it gets a bit trickier18:17
rkukuraSo even if it looks OK when creating the L3P, the subnet_prefix_length could be outside the range when the subnetpool is actually used.18:17
rkukuraOne option would be to ignore that subnetpool (allocation would fail I think) and move onto the next (if available)18:18
rkukuraDo others agree that when a subnetpool (implicit or not) is widely shared between different L3Ps and non-GBP neutron code, tuning the subnet size at the L3P granularity is important?18:19
SumitNaiksatamrkukura: so this is a case where multiple L3Ps map to the same/shared address-scope and subnetpool?18:20
tbachmanrkukura: here you’re referring to the possibility of there being multiple subnets in the pool?18:20
rkukuraSumitNaiksatam: yes18:20
rkukuratbachman: I was referring above to the case where the L3P has multiple subnetpools, if that’s what you mean. A subnetpool generally can allocate many subnets (even of different sizes)18:21
tbachmanrkukura: right. We’re on the same page then18:21
tbachmanMy understanding was this was a possible use case where multiple projects supply their own pools18:22
SumitNaiksatamrkukura: what you say makes sense in theory, but i am not familiar with a strong usecase requiring that (parding my ignorance here)18:22
tbachman(sorry — own subnets to the pool, not own pools)18:22
SumitNaiksatamrkukura: of course, what you propose, is more flexible/granular18:22
rkukuraThe problem with lots of subnetpools is that public address space is a very scarce resource, so splitting into many pools, each only partially used, is very wasteful18:23
*** VW has quit IRC18:23
SumitNaiksatamrkukura: sure18:23
tbachmanrkukura: agreed with public. Not so much with private.18:23
SumitNaiksatamtbachman: good point18:23
*** VW has joined #openstack-meeting-318:23
rkukuraI think its a better practice to widely share a single subnetpool (for public space at least) and allocate what’s needed, of the size needed, from it18:23
tbachmanrkukura: that sounds like a good practice. I’m not familiar enough with use cases to know whether or not that’s the way this works with cloud providers18:24
tbachman(for private address space)18:24
tbachmanI can see there being a need for the flexibility of the customer providing their addressing needs18:25
SumitNaiksatamrkukura: it would have been ideal if the allocation was a little more predictable (for the user)18:25
tbachman(where “customer” would be a tenant)18:25
SumitNaiksatamthats my recurring concern (but perhaps is trumped by the use requirement to provide the flexibility)18:26
*** Sukhdev has joined #openstack-meeting-318:26
tbachmanrkukura: I think you have a good point on being explicit of the behaviors here. I don’t believe my changes cover that well18:26
*** Sukhdev has quit IRC18:27
*** salv-orlando has quit IRC18:27
SumitNaiksatami am wondering if there is a way we annotate which attribute was used to make the allocation?18:28
rkukuraShould we let tbachman try to include this in the updated spec, and see if we think it is usable enough?18:28
rkukuraIf subnet_prefix_length is None, that means not to use it, and use the IPv4 subnetpool’s default_subnetlen instead.18:29
SumitNaiksatamin my iteration of the spec i was achieving this by setting certain attributes to None18:29
SumitNaiksatamrkukura: ah just saying that :-)18:29
rkukuraSo setting it None “annotates” that the user does not want it used ;)18:30
SumitNaiksatamrkukura: right, yeah so if we can remove/reduce any ambiguity that way, it makes it a lot easier to consume18:30
rkukuraI think we just need the first part of the spec to focus on how the subnetpools and address scopes get created and/or associated with the L3P. Then the next part describes he subnets are allocated.18:31
rkukuraNot much change is needed - I have comments almost ready to post with most of them18:32
tbachmanrkukura: SumitNaiksatam: I’ll wait for the review comments, then update the spec accordingly18:32
tbachman(along with what we’ve discussed here)18:32
rkukurasounds good18:32
SumitNaiksatamtbachman: okay sure18:34
SumitNaiksatamrkukura: thanks18:34
SumitNaiksatamand tbachman thanks as well for shepherding this, it is pretty hairy18:34
tbachmanSumitNaiksatam: np! Had a lot of help from the work you did, as well as the reviews and comments by rkukura, annak, and yourself!18:34
SumitNaiksatamtbachman: rkukura: anything else you want to discuss on this?18:35
SumitNaiksatam#topic Open Discussion18:35
*** openstack changes topic to "Open Discussion (Meeting topic: networking_policy)"18:35
tbachmanSumitNaiksatam: I think I’m good18:35
rkukuranothing else on the spec18:35
SumitNaiksatamwant to highlight the work annak is doing in terms of bringing the project up to speed with neutron-lib18:35
SumitNaiksatamannak: thanks18:35
SumitNaiksatamhere is another one:18:35
SumitNaiksatami dont have anything else for today18:36
rkukuraone quick question for annak on those patches18:37
annakrkukura: sure18:37
*** Daviey_ has joined #openstack-meeting-318:38
rkukurafor code that we plan to backport to stable/mitaka, will we need to edit the back-ports, or did these deprecations start in mitaka (or earlier)?18:38
*** fnordahl_ has joined #openstack-meeting-318:38
*** igordcar1 has joined #openstack-meeting-318:38
SumitNaiksatamrkukura: these are mostly newton and beyond18:38
rkukuraI admit I haven’t looked yet18:38
*** Daviey has quit IRC18:38
*** annegentle has quit IRC18:38
*** eglute has quit IRC18:38
*** dhellmann has quit IRC18:38
*** fnordahl has quit IRC18:38
*** igordcard has quit IRC18:38
rkukuraso we will need different code for mitaka vs. newer branches, OK18:39
*** eglute has joined #openstack-meeting-318:39
*** dhellmann has joined #openstack-meeting-318:39
rkukurajust wanted know what to expect18:39
SumitNaiksatamrkukura: at this point i am not expecting mitaka backports for these18:39
annakI'm not sure, I think I started seeing deprecations  in newton18:39
SumitNaiksatamrkukura:  i mean most of them are not relevant for mitaka18:39
SumitNaiksatamannak: right18:40
rkukuraMy point is simply that new code being written (for stable/newton compatibility) that avoids the deprecations may need modification when back-ported to stable/mitaka, if the new APIs were not in mitaka18:40
SumitNaiksatamrkukura: yeah backports to mitaka are becoming messy18:41
annakmost of the changes are in imports, so its not that bad18:41
annakbut not all18:41
SumitNaiksatamrkukura: for instance, i am not backporting any of the notifications’ latest changes to mitaka18:41
SumitNaiksatamrkukura: because not all of it is applicable18:41
rkukuraSumitNaiksatam: Sure, but I believe the IPv6 work tbachman and I are doing will need to be back-ported to mitaka18:42
SumitNaiksatamrkukura: yeah, i hope its not messy!18:42
SumitNaiksatamalrighty, lets wrap it up for today then!18:43
SumitNaiksatamthanks all for joining18:43
tbachmanSumitNaiksatam: thanks!18:43
annakthanks! bye18:43
*** openstack changes topic to "OpenStack Meetings ||"18:44
openstackMeeting ended Thu Apr 27 18:44:00 2017 UTC.  Information about MeetBot at . (v 0.1.4)18:44
openstackMinutes (text):
rkukurathanks SumitNaiksatam!18:44
*** tbachman has left #openstack-meeting-318:44
*** donghao has joined #openstack-meeting-318:44
*** annak has quit IRC18:46
*** donghao has quit IRC18:49
*** Sukhdev has joined #openstack-meeting-318:51
*** SumitNaiksatam has quit IRC18:54
*** rbak has joined #openstack-meeting-318:54
*** tellesnobrega has quit IRC18:57
*** annegentle has joined #openstack-meeting-318:57
*** MarkBaker has quit IRC19:07
*** egallen_ has joined #openstack-meeting-319:12
*** egallen has quit IRC19:13
*** egallen_ is now known as egallen19:13
*** tellesnobrega has joined #openstack-meeting-319:26
*** salv-orlando has joined #openstack-meeting-319:30
*** nandal has joined #openstack-meeting-319:38
*** spzala has joined #openstack-meeting-319:43
*** srobert has quit IRC19:53
*** MarkBaker has joined #openstack-meeting-319:55
*** makowals has joined #openstack-meeting-320:11
*** sambetts is now known as sambetts|afk20:14
*** rkukura has left #openstack-meeting-320:24
*** Sukhdev has quit IRC20:32
*** makowals has quit IRC20:33
*** dimtruck is now known as zz_dimtruck20:37
*** salv-orlando has quit IRC20:39
*** salv-orlando has joined #openstack-meeting-320:39
*** pvaneck has joined #openstack-meeting-320:52
*** mickeys has quit IRC20:54
*** Sukhdev has joined #openstack-meeting-320:58
*** tongli has joined #openstack-meeting-320:59
*** mfedosin has quit IRC21:05
*** tellesnobrega has quit IRC21:09
*** iyamahat has quit IRC21:18
*** zz_dimtruck is now known as dimtruck21:20
*** iyamahat has joined #openstack-meeting-321:20
*** tongli has quit IRC21:22
*** julim has quit IRC21:27
*** zigo has joined #openstack-meeting-321:32
*** hichihara has joined #openstack-meeting-321:35
*** yamahata_ has joined #openstack-meeting-321:37
*** bobh has quit IRC21:42
*** seanatcisco has quit IRC21:47
*** seanatcisco has joined #openstack-meeting-321:47
*** salv-orl_ has joined #openstack-meeting-321:50
*** kbyrne has quit IRC21:50
*** salv-orlando has quit IRC21:52
*** xavierr has quit IRC21:52
*** kbyrne has joined #openstack-meeting-321:54
*** tellesnobrega has joined #openstack-meeting-321:55
*** mickeys has joined #openstack-meeting-321:56
*** slaweq has joined #openstack-meeting-321:59
*** annegentle has quit IRC22:00
*** annegentle has joined #openstack-meeting-322:01
*** salv-orl_ has quit IRC22:01
*** mickeys has quit IRC22:02
*** Sukhdev_ has joined #openstack-meeting-322:05
*** annegentle has quit IRC22:06
*** lyan has quit IRC22:07
*** VW has quit IRC22:07
*** abramley has quit IRC22:13
*** raj_sing- has joined #openstack-meeting-322:14
*** jungleboyj has quit IRC22:14
*** mrmartin has quit IRC22:14
*** peterstac has quit IRC22:14
*** harlowja has quit IRC22:14
*** raj_singh has quit IRC22:14
*** mrmartin has joined #openstack-meeting-322:15
*** SWDevAngel has quit IRC22:17
*** nikhil has quit IRC22:17
*** xgerman has quit IRC22:17
*** sweston has quit IRC22:17
*** SWDevAngel__ has quit IRC22:17
*** tdurakov has quit IRC22:17
*** sweston has joined #openstack-meeting-322:21
*** mickeys has joined #openstack-meeting-322:22
*** SWDevAngel has joined #openstack-meeting-322:23
*** SWDevAngel__ has joined #openstack-meeting-322:25
*** baoli has quit IRC22:26
*** nikhil has joined #openstack-meeting-322:26
*** tdurakov has joined #openstack-meeting-322:27
*** rbak has quit IRC22:27
*** rbak has joined #openstack-meeting-322:28
*** abramley has joined #openstack-meeting-322:36
*** salv-orlando has joined #openstack-meeting-322:37
*** peterstac has joined #openstack-meeting-322:37
*** egallen has quit IRC22:38
*** Patifa has quit IRC22:41
*** Patifa has joined #openstack-meeting-322:42
*** dimtruck is now known as zz_dimtruck23:00
*** diablo_rojo has joined #openstack-meeting-323:03
*** rbak has quit IRC23:04
*** zz_dimtruck is now known as dimtruck23:04
*** seanatcisco has quit IRC23:05
*** Sukhdev has quit IRC23:06
*** slaweq has quit IRC23:06
*** lyan has joined #openstack-meeting-323:08
*** salv-orlando has quit IRC23:08
*** sdague has quit IRC23:08
*** hichihara has quit IRC23:08
*** lamt has quit IRC23:09
*** diablo_rojo has quit IRC23:17
*** Patifa has quit IRC23:20
*** dimtruck is now known as zz_dimtruck23:22
*** harlowja has joined #openstack-meeting-323:23
*** chyka has quit IRC23:26
*** chyka has joined #openstack-meeting-323:27
*** chyka has quit IRC23:33
*** chyka has joined #openstack-meeting-323:34
*** chyka has quit IRC23:38
*** markvoelker has quit IRC23:40
*** jungleboyj has joined #openstack-meeting-323:55
*** mickeys has quit IRC23:58

Generated by 2.14.0 by Marius Gedminas - find it at!