21:00:13 <mestery> #startmeeting networking
21:00:15 <openstack> Meeting started Mon Sep 14 21:00:13 2015 UTC and is due to finish in 60 minutes.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.
21:00:16 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
21:00:19 <openstack> The meeting name has been set to 'networking'
21:00:29 <mestery> #link https://wiki.openstack.org/wiki/Network/Meetings Agenda
21:00:29 <blogan> hello
21:00:37 <mestery> We've got a mostly liberty-rc1 focused agenda for today, so lets get started!
21:00:38 <kevinbenton> hi
21:00:42 <mestery> #topic Announcements
21:00:45 <armax> yello
21:00:49 <njohnston> hi
21:00:51 <ajmiller> Hi
21:00:51 <mestery> #link https://wiki.openstack.org/wiki/ReleaseNotes/Liberty#OpenStack_Liberty_Release_Notes Liberty Release Notes
21:00:52 <russellb> o/
21:00:56 <fitoduarte> hi
21:01:00 <markmcclain> o/
21:01:00 <mestery> #info Please continue adding high quality release notes to the release notes page
21:01:04 <neiljerram_bb> o/
21:01:06 <beagles> o/
21:01:10 <mestery> My thanks to those of you who have already plastered stuff on that page! Way to go!
21:01:12 <vichoward> o/
21:01:17 <hoangcx> Hi
21:01:36 <mestery> #info The Tempest plugin interface is now ready!
21:01:43 <emagana> mestery: is there a plan to move release notes into openstack-manuals?
21:01:45 <mestery> #link https://review.openstack.org/#/c/201955/ An example change using this
21:01:46 <carl_baldwin> Hi
21:01:59 <mestery> #link http://docs.openstack.org/developer/tempest/plugin.html Documentation for Tempest plugin
21:02:06 <mestery> emagana: I don't think so, those stay on the wiki page per past releases
21:02:22 <emagana> mestery: should we move them?
21:02:28 <ajo> hi :)
21:02:31 <emagana> mestery: correction.. copy them
21:02:50 <mestery> emagana: Copying them is fine, but I'd wait a bit, we still have more to add
21:02:59 <emagana> mestery: roger that!
21:03:00 <mestery> #link https://wiki.openstack.org/wiki/PTL_Elections_September_2015 PTL Elections have begun!
21:03:09 <mestery> #info I encourage anyone interested in running for Neutron PTL to throw their hat into the ring!
21:03:19 <mestery> We have a deep bench of leadership
21:03:29 <mestery> The next PTL is gonna be awesome :)
21:03:39 <mestery> Any other announcements for the team?
21:03:40 <kevinbenton> mestery: i was confused about your candidacy email. it made it sound like you weren't going to run
21:03:48 <mestery> kevinbenton: lol
21:03:49 <russellb> kevinbenton: lol
21:03:50 <ajo> kevinbenton lol
21:03:54 <markmcclain> haha
21:04:03 * Sukhdev salutes to outgoing PTL for awesome job he has done
21:04:12 <mestery> Also note: You can nominate someone else, that person has to +1 the nomination
21:04:19 <russellb> mestery: thanks for everything, mestery!  You've left the project in great shape
21:04:21 <mestery> Sukhdev: thanks :)
21:04:28 <ajo> yes, you have
21:04:35 <emagana> russellb: +1
21:04:36 <blogan> hear hear
21:04:41 <mestery> russellb: I'm just doing the final walkthrough before turning the keys over :)
21:04:44 <salv-orl_> kevinbenton: I think there is a bylaw for which if nobody runs the old PTL stays in charge indefinetely until one is found
21:04:46 <rossella_s> yes indeed! thanks Kyle, Neutron community is so much better now
21:05:01 <mestery> salv-orl_: Wait, no one told me that!
21:05:04 <ajo> salv-orl_: lol :)
21:05:04 <Sam-I-Am> moo.
21:05:13 <mestery> Any other announcements for the team?
21:05:22 <russellb> in all seriousness, if nobody runs, it falls to the TC to find and designate someone
21:05:30 <russellb> not that i expect that to happen here ...
21:05:36 <russellb> i think people are just holding off to build up suspense
21:05:38 <russellb> :)
21:05:42 <Sam-I-Am> looks like mike perez is freeing himself up :)
21:05:59 <mestery> :)
21:06:02 <carl_baldwin> #link http://git.openstack.org/cgit/openstack/governance/tree/resolutions/20141128-elections-process-for-leaderless-programs.rst
21:06:09 <carl_baldwin> ;)
21:06:14 <mestery> russellb: As the outgoing PTL, I'd be happy to provide a list of names to the TC should that happen :)
21:06:17 <mestery> Thanks carl_baldwin
21:06:24 <Sam-I-Am> mestery: carl first?
21:06:38 <russellb> mestery: the appointee has to agree though :(
21:06:40 <mestery> Sam-I-Am: Please, nominate carl_baldwin! Anyone can nominate anyone else
21:06:46 <mestery> russellb: That's no fun :(
21:06:47 <mlavalle> Sam-I-Am: ++
21:06:56 <Sam-I-Am> mestery: he's sitting next to me
21:06:59 <Sam-I-Am> i'm waiting to get punched
21:07:02 <mestery> Sam-I-Am: lol
21:07:05 <Sam-I-Am> there
21:07:18 <Sukhdev> Sam-I-Am :-)
21:07:21 <mestery> Seriously folks, we have many great leaders in our community! I know we'll support whoever becomes the next PTL and Neutron will continue to rock!
21:07:23 <mestery> OK
21:07:31 <mestery> Lets move along now :)
21:07:36 <mestery> #topic Bugs
21:07:39 <mestery> I know ... BUGS :(
21:07:46 <ajo> damn bugs :)
21:07:48 <mestery> First up
21:07:50 <mestery> #link https://bugs.launchpad.net/neutron/+bug/1484148
21:07:51 <openstack> Launchpad bug 1484148 in neutron "neutronclient gate broken following VPNaaS infra changes" [Critical,Confirmed] - Assigned to Paul Michali (pcm)
21:07:58 <armax> bugs: the life of this community
21:08:00 <mestery> pc_m: Looks like this one is under control?
21:08:04 <mestery> armax: lifeblood!
21:08:12 <pc_m> mestery: yes. Just need reviews.
21:08:24 <mestery> pc_m: I voted positively on your infra review
21:08:29 <mestery> Looks like you need that one first
21:08:36 <pc_m> Doesn't need to be critical, as there is a workaround (disabled tests)
21:08:48 <mestery> pc_m: OK, bumping down! :)
21:08:48 <pc_m> mestery: yes. thanks
21:09:05 <mestery> Next up
21:09:06 <mestery> #link https://bugs.launchpad.net/neutron/+bug/1477192
21:09:08 <openstack> Launchpad bug 1477192 in neutron "neutron test_multi_prefix_slaac failing in the gate with ping failures starting around 7/22" [High,Confirmed] - Assigned to Henry Gessau (gessau)
21:09:20 <HenryG> I took an initiall look
21:09:21 <mestery> HenryG: Thanks for correcting me on there :)
21:09:30 <mestery> HenryG: I don't know if this one deservers to be high based on your input. Thoughts?
21:09:31 <HenryG> It's not as bad as the query lets on
21:09:34 <mestery> Right
21:09:37 <mestery> Maybe it's medium?
21:09:43 <HenryG> probably
21:09:48 <mestery> Sold!
21:09:58 <HenryG> But there is a problem in there somewhere, that needs looking at
21:09:59 <mestery> HenryG: Thanks!
21:10:00 <mestery> Moving on
21:10:13 * mestery nods
21:10:15 <mestery> #link https://bugs.launchpad.net/neutron/+bug/1439696
21:10:16 <openstack> Launchpad bug 1439696 in neutron "Referencing a lb-healthmonitor ID for the first time from Heat would fail" [High,Confirmed] - Assigned to Doug Wiegley (dougwig)
21:10:32 <mestery> dougwig: I'm not sure this deserves to be high, do you agree?
21:10:37 <mestery> dougwig: It's been sitting here for a while now
21:10:46 <xgerman> Medium
21:10:59 <mestery> xgerman: Sold!
21:11:06 <Sam-I-Am> doug says it doesnt need t be high
21:11:07 <mestery> dougwig is predisposed at the QA midcycle now, so lets move along
21:11:08 <Sam-I-Am> he's standing here
21:11:10 <mestery> Sam-I-Am: Thanks!
21:11:16 <Sam-I-Am> should be joining shortly
21:11:23 <mestery> Sam-I-Am: Tell him he's up for this one too
21:11:29 <mestery> #link https://bugs.launchpad.net/neutron/+bug/1163569
21:11:30 <openstack> Launchpad bug 1163569 in neutron "security groups don't work with vip and ovs plugin" [High,Confirmed] - Assigned to Doug Wiegley (dougwig)
21:11:39 <mestery> This one has a security note attached which lifeless was curious to have someone from Neutron look at.
21:11:46 <mestery> Hoping dougwig can verify this yet
21:11:48 <kevinbenton> that bug is older than i am
21:11:53 <mestery> lol
21:11:57 <xgerman> sc68cal ?
21:11:57 <kevinbenton> i don't understand how it's been sitting there that long
21:12:00 <mestery> kevinbenton: To be fair, you're like 14, right?
21:12:07 <sc68cal> hmm?
21:12:14 <dougwig> we havent looked yet.  bad devs, no biscuit.
21:12:29 <xgerman> sc68cal SH is our wheelouse
21:12:32 <mestery> dougwig: Can you eyeball this one closer this week yet when you get a moment?
21:12:33 <xgerman> SG
21:12:46 <mestery> xgerman: Yes, sc68cal looking would be great too
21:12:48 <mestery> sc68cal: https://bugs.launchpad.net/neutron/+bug/1163569
21:12:49 <openstack> Launchpad bug 1163569 in neutron "security groups don't work with vip and ovs plugin" [High,Confirmed] - Assigned to Doug Wiegley (dougwig)
21:12:57 <dougwig> mestery: yes, hopefully i can delegate that eyeball, but yes.
21:13:02 * sc68cal adds to his trello
21:13:18 <mestery> :)
21:13:20 <mestery> OK, moving on
21:13:28 <mestery> #link https://bugs.launchpad.net/neutron/+bug/1491131
21:13:30 <openstack> Launchpad bug 1491131 in neutron kilo "Ipset race condition" [High,New]
21:13:33 <mestery> This one was reported by an actual operator!
21:13:44 <Sam-I-Am> we have those?
21:13:45 <mestery> Looks like ZZelle__ assigned it to himself
21:14:11 <ZZelle__> mestery, yes, that's my tomorrow job
21:14:12 <ajo> yikes, I forgot to follow up
21:14:23 <ajo> I see shihanzhang came with a few patches that can be backported to kilo
21:14:23 <mestery> ajo: :)
21:14:29 <mestery> ajo: Excellent!
21:14:36 <mestery> ajo: Can you propose those ones if they aren't already proposed?
21:14:46 <ajo> I didn't see ocurrences of what the operator saw in logstash
21:14:53 <ajo> but that doesn't mean it's not in kilo
21:15:08 <ajo> mestery: I will
21:15:22 <mestery> ajo: AWesome sir, thanks :)
21:15:35 <mestery> Does anyone have any bugs for the team to talk about this week?
21:15:42 <armax> mestery: well
21:15:54 <armax> we should inform the group that DVR job went back to non-voting
21:15:59 * mestery straps in for the armax bug assault
21:16:01 <armax> Swami: ^^
21:16:08 <mestery> #info the DVR job is non-voting again :(
21:16:13 <mestery> armax: tl;dr for the team?
21:16:15 <Sam-I-Am> there's an email going around
21:16:17 <Sam-I-Am> sc68cal: ^
21:16:33 <armax> carl_baldwin, dougwig, sc68cal and ryan would tell you more
21:16:33 <sc68cal> yep, sent it about 30 mins ago for people to review
21:16:38 <mestery> #link http://lists.openstack.org/pipermail/openstack-dev/2015-September/074433.html
21:16:41 <mestery> sc68cal: ^^^
21:16:41 <armax> they were the ones charging the coup
21:16:54 <dougwig> off with its head.
21:17:00 <Sam-I-Am> is this all dvr jobs or just dvr-multi?
21:17:03 <Swami> armax: hi
21:17:28 <dougwig> more seriously, we have some work to do, as a team, to make sure our jobs are stable.  and since dvr has merged, it is our responsibility. if we don't want that, it needs to be out.
21:17:29 <pc_m> #info VPN functional tests for Neutron commits is upstreamed as experimental job
21:17:42 <mestery> dougwig: Spoken like a true PTL! :)
21:17:45 <ajo> I'm cleaning up the QoS house with this: https://launchpad.net/bugs/1486039,  but you will see me pushing for a refactor just in front, to avoid fixing the same thing twice in different qos drivers..
21:17:46 <openstack> Launchpad bug 1486039 in neutron "Setting a policy to a network will limit the router/dhcp/net-device ports, that's not expected" [High,In progress] - Assigned to Miguel Angel Ajo (mangelajo)
21:17:59 <mestery> ajo: Ack
21:18:09 <ajo> I know is a bit late in the cycle to be doing refactors, but I guess QoS is experimental, and not a bad thing to cleanup asap
21:18:29 <mestery> ajo: +1000.5
21:18:31 <mestery> Any other bugs for the team?
21:18:41 <mestery> armax: You have another few up your sleeve today?
21:18:44 <ZZelle__> Do we need such feature in Liberty? https://review.openstack.org/#/c/221508
21:18:48 <armax> dougwig: yes, that applies to any job, dvr, functional, api, etc
21:18:50 <Sam-I-Am> nice to see a lot of linuxbridge stuff has been addressed
21:18:59 <armax> mestery: no I am good
21:19:01 <Sam-I-Am> i'm currently reworking the install guide to use it
21:19:03 <mestery> armax: ack
21:19:09 <armax> I did my bug scrub during the past few days
21:19:27 <mestery> ZZelle__: I'm on the fence there, lets iterate on the review for that one
21:19:31 <armax> I am content
21:19:33 <mestery> armax: That's because you're awesome.
21:19:35 <ajo> ZZelle__, what's the thing, which bridges don't we clean now?
21:19:36 <russellb> Sam-I-Am: LB with provider networks?
21:19:41 <russellb> (the install guide i mean)
21:19:58 <ZZelle__> mestery, ok
21:20:04 <Sam-I-Am> russellb: yes, and augmenting that arch to do l3 things
21:20:12 <russellb> Sam-I-Am: cool
21:20:22 <mestery> OK, lets slide along into the next section ..
21:20:23 <Sam-I-Am> will talk about it more in a bit here
21:20:23 <mestery> #topic Docs
21:20:29 <mestery> emagana: hi there!
21:20:31 <mestery> Sam-I-Am: Also, hi there
21:20:34 <emagana> mestery: Hi!
21:20:36 <Sam-I-Am> yeah... like here :)
21:20:43 <mestery> Sam-I-Am: You see what I did there?
21:20:56 <emagana> All the open reviews for IPv6 have been completed. Thanks!
21:20:56 <Sam-I-Am> yep
21:21:04 <sc68cal> yaaaaaay
21:21:06 <ZZelle__> ajo, see https://bugs.launchpad.net/neutron/+bug/1328546
21:21:07 <openstack> Launchpad bug 1328546 in neutron "Race condition when hard rebooting instance" [High,Fix released] - Assigned to Li Ma (nick-ma-z)
21:21:08 <Sam-I-Am> whats ipv6?
21:21:25 <emagana> Working on the sub-chapter for QoS hoping to get a lot of help from ajo
21:21:39 <ajo> yes emagana , thanks, that will help a lot,
21:21:44 <Sam-I-Am> docs are good
21:21:46 <mestery> awesome! Thanks emagana and ajo!
21:21:53 <ajo> emagana, just fighting the last life of qos bugs to jump into it,
21:22:05 <emagana> ajo: I will get more staff between today and tomorrow.. wait for my next patch
21:22:15 <ajo> emagana+++++++++
21:22:41 <emagana> mestery: I will review the release notes and make sure we have some coverage in the networking guide
21:23:03 <emagana> Sam-I-Am and sc68cal Do you guys want to add something?
21:23:03 <mestery> emagana: Awesome! In particular, RBAC networks, QoS and pluggable IPAM are probably worthy of documentation notes
21:23:09 <Sam-I-Am> emagana: yeah
21:23:11 <mestery> carl_baldwin kevinbenton ajo: ^^^
21:23:21 <emagana> Sam-I-Am: go for it!
21:23:23 <ajo> +1 :)
21:23:25 <Sam-I-Am> i'm working on the installation guide changes to make linuxbridge go in liberty
21:23:29 <Sam-I-Am> #link https://review.openstack.org/#/c/221560/
21:23:39 <mestery> Sam-I-Am: nice nice nice!
21:23:43 <sc68cal> advanced services need docs in the networking guide
21:23:46 <Sam-I-Am> here's the plan...
21:23:49 <sc68cal> *cough* fwaas ;)
21:24:00 <mestery> sc68cal: I'm going to add a release note there
21:24:05 <xgerman> e\\\yep
21:24:08 <Sam-I-Am> there's only one architecture... two nodes, two network interfaces per node
21:24:09 <mestery> indicating we're rebooting it and will remove the existing API in Mitaka
21:24:12 <mestery> That sound right?
21:24:15 <mestery> xgerman sc68cal : ^^^^
21:24:19 <xgerman> yes
21:24:20 <Sam-I-Am> this way no one has to choose a particular arch based on hardware limitations
21:24:21 <mestery> cool
21:24:40 <Sam-I-Am> we start people out with provider networks, then optionally let them add L3 support
21:24:54 <Sam-I-Am> if they have L3 support, they can use both provider and project networks
21:25:28 <Sam-I-Am> this also solves the common gripe of 'why cant i launch a vm on the ext/public net' when they used the neutron arch
21:25:42 <Sam-I-Am> now it supports both... with less hardware
21:26:14 <Sam-I-Am> i've tested the new arch and it works
21:26:14 <ajo> cool :)
21:26:27 <Sam-I-Am> hopefully we can get the patches written and merged in a couple of weeks
21:26:39 <kevinbenton> Sam-I-Am: i'm not following
21:26:47 <Sam-I-Am> kevinbenton: que?
21:26:51 <kevinbenton> Sam-I-Am: what patches? neutron should have supported this for a long time
21:27:05 <Sam-I-Am> kevinbenton: docs patches
21:27:08 <Sam-I-Am> upstream install guide
21:27:13 <Sam-I-Am> neutron is fine :)
21:27:18 <kevinbenton> Sam-I-Am: oh, i see
21:27:19 * mestery quotes Sam-I-Am
21:27:24 <Sam-I-Am> haha
21:27:28 <ajo> :) lol
21:27:33 <Sam-I-Am> * for various kinds of neutron
21:28:04 <Sam-I-Am> we will point users of the install guide to the networking guide for more details
21:28:09 <mestery> Sam-I-Am: ++
21:28:10 <Sam-I-Am> rather, more production-worthy archs
21:28:15 <Sam-I-Am> now that we have it
21:28:49 <mestery> Sam-I-Am: That's a good goal, thanks for that!
21:28:59 <mestery> Looks like lots of awesome work going on the docs area. Thanks emagana and Sam-I-Am!
21:29:06 <sc68cal> +++
21:29:08 * russellb is very thankful for folks working on docs :)
21:29:17 <mestery> russellb: +1000.5
21:29:21 <Sam-I-Am> sure thing
21:29:26 <Sam-I-Am> getting there...
21:29:29 <mestery> :)
21:29:35 <emagana> nothing else from me!!
21:29:36 <mestery> OK, lets move along to the meat of the meeting.
21:29:45 <mestery> #topic Liberty-RC1
21:29:51 <mestery> #link https://launchpad.net/neutron/+milestone/liberty-rc1
21:30:01 <mestery> Lets see where we're at
21:30:15 <mestery> BPs: 5 down, 7 to go
21:30:21 <mestery> #info Blueprints: 5 down, 7 to go
21:30:22 <mestery> Not bad
21:30:29 <mestery> First up
21:30:29 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/lbaas-ref-octavia
21:30:35 <mestery> xgerman: This is on track yet for this week?
21:30:40 <xgerman> YES
21:30:40 <johnsom> https://review.openstack.org/#/c/223265/1
21:30:41 <dougwig> octavia as ref is done, just needs to be enabled in our devstack plugin.
21:30:44 <mestery> AWESOME!
21:30:45 <xgerman> one patch missing, some bugs
21:30:46 <mestery> MOAR LBAAS!
21:30:59 <mestery> That was easy. Thanks dougwig and xgerman
21:31:00 <xgerman> yep
21:31:01 <mestery> Next up
21:31:02 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/wsgi-pecan-switch
21:31:04 <dougwig> all props to the octavia folks.
21:31:06 <mestery> kevinbenton: MOAR PECAN!
21:31:13 <sc68cal> +++++
21:31:24 <kevinbenton> patch for bulk up late tonight/early tomorrow
21:31:26 <kevinbenton> then merge
21:31:30 <mestery> I think this one can land this week once kevinbenton completes MOAR BULK support
21:31:33 <mestery> kevinbenton: Thank you!
21:31:45 <mestery> Next up
21:31:47 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/external-dns-resolution
21:31:53 <mestery> mlavalle: This one needs a respin and then maybe it's good?
21:31:59 <mestery> I know carl_baldwin has been following it very closely
21:32:20 * carl_baldwin needs to check up on it.
21:32:32 <mestery> carl_baldwin: I think it's a small patch which mlavalle is addressing a few final nits
21:32:33 <mlavalle> mestery: ok, will do
21:32:37 <mestery> mlavalle: Awesome!
21:32:53 <mestery> Our first possibly contentious BP
21:32:54 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/add-availability-zone
21:33:08 <armax> I had a pass
21:33:09 <hichihara> armax: Can you review again?
21:33:13 <mestery> russellb armax: I know you two had looked at this one
21:33:14 <armax> hichihara: will do
21:33:14 <mestery> Thanks armax!
21:33:18 <mestery> armax: Early thoughts?
21:33:18 <hichihara> awesome
21:33:21 <mestery> What shape is it in?
21:33:32 <armax> it needed some work when I looked at it
21:33:35 * russellb thought he might review at night last week, but never had the energy
21:33:39 <russellb> i was traveling all week
21:33:41 <armax> amotoki also looked at it
21:33:43 <mestery> no worries russellb
21:33:46 <mestery> armax: Cool!
21:33:50 <mestery> OK, lets leave it targeted at this point.
21:33:54 <russellb> i did look today and it seemed like there was more coming?
21:34:01 <mestery> We've still got another week until potential RCs are cut
21:34:03 <armax> we’ll look at it again…but I got nervous when I looked at it
21:34:04 <markmcclain> mestery: I've also looked at it too
21:34:09 <markmcclain> armax: ++
21:34:16 <mestery> Thanks markmcclain, looks like this one has plenty of coverage :)
21:34:20 <mestery> Awesome!
21:34:22 <russellb> how bad would it be if it missed?
21:34:22 <ajo> 1I will try to run a pass too
21:34:26 <hichihara> Thanks folks
21:34:28 <mestery> MOAR AVAILABILTY ZONES!
21:34:33 * mestery notices the hogpile happening
21:34:35 <mestery> :)
21:34:35 <kevinbenton> russellb: neutron would be cancelled
21:34:40 <russellb> kevinbenton: oh ok
21:34:46 <mestery> Please folks, save some energy for ...
21:34:48 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms
21:34:53 <mestery> VLAN aware VMs
21:34:59 <mestery> That's right
21:35:12 <mlavalle> mestery: can we revisit #link https://blueprints.launchpad.net/neutron/+spec/external-dns-resolution?
21:35:16 <russellb> just feels like the point where we look for things to say no to instead of doing anything risky this late
21:35:23 <mestery> russellb: ++
21:35:33 <mestery> mlavalle: We can indeed! What is your case for that one?
21:35:40 <kevinbenton> mestery: doesn't vlan-aware VMs require a nova change?
21:35:43 <markmcclain> russellb: ++
21:35:45 <russellb> avail zones is pretty invasive
21:35:56 <russellb> so i'd be inclined to bump it ... and i apologize for not reviewing faster
21:35:59 <mestery> kevinbenton: Yes, but even outside that, my gut says no at this point
21:36:03 <mestery> russellb: ++
21:36:08 <mlavalle> mestery: functionality is veru advanced. Problem is the gate.... we need neutron with designate to be able to approve it
21:36:10 <mestery> armax: Thoughts on bumping avail zones?
21:36:10 <salv-orl_> I've never been a great fan of that avail zones work
21:36:15 <mestery> mlavalle: Yikes
21:36:18 <mestery> mlavalle: This late in the cycle?
21:36:28 <salv-orl_> so yes, if my opinion is worth anything that's something I'd bump
21:36:29 <armax> it depends how the suggestions have been addressed
21:36:29 <mestery> the case against avail zones is building ...
21:36:31 <kevinbenton> mestery: well if it needs nova changes then there is completely no point in merging
21:36:31 <mlavalle> mestery: I am working with Kiall, the designate ptl to get that fixed
21:36:45 <mestery> kevinbenton: Aye aye captain, it's out!
21:36:45 <russellb> i don't think it needs nova changes
21:36:53 <armax> mestery: if work had been done not so invasively merging it now wouldn’t be a problem
21:36:54 <russellb> but how far along is it?
21:36:58 <russellb> actually ready?
21:37:02 <armax> need to see how the author addressed my comments
21:37:03 <mestery> russellb: Patches were propsed 3 weeks ago ...
21:37:15 <mestery> armax: Sounds like you're not in favor either
21:37:16 <russellb> it doesn't need nova changes if you just create the ports in advance and pass the trunk port to nova (in theory)
21:37:20 <russellb> but i haven't looked at hte latest code :)
21:37:23 <mestery> :)
21:37:24 <russellb> if it's not implemented that way, i'd -1
21:37:26 <armax> I haven’t looked the new patchsets
21:37:38 <mlavalle> mestery: can I ping you Wednesday or Thursday to see how much progress we get this week?
21:37:38 <mestery> ++
21:37:39 <armax> but the entire code was proposed
21:37:46 <mestery> mlavalle: Lets do it! I'll eave it there for now
21:37:48 <mestery> *leave
21:37:56 <mlavalle> mestery: :-)
21:37:56 <salv-orl_> my 2p is that they way they're built currently, they're not going to be useful for operators.
21:38:04 <mestery> salv-orl_: vlan trunk ports?
21:38:15 <russellb> https://review.openstack.org/#/q/topic:bp/vlan-aware-vms,n,z
21:38:17 <salv-orl_> sorry I was still talking about av zones
21:38:19 <russellb> they are all set workflow -1
21:38:21 <mestery> :)
21:38:23 <salv-orl_> did not noticed you moved one
21:38:26 <salv-orl_> on
21:38:30 <mestery> russellb: That seals it then
21:38:34 <russellb> yeah we're talking about 3 at once i think
21:38:47 <mestery> #info VLAN aware VMs is out of Liberty
21:39:08 * salv-orl_ a wave rage awaits mestery
21:39:08 <russellb> to be clear, i'm a fan of that feature though
21:39:18 <russellb> just seems too late
21:39:29 <kevinbenton> russellb: yes
21:39:31 <ajo> russellb: +1
21:39:43 <emagana> russellb: Well, we have our first pririty for M
21:39:47 <mestery> OK
21:39:50 <emagana> priority*
21:39:53 <armax> we are always fun of features, it’s the code we’re not so fond of
21:39:53 <ajo> emagana: that makes sense :)
21:39:59 <mestery> On to avail zones now ...
21:40:00 <mestery> That one also out?
21:40:02 <russellb> armax: :)
21:40:04 <mestery> Seemed like the team was headed that way
21:40:22 <russellb> if it was just waiting on getting through the gate or something, that'd be one thing
21:40:27 <markmcclain> I think delaying makes sense
21:40:30 <armax> as dougwig pointed out, the onus is on the team to bear the cost
21:40:32 <mestery> Right
21:40:41 <mestery> Exactly
21:40:43 <mestery> armax: Words to live by
21:40:50 <russellb> it's invasive, and it's RC1 time
21:40:53 <russellb> i'd bump it
21:40:53 <mestery> yes
21:40:56 <armax> I have that tatooed on my right arm
21:41:03 <salv-orl_> bump looks good for me
21:41:04 <armax> the whole phrase
21:41:10 <kevinbenton> armax: "i'd bump it"?
21:41:12 <russellb> and again, i think the feature is OK ... but don't see a need to rush it
21:41:21 <armax> kevinbenton: yes, that one
21:41:35 <mestery> It's out
21:41:45 <mestery> Next up
21:41:46 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/add-port-timestamp
21:41:50 <mestery> I added this one back in today
21:41:59 <mestery> Because it was approved and slipped the cracks
21:42:00 <mestery> But the lone Neutron patch out for review
21:42:04 <mestery> indicates it only partially implements
21:42:06 <mestery> so ....
21:42:29 <armax> mestery: there’s no code posted for it
21:42:29 <mestery> #link https://review.openstack.org/#/c/213586/
21:42:31 <armax> afaik
21:42:35 <mestery> armax: https://review.openstack.org/#/c/213586/
21:42:43 <armax> oops
21:42:49 <mestery> armax: And https://review.openstack.org/#/c/220804/
21:42:50 <mestery> :)
21:42:56 <armax> well…there’s no sane code posted for it
21:43:02 <mestery> armax: Taht may be tru
21:43:03 <russellb> partially-implements ?
21:43:03 <mestery> *true
21:43:05 <mestery> I know
21:43:09 <mestery> russellb: My concern as well :(
21:43:09 <HenryG> I think we should talk more with the api-wg first
21:43:12 <mestery> Thus my question in the review
21:43:16 <russellb> HenryG: ++
21:43:21 <mestery> HenryG: We have salv-orl_ for that
21:43:23 <russellb> is it missing the changes-since filter?
21:43:25 <armax> btw there’s work that kevinbenton is doing to make these sorts of additions easier
21:43:33 <kevinbenton> WAT
21:43:39 <armax> so I think it’s safe to say this should be deferred
21:43:40 <russellb> that was a key part of that IIRC
21:43:45 <armax> kevinbenton: https://review.openstack.org/#/c/222079/
21:43:47 <mestery> armax: Awesome sir
21:43:52 * mestery moves it out
21:43:56 <armax> kevinbenton: ^
21:44:02 <salv-orl_> russellb: indeed
21:44:04 <russellb> i actually kind of hated these attributes in the nova API
21:44:21 <russellb> but it was largely due to implementation details
21:44:24 <russellb> anyway.
21:44:33 <russellb> doesn't look complete
21:44:34 <salv-orl_> current impl is concerned to make timestamp work, which is ok
21:44:54 <salv-orl_> but does not worry about the overall openstack api consumer experience
21:44:56 <russellb> yeah but their use case specifically was that + ability to do changes_since filtering
21:45:02 <mestery> Our last one
21:45:05 <mestery> #link https://blueprints.launchpad.net/neutron/+spec/neutron-flavor-framework-templates
21:45:11 <mestery> dougwig xgerman: Status update?
21:45:14 <salv-orl_> definetely not critcial feature, so I have all the time to bring that up with the rest of the api-wg
21:45:25 <xgerman> code is all submitted
21:45:30 <xgerman> https://www.irccloud.com/pastebin/yjizL2r9/
21:45:35 <russellb> salv-orl_: cool, definitely something worth trying to make sure is consistent where possible
21:45:52 <kevinbenton> AbtractFlavorFrameworkFactory
21:45:58 <salv-orl_> mestery: I see only one patch on the lp whiteboard and it;'s merged
21:46:19 <mestery> salv-orl_: For which spec?
21:46:21 <salv-orl_> ah found th eother patch(es)
21:46:27 <mestery> salv-orl_: got it
21:46:29 <salv-orl_> https://blueprints.launchpad.net/neutron/+spec/neutron-flavor-framework-templates
21:46:29 <mestery> port timestamp right?
21:46:32 <mestery> Ah
21:46:33 <mestery> OK
21:46:48 <xgerman> need to update the whiteboard then
21:46:54 <russellb> kevinbenton: you go wash that dirty mouth out with soap, young man
21:46:59 <mestery> #link https://www.irccloud.com/pastebin/yjizL2r9/
21:47:04 <mestery> lol
21:47:29 <kevinbenton> with the timstamp work deferred, i wonder if we should improve on it and just have a change log for resources
21:47:57 <xgerman> updated the whiteboard...
21:47:58 <salv-orl_> xgerman: other patches are in "work items". Topics do mot match that's why they are not in the wb
21:47:59 <mestery> kevinbenton: Seems like a nice idea
21:48:16 <ajo> kevinbenton: changelogs on busy DBs tend to grow huge tables
21:48:43 <salv-orl_> kevinbenton: if there is a use for it that's ok, otherwise let's not bother with stuff that can grow indefinetely in size.
21:48:44 <ajo> kevinbenton: do you mean keeping a change log of what changed on every resource?
21:48:54 <salv-orl_> think about the changelog for the default external network
21:49:24 <kevinbenton> ajo: right
21:49:59 <mestery> That was the last one
21:50:00 <ajo> kevinbenton, I don't mean I'm against it, if there are interesting use cases, let's just consider the risks :)
21:50:00 <mestery> We're down to 4 left
21:50:07 <mestery> So I encourage folks to review code for those BPs this week
21:50:09 <kevinbenton> salv-orl_: well that wouldn't have many changes
21:50:17 <salv-orl_> anyway: flavor framework. The api change by itself is not disruptive, so it's ok. It might not be the best way of doing it, but since we don't know we shiuld just go ahead and experiment with it rather than bikeshedding
21:50:29 * mestery notes there are 2 items left on the agenda
21:50:35 <ajo> salv-orl_: +1
21:50:40 <salv-orl_> kevinbenton: I know you would have said that. You want to carry me in a rabbit hole. I might say then floating IP
21:50:41 <xgerman> salv-orl_ +1
21:50:56 <salv-orl_> but then you would argue that the change log are in the port associated with it
21:51:04 <kevinbenton> salv-orl_: right :)
21:51:08 <mestery> OK
21:51:10 <mestery> moving along
21:51:13 <hogepodge> o/
21:51:16 <ajo> :)
21:51:17 <mestery> And this will be quick
21:51:20 <salv-orl_> kevinbenton: go for it then. It's awesome.
21:51:20 <mestery> #topic Mitaka Design Summit
21:51:22 <mestery> #link https://etherpad.openstack.org/p/neutron-mitaka-designsummit
21:51:25 <ajo> mestery: we like quick
21:51:30 <mestery> Please keep proposing fun ideas to discuss in Tokyo there
21:51:47 <mestery> The next PTL will handle scheduling the sessions (yay!) :)
21:52:01 <armax> you’re ptl until the week of the 24th
21:52:05 <armax> get to work
21:52:12 <mestery> armax: That long?
21:52:14 <hichihara> When must we do by?
21:52:16 <armax> yes
21:52:17 <mlavalle> armax: +++
21:52:26 <armax> leave a lasting legacy
21:52:28 <mestery> hichihara: I can't speak for the next PTL, but if it was up to me, sooner is beter than later :)
21:52:33 <armax> and since you bailed the week of feature freeze
21:52:33 <mestery> OK
21:52:37 <mestery> rofl
21:52:41 <neiljerram_bb> Does anyone try to add structure or organisation to all those ideas?
21:52:42 <armax> that’s the least you could do for the next ptl
21:52:44 <mestery> armax: Are you saying I owe the next PTL a week of time?
21:52:47 <mestery> neiljerram_bb: Yes
21:52:49 <mestery> the PTL does :)
21:52:49 <hichihara> lol
21:52:50 <armax> mestery: yes
21:52:59 <mestery> In general, the PTL and drivers team schedules the summit sessions
21:53:09 <mestery> And tries hard to make sure we address the less sexy ideas which are important for the community
21:53:19 <mestery> We'll have a bunch of those as well
21:53:19 <neiljerram_bb> Lucky new PTL!
21:53:21 <salv-orl_> neiljerram_bb: anarchy and chaos are the main drivers for our team. Structure and organization are two unknown values to us ;)
21:53:39 <russellb> can we have a "neutron users stories / priorities" session again?
21:53:43 <russellb> where people show up and scream at the room?
21:53:49 <mestery> russellb: YES!
21:53:52 <mestery> Also, lightning talks again
21:53:56 <ajo> screaming++
21:53:59 <mestery> Do people like those still?
21:53:59 <mestery> Seemed like they did
21:54:00 <neiljerram_bb> salv - thx, will adjust my paradigms
21:54:01 <russellb> because i loved that
21:54:10 <mestery> :)
21:54:12 <mestery> OK
21:54:14 <mestery> Lets move along
21:54:16 <mestery> Keep submitting
21:54:18 <mestery> We'll keep reviewing
21:54:19 <mestery> And planning
21:54:21 <mestery> For screaming
21:54:22 <kevinbenton> MILLIONS OF DOLLARS!
21:54:29 <mestery> rofl
21:54:31 <mestery> kevinbenton: daring
21:54:34 <emagana> sc68cal: +1operators meet-up and all we heard was crickets!
21:54:35 <mestery> #topic DefCore Update
21:54:52 <mestery> hogepodge: you're up!
21:54:59 <mestery> 5 minutes left even!
21:55:01 <hogepodge> not so much a defcore thing, but on the openstack compatible logo
21:55:04 <dougwig> he's typing.
21:55:07 <mestery> :)
21:55:08 <mestery> dougwig: lol
21:55:14 <Sam-I-Am> hogepodge: you need a louder keyboard
21:55:23 <sc68cal> emagana: that's good right?
21:55:29 <hogepodge> we'd like to ask vendors to test their compatible products, based on how projects define that testing
21:55:48 <emagana> sc68cal: indeed!
21:55:59 <hogepodge> so, would reviving some third party ci in neutron be a thing that could happen in 2016?
21:56:37 <neiljerram_bb> Is that not already a thing?
21:56:45 <mestery> hogepodge: It could, it needs a leader
21:56:46 <hogepodge> It's a larger topic, but I wanted to throw it out there for a possible future agenda.
21:56:53 <salv-orl_> hogepodge: the 3rd party CIs never died. They just mind their own business
21:56:56 <salv-orl_> but they're there
21:57:10 <mestery> hogepodge: In Vancouver the team determined 3rd party CI didn't have a ton of value, but perhaps that opinion has changed
21:57:12 <dougwig> they don't follow a uniform testing standard really, which is what this implies.
21:57:16 <mestery> dougwig: Right
21:57:18 <mestery> The problem with that
21:57:21 <mestery> is someone has to enforce it
21:57:29 <mestery> And that job of enforcing
21:57:30 <mestery> sucks
21:57:31 <mestery> REally bad
21:57:33 <salv-orl_> mestery: to be fair we said that reporting from 3rd party CI does not have value
21:57:36 <mestery> So unless someone steps upo
21:57:36 <hogepodge> yeah, it would need to be uniform. Similar to what cinder is doing.
21:57:42 <salv-orl_> and policing is a PITA
21:57:48 <hogepodge> mestery: that's what I keep hearing.
21:57:49 <russellb> i don't think it was that it didn't have value
21:57:51 <mestery> Unless someone steps up to enforce it and run it
21:57:54 <mestery> It's not gonna work
21:57:57 <russellb> it was more thatn enforcing rules around it wasn't worth it
21:58:06 <mestery> emagana and I tried and it was a full time job
21:58:06 <salv-orl_> but if you run a plugin or a driver, 3rd party CI is surely valuable for you
21:58:10 <mestery> So not trying to scare folks
21:58:12 <mestery> But being honest here
21:58:20 <hogepodge> so can I have time next week to make rough outline and also gather info? (say from salv-orl_)
21:58:22 <russellb> and that it was up to the driver maintainers to decide how valuable it was to them, for the quality they wanted to achieve
21:58:28 <mestery> hogepodge: Yes
21:58:41 <hogepodge> mestery: honesty is what I want. Scary or not. I prefer scary.
21:58:42 * salv-orl_ so scared now
21:58:45 <mestery> :)
21:58:48 <hogepodge> to sugarcoated
21:58:49 * mestery trembles
21:58:59 <mestery> hogepodge: It's worth trying again
21:58:59 <mestery> For sure
21:59:07 <mestery> OK
21:59:09 <mestery> Thanks hogepodge!
21:59:09 <hogepodge> Thanks for letting me ci bomb your meeting. :-D
21:59:13 <mestery> I look forawrd to move discussions here :)
21:59:19 <anteaya> o/
21:59:29 <mestery> OK, lets focus on Liberty-rc1 now!
21:59:32 <mestery> Not much time left :)
21:59:34 <armax> bye
21:59:36 <mestery> Thanks folks!
21:59:38 <mestery> #endmeeting