Friday, 2019-07-26

*** jamesmcarthur has joined #openstack-meeting00:03
*** mattw4 has quit IRC00:03
*** jamesmcarthur has quit IRC00:06
*** jamesmcarthur has joined #openstack-meeting00:06
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:15
*** gyee has quit IRC00:19
*** brinzhang_ has quit IRC00:38
*** brinzhang_ has joined #openstack-meeting00:39
*** igordc has quit IRC00:45
*** brinzhang has quit IRC00:47
*** brinzhang has joined #openstack-meeting00:47
*** brinzhang has quit IRC00:51
*** brinzhang_ has quit IRC00:52
*** yamamoto has joined #openstack-meeting00:52
*** ricolin has joined #openstack-meeting00:56
*** raildo has quit IRC01:10
*** baojg has quit IRC01:22
*** diablo_rojo has quit IRC01:27
*** jamesmcarthur has quit IRC01:30
*** mhen has quit IRC01:39
*** boxiang_ has quit IRC01:40
*** yaawang has quit IRC01:44
*** yaawang has joined #openstack-meeting01:44
*** brinzhang_ has joined #openstack-meeting01:48
*** brinzhang has joined #openstack-meeting01:48
*** ekcs has quit IRC01:55
*** tinwood has quit IRC02:10
*** slaweq has joined #openstack-meeting02:11
*** tinwood has joined #openstack-meeting02:12
*** brinzhang_ has quit IRC02:14
*** brinzhang has quit IRC02:14
*** brinzhang has joined #openstack-meeting02:14
*** brinzhang_ has joined #openstack-meeting02:14
*** slaweq has quit IRC02:16
*** bobh has joined #openstack-meeting02:22
*** whoami-rajat has joined #openstack-meeting02:26
*** bobh has quit IRC02:36
*** yamamoto has quit IRC02:36
*** baojg has joined #openstack-meeting02:40
*** yamamoto has joined #openstack-meeting02:50
*** qinhaizhong has joined #openstack-meeting02:53
*** cheng1 has joined #openstack-meeting02:54
*** jamesmcarthur has joined #openstack-meeting02:59
*** EmilienM|pto is now known as EmilienM03:01
*** _hemna has joined #openstack-meeting03:02
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:15
*** psachin has joined #openstack-meeting03:22
*** psachin has quit IRC03:23
*** _hemna has quit IRC03:25
*** psachin has joined #openstack-meeting03:26
*** artom has quit IRC03:27
*** dviroel has quit IRC03:29
*** baojg has quit IRC03:34
*** baojg has joined #openstack-meeting03:34
*** diablo_rojo has joined #openstack-meeting03:43
*** Luzi has joined #openstack-meeting03:48
*** ykatabam has quit IRC03:55
*** ekcs has joined #openstack-meeting03:58
*** akhil_jain has joined #openstack-meeting04:00
*** ykatabam has joined #openstack-meeting04:00
ekcs#startmeeting congressteammeeting04:01
openstackMeeting started Fri Jul 26 04:01:09 2019 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: congressteammeeting)"04:01
*** ykatabam has quit IRC04:01
openstackThe meeting name has been set to 'congressteammeeting'04:01
ekcshello. topics kept here as usual. feel free to add yours! https://etherpad.openstack.org/p/congress-meeting-topics04:01
*** ykatabam has joined #openstack-meeting04:01
akhil_jainekcs: hi04:01
ekcshi akhil_jain ! how’s it been?04:01
akhil_jainvery much busy days04:02
akhil_jainsorry for long un-announced inactivity04:02
akhil_jaini have been relocating to other state, with new job in IBM04:03
ekcshaha got it. hope it’s been good though!04:03
ekcsoh wait new employer?04:03
akhil_jainyup04:03
ekcsoh wow! congrats hope it’s a happy move!04:04
akhil_jainnew role as well(will be more on K8, terraform side), but will try my best with activity here04:04
akhil_jainoh yes thanks, missing old job as well enjoying new one04:05
ekcsvery exciting! hope to learn more from you on those topics =)04:05
*** ykatabam has quit IRC04:05
*** imsurit has joined #openstack-meeting04:05
akhil_jainyes sure04:06
ekcsI’ve been pulled away by stuff too. been bogged down with vmware internal work past few weeks. definitely looking forward to refocusing on congress though.04:07
ekcs#topic summit presentations04:07
*** openstack changes topic to "summit presentations (Meeting topic: congressteammeeting)"04:07
akhil_jainis result out?04:08
ekcswell the only topic I have now is just a update that I submitted a talk for using congress with monasca analytics to do predictive fault management.04:08
ekcsresult not out yet.04:08
akhil_jainoh ok04:09
ekcsI found one of the main contributors to monasca analytics with an interest in the area. pretty interesting work but not sure if it’ll be accepted or not.04:09
ekcsI didn’t get to add you at the submission but thought we could add you after. though not sure if you have time for that now. we can talk about if offline.04:10
ekcsoh I guess the voting is open now!04:11
*** slaweq has joined #openstack-meeting04:11
ekcsoh nvm it’s closed now.04:11
akhil_jainyes will be bit busy with catching up with new role here04:11
akhil_jainthanks for considering04:11
ekcsok I don’t have anything else for today. very nice to catch up and hear the exciting news though!04:12
akhil_jainhaha, yes that great.04:13
akhil_jainnothing else from my side04:13
*** slaweq has quit IRC04:15
ekcsalright let’s end the meeting here than!04:16
ekcshave a great weekend!04:16
ekcs#endmeeting04:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"04:16
openstackMeeting ended Fri Jul 26 04:16:15 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)04:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2019/congressteammeeting.2019-07-26-04.01.html04:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2019/congressteammeeting.2019-07-26-04.01.txt04:16
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2019/congressteammeeting.2019-07-26-04.01.log.html04:16
*** apetrich has quit IRC04:20
*** yaawang has quit IRC04:24
*** yaawang has joined #openstack-meeting04:24
*** jamesmcarthur has quit IRC04:32
*** yamamoto_ has joined #openstack-meeting04:46
*** links has joined #openstack-meeting04:49
*** links is now known as Jaison|interview04:49
*** Jaison|interview is now known as links04:49
*** yamamoto has quit IRC04:50
*** diablo_rojo has quit IRC04:56
*** jbadiapa has quit IRC05:02
*** ekcs has quit IRC05:05
*** armax has quit IRC05:16
*** qinhaizhong has quit IRC05:35
*** qinhaizhong has joined #openstack-meeting05:36
*** jraju__ has joined #openstack-meeting05:40
*** links has quit IRC05:40
*** rtjure has joined #openstack-meeting05:42
*** yamamoto_ has quit IRC05:43
*** zbr has joined #openstack-meeting05:44
*** jamesmcarthur has joined #openstack-meeting05:45
*** yamamoto has joined #openstack-meeting05:56
*** rcernin has quit IRC06:08
*** slaweq has joined #openstack-meeting06:11
*** qinhaizhong has quit IRC06:11
*** qinhaizhong01 has joined #openstack-meeting06:11
*** apetrich has joined #openstack-meeting06:15
*** slaweq has quit IRC06:16
*** yamamoto_ has joined #openstack-meeting06:19
*** yamamoto has quit IRC06:21
*** jbadiapa has joined #openstack-meeting06:24
*** Lucas_Gray has quit IRC06:26
*** jamesmcarthur has quit IRC06:33
*** tesseract has joined #openstack-meeting07:03
*** brinzhang_ has quit IRC07:03
*** brinzhang has quit IRC07:03
*** brinzhang has joined #openstack-meeting07:04
*** brinzhang has quit IRC07:04
*** qinhaizhong has joined #openstack-meeting07:05
*** brinzhang has joined #openstack-meeting07:06
*** slaweq has joined #openstack-meeting07:06
*** qinhaizhong01 has quit IRC07:08
*** qinhaizhong01 has joined #openstack-meeting07:14
*** qinhaizhong has quit IRC07:18
*** akhil_jain has quit IRC07:19
*** qinhaizhong01 has quit IRC07:25
*** qinhaizhong has joined #openstack-meeting07:25
*** kopecmartin|off is now known as kopecmartin07:26
*** brault has joined #openstack-meeting07:35
*** qinhaizhong01 has joined #openstack-meeting07:44
*** pcaruana has joined #openstack-meeting07:44
*** qinhaizhong01 has quit IRC07:45
*** cheng1 has quit IRC07:46
*** qinhaizhong01 has joined #openstack-meeting07:46
*** cheng1 has joined #openstack-meeting07:46
*** qinhaizhong has quit IRC07:47
*** qinhaizhong01 has quit IRC07:48
*** qinhaizhong01 has joined #openstack-meeting07:48
*** qinhaizhong01 has quit IRC07:49
*** qinhaizhong01 has joined #openstack-meeting07:50
*** qinhaizhong01 has quit IRC07:51
*** brinzhang_ has joined #openstack-meeting07:55
*** ralonsoh has joined #openstack-meeting07:56
*** brinzhang has quit IRC07:58
*** ttsiouts has joined #openstack-meeting08:03
*** brinzhang_ has quit IRC08:04
*** yamamoto_ has quit IRC08:05
*** brinzhang has joined #openstack-meeting08:06
*** tssurya has joined #openstack-meeting08:08
*** yamamoto has joined #openstack-meeting08:13
*** ricolin has quit IRC08:19
*** tssurya has quit IRC08:23
*** dmacpher has joined #openstack-meeting08:52
*** yaawang has quit IRC09:08
*** yaawang has joined #openstack-meeting09:10
*** e0ne has joined #openstack-meeting09:16
*** jbadiapa has quit IRC09:39
*** ttsiouts has quit IRC09:46
*** ttsiouts has joined #openstack-meeting09:47
*** ttsiouts has quit IRC09:51
*** priteau has joined #openstack-meeting09:53
*** brinzhang_ has joined #openstack-meeting09:54
*** brinzhang has quit IRC09:58
*** ttsiouts has joined #openstack-meeting10:01
*** brinzhang has joined #openstack-meeting10:08
*** yamamoto has quit IRC10:10
*** brinzhang_ has quit IRC10:12
*** carloss has joined #openstack-meeting10:14
*** yamamoto has joined #openstack-meeting10:14
*** yamamoto has quit IRC10:15
*** ttsiouts has quit IRC10:25
*** ttsiouts has joined #openstack-meeting10:25
*** tdasilva has quit IRC10:29
*** ttsiouts has quit IRC10:30
*** brinzhang has quit IRC10:32
*** brtknr has quit IRC10:36
*** brtknr has joined #openstack-meeting10:37
*** psachin has quit IRC10:38
*** Luzi has quit IRC10:44
*** yamamoto has joined #openstack-meeting10:45
*** brtknr has quit IRC11:02
*** psachin has joined #openstack-meeting11:02
*** brtknr has joined #openstack-meeting11:02
*** brtknr has quit IRC11:02
*** brtknr has joined #openstack-meeting11:03
*** brtknr has quit IRC11:06
*** ttsiouts has joined #openstack-meeting11:06
*** tssurya has joined #openstack-meeting11:08
*** brtknr has joined #openstack-meeting11:10
*** EmilienM has quit IRC11:27
*** EmilienM has joined #openstack-meeting11:28
*** jbadiapa has joined #openstack-meeting11:37
*** imsurit has quit IRC11:42
*** yamamoto has quit IRC11:51
*** larainema has joined #openstack-meeting11:51
*** irclogbot_2 has quit IRC11:53
*** yamamoto has joined #openstack-meeting11:54
*** irclogbot_2 has joined #openstack-meeting11:55
*** dviroel has joined #openstack-meeting12:03
*** artom has joined #openstack-meeting12:04
*** jbadiapa has quit IRC12:08
*** jbadiapa has joined #openstack-meeting12:08
*** raildo has joined #openstack-meeting12:13
*** yamamoto has quit IRC12:34
*** yamamoto has joined #openstack-meeting12:38
*** Luzi has joined #openstack-meeting12:47
*** mriedem has joined #openstack-meeting12:53
*** ttsiouts has quit IRC12:56
*** yamamoto has quit IRC12:57
*** brtknr has quit IRC13:01
*** brtknr has joined #openstack-meeting13:03
*** brtknr has quit IRC13:05
*** brtknr has joined #openstack-meeting13:05
*** brtknr has quit IRC13:05
*** brtknr has joined #openstack-meeting13:06
*** brtknr has quit IRC13:06
*** brtknr has joined #openstack-meeting13:06
*** artom has quit IRC13:09
*** artom has joined #openstack-meeting13:09
*** yaawang has quit IRC13:11
*** yaawang has joined #openstack-meeting13:12
*** ttsiouts has joined #openstack-meeting13:14
*** b3nt_pin is now known as beagles13:15
*** jawad_axd has joined #openstack-meeting13:24
*** artom has quit IRC13:26
*** smcginnis has joined #openstack-meeting13:29
*** yamamoto has joined #openstack-meeting13:31
*** brinzhang has joined #openstack-meeting13:36
*** jawad_axd has quit IRC13:37
*** yamamoto has quit IRC13:45
*** yamamoto has joined #openstack-meeting13:48
*** liuyulong has joined #openstack-meeting13:55
*** mlavalle has joined #openstack-meeting13:59
mlavalle#startmeeting neutron_drivers14:00
openstackMeeting started Fri Jul 26 14:00:10 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
slaweqhi14:00
mlavallehey14:00
yamamotohi14:00
amotokihi14:00
ralonsohhi14:00
liuyulonghello14:00
*** gagehugo has left #openstack-meeting14:01
mlavallehaleyb|away: is off on vacation, so we are good to go14:01
mlavalle#topic RFEs14:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:01
mlavalleGood to see yamamoto is recovered from his surgery. \o/14:02
amotoki\o/14:02
yamamotothank you14:02
njohnstono/14:02
*** eharney has joined #openstack-meeting14:02
mlavalleThis is the RFE to be discussed today: https://bugs.launchpad.net/neutron/+bug/183683414:02
openstackLaunchpad bug 1836834 in neutron "[RFE] introduce distributed locks to ipam" [Wishlist,Confirmed] - Assigned to qinhaizhong (qinhaizhong)14:02
mlavalleand its associated spec: https://review.opendev.org/#/c/657221/14:03
brinzhangthis spec already +2, maybe need some others propose changes or W+114:06
njohnstonI will say that the spec is lacking a bit of detail on the basic operation of this proposal.  For example, we are implementing distributed locks, but what precisely is getting locked?  If a process fails to release a lock, how is that sensed and remedied?14:06
slaweqfor me it looks good as separate driver14:06
*** radeks has joined #openstack-meeting14:07
njohnstonIs the lock on a per-subnet basis or is it for all IPAM IP allocation?  Is there a fallback mode if the backend tooz points to does not respond in a timely manner?14:07
brinzhangI think these implementations will be reflected in the code logic, this is a new driver that you can configure to use.14:07
njohnstonbrinzhang: I understand, and there are many details that will be determined at implementation.  But the spec says "We will fix IP allocation conflicts by using locks" without saying *how* using locks fixes IP allocation conflicts.14:09
liuyulongbrinzhang, you may give us some brief summary about the implementation. : ) njohnston's concern is worth clarifying.14:10
brinzhangBased on subnet-id + ip14:10
ralonsohI agree with njohnston . We can be relaxed with the spec description, but something more detailed could be defined in the document14:10
amotokinjohnston: good point. the spec should clarify a basic approach and how the problem can be solved.14:11
brinzhangnjohnston: qinhaizhong will be attendance, wait please.14:11
*** qinhaizhong has joined #openstack-meeting14:12
mlavallethe other question is, how much experience does the team proposing this spec have with tooz? I mean, have you solved previous scale up problems using it?14:12
slaweqI was thinking about this spec more like some overall description of problem and wanted to see implementation details as PoC and to check if it will really improve IPAM, but I can also wait for some more detailed spec14:13
slaweqmlavalle: I don't have much experience with tooz but I know that when lucasgomes implemented some "hash ring" mechanism in networking-ovn using tooz, it speed up process of creating trunk subports about 10 times or something like that, so it may help with such problems for sure14:14
njohnstonI don't think there has to be a deep deep description, just a few sentences laying out the approach so it's transparent to the community why this is a superior approach14:15
liuyulongMoreover, this will introduce a new lock store? What if the lock DB is down? No port can be created successfully?14:15
mlavalleI am not doubting tooz. I just want evidence that it has chances to help indeed14:15
mlavalleand the ovn experience you mention is a good data point. thanks for mentioning it14:16
ralonsohliuyulong, I don't think this rely on the same DB, but I'm not sure14:16
slaweqmlavalle: I understand, and IMO best evidence would be if we would have PoC and could compare it with current driver :)14:16
ralonsohslaweq, agree14:17
brinzhangslaweq: I agree.14:17
*** qinhaizhong01 has joined #openstack-meeting14:17
liuyulongralonsoh, tooz can use various store drivers, like redis, mysql and so on.14:17
ralonsoh(and a more detailed description in the spec)14:17
njohnstonIf the authors wanted to work out the details in a POC and then update the spec with a concise description of the approach once they have worked it out, I think that would allay my concerns about transparency14:17
ralonsohliuyulong, I know, just guessing14:17
slaweqnjohnston++14:18
amotokinjohnston: agree14:19
*** qinhaizhong has quit IRC14:19
brinzhangqinhaizhong01: njohnston: I was thinking about this spec more like some overall description of problem and wanted to see implementation details as PoC and to check if it will really improve IPAM, but I can also wait for some more detailed spec14:20
brinzhangmlavalle: I don't have much experience with tooz but I know that when lucasgomes implemented some "hash ring" mechanism in networking-ovn using tooz, it speed up process of creating trunk subports about 10 times or something like that, so it may help with such problems for sure14:20
mlavallePerformance and scalibility improvement is very important for Neutro14:21
mlavalleNeutron14:21
qinhaizhong01Based on the original _generate_ips algorithm, this method will be reimplemented. The ips calculated for _generate_ips will be "ip+subnet_id" as the key plus the distributed lock.14:21
mlavalleSo I like in principle this proposal, even in an exploratory fashion14:22
liuyulongIntroduce such centralized components, always increase the deployment difficulties of operation and maintenance. (I'm not saying this is not acceptable, just some thoughts.)14:22
*** psachin has quit IRC14:22
amotokiI would like to see why and how a distributed lock addresses the problem in the spec.14:22
mlavallewith that in mind and seeing the feedback from the team, this is what we propose:14:23
mlavalle1) We approve the RFE today with the understanding that14:23
mlavalle2) A more detailed spec will be proposed with the feedback from the team today14:24
mlavalle3) We will see the code as a PoC. We will use the experience of the PoC to feedback on the spec if needed14:24
njohnston+114:24
mlavalle4) The code will come with Rally tests, so we can measure improvement14:25
*** enriquetaso has joined #openstack-meeting14:25
mlavalleIMO, we should welcoming experimenting14:26
mlavallewhat do others think?14:26
*** bnemec is now known as beekneemech14:26
liuyulong+114:26
amotokiit totally makes sense to me14:26
*** artom has joined #openstack-meeting14:26
slaweq+!14:26
yamamoto+114:26
slaweq+114:26
njohnstonI really like that approach14:26
brinzhang+114:26
ralonsoh+114:27
mlavallebrinzhang, qinhaizhong01: let me be clear. we are heading towards the final milestone of the cycle. And we are taking this proposal as a PoC. So the chances of this merging in TRain are rather slim. ok?14:28
mlavalleI'll take the silence as acquiescence :-)14:30
*** smrcascao has joined #openstack-meeting14:31
mlavalleI'll approve the RFE at the end of the meeting, adding the four points ^^^^ in the comments section14:31
mlavalleLet's move on then14:32
mlavalleNext one we have today is https://bugs.launchpad.net/neutron/+bug/183784714:32
openstackLaunchpad bug 1837847 in neutron "[RFE] neutron-vpnaas OpenVPN driver" [Undecided,New]14:32
mlavalleI am not sure we should discuss it today. I don't understand all the details in this proposal14:33
*** dmacpher has quit IRC14:33
mlavalleI am bringing it up today with the hope that amotoki and yamamoto who know more about VPN could comment on it and help us triage it14:33
brinzhangmlavalle: where let you confusing?14:33
qinhaizhong01What details?14:34
mlavalleI am talking now about another RFE, not yours brinzhang ann qinhaizhong0114:34
*** ricolin has joined #openstack-meeting14:36
amotokiI haven't looked at the OpenVPN driver RFE...14:36
slaweqI'm not vpnaas expert so it's hard for me to talk about it14:36
njohnstonWhen he says his use case is to have broadcast/multicast communication with the instances, does that mean the vpn IP needs to be within the same L2 domain?14:36
mlavallegood question to ask in the RFE14:37
njohnstonIf so, then I don't see how going through Neutron IPAM can be avoided, whether it's in a pre-reservation capacity or on-demand.14:37
* njohnston posts the question14:38
mlavalleThanks!14:38
amotokinjohnston is much faster than me.14:39
liuyulongLooks like it will involved with DHCP? A spec with some detail is needed also.14:39
amotokiAt a glance, I cannot understand that point and am thinking....14:39
amotokiliuyulong: perhaps we need to understand what is the actual problem first before a spec.14:40
liuyulongA spec always has the section "Problem Description" : )14:41
mlavalleok, let's post questions in the RFE and see if we can move it forward14:41
mlavalleanythong else we should discuss today?14:42
liuyulongI have one14:42
liuyulonghttps://bugs.launchpad.net/neutron/+bug/181788114:43
openstackLaunchpad bug 1817881 in neutron " [RFE] L3 IPs monitor/metering via current QoS functionality (tc filters)" [Wishlist,In progress] - Assigned to LIU Yulong (dragon889)14:43
liuyulongWe discussed this once in drivers meeting.14:43
liuyulongBut we have no result.14:43
*** jamesmcarthur has joined #openstack-meeting14:43
liuyulongBasicly we have a consensus is adding a new l3 agent extension.14:43
liuyulongBut it is not approved yet.14:43
slaweqone question: is it still proposal only for FIPs with QoS set?14:44
liuyulongslaweq, it relay on that, the tc statistics.14:45
slaweqcan't we use tc statistics without QoS enabled for FIP?14:46
slaweqit doesn't look like something user friendly: "do You want metering, You need to set QoS on FIP" :)14:46
liuyulongI'm not sure, but I can. Once tc filters accept 0 for rate and burst.14:46
liuyulongBut now, we may need a very large value for it as default.14:47
slaweqif we want to have metering enabled, it should be done for all FIPs/routers handled by L3 agent14:47
ralonsohslaweq, we need to measure the possible performance impact14:47
slaweqand should be independent of QoS feature14:48
ralonsohif we are adding a TC filter in a interface, without needing it, this can slow down it14:48
liuyulongBandwidth limitation and metering of public IP is a basic rule.14:48
*** rsimai has quit IRC14:49
amotokiliuyulong: do you mean all deployments should have bandwidth limitation and metering of public IPs?14:49
mlavallebut we only need the TC filter if the operator configures metering, right?14:49
mlavallein this scenario I mean14:49
ralonsohmlavalle, right now yes14:49
ralonsohsorry, we have TC filters if we ask for QoS14:49
liuyulongFYI, the discuss once: http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-03-29-14.00.log.html14:49
slaweqmlavalle: yes, and IMO it should be like that: "You want metering - You should enable metering in config file" and not "You want metering - You should enable QoS for FIP with some custom, very high value for bw limit" :)14:50
liuyulongmlavalle, yes, tc filter rule is enough. It has a accurate statistics data.14:51
mlavalleso will slaweq's point be addressed?14:51
liuyulongamotoki, no, it is not a compulsory requirements, I mean it's more like a deployment consensus.14:52
liuyulongSo, what's value will be considered as very large for filter default?14:53
liuyulong10Gpbs?14:53
liuyulong40Gbps?14:53
ralonsohConnectX-6 HCAs with 200Gbps14:54
ralonsohfrom the Mellanox website14:54
liuyulongHaha, It seems that there will always be higher values.14:55
*** qinhaizhong01 has quit IRC14:55
*** kopecmartin is now known as kopecmartin|off14:56
slaweqthere is spec for this, I will try to review it in next few days, will it be ok liuyulong?14:58
liuyulongslaweq, OK, let me paste it here.14:58
liuyulong#link https://review.opendev.org/#/c/658511/14:58
slaweqliuyulong: thx14:58
liuyulongTitle "14:59
liuyulongL3 agent self-service metering"14:59
mlavalleok, let's all review the spec and we start with this RFE next week14:59
slaweqmlavalle++14:59
mlavalleHave a nice weekend14:59
mlavalle#endmeeting14:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:59
openstackMeeting ended Fri Jul 26 14:59:48 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
slaweqthx, You too mlavalle14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-07-26-14.00.html14:59
ralonsohbye14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-07-26-14.00.txt14:59
amotokithanks all14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-07-26-14.00.log.html14:59
*** mlavalle has left #openstack-meeting15:05
*** yamamoto has quit IRC15:06
*** yamamoto has joined #openstack-meeting15:09
*** yamamoto has quit IRC15:10
*** jamesmcarthur has quit IRC15:17
*** jamesmcarthur has joined #openstack-meeting15:21
*** cmurphy is now known as cmorpheus15:25
*** ttsiouts has quit IRC15:27
*** ttsiouts has joined #openstack-meeting15:28
*** iyamahat has joined #openstack-meeting15:31
*** ttsiouts has quit IRC15:32
*** ttsiouts has joined #openstack-meeting15:33
*** yamamoto has joined #openstack-meeting15:35
*** jbadiapa has quit IRC15:39
*** yamamoto has quit IRC15:41
*** Luzi has quit IRC15:42
*** armax has joined #openstack-meeting15:43
*** jraju__ has quit IRC15:53
*** brinzhang has quit IRC15:55
*** eharney has quit IRC15:57
*** gyee has joined #openstack-meeting15:59
*** e0ne has quit IRC16:12
*** jamesmcarthur has quit IRC16:15
*** jamesmcarthur has joined #openstack-meeting16:16
*** ttsiouts has quit IRC16:17
*** mattw4 has joined #openstack-meeting16:17
*** ttsiouts has joined #openstack-meeting16:17
*** diablo_rojo has joined #openstack-meeting16:21
*** jamesmcarthur has quit IRC16:21
*** ttsiouts has quit IRC16:22
*** tssurya has quit IRC16:23
*** ricolin has quit IRC16:23
*** larainema has quit IRC16:25
*** enriquetaso has quit IRC16:30
*** jamesmcarthur has joined #openstack-meeting16:31
*** mriedem is now known as mriedem_lunch16:35
*** jamesmcarthur has quit IRC16:36
*** jamesmcarthur has joined #openstack-meeting16:36
*** enriquetaso has joined #openstack-meeting16:49
*** mattw4 has quit IRC16:54
*** mattw4 has joined #openstack-meeting16:58
*** eharney has joined #openstack-meeting17:01
*** jamesmcarthur has quit IRC17:08
*** bobh has joined #openstack-meeting17:23
*** bobh has quit IRC17:26
*** igordc has joined #openstack-meeting17:34
*** igordc has quit IRC17:36
*** igordc has joined #openstack-meeting17:36
*** electrofelix has quit IRC17:38
*** brault has quit IRC17:46
*** rtjure has quit IRC17:50
*** mriedem_lunch is now known as mriedem17:50
*** tesseract has quit IRC17:54
*** rtjure has joined #openstack-meeting17:56
*** chason has quit IRC17:56
*** mattw4 has quit IRC18:02
*** mattw4 has joined #openstack-meeting18:02
*** mattw4 has quit IRC18:46
*** bobh has joined #openstack-meeting18:48
*** mattw4 has joined #openstack-meeting18:51
*** bobh has quit IRC19:02
*** vishalmanchanda has quit IRC19:05
*** diablo_rojo has quit IRC19:26
*** igordc has quit IRC19:37
*** brtknr has quit IRC19:40
*** brtknr has joined #openstack-meeting19:40
*** slaweq has quit IRC19:41
*** ralonsoh has quit IRC19:55
*** igordc has joined #openstack-meeting20:10
*** slaweq has joined #openstack-meeting20:11
*** slaweq has quit IRC20:16
*** brtknr_ has joined #openstack-meeting20:20
*** brtknr has quit IRC20:22
*** priteau has quit IRC20:53
*** hemna has quit IRC20:57
*** artom has quit IRC21:06
*** beekneemech is now known as bnemec-pto21:22
*** eharney has quit IRC21:23
*** Lucas_Gray has joined #openstack-meeting21:29
*** rfolco|rover has quit IRC21:30
*** jaypipes has quit IRC21:44
*** mattw4 has quit IRC21:53
*** jamesmcarthur has joined #openstack-meeting21:55
*** brtknr_ has quit IRC22:01
*** whoami-rajat has quit IRC22:06
*** dviroel has quit IRC22:06
*** slaweq has joined #openstack-meeting22:11
*** jamesmcarthur has quit IRC22:15
*** slaweq has quit IRC22:16
*** carloss has quit IRC22:20
*** mattw4 has joined #openstack-meeting22:38
*** gyee has quit IRC22:39
*** jamesmcarthur has joined #openstack-meeting22:45
*** gyee has joined #openstack-meeting22:55
*** jamesmcarthur has quit IRC23:00
*** mriedem has quit IRC23:08
*** jamesmcarthur has joined #openstack-meeting23:10
*** slaweq has joined #openstack-meeting23:11
*** slaweq has quit IRC23:15
*** diablo_rojo has joined #openstack-meeting23:28
*** jamesmcarthur has quit IRC23:42
*** mattw4 has quit IRC23:45

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