Wednesday, 2020-02-19

*** Liang__ has joined #openstack-meeting00:04
*** igordc has quit IRC00:06
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:15
*** jmasud has quit IRC00:26
*** jmasud has joined #openstack-meeting00:28
*** maohongbo1 has joined #openstack-meeting00:31
*** maohongbo has quit IRC00:31
*** maohongbo1 is now known as maohongbo00:31
*** jmasud has quit IRC00:40
*** Liang__ has quit IRC00:46
*** Liang__ has joined #openstack-meeting00:48
*** epei has joined #openstack-meeting00:56
*** epei has quit IRC01:01
*** brinzhang has quit IRC01:02
*** brinzhang has joined #openstack-meeting01:02
*** zhangchi has joined #openstack-meeting01:06
zhangchi#startmeeting tricircle01:07
openstackMeeting started Wed Feb 19 01:07:33 2020 UTC and is due to finish in 60 minutes.  The chair is zhangchi. Information about MeetBot at http://wiki.debian.org/MeetBot.01:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.01:07
*** openstack changes topic to " (Meeting topic: tricircle)"01:07
openstackThe meeting name has been set to 'tricircle'01:07
*** slaweq has joined #openstack-meeting01:11
zhangchiMoring All Welcome to tricircle bi-weekly meeting01:11
*** slaweq has quit IRC01:15
*** jamesmcarthur has joined #openstack-meeting01:17
*** jamesmcarthur has quit IRC01:39
*** jmasud has joined #openstack-meeting01:49
*** jamesmcarthur has joined #openstack-meeting01:51
*** yamamoto has joined #openstack-meeting01:53
*** yamamoto has quit IRC01:53
zhangchi#link https://etherpad.openstack.org/p/tricircle-ussuri-plan01:55
zhangchiOther Issuses please contact my IRC01:57
zhangchi#endmeeting01:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"01:57
openstackMeeting ended Wed Feb 19 01:57:15 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)01:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tricircle/2020/tricircle.2020-02-19-01.07.html01:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tricircle/2020/tricircle.2020-02-19-01.07.txt01:57
openstackLog:            http://eavesdrop.openstack.org/meetings/tricircle/2020/tricircle.2020-02-19-01.07.log.html01:57
*** yamamoto has joined #openstack-meeting01:57
*** jamesmcarthur has quit IRC02:01
*** zhangchi has quit IRC02:02
*** slaweq has joined #openstack-meeting02:11
*** ociuhandu has joined #openstack-meeting02:13
*** yamamoto has quit IRC02:15
*** slaweq has quit IRC02:16
*** yamamoto has joined #openstack-meeting02:16
*** ociuhandu has quit IRC02:17
*** Roamer` has quit IRC02:36
*** yamamoto has quit IRC02:38
*** yamamoto has joined #openstack-meeting02:42
*** larainema has joined #openstack-meeting02:42
*** yamamoto has quit IRC02:43
*** JangwonLee_ has joined #openstack-meeting02:44
*** hyunsikyang__ has joined #openstack-meeting02:44
*** yamamoto has joined #openstack-meeting02:45
*** JangwonLee has quit IRC02:46
*** hyunsikyang has quit IRC02:46
*** jamesmcarthur has joined #openstack-meeting02:48
*** yamamoto has quit IRC02:49
*** hongbin has joined #openstack-meeting02:53
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:16
*** yamamoto has joined #openstack-meeting03:21
*** hongbin has quit IRC03:23
*** jamesmcarthur has quit IRC03:26
*** psachin has joined #openstack-meeting03:35
*** jamesmcarthur has joined #openstack-meeting03:48
*** enriquetaso has joined #openstack-meeting03:49
*** artom has quit IRC04:05
*** dmacpher has joined #openstack-meeting04:10
*** slaweq has joined #openstack-meeting04:11
*** jmasud has quit IRC04:12
*** jmasud has joined #openstack-meeting04:14
*** slaweq has quit IRC04:16
*** gyee has quit IRC04:20
*** lbragstad has quit IRC04:22
*** yamamoto has quit IRC04:36
*** enriquetaso has quit IRC04:42
*** vishalmanchanda has joined #openstack-meeting04:54
*** jamesmcarthur has quit IRC04:58
*** jamesmcarthur has joined #openstack-meeting04:59
*** macz_ has quit IRC05:00
*** masahito has joined #openstack-meeting05:03
*** yamamoto has joined #openstack-meeting05:07
*** jamesmcarthur has quit IRC05:07
*** masahito has quit IRC05:08
*** jamesmcarthur has joined #openstack-meeting05:10
*** slaweq has joined #openstack-meeting05:11
*** yamamoto has quit IRC05:12
*** yamamoto has joined #openstack-meeting05:15
*** slaweq has quit IRC05:16
*** masahito has joined #openstack-meeting05:19
*** masahito has quit IRC05:20
*** jamesmcarthur has quit IRC05:22
*** epei has joined #openstack-meeting05:22
*** masahito has joined #openstack-meeting05:25
*** epei has quit IRC05:27
*** jamesmcarthur has joined #openstack-meeting05:28
*** jamesmcarthur has quit IRC05:32
*** links has joined #openstack-meeting05:35
*** jamesmcarthur has joined #openstack-meeting06:08
*** slaweq has joined #openstack-meeting06:11
*** jamesmcarthur has quit IRC06:14
*** slaweq has quit IRC06:15
*** hongbin has joined #openstack-meeting06:23
*** hongbin has quit IRC06:28
*** jamesmcarthur has joined #openstack-meeting06:30
*** brinzhang has quit IRC06:30
*** lajoskatona has joined #openstack-meeting06:31
*** brinzhang has joined #openstack-meeting06:31
*** masahito has quit IRC06:34
*** jamesmcarthur has quit IRC06:35
*** maohongbo1 has joined #openstack-meeting06:35
*** maohongbo has quit IRC06:37
*** maohongbo1 is now known as maohongbo06:37
*** yamamoto has quit IRC06:39
*** yamamoto has joined #openstack-meeting06:41
*** lajoskatona has left #openstack-meeting06:50
*** masahito has joined #openstack-meeting06:55
*** Lucas_Gray has joined #openstack-meeting06:58
*** openstack has joined #openstack-meeting07:18
*** ChanServ sets mode: +o openstack07:18
*** Lucas_Gray has quit IRC07:20
*** openstack has joined #openstack-meeting07:42
*** ChanServ sets mode: +o openstack07:42
*** maciejjozefczyk has joined #openstack-meeting07:47
*** slaweq has joined #openstack-meeting07:51
*** Lucas_Gray has quit IRC07:55
*** Lucas_Gray has joined #openstack-meeting07:57
*** tesseract has joined #openstack-meeting08:07
*** tetsuro has joined #openstack-meeting08:12
*** jmasud has quit IRC08:13
*** tetsuro__ has joined #openstack-meeting08:13
*** jmasud has joined #openstack-meeting08:14
*** tetsuro_ has quit IRC08:14
*** tetsuro has quit IRC08:16
*** tetsuro has joined #openstack-meeting08:17
*** yamamoto has quit IRC08:18
*** tetsuro__ has quit IRC08:21
*** mattia has quit IRC08:23
*** links has quit IRC08:24
*** takamatsu has quit IRC08:27
*** maohongbo has quit IRC08:30
*** maohongbo has joined #openstack-meeting08:30
*** jamesmcarthur has joined #openstack-meeting08:31
*** viks___ has quit IRC08:34
*** arne_wiebalck has quit IRC08:36
*** jamesmcarthur has quit IRC08:36
*** vishalmanchanda has quit IRC08:36
*** arne_wiebalck has joined #openstack-meeting08:37
*** vishalmanchanda has joined #openstack-meeting08:37
*** rpittau|afk is now known as rpittau08:37
*** yamamoto has joined #openstack-meeting08:53
*** ralonsoh has joined #openstack-meeting08:54
*** yamamoto has quit IRC08:58
*** lucasagomes has joined #openstack-meeting08:58
*** Lucas_Gray has quit IRC09:00
*** dougsz has joined #openstack-meeting09:00
*** links has joined #openstack-meeting09:01
*** Lucas_Gray has joined #openstack-meeting09:07
*** ociuhandu has joined #openstack-meeting09:08
*** tetsuro_ has joined #openstack-meeting09:09
*** tetsuro has quit IRC09:09
*** viks___ has joined #openstack-meeting09:11
*** tetsuro has joined #openstack-meeting09:21
*** ociuhandu has quit IRC09:25
*** tetsuro_ has quit IRC09:25
*** ociuhandu has joined #openstack-meeting09:27
*** tetsuro has quit IRC09:27
*** masahito_ has joined #openstack-meeting09:30
*** masahito has quit IRC09:30
*** yamamoto has joined #openstack-meeting09:34
*** yamamoto has quit IRC09:37
*** e0ne has joined #openstack-meeting09:41
*** ociuhandu has quit IRC10:03
*** masahito has joined #openstack-meeting10:12
*** masahito_ has quit IRC10:12
*** masahito has quit IRC10:34
*** Lucas_Gray has quit IRC10:34
*** Lucas_Gray has joined #openstack-meeting10:38
*** yamamoto has joined #openstack-meeting10:51
*** yamamoto has quit IRC10:52
*** hyunsikyang has joined #openstack-meeting10:52
*** Lucas_Gray has quit IRC10:55
*** hyunsikyang__ has quit IRC10:55
*** hyunsikyang__ has joined #openstack-meeting10:56
*** hyunsikyang has quit IRC10:56
*** Lucas_Gray has joined #openstack-meeting10:58
*** slaweq has quit IRC11:06
*** yamamoto has joined #openstack-meeting11:09
*** slaweq has joined #openstack-meeting11:11
*** yamamoto has quit IRC11:13
*** maciejjozefczyk_ has joined #openstack-meeting11:13
*** maciejjozefczyk has quit IRC11:14
*** maciejjozefczyk_ has quit IRC11:14
*** maciejjozefczyk_ has joined #openstack-meeting11:14
*** epei has joined #openstack-meeting11:21
*** epei has quit IRC11:26
*** slaweq has quit IRC11:32
*** takamatsu has joined #openstack-meeting11:32
*** slaweq has joined #openstack-meeting11:34
*** rpittau is now known as rpittau|bbl11:40
*** raildo has joined #openstack-meeting11:42
*** yamamoto has joined #openstack-meeting11:59
*** Lucas_Gray has quit IRC12:02
*** takamatsu has quit IRC12:08
*** ociuhandu has joined #openstack-meeting12:10
*** ociuhandu has quit IRC12:11
*** jmasud has quit IRC12:11
*** ociuhandu has joined #openstack-meeting12:12
*** dmacpher has quit IRC12:12
*** dmacpher has joined #openstack-meeting12:13
*** takamatsu has joined #openstack-meeting12:13
*** jmasud has joined #openstack-meeting12:14
*** ociuhandu has quit IRC12:16
*** rfolco has joined #openstack-meeting12:18
*** Lucas_Gray has joined #openstack-meeting12:24
*** dmacpher has quit IRC12:27
*** dmacpher has joined #openstack-meeting12:27
*** rcernin has quit IRC12:37
*** rh-jelabarre has joined #openstack-meeting12:50
*** b3nt_pin has joined #openstack-meeting12:51
*** brinzhang_ has joined #openstack-meeting12:53
*** yamamoto has quit IRC12:53
*** brinzhang has quit IRC12:56
*** ysandeep is now known as ysandeep|away12:57
*** b3nt_pin is now known as beagles13:01
*** rpittau|bbl is now known as rpittau13:02
*** yamamoto has joined #openstack-meeting13:15
*** ykatabam has quit IRC13:16
*** jamesmcarthur has joined #openstack-meeting13:17
*** ociuhandu has joined #openstack-meeting13:23
*** liuyulong has joined #openstack-meeting13:29
*** jamesmcarthur has quit IRC13:36
*** enriquetaso has joined #openstack-meeting13:44
*** lbragstad has joined #openstack-meeting13:47
*** jamesmcarthur has joined #openstack-meeting13:48
*** lbragsta_ has joined #openstack-meeting13:52
*** maciejjozefczyk_ is now known as maciejjozefczyk13:52
*** lbragstad has quit IRC13:54
*** Liang__ is now known as LiangFang13:58
*** eharney has joined #openstack-meeting13:59
*** sfernand has joined #openstack-meeting14:00
*** andrebeltrami has joined #openstack-meeting14:00
liuyulong#startmeeting neutron_l314:01
openstackMeeting started Wed Feb 19 14:01:10 2020 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: neutron_l3)"14:01
openstackThe meeting name has been set to 'neutron_l3'14:01
liuyulonghi there14:01
liuyulong#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"14:01
liuyulong#link http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-02-17-21.00.log.html14:01
liuyulongSince we have networking team meeting, I may have no announcement here.14:02
ralonsohhi14:02
liuyulongJust some reminding: https://etherpad.openstack.org/p/neutron-victoria-ptg14:03
liuyulongralonsoh, hi14:03
liuyulongOK, let's move to next topic.14:04
liuyulong#topic Bugs14:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:05
liuyulong#link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012610.html14:05
liuyulongAkihiro Motoki was our bug deputy last week.14:05
liuyulongFirst one:14:06
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186311014:06
openstackLaunchpad bug 1863110 in neutron "2/3 snat namespace transitions to master" [Undecided,New]14:06
liuyulongslaweq and haleyb|away had replied on the bug, maybe a bug from low version keepalived.14:08
slaweqhi, sorry for being late14:08
slaweqI have another meeting in the same time, so I will be only lurking here today, sorry14:08
liuyulongslaweq, sure, no worries14:09
liuyulongAnd the Marek Grudzinski had left the version of the keepalived, it is 1.3.9.14:10
liuyulongThe version is higher than my test ENV.14:11
liuyulongSo I guess maybe the VRRP heartbeats were dropped between the hosts for their LVS clusters.14:12
liuyulongI will leave this comment to the bug.14:12
liuyulongMore about that could be: 1. security group rules14:14
liuyulong2. port security14:14
liuyulong3. allowed address pair14:14
*** jamesmcarthur has quit IRC14:14
liuyulongOK, let's filter the next one...14:15
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186321314:17
openstackLaunchpad bug 1863213 in neutron "Spawning of DHCP processes fail: invalid netcat options" [Undecided,New] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:17
liuyulongI met this issue also.14:17
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186383014:17
openstackLaunchpad bug 1863213 in neutron "duplicate for #1863830 Spawning of DHCP processes fail: invalid netcat options" [Undecided,New] - Assigned to Rodolfo Alonso (rodolfo-alonso-hernandez)14:17
*** links has quit IRC14:18
ralonsohI reverted the patch merged14:18
liuyulongSo I will try that revert locally.14:18
ralonsohAnd I've submitted a patch to mark those tests as unstable14:18
liuyulongralonsoh, yes, I just marked it as duplicated.14:19
ralonsohI still need to know why, sometimes, the netcat rootwrap filters don't work14:19
ralonsohmost of the time do14:19
liuyulongI run dsvm-functional case locally, it fails 100% times.14:20
liuyulonghttp://logstash.openstack.org/#/dashboard/file/logstash.json?query=message:%20%5C%22Exit%20code:%202%3B%20Stdin:%20%3B%20Stdout:%20%3B%20Stderr:%20Ncat:%20Invalid%20-w%20timeout%20(must%20be%20greater%20than%200).%20QUITTING.%5C%2214:20
*** lbragsta_ has quit IRC14:20
liuyulongWe have lots of these logs.14:20
ralonsohthat was solved in https://review.opendev.org/#/c/707786/14:21
liuyulongralonsoh, yes, I know that revert patch. : )14:22
liuyulongI'm going to try that locally14:22
*** Lucas_Gray has quit IRC14:24
liuyulongNext one:14:24
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186309114:24
openstackLaunchpad bug 1863091 in neutron "IPVS setup fails with openvswitch firewall driver, works with iptables_hybrid" [Undecided,New]14:24
liuyulongAlright, it is not so related to L3...14:25
liuyulongBut I have to say for the LVS(ipvs) loadbalancer, it the mode was DR (direct routing), the LVS server and real server may have some config in different.14:26
*** slaweq has quit IRC14:27
liuyulongThe LVS server (frontend) should disable the security group and port_security.14:27
liuyulongThe real server (backend) should add allowed address pair with VIP, and set this VIP to the lo device.14:28
liuyulongOK, I will leave this to the bug.14:28
liuyulongOK, next one:14:30
liuyulong#link https://launchpad.net/bugs/185983214:30
openstackLaunchpad bug 1859832 in neutron "L3 HA connectivity to GW port can be broken after reboot of backup node" [Medium,In progress] - Assigned to LIU Yulong (dragon889)14:30
*** slaweq has joined #openstack-meeting14:30
liuyulongI just want to add the fix from me here:14:31
liuyulong#link https://review.opendev.org/#/c/707406/14:31
liuyulongA totally L3 side change for this bug.14:31
*** jamesmcarthur has joined #openstack-meeting14:32
*** jamesmcarthur_ has joined #openstack-meeting14:33
liuyulongJust update and rebase the code.14:33
liuyulongOK, no more bugs from me then.14:33
liuyulongAny updates?14:33
ralonsohno14:33
liuyulongOK, let's move on.14:35
liuyulong#topic OVN_L314:35
*** openstack changes topic to "OVN_L3 (Meeting topic: neutron_l3)"14:35
ralonsohmaciejjozefczyk, lucasagomes ping14:36
*** jamesmcarthur has quit IRC14:36
ralonsohany update this week in OVN L3?14:36
lucasagomeshi there, I don't think I have any updates14:37
lucasagomessame as last week, we still having some problems while merging the functional tests patch14:37
ralonsohjust one topic: we are reviewing the extensions (including L3 ones) just to know which are really supported14:37
ralonsohthat's all from me14:38
lucasagomesoh yeah, that as well14:38
liuyulongI have on question: the migrated networking-ovn code in neutron repo can run full L2/L3 functionalities?14:40
liuyulongs/on/one14:40
ralonsohdhcp, FIP, DVR, qos (partially)...14:41
liuyulongAll have been aligned to networking-ovn?14:44
ralonsohthat is the goal14:44
liuyulongI mean no gaps between neutron-ovn (a temporary name) and networking-ovn?14:44
liuyulongOK14:44
liuyulongThank you for the information. : )14:45
ralonsohyw14:45
liuyulongSo we have a name for the OVN extensions/drivers/mechanism/plugins in Neutron? I just gave us one: neutron-ovn. : )14:46
ralonsohin L3 ovn-router14:47
*** yamamoto has quit IRC14:48
*** TrevorV has joined #openstack-meeting14:48
liuyulonghttps://review.opendev.org/#/q/topic:bp/neutron-ovn-merge+(status:open+OR+status:merged) so I will put eyes on this bp.14:48
liuyulong#link https://blueprints.launchpad.net/neutron/+spec/neutron-ovn-merge14:48
liuyulong#link https://bugs.launchpad.net/neutron/+bug/185591214:49
openstackLaunchpad bug 1855912 in neutron "MariaDB 10.1 fails during alembic migration" [High,Confirmed]14:49
liuyulongI have a question on this.14:49
liuyulongThis could cause an upgrading issue if user try to update the neutron DB schema with 10.1 mariadb.14:51
ralonsohyes14:51
ralonsohno, not an upgrade14:51
ralonsohbut neutron server will fail during runtime14:51
ralonsohsorry sorry, yes, during upgrade14:52
ralonsohalembic migration14:52
liuyulongFor a cloud deployment, we should warn users that they should check their DB version before upgrading neutron.14:53
ralonsohwe could add a sanity check14:53
liuyulongralonsoh, yes, this could cause the upgrading failure.14:53
liuyulongralonsoh, that's a good approach.14:54
liuyulongBut anyway, if user need to upgrade the basic components, all there neutron server and agent may have a potential long down time.14:55
*** eharney has quit IRC14:56
liuyulongSo I have another idea, something like the "--subproject" for neutron-db-manage.14:56
*** irclogbot_0 has quit IRC14:56
liuyulongIf users' deployment is not OVN and will not upgrade to use OVN, so these tables will not be used.14:57
*** artom has joined #openstack-meeting14:57
liuyulongMaybe we could add a independent upgrade branch for OVN DB schemas only.14:57
ralonsohliuyulong, not, but there are plenty of other tables that, by default, are not used14:57
ralonsohno, this is a risk14:58
ralonsohhaving different DB upgrade paths could lead to errors in a future14:58
ralonsohdue to convergence problems14:58
ralonsohthis is backend problem, not Neutron14:58
ralonsohsame as other problems in OVS, dnsmasq, iproute2, etc14:59
ralonsoh(time goes by so slowly)15:01
liuyulongralonsoh, it is just like the current networking-ovn, vpnaas, fwaas, and so on.15:01
liuyulongWe have no Xaas, so we have no tables for that.15:02
*** irclogbot_3 has joined #openstack-meeting15:02
liuyulongalright, time is up.15:02
liuyulongLet end here.15:03
liuyulong#endmeeting15:03
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:03
openstackMeeting ended Wed Feb 19 15:03:06 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-02-19-14.01.html15:03
liuyulongbye guys!15:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-02-19-14.01.txt15:03
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-02-19-14.01.log.html15:03
liuyulongThank you.15:03
ralonsohbye15:03
*** psachin has quit IRC15:09
*** lpetrut has quit IRC15:11
*** ociuhandu has quit IRC15:11
*** Lucas_Gray has joined #openstack-meeting15:11
*** ociuhandu has joined #openstack-meeting15:17
*** johanssone has quit IRC15:24
*** johanssone has joined #openstack-meeting15:27
*** lucasagomes has quit IRC15:28
*** priteau has joined #openstack-meeting15:32
*** lucasagomes has joined #openstack-meeting15:39
*** Trevor_V has joined #openstack-meeting15:40
*** eharney has joined #openstack-meeting15:40
*** Trevor__V has joined #openstack-meeting15:41
*** TrevorV has quit IRC15:43
*** Trevor_V has quit IRC15:44
*** ociuhandu_ has joined #openstack-meeting15:51
*** ociuhandu has quit IRC15:54
*** ociuhandu_ has quit IRC15:55
*** artom has quit IRC16:13
*** artom has joined #openstack-meeting16:13
*** TrevorV has joined #openstack-meeting16:13
*** Trevor__V has quit IRC16:15
*** ysandeep|away is now known as ysandeep16:17
*** ysandeep is now known as ysandeep|gone16:24
*** liuyulong has quit IRC16:24
*** TrevorV has quit IRC16:27
*** TrevorV has joined #openstack-meeting16:33
*** gyee has joined #openstack-meeting16:36
*** Lucas_Gray has quit IRC16:38
*** epei has joined #openstack-meeting16:44
*** rpittau is now known as rpittau|afk16:48
*** ociuhandu has joined #openstack-meeting16:48
*** ociuhandu has quit IRC16:52
*** mattw4 has joined #openstack-meeting16:54
*** epei has quit IRC16:56
*** epei has joined #openstack-meeting16:57
*** igordc has joined #openstack-meeting16:59
*** sfernand has quit IRC17:00
*** lucasagomes has quit IRC17:03
*** andrebeltrami has quit IRC17:10
*** jmasud has quit IRC17:12
*** nicolasbock has joined #openstack-meeting17:24
*** nicolasbock has quit IRC17:31
*** TrevorV has quit IRC17:33
*** nicolasbock has joined #openstack-meeting17:46
*** igordc has quit IRC17:46
*** dougsz has quit IRC17:51
*** jmasud has joined #openstack-meeting17:52
*** ociuhandu has joined #openstack-meeting17:53
*** ociuhandu has quit IRC17:59
*** e0ne has quit IRC18:00
*** TrevorV has joined #openstack-meeting18:01
*** jmasud has quit IRC18:04
*** epei has quit IRC18:09
*** jmasud has joined #openstack-meeting18:14
*** epei has joined #openstack-meeting18:18
*** jmasud has quit IRC18:18
*** igordc has joined #openstack-meeting18:22
*** witek has quit IRC18:25
*** priteau has quit IRC18:27
*** priteau has joined #openstack-meeting18:29
*** priteau has quit IRC18:33
*** jmasud has joined #openstack-meeting18:35
*** jamesmcarthur has joined #openstack-meeting18:39
*** jmasud has quit IRC18:40
*** jamesmcarthur_ has quit IRC18:41
*** lajoskatona has joined #openstack-meeting18:46
*** larainema has quit IRC18:47
*** ralonsoh has quit IRC18:52
*** lajoskatona has quit IRC18:58
*** maciejjozefczyk has quit IRC19:02
*** vishalmanchanda has quit IRC19:11
*** tesseract has quit IRC19:16
*** lajoskatona has joined #openstack-meeting19:33
*** lajoskatona has quit IRC19:40
*** eharney has quit IRC19:56
*** jamesmcarthur has quit IRC20:06
*** eharney has joined #openstack-meeting20:08
*** ociuhandu has joined #openstack-meeting20:12
*** ociuhandu has quit IRC20:16
*** ociuhandu has joined #openstack-meeting20:24
*** epei has quit IRC20:25
*** jmasud has joined #openstack-meeting20:27
*** ociuhandu has quit IRC20:31
*** ociuhandu has joined #openstack-meeting20:31
*** eharney has quit IRC20:53
timburke#startmeeting swift21:00
openstackMeeting started Wed Feb 19 21:00:11 2020 UTC and is due to finish in 60 minutes.  The chair is timburke. Information about MeetBot at http://wiki.debian.org/MeetBot.21:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:00
*** openstack changes topic to " (Meeting topic: swift)"21:00
openstackThe meeting name has been set to 'swift'21:00
timburkewho's here for the swift meeting?21:00
rledisezhi o/21:00
seongsoochoo/21:00
kota_o/21:00
mattoliverauo/21:01
*** zaitcev has joined #openstack-meeting21:01
timburkeas always, agenda's at https://wiki.openstack.org/wiki/Meetings/Swift21:02
timburke#topic vancouver21:02
*** openstack changes topic to "vancouver (Meeting topic: swift)"21:02
timburkeso first off, a reminder that the PTG in vancouver is coming up21:02
timburkeJune 8-1121:02
timburke#link https://www.openstack.org/events/opendev-ptg-2020/21:02
timburkethe foundation's looking for some attendance estimations, so if you know you're going to be going, that'd be nice for me to know!21:03
zaitcevWell, I plan to go.21:04
zaitcevFWIW21:04
seongsoochoI will go there.21:04
zaitcevNever a given at my age.21:04
kota_planning (not yeg got approval)21:05
timburkeit looks like i *won't* be able to go (my wife has her own conference that week, and i figure i owe her one) but i'm happy to make sure that there's space for swifters and help with any planning21:05
rledisezFor me and alecuyer, no approval yet21:05
clayg🎉???21:06
claygif seongsoocho is gunna go I wanna go21:06
seongsoochowow.. 🙂21:06
*** jamesmcarthur has joined #openstack-meeting21:07
mattoliverauThere might be a meeting in NUE at the suse office around that time. If it doesn't clash, then I might see if I can apply for travel support :)21:07
*** jamesmcarthur has quit IRC21:07
claygkota_: everyone in the swiftstack office is all about https://events.static.linuxfound.org/sites/events/files/slides/linuxcon15_bando.pdf21:07
*** jamesmcarthur has joined #openstack-meeting21:07
timburkeshould we plan on requesting an ops feedback session again? i feel like that was nice in shanghai21:07
claygkota_: so if you could lookup Yuichi Bando in the company directory and send him a virtual high five that'd be awesome!21:07
kota_OH21:08
claygtimburke: I feel like I remember prior-to-shanghai ops feedback sessions way better than shanghai21:08
timburkefair enough21:08
clayg... we were all just in that one room?  were their ops people that came by at some point?21:08
kota_IIRC... he left...21:09
claygkota_: well... his legacy lives on!21:09
claygtimburke: or no, there WAS an ops session in one of the speaking rooms - seperate from the PTG21:09
kota_that sounds awesome. good to know21:09
timburkeclayg, maybe it could just be done as some set-aside time in the working sessions, then21:09
timburke*shrug*21:09
claygonly it was mostly like just us21:09
timburkeyeah, we wrote some stuff down at least: https://etherpad.openstack.org/p/PVG-swift-ops-feedback21:10
claygno no, I do remember that now - there was a couple of people in there...21:10
timburkei think sorrison came by and wouldn't have necessarily done so for just the working sessions21:11
timburkeanyway, something to think about: do you guys want one, and if so, who would like to lead it21:11
claygtimburke: yes I 100% agree, I just forgot - the ops sessions are great and we should definately have another one not just the working sessions21:12
timburke👍21:12
claygseongsoocho: could be the MC like "I run swift, it's not my LEAST favorite piece of software - how about y'all?"21:12
timburkeanyway, i think that's all i've got for vancouver -- thanks zaitcev, seongsoocho for the solid yes, and kota_, rledisez, alecuyer, clayg, mattoliverau for the tenative maybes ;-)21:14
timburkei figure by the time i need to actually get a response in, we'll all know a bit more about what's approved21:14
timburke#topic swiftclient release21:15
*** openstack changes topic to "swiftclient release (Meeting topic: swift)"21:15
timburke(sorry, a little out of order)21:15
timburkeso, we had one! there's a 3.9.0 now21:15
diablo_rojotimburke, we will miss you21:15
timburkethis was actually kinda unplanned; milestone 2 came up and i forgot that we need to get a client library out by then21:15
timburkebut i *would* like to get another out in the not-too-distant future!21:16
timburkein particular to pick up versioning support21:16
timburke#link https://review.opendev.org/#/c/691877/21:16
timburkeand symlink support21:17
timburke#link https://review.opendev.org/#/c/694211/21:17
zaitcevWell poke tdasilva with a physical stick21:17
timburkecharz has apparently been rather busy :-) i'm also pretty excited about the ideas in https://review.opendev.org/#/c/707409/21:18
timburkethe filtering in https://review.opendev.org/#/c/708074/ is kind of interesting, too, and probably closer to mergable21:19
claygzaitcev: can you make a summary of the debate about the interface for symlink support?21:19
*** jamesmcarthur has quit IRC21:19
timburkeand i remember people specifically asking for keystone credential support in shanghai, so https://review.opendev.org/#/c/699457/ might be good21:20
claygzaitcev: I remember thinking when I looked at it that the interface did not at a glance resemble the existing copy command (which I thought it reasonably MIGHT)21:20
zaitcevclayg:  swift link [--cont2=c2] c a b  versus  swift link c1 a c2 b21:20
claygso i'm not sure if things have moved to "no it's just like copy now" or "copy was wrong; and this is better"21:20
clayg... or maybe even "why would creating a link be like copying?!"21:21
zaitcevA pinnacle of byteshedding. Although, I recall that Tim told me that we already have something like it, like "swift copy" so maybe we should just be consistent with that.21:21
*** jamesmcarthur has joined #openstack-meeting21:21
kota_sounds reasonable21:23
claygok so maybe that one isn't done yet21:24
claygthe versioning one is GTG I think, and I'd love to have it21:24
timburkei'll find some time to review it this week21:25
timburkeanything else to bring up with regard to swiftclient?21:25
*** jamesmcarthur has quit IRC21:26
timburke#topic EC gets and long tail latency21:27
*** openstack changes topic to "EC gets and long tail latency (Meeting topic: swift)"21:27
timburkeso we here at swiftstack have a customer very interested in bringing down their 99.9%tile latencies21:27
timburkewe realized that even though they had concurrent gets turned on, it wasn't actually helping, because all the data was EC'ed21:28
*** raildo has quit IRC21:28
timburkeand the way that works is we spin up ndata connections, then wait up to node_timeout for them to indicate they're ready before ever spinning up any alternate connections21:29
timburkeso we had this real interesting distribution of request timings where you'd see a big peak close to zero, then a pretty smooth drop-off until you got to node_timeout21:30
claygand so if you have a "slow" frag it slows down the whole mess21:30
claygtimburke: were we able to isolate any of those specific requests up there around node_timeout and look at logs validate there was a XXXms fragment GET after a Xs node_timeout?21:31
timburkeat which point you got another peak and drop-off until 2x node_timeout, at which point you've got one more little peak and only a smattering of longer requests21:31
timburkeclayg, haven't yet; probably a good idea to validate assumptions21:32
timburkeso i guess i've got two main questions for people21:32
timburke1) has anyone else noticed this sort of behavior? got any users complaining about latencies?21:33
timburkeand 2) how *should* it behave? spin up ndata+nparity connections immediately and wait for ndata? spin up ndata then have the concurrency_timeout behavior we currently have with replicated? should there be any special logic around handoff nodes?21:34
rledisez1/ not really. yes we clearly see the ttfb is higher on EC than replica, but we didn't really investigate because by design our EC policy will be slower (and we didn't get complain from our users)21:35
rledisez2/ i don't want that the proxy reach all nodes immediately because it will have an impact in terms of IO. it would be ok if the IO cost was nearly zero (aka storing meta on a faster device)21:35
zaitcevFascinating.21:36
rledisezbut as we are considering droping replica and move all EC, this is clearly a topic i'm interested in21:36
mattoliverauHow long does it normall take for a node to become "ready"21:36
mattoliveraudoes it take node_timeout21:36
mattoliverauor can we use conn_timeout like in default concurrency21:36
mattoliverau*default concurrency timeout21:37
mattoliverauSo their staggered, but not waiting too long.21:37
claygmattoliverau: I think defaulting concurrent gets to conn_timeout has proven to be absolutely brilliant and has undoubtly smoothed out latency tails on replicated GETs21:37
claygrledisez: I 100% agree that use-case expectation setting for "replicated is faster ttfb" proves out for the data - and I don't believe this deployment has dont A/B comparison to quantify that21:38
claygrledisez: OTOH, if we can do a good job translating what mattoliverau taught us when implementing concurrent gets for replicated it's possible that difference could be diminished21:39
timburkefwiw, i've got a smallish log sample where 50% are <100ms, 90% are <600ms, and 99% are <2s21:40
rledisezi agree it looks like the right way to do it, especially since it's configurable, operators can choose to be aggressive or not on the timeout21:41
timburke(though i maybe need to clean that up, i don't think i filtered it to only look at object gets)21:41
timburkeone thought that i'd had was to wait until we have max(0, ndata-nparity) connection in hand before switching to the concurrent-get behavior, but maybe that's just over-complicating things21:42
mattoliverauSounds like conn_timeout a first thing to try and see how it goes. worst case is we get less of a tail and more connections.. which isn't great, but might be ok. Conn timeout defaults at 0.5 so might catch 90% of cases if were lucky.21:42
timburkeand i *think* https://review.opendev.org/#/c/706361/ might help with the extra connections -- we were definitely seeing connections on the proxy that would hang around well past the client response on the same cluster...21:44
timburkeanyway, just wanted to let people know about some of the stuff we've been poking at lately21:46
timburke#topic open discussion21:46
*** openstack changes topic to "open discussion (Meeting topic: swift)"21:46
timburkewhat else would people like to bring up?21:46
clayg👍 we can trivially demonstrate in unittests and development that those greenthreads spawned and abandoned from the proxy after the client response goes through are still running and will finish21:46
zaitcevSo, anyone wants to help out with that dark data thing? Romain, you had an opinion about the separation.21:47
claygwe leverage this behavior on purpose in the object-server with the container-update-timeout21:47
zaitcevUnfortunately, Sam left for Google, so I cannot debate him. He typically knew what he was doing about this, so I'm not very happy to conclude that he was wrong. https://review.opendev.org/70665321:48
claygmattoliverau: so for waterfall-ec your suggestion is spawn ec_ndata connections like we currently do, then use concurrent_gets to wait up to concurrency_timeout (defaults to connection timeout) before spawning more requests21:49
rledisezon the replace-md5-for-checksum side, I'm planning to put as a requirement, before the operator decide to use something else than md5 for checksum, that he must ensure that the whole cluster is upgraded to the right version. is that ok for everybody? i don't think it's possible to just let the proxy do its best to guess if it should use md5 or something else21:49
rledisezzaitcev: do you have a pointer on the dark-data thing? (bugreport, review, …)21:49
claygmattoliverau: I assume like replicated concurrent gets we'd stop spawning once we get into handoffs until we get an non-success (maybe timeout) response from a primary21:50
timburkezaitcev, i think he had a goal of allowing marginally-trusted code to run; if we're content to say "you wan to run this? make sure it's stable!" i think i'd probably be ok with the simpler approach21:50
mattoliverauclayg: yeah, then we also dog food the same settings on EC and REPL. But of course, only brain storming atm21:51
zaitcevrledisez: I had a couple of cases where the loss of capacity was significant. It always was associated with some kind of catastrophic mismanagement by the operator: a bothched restore from a backup, or having half of the drives go down.21:51
timburkerledisez, https://review.opendev.org/#/c/706653/ i believe21:51
claygso if we have a 4+2, we spawn 4, then 500ms later if we're still waiting on at least 2 of the 4 responses - we spawn 2 more21:52
mattoliverauyup21:52
mattoliverauthen the ndata get a chance to give use the goods, and if not we can fall back to a rebuild. but not go searching handoffs.. though I guess we could21:52
zaitcevrledisez: I am comfortable to think that OVH or RAX aren't going to have any dark data even if clusters are heavily loaded. It's just that Red Hat sells this private cloud solution to people who don't care about running their clusters, and so this happens regularly.21:52
mattoliverauworst case, other then connections, we may get a frag back.21:53
timburkerledisez, on the hashing, yeah, that seems reasonable -- rather like what we documented for turning on encryption in an existing cluster21:53
claygmattoliverau: I think the code is going to be fairly amicable to that change, thanks for thinking through it21:53
rledisezzaitcev: I'm pretty confident we have dark data hanging around :) but probably nothing massive. don't forget that container may not be up2date immediately, so you should allow a delay before checking the container server21:55
*** jamesmcarthur has joined #openstack-meeting21:56
rledisezI don't really like that because I can't imagine how long it would take, but I don't have any better option. if there is async_pendings somewhere, you might end up deleting valid object21:56
claygzaitcev: same here, it's unfortunately all to human to have "some kind of catastrophic mismanagement by the operator" 😁21:56
zaitcevYeah... It can be stuck in an update somewhere21:57
claygrledisez: on the md5 thing - i'm not sure I follow how you're suggesting we *enforce* "make sure your whole cluster is upgraded"21:57
seongsoochorledisez:  In my cluster, The swift proxy-server support multiple checksum.  Some container use md5 for checksum and some container use SHA256 for checksum.  The customer wants to choose  the checksum..21:57
zaitcevThe main problem I'm having with this isolation thing is the throttling21:58
*** jamesmcarthur has quit IRC21:58
rledisezclayg: we can't enforce it, but we can write in the changelog/doc "if you don't do it, you'll be in trouble"21:58
claygseongsoocho: !!! that's awesome!  It's possible you avoided some of the hard problems rledisez is trying to solve - but I think generally that's the idea we'd like to support21:58
zaitcevMy container servers are on rotating storage and they are slower than object auditors at times.21:58
*** jamesmcarthur has joined #openstack-meeting21:58
timburkeseongsoocho, whoa, cool! is that stored in the container db, too, or just used for etags, or something else? i'm sad i won't be in vancouver to ask you more about it in person!21:58
claygseongsoocho: i'm guessing there's at least proxy middleware to handle setting sysmeta?  How much can you share?21:59
zaitcevSo, very soon you start skipping on the checks. No big deal, just recheck on next pass, right21:59
seongsoochotimburke:  It just used for etags .21:59
seongsoochoclayg:   I try to write the details on etherpad as soon as possible.22:00
zaitcevWell, but now suppose it says that you have 0.03% capacity used up by dark data. Is that trustworthy? But one other thing is, with these separate processes everything is harder to analyze.22:00
claygzaitcev: oh, ok, so but the "audit_dark_data" example watcher is new - sam's original design didn't include a concrete example?22:01
timburkeall right, looks like we're about out of time -- but we can keep chatting in -swift for sure!22:01
timburke(sorry, not sure if there's anyone who'd be waiting on the room)22:01
timburkethank you all for coming, and thank you for working on swift!22:01
timburke#endmeeting22:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"22:02
openstackMeeting ended Wed Feb 19 22:01:59 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-02-19-21.00.html22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-02-19-21.00.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2020/swift.2020-02-19-21.00.log.html22:02
zaitcevAnd finally, the straw that overflowed that cup for me: I wrote a test and I needed to verify logging. It was a hell on a stick to extract from those isolation processes. I wrote some stupid thing that dumped into files. I completed it, it's in a separate review. So it can be done. But whyyyyyyy, Sam22:02
zaitcevok22:02
*** zaitcev has left #openstack-meeting22:03
*** jamesmcarthur_ has joined #openstack-meeting22:09
*** jamesmcarthur has quit IRC22:13
*** ykatabam has joined #openstack-meeting22:14
*** TrevorV has quit IRC22:21
*** eharney has joined #openstack-meeting22:21
*** slaweq has quit IRC22:29
*** ociuhandu has quit IRC22:38
*** slaweq has joined #openstack-meeting22:40
*** slaweq has quit IRC22:45
*** enriquetaso has quit IRC22:53
*** rcernin has joined #openstack-meeting23:04
*** rh-jelabarre has quit IRC23:06
*** ysandeep|gone is now known as ysandeep23:27
*** jamesmcarthur_ has quit IRC23:32
*** jamesmcarthur has joined #openstack-meeting23:33
*** jamesmcarthur has quit IRC23:39
*** ociuhandu has joined #openstack-meeting23:45
*** eharney has quit IRC23:55

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