14:00:27 <armax> #startmeeting networking
14:00:27 <openstack> Meeting started Tue Dec  1 14:00:27 2015 UTC and is due to finish in 60 minutes.  The chair is armax. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:28 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
14:00:30 <openstack> The meeting name has been set to 'networking'
14:00:32 <scheuran> hi
14:00:37 <obondarev_afk> hi
14:00:39 <ihrachys> o/
14:01:06 <ajo> morning / afternoon / night ;)
14:01:07 <ihrachys> obondarev_afk: using special psycho technics to connect to the channel?
14:01:09 <gsagie> Hello
14:01:22 <carl_baldwin> Hi
14:01:28 <ajo> ihrachys : obondarev  lol
14:01:31 <armax> hello folks
14:01:32 <obondarev> ihrachys: yep :-)
14:01:38 <dasm> ihrachys: worked :)
14:01:42 <mestery> o/
14:01:45 <rossella_s> hi
14:01:52 <Sam-I-Am> howdy
14:01:54 * regXboi marvels at armax's ability to function at this hour
14:02:02 * HenryG attends from a seat in the sky
14:02:10 <mhickey> Hey
14:02:12 * armax wonders too
14:02:18 <kevinbenton> Hi
14:02:18 <garyk1> is the neutron meeting now?
14:02:19 <armax> welcome to this fine Neutron meeting
14:02:21 <russellb> hi
14:02:25 * ajo hands over some coffee to armax, thanks for joining this soon btw ;)
14:02:30 <armax> today’s agenda:
14:02:31 <regXboi> HenryG: morning - where exactly are you in the sky?
14:02:32 <armax> #link https://wiki.openstack.org/wiki/Network/Meetings
14:02:36 * Sam-I-Am has a bowl of coffee
14:02:36 <ajo> soon->early
14:02:43 <armax> let’s dive in before I fall asleep on the keyboard
14:02:54 <armax> #topic Announcements
14:02:55 <dougwig> o/
14:03:07 <armax> #link https://wiki.openstack.org/wiki/Network/Meetings#Announcements_.2F_Reminders
14:03:08 <garyk1> neutronlbaas gate is borke
14:03:10 * regXboi is already asleep in the back of the room, this is just an AI chat-bot :)
14:03:15 <xgerman> :-(
14:03:19 <armax> garyk: yay!
14:03:29 <armax> garyk: is that because of pep8?
14:03:33 <garyk1> ack
14:03:43 <xgerman> yep
14:03:46 <armax> garyk: right, ok
14:03:51 <garyk1> i am trying to change import order (resolved pylint stuff). but that is just a deadend
14:03:55 <armax> garyk: someone ought to fix it!
14:04:15 <armax> garyk: best would be to pin astroid
14:04:15 <xgerman> someone ought to fix pep8
14:04:16 <pc_m> I've been doing work on the pep8 issue
14:04:24 <HenryG> regXboi: 30,000 ft up :)
14:04:32 <dougwig> i forgot how much i hate daylight savings.
14:04:32 <pc_m> Worked with infra last night.
14:04:36 <armax> garyk: that was caused by a release of both pylint and astroid
14:04:50 <Sam-I-Am> dougwig: you mean standard time? its just earlier now.
14:05:06 <armax> on Nov 29
14:05:07 <pc_m> armax: new astroid (not pinned) incompatible with pylint 1.4.4
14:05:09 <ihrachys> I still don't get why we don't skip the check, but meh.
14:05:30 <garyk1> its odd that it does not break any other repos.
14:05:41 <pc_m> it breaks vpn
14:05:42 <garyk1> anyways, i have digressed
14:05:43 <armax> garyk: that’s because their imports are not the same
14:05:48 <ihrachys> garyk: no one uses pylint? :D
14:05:56 <armax> garyk: besides, Neutron is unaffected because we have constrained jobs in force
14:06:07 <ihrachys> yay for constraints
14:06:08 <ihrachys> armax: but not for *aas
14:06:09 <pc_m> armax: right
14:06:18 * ihrachys has some patches for *aas, still WIP
14:06:26 <pc_m> armax: looks like kilo/juno in neutron are affected.
14:06:29 <armax> ihrachys: right, someone ought to switch
14:06:31 <armax> :)
14:06:35 <ihrachys> SOMEONE
14:06:42 <armax> pc_m: yes, that’s true
14:06:44 * ihrachys rolls his eyes around the room
14:06:58 <pc_m> armax: I have patches out for neutron juno/kilo
14:07:13 <pc_m> juno failing. need to see if we drop that fix
14:07:18 <armax> pc_m: I’ll look
14:07:22 <pc_m> #info http://lists.openstack.org/pipermail/openstack-dev/2015-December/080939.html
14:07:38 <pc_m> Captured some info on issue,
14:07:42 <armax> ok, mestery you had something you wanted to share?
14:07:53 <mestery> armax: I did?
14:07:54 <armax> this week is Milestone week
14:07:56 <pc_m> and some proposals for fix.
14:08:00 <mestery> Ah yes
14:08:03 <armax> mestery: yes you did
14:08:03 <regXboi> mestery, do you have donuts?
14:08:10 <Sam-I-Am> mmm donuts
14:08:10 <armax> yum
14:08:26 <mestery> If it's milestone related, we'll be proposing the patches to openstack/release to tag those today/tomorrow, but I guess we need to wait for lbaas to work again first :)
14:08:30 <ajo> ihrachys : that look for "someone" means we need sombody handling pinnings for stable branches?
14:08:48 <garyk1> chanuka and donuts are two weeks times. but miracales may always occur
14:09:05 <pc_m> ajo: I've pinned for neutron
14:09:06 <armax> mestery: that, plus invite people to get familiar with the new release process :)
14:09:16 <ajo> pc_m , sorry, right I just finished reading your link
14:09:17 <ajo> :)
14:09:20 <mestery> armax: Heh, yes.
14:09:20 <pc_m> ajo: and pinning on VPN (kilo so far)
14:09:25 <regXboi> is there a link to the new release process?
14:09:33 <mestery> #info The new release process is we propose a patch to openstack/release, and the release team cuts the release
14:09:36 <mestery> It's much more efficient this way
14:09:40 <armax> where they are supposed to add release notes for patches that are meant to deliver functionality that is worth release noting about
14:10:40 <mestery> Why, in the releasenotes of course :)
14:10:48 <armax> indeed
14:10:51 <mestery> Now, I think we'll have to sort some things out there as we go
14:11:00 <mestery> But that's what the milestone releases are for
14:11:00 <armax> I am sure we’ll forget a few times
14:11:07 <mestery> Forget and misformat
14:11:09 <mestery> Almost guaranteed
14:11:16 <armax> but we’ll get better and more trained over time
14:11:47 <mestery> We'll see :)
14:11:58 <ajo> :)
14:12:07 <armax> there’s also another change to the release process
14:12:09 <ihrachys> reviewers should enforce it until it becomes general habit.
14:12:16 <armax> #link http://lists.openstack.org/pipermail/openstack-dev/2015-November/080288.html
14:13:00 <dougwig> this is a new meeting format we have today, i see.  :)
14:13:02 <armax> where it’s being proposed to skip the ‘Fix Committed’ phase and go straight to ‘Fix released’ when a patch targeting the bug merges
14:13:18 <armax> dougwig: how so?
14:13:34 <mestery> lol
14:13:36 <dougwig> did we skip announcements and all the usual?
14:13:46 <kevinbenton> dougwig: no, you just slept through them
14:13:57 <regXboi> i thought this *was* the announcements
14:13:58 <Sam-I-Am> i think the announcement was 'its early'
14:14:14 <armax> I believe we’re announcing stuff, even though I am only functioning at 25% of my abilities
14:14:17 <armax> anyhow..
14:14:31 <armax> another change worth raising awareness for is this one:
14:14:40 <armax> #link https://review.openstack.org/#/c/226157/
14:14:59 <armax> that discusses how to ensure backwards compatibility for clients and libraries
14:15:04 <regXboi> does going directly to fix released have any serious impact on our workflow? I'm not seeing it this morning...
14:15:19 <armax> regXboi: I don’t think so
14:15:34 <regXboi> armax: that's why I'm asking, I don't see any either
14:15:44 <garyk1> armax: i have a concern related to that and the decomposition of the neutron client - how do we support backwards compatibility
14:15:45 <armax> regXboi: I have asked when the process change would be in force, but no-one cared to reply to miss or I missed the response
14:16:14 <garyk1> say a user is running client X and they upgrade and some support has been moved out - then they need to install additional packages
14:16:32 <regXboi> armax: you missed the response: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080372.html
14:16:48 <regXboi> armax: Doug is talking next week
14:17:03 <regXboi> er *targeting*
14:17:05 <armax> regXboi: I knew it I wouldn’t be ignored :)
14:17:09 <armax> regXboi: thanks
14:17:13 <regXboi> armax: yw
14:17:30 <armax> garyk1: I think the proposal in the table is to prevent such scenarios from occurring in the first place
14:17:43 <armax> garyk1: but I’ll have to digest more what the patch is dicussing
14:17:47 <armax> proposing
14:18:28 <garyk1> k
14:19:19 <armax> ok, let’s wrap up this section with two latest announcements/reminders
14:20:14 <armax> we started a thread to discuss the Neutron and its evolution
14:20:15 <armax> http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html
14:20:19 <armax> #link   http://lists.openstack.org/pipermail/openstack-dev/2015-December/080865.html
14:20:31 <armax> you’re welcome to share the opinion on the ML
14:20:38 <armax> and
14:20:43 <armax> this week is M-1 week
14:20:59 <ihrachys> the 'move most RFEs to M2' week
14:21:01 <armax> so we’ll cut the milestone sometime mid-week, gate permitting
14:21:06 <armax> ihrachys: yes
14:21:15 <armax> there are a few things in flight that are likely to be complete by M-1
14:21:24 <armax> whoever is assigned here:
14:21:29 <armax> #link https://blueprints.launchpad.net/neutron/mitaka/+assignments
14:21:41 <armax> should know what can wrap up in the next day or two
14:22:01 <armax> especially for those that were Liberty backlog items
14:22:13 <armax> this link brings me to the section of the meeting
14:22:14 <armax> which
14:22:15 <armax> is
14:22:18 <armax> …
14:22:20 <armax> dougwig: wait for it
14:22:26 <regXboi> the gate?
14:22:27 <regXboi> :0
14:22:31 <armax> #topic Blueprints
14:22:53 <armax> #link https://launchpad.net/neutron/+milestone/mitaka-1
14:23:30 <armax> right now we are at 30-odd blueprints and 20-odd RFE
14:23:55 <ihrachys> I know three we can safely move to M2
14:24:05 <pc_m> armax: Are there any that are not odd?
14:24:07 <pc_m> :)
14:24:17 <armax> ihrachys: for everything that has not been marked complete, I’ll move to M2
14:24:22 * regXboi listens for the rim shot
14:24:29 <armax> pc_m: I am sure there are
14:24:32 <armax> haleyb: ping
14:24:58 <haleyb> armax: pong
14:25:22 * haleyb knows the question...
14:25:34 <armax> haleyb: well, it’s more of a stamtenet
14:25:43 <armax> HenryG is going to help you with https://blueprints.launchpad.net/neutron/+spec/get-me-a-network
14:25:59 <amotoki_> sorry for late
14:26:00 <Sam-I-Am> also one that needs some docs
14:26:24 <haleyb> yes, he pinged me last week, i will follow up with him today
14:26:26 <armax> I believe that HenryG has cycles to take over some of the work that you started
14:26:38 <kevinbenton> Sam-I-Am: which one needs docs?
14:26:42 <armax> so perhaps you may want to switch roles on the spec
14:26:46 <Sam-I-Am> get-me-a-network
14:26:51 <armax> him being the assignee and you becoming the approver
14:27:06 <Sam-I-Am> at least make sure we're tracking them
14:27:07 <armax> but more eyes on the efforts are always welcome
14:27:11 <kevinbenton> Sam-I-Am: it doesn't exist yet though
14:27:12 <armax> but please not everyone at once
14:27:15 <kevinbenton> Sam-I-Am: ah
14:27:23 <armax> let’s not smother our two beloved developers
14:27:38 <haleyb> armax: i think HenryG can definitely add some momentum
14:27:53 <armax> that’s the hope
14:28:08 <armax> ihrachys: this one
14:28:10 <armax> #link https://blueprints.launchpad.net/neutron/+spec/l2-api-extensions
14:28:14 <armax> doesn’t have an approver
14:28:20 <ihrachys> armax: thanks for getting it targeted
14:28:21 <armax> do you have anyone in mind that can help you with?
14:28:31 <ihrachys> armax: rossella maybe?
14:28:47 <rossella_s> armax, ihrachys I was going to volunteer, you were faster ;)
14:29:00 <armax> rossella_s: if rossella_s can take it, let’s do it
14:29:16 <ajo> I will track it too, it seems that QoS / DSCP is going to need it.
14:29:23 <ajo> rossella_s++
14:29:28 <ihrachys> I just read your mind and decided to be quicker than you type. rossella_s, thanks.
14:29:39 <ihrachys> yeah, it turned out it's a blocker for QoS DSCP
14:29:46 <rossella_s> I am happy to help
14:29:49 <armax> dasm: ping
14:29:58 <armax> last time or so we talked about
14:29:59 <armax> #link https://blueprints.launchpad.net/neutron/+spec/rename-tenant-to-project
14:30:01 <dasm> armax: pong
14:30:03 <ajo> QoS OVS/DSCP specifically, other implementations may not need any integration back to the L2 agent (may be LinuxBridge)
14:30:05 <rossella_s> ajo you are welcome too if you want to join the effort
14:30:09 <armax> I wonder if you had given it any thought
14:30:24 <dasm> yeah. basically API seems to be pretty straight forward
14:30:39 <dasm> but for everything else.. we have about 1.6k places where tenant_id is used
14:30:50 <armax> fo you have anything in writing that is worth sharing?
14:31:17 <dasm> yesterday started spec. didn't have time to wrap it up and send to review
14:31:20 <dasm> still working on it
14:31:39 <kevinbenton> even API will be a bit annoying because we have to support filtering and policy on both
14:31:41 <dasm> but i see it as (at least) two-step process.
14:31:47 <dasm> kevinbenton: true
14:31:58 <armax> dasm: ok thanks for the effort
14:32:23 <armax> dasm: so let’s give you more time and we’ll figure out who can help you on reviewing the code etc
14:32:23 <dasm> armax: np. i'll send spec + probably some ML info about it.
14:32:34 <dasm> armax: +1
14:33:10 <Sam-I-Am> plenty of docs probably need changing too
14:33:29 <Sam-I-Am> i think the networking guide already uses project, but most of the earlier docs do not
14:33:46 <dasm> one thing i'm wondering is support for all external projects.
14:33:57 <dasm> i do not know how it will interfere with others
14:34:19 <dasm> "external" i mean: all drivers, etc.
14:34:20 <armax> dasm: let’s take this offline, but the objective is that it would not
14:34:26 <armax> #topic Bugs
14:34:40 <armax> rossella_s: you’re up
14:34:44 <rossella_s> yep
14:34:49 <armax> this was also a semi-quite week I noticed
14:34:53 <rossella_s> so this week was quite
14:35:16 <rossella_s> nothing to highlight apart from the lbaas thing
14:35:35 <ihrachys> which thing?
14:35:39 <armax> pep8?
14:35:42 <rossella_s> yep
14:35:57 <pc_m> armax: For pinning do we need to do this for Juno?
14:36:13 <armax> ok, so it’s either that we’re become rock solid, people have given up reporting burning issues?
14:36:18 <pc_m> armax: Looks like Kilo pinning patch is working. Juno has issues.
14:36:27 <ihrachys> Juno is dead, we should dig it deep and forget.
14:36:43 <rossella_s> something worth noticing is that there were changes in the DocImpact flag. Now if a neutron commit has a DocImpact flag the bug is filed to Neutron directly, no more to the doc team. I was confused when I found the first doc bug. More info here http://lists.openstack.org/pipermail/openstack-dev/2015-November/080294.html
14:36:55 <Sam-I-Am> yep
14:37:01 <Sam-I-Am> trying to fix the docs problem
14:37:02 <armax> rossella_s: good point, I noticed it too
14:37:12 <ajo> ihrachys , may be we can put some roses on the gravestone
14:37:36 <ajo> for our long loved june... ;)
14:38:16 <Sam-I-Am> docimpact changes things a bit
14:38:26 <armax> rossella_s: anything else?
14:38:40 <armax> we have dougwig as deputy for next week
14:38:47 <armax> any taker for the after that?
14:39:04 <armax> and please, pretty please…do not rush at all once to get tht eweek of christmas
14:39:06 <armax> :)
14:39:06 <mestery> armax: Has everyone done it at least once?
14:39:08 <rossella_s> armax there's a proposal upstream to use a special tag for bugs for new contributors http://lists.openstack.org/pipermail/openstack-dev/2015-November/080482.html
14:39:12 <mestery> armax: You should know the answer to that
14:39:20 <garyk1> i can take the week of xmas
14:39:32 <amotoki_> the week of Dec 7?
14:39:35 * dougwig is quivering in anticipation.
14:39:47 <HenryG> I can do it after dougwig
14:40:02 <mestery> Did I scare armax?
14:40:16 <kevinbenton> then i can go after HenryG
14:40:22 <armax> rossella_s: ok, I’ll read through, but we do have the low-hanging-fruit tag in Neutron bugs for some time now
14:40:35 <armax> ok, so HenryG goes next
14:40:50 <kevinbenton> dougwig, HenryG, kevinbenton, garyk1 and we have Dec covered!
14:40:51 <armax> garyk1: you did it once already, let’s give someone else the opportunity to step up
14:40:52 <dougwig> when i was a newbie, low-hanging-fruit was useless, btw. but that's a tangent.
14:40:59 <rossella_s> armax, yes it's just a proposal, it's still being discussed. I can watch it and report if any action from us is needed
14:41:17 <kevinbenton> dougwig: take your paint elsewhere! :)
14:41:24 <Sam-I-Am> the bug itself might be easy to fix - its the process thats more complicated
14:41:27 <mhickey> dougwig: I agree
14:41:40 <armax> dougwig: I never remember you coming to me and bitch about it thought
14:41:45 <rossella_s> dougwig, that's what the proposal tries to fix
14:42:06 <dougwig> armax: i was a newbie, how would i know who to complain to?
14:42:07 <armax> rossella_s: ok, so the thread is deflinitely worth reading
14:42:18 <rossella_s> I didn't want to start a discussion here, let's discuss using the thread then :)
14:42:28 <armax> dougwig: aw
14:42:55 <armax> next section up
14:42:57 <armax> #topic Docs
14:43:07 <Sam-I-Am> yay docs
14:43:10 <armax> emagana or edgar doesn’t seem to be here
14:43:15 <armax> Sam-I-Am: yo
14:43:21 <armax> anything worth sharing?
14:43:39 <Sam-I-Am> sure. docs spec for ovn in the networking guide was approved.
14:43:59 <Sam-I-Am> #link http://specs.openstack.org/openstack/docs-specs/specs/mitaka/networkguide-ovn.html
14:44:08 <Sam-I-Am> now just to find time for adding content
14:44:24 <Sam-I-Am> edgar is supposedly restarting the networking guide meeting this or next week
14:44:29 <Sam-I-Am> the times are a little sketchy still
14:44:59 <Sam-I-Am> when that happens, we're going to discuss how to improve the scenarios in the networking guide (mostly around how to make it possible to connect VMs to ext/public networks for all cases)
14:45:09 <armax> Sam-I-Am: how do I land on the OVN spec site?
14:45:22 <armax> Sam-I-Am: from http://specs.openstack.org/ I mean
14:45:55 <Sam-I-Am> well, the neutron specs are here - http://specs.openstack.org/openstack/neutron-specs/
14:46:11 <Sam-I-Am> i dont see ovn stuff there
14:46:24 <russellb> there is no ovn specs site
14:46:34 <armax> well, that’s a docs spec as far as I can tell
14:46:38 <salv-orlando> I don't think ovn specs get submitted there
14:46:51 <russellb> the doc spec is what Sam-I-Am was reporting on
14:47:23 <salv-orlando> ans should there be a neutron counterpart to it? I don't think so but I know nothing about this.
14:47:24 <Sam-I-Am> the key here is trying to get usable docs before a large feature becomes available
14:47:39 <armax> sorry, let me rephrase
14:48:00 <armax> the spec states: Add OVN content to the networking guide in coordination with the development process
14:48:18 <russellb> add content about features as they become available?
14:48:31 <russellb> words are hard
14:48:34 <armax> how is someone going to access this content
14:48:38 <Sam-I-Am> yeah, they are hard :)
14:48:44 <russellb> the networking guide
14:49:27 <armax> http://docs.openstack.org/networking-guide/
14:49:28 <Sam-I-Am> devs+docs people munge content from a variety of sources into official docs as it becomes available
14:49:32 <armax> yes but where!
14:49:35 <armax> never mind
14:49:37 <armax> let’s move on
14:49:51 <armax> #topic Open Discussion
14:49:59 <salv-orlando> I think Sam-I-Am was just looking for a place for said content in neutron-specs
14:50:09 <Sam-I-Am> armax: i havent figured out where the content goes in that guide yet
14:50:23 <ihrachys> I had something on tempest gating for qos
14:50:30 <ihrachys> armax: ping me when slot is up^
14:50:44 <armax> ihrachys: go ahead
14:50:48 <gsagie> Sam-I-Am : i think what armax is wondering, and so am i, where in this guide do you have a section for the various different backends, or OVN is going to be the first one besides the reference implementation (OVS) ?
14:51:00 <ihrachys> ok, so we are looking at getting qos tempest scenarios in gate
14:51:13 <ihrachys> and we have some patches to add new job with qos enabled: https://review.openstack.org/#/q/status:open+branch:master+topic:neutron-tempest-gate-hook,n,z
14:51:25 <ihrachys> the question that amuller asked me lately is why separate job
14:51:38 <ihrachys> maybe we want to have it in existing jobs?
14:51:46 <amuller> Tiny bit of context: The Neutron API job is running QoS tests, Ihar is talking about Tempest scenario tests right now
14:51:54 <Sam-I-Am> gsagie: the guide covers linuxbridge and conventional ovs now. ovn will be added to that list either as something that uses ovs, or completely new mechanism because it deprecates the conventional l3 and dhcp agents
14:51:56 <ihrachys> the problem with that is that infra does not allow to use devstack plugins in integrated jobs
14:52:10 <ihrachys> so then we would need to move devstack plugin that currently configures qos into devstack repo
14:52:23 <ihrachys> which is fine for me, but we got some resistance in the past against doing it
14:52:40 <armax> ihrachys: no, I believe we should be able to keep the qos stuff in neutron
14:52:48 <gsagie> Sam-I-Am : and if i or anyone else would like to add documentation for any other backend solution, is that possible? if yes, would love if you can elaborate how
14:53:03 <amuller> armax: The question is how do we do that but not create a new job for 'advanced configurations', first one being QoS
14:53:07 <ihrachys> or maybe we want to have some kind of 'advanced' job that will enable all the random things we may want to test out of integrated
14:53:09 <dougwig> this review is also related to the greater issue here, btw: https://review.openstack.org/#/c/221143/
14:53:12 <hichihara> I agree with armax. devstack don't have qos configure
14:53:13 <armax> ihrachys: I wonder if mordred had a chance to review the latest comment/question posted on https://review.openstack.org/#/c/247697/
14:53:19 <ajo> the scenario tests are important not just to validate our behaviour but to validate other vendor plugins behaviour when implementing QoS
14:53:32 <salv-orlando> fwiw I too do not thing QoS is of specific interest for the integrated gate
14:53:55 <dougwig> there is also armax's idea of putting the new dsvm jobs into the post-merge queue instead of check/gate
14:54:10 <armax> I have a draft mail to propose a solution about this
14:54:13 <armax> that’s long overdue
14:54:25 <armax> if nothing distracts me, I shall be able to send it out today
14:54:33 * mordred goes to look
14:54:43 <Sam-I-Am> gsagie: right now the guide supports reference arch (read: non-vendor) backends, so i'd need to know what you were thinking.
14:54:51 <salv-orlando> ajo: what you say make sense - but as a vendor I can ran those tests even if they're not part of the integrated way. As long as you write them enough black-ish that I can use them with my backend
14:54:57 <ihrachys> so whatever works for you folks. I am good either way.
14:54:58 <mordred> oh! whoops. removing -2 now
14:55:07 <amuller> armax: so no problem with another new job that will run on every patch?
14:55:23 <mordred> done - thanks!
14:55:23 <russellb> Sam-I-Am: "non-vendor" is a complicated line to draw :-)
14:55:28 <amuller> sorry, every patchset
14:55:37 <armax> mordred: thanks for keeping us in check!
14:55:46 <armax> amuller: it depends
14:55:47 <sc68cal> I don't think the networking guide benefits from having 10+ backends
14:55:58 <ajo> salv-orlando , it could be available and disabled by default in config, if that's what you mean, true
14:55:58 <gsagie> Sam-I-Am: if you allow OVN to have docs there then you should allow it for any other Open Source project (and in my mind also non Open Source ones)
14:56:05 <armax> I am getting lost
14:56:06 <salv-orlando> the "networking encyclopedia"
14:56:11 <armax> people are still talking about docs
14:56:16 <ihrachys> armax: maybe having a single job for advanced stuff? qos, flavors, ponnies
14:56:17 <ajo> ':)
14:56:23 <armax> a single job for docs?
14:56:29 <armax> ihrachys: :)
14:56:39 <armax> or a doc to rule them all?
14:56:47 <ajo> both.. :)
14:56:54 <salv-orlando> unicorns. I want unicorns too.
14:57:06 <ajo> salv-orlando : not without rainbows
14:57:06 <Sam-I-Am> what about rainbows?
14:57:07 <ihrachys> salv-orlando: I will put it into todo list for Apr 1
14:57:23 <kevinbenton> russellb: right. especially when a lot of the vendor plugins are also open source ...
14:57:28 <russellb> yep
14:57:31 <dougwig> oh jeez, this early meeting gets off the rails fast.
14:57:41 <armax> amuller, ihrachys: let’s make sure we make progress on that topic you raised this week
14:57:41 <kevinbenton> dougwig: just wait until the one after this! :)
14:57:49 <armax> I’ll give you guys 3 minutes back
14:57:51 <armax> #endmeeting