Wednesday, 2020-02-12

*** Liang__ has quit IRC00:03
*** Liang__ has joined #openstack-meeting00:04
*** rcernin has joined #openstack-meeting00:08
*** artom has quit IRC00:10
*** slaweq has joined #openstack-meeting00:11
*** ykatabam has quit IRC00:14
*** artom has joined #openstack-meeting00:14
*** artom has quit IRC00:15
*** artom has joined #openstack-meeting00:15
*** slaweq has quit IRC00:16
*** ykatabam has joined #openstack-meeting00:18
*** macz has quit IRC00:38
*** armax has joined #openstack-meeting00:43
*** rf0lc0 has quit IRC00:50
*** rcernin has quit IRC00:55
*** rcernin has joined #openstack-meeting00:55
*** masayukig is now known as migawa|AFK01:08
*** migawa|AFK is now known as migawa01:09
*** slaweq has joined #openstack-meeting01:11
*** ykatabam has quit IRC01:12
*** jamesmcarthur has joined #openstack-meeting01:12
*** ykatabam has joined #openstack-meeting01:12
*** slaweq has quit IRC01:16
*** jmasud has joined #openstack-meeting01:17
*** brinzhang has quit IRC01:22
*** jamesmcarthur has quit IRC01:23
*** jamesmcarthur has joined #openstack-meeting01:36
*** TomStappaerts has quit IRC01:42
*** TomStappaerts has joined #openstack-meeting01:43
*** ykatabam has quit IRC01:44
*** ykatabam has joined #openstack-meeting01:49
*** brinzhang has joined #openstack-meeting01:51
*** yamamoto has joined #openstack-meeting01:57
*** ykatabam has quit IRC02:02
*** ykatabam has joined #openstack-meeting02:05
*** slaweq has joined #openstack-meeting02:11
*** ykatabam has quit IRC02:11
*** yamamoto has quit IRC02:12
*** yamamoto has joined #openstack-meeting02:13
*** slaweq has quit IRC02:16
*** yamamoto has quit IRC02:17
*** ricolin has joined #openstack-meeting02:19
*** ykatabam has joined #openstack-meeting02:23
*** ykatabam has quit IRC02:28
*** ykatabam has joined #openstack-meeting02:29
*** ykatabam has joined #openstack-meeting02:30
*** jamesmcarthur has quit IRC02:38
*** macz has joined #openstack-meeting02:40
*** yamamoto has joined #openstack-meeting02:40
*** macz has quit IRC02:45
*** jamesmcarthur has joined #openstack-meeting02:53
*** yamamoto has quit IRC03:01
*** yamamoto has joined #openstack-meeting03:03
*** rcernin has quit IRC03:06
*** ykatabam has quit IRC03:06
*** ykatabam has joined #openstack-meeting03:07
*** slaweq has joined #openstack-meeting03:11
*** slaweq has quit IRC03:16
*** psachin has joined #openstack-meeting03:21
*** rcernin has joined #openstack-meeting03:23
*** masahito_ has joined #openstack-meeting03:24
*** senrique_ has quit IRC03:40
*** jamesmcarthur has quit IRC03:55
*** gyee has quit IRC04:08
*** jmasud has quit IRC04:10
*** slaweq has joined #openstack-meeting04:11
*** vishalmanchanda has joined #openstack-meeting04:13
*** slaweq has quit IRC04:16
*** rcernin has quit IRC04:16
*** rcernin has joined #openstack-meeting04:16
*** masahito_ has quit IRC04:28
*** psachin has quit IRC04:33
*** artom has quit IRC04:35
*** macz has joined #openstack-meeting04:41
*** macz has quit IRC04:46
*** migawa is now known as migawa|lunch|AFK04:50
*** rcernin is now known as rcernin|lunch05:01
*** slaweq has joined #openstack-meeting05:11
*** slaweq has quit IRC05:16
*** migawa|lunch|AFK is now known as migawa|lunch05:18
*** TomStappaerts has quit IRC05:32
*** TomStappaerts has joined #openstack-meeting05:33
*** mmethot_ has joined #openstack-meeting05:35
*** mmethot has quit IRC05:37
*** macz has joined #openstack-meeting05:41
*** macz has quit IRC05:45
*** jamesmcarthur has joined #openstack-meeting05:57
*** macz has joined #openstack-meeting05:58
*** jamesmcarthur has quit IRC06:01
*** macz has quit IRC06:03
*** slaweq has joined #openstack-meeting06:11
*** TomStappaerts has quit IRC06:15
*** TomStappaerts has joined #openstack-meeting06:15
*** slaweq has quit IRC06:16
*** slaweq has joined #openstack-meeting07:08
*** slaweq has quit IRC07:15
*** jmasud has joined #openstack-meeting07:17
*** rsimai has joined #openstack-meeting07:20
*** rpittau|afk is now known as rpittau07:21
*** macz has joined #openstack-meeting07:24
*** macz has quit IRC07:29
*** brinzhang has quit IRC07:29
*** lpetrut has joined #openstack-meeting07:31
*** kopecmartin|afk is now known as kopecmartin07:44
*** TomStappaerts has quit IRC07:46
*** ianychoi has joined #openstack-meeting07:46
*** TomStappaerts has joined #openstack-meeting07:46
*** slaweq has joined #openstack-meeting07:51
*** maciejjozefczyk has joined #openstack-meeting07:54
*** slaweq has quit IRC07:57
*** hammad_ has joined #openstack-meeting07:57
*** slaweq has joined #openstack-meeting07:58
*** lajoskatona has joined #openstack-meeting08:00
*** hammad_ has quit IRC08:07
*** hammad_ has joined #openstack-meeting08:07
*** witek has joined #openstack-meeting08:10
*** jmasud has quit IRC08:13
*** jmasud has joined #openstack-meeting08:14
*** Liang__ has quit IRC08:22
*** Liang__ has joined #openstack-meeting08:23
*** yamamoto has quit IRC08:30
*** ralonsoh has joined #openstack-meeting08:38
*** yamamoto has joined #openstack-meeting08:44
*** TomStappaerts has quit IRC08:47
*** TomStappaerts has joined #openstack-meeting08:47
*** etp has joined #openstack-meeting08:52
*** mdelavergne has joined #openstack-meeting08:56
*** oneswig has joined #openstack-meeting08:58
*** masahito has joined #openstack-meeting08:59
ttx#startmeeting large_scale_sig09:00
openstackMeeting started Wed Feb 12 09:00:39 2020 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.09:00
ttx#topic Rollcall09:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.09:00
*** openstack changes topic to " (Meeting topic: large_scale_sig)"09:00
openstackThe meeting name has been set to 'large_scale_sig'09:00
*** openstack changes topic to "Rollcall (Meeting topic: large_scale_sig)"09:00
oneswighello09:00
mdelavergneHi!09:00
ttxHello hello everyone09:01
ttxAgenda at:09:01
witekgood morning09:01
ttx#link https://etherpad.openstack.org/p/large-scale-sig-meeting09:01
*** dougsz has joined #openstack-meeting09:01
ttxLet's wait for our Asian friends to join09:01
dougszo/09:01
masahitoo/09:02
etpo/09:02
ttxOK, let's get started and maybe others will join09:02
ttx#topic Show and tell09:02
*** openstack changes topic to "Show and tell (Meeting topic: large_scale_sig)"09:02
oneswigThanks ttx09:03
ttxWe'll start with oneswig presenting09:03
ttxoneswig: floor is yours09:03
oneswigI put a link in the etherpad but here's a kind-of presentation... http://www.stackhpc.com/resources/HAproxy-telemetry.pdf09:03
oneswigjust a few slides as talking points.  We do this in the Scientific SIG sometimes and it mostly works09:03
* ttx clicks09:03
oneswigSo I wanted to share some work my colleague dougsz has been doing :-)09:04
oneswigWe noticed that HAproxy had sprouted some new telemetry data and wanted to use it.09:04
oneswigIt's published in prometheus protocol.09:04
oneswigDoug has done some useful work recently with Monasca-Agent (our monitoring infra) to extend support for drawing data from prometheus sources09:05
oneswigthis is desirable because there's a lot of new work coming in that format - Ceph, HAproxy, etc.09:06
*** lucasagomes has joined #openstack-meeting09:06
ttxand oslo.metric09:07
oneswigttx: indeed :-) It works nicely for us because we get the innovation in prometheus coupled with the advantages of Monasca09:07
oneswigOK, so on slide 2 we have a diagram of Monasca services and how the agent pulls data from prometheus endoints, does some preliminary sanitisation and pushes them to the Monasca API09:08
oneswigSlide 4 is an example end-to-end.  That's the API response latencies, as measured by haproxy, sampled and averaged, collated by API endpoint09:09
oneswigIts interesting - to a point.09:09
oneswigOne problem with the prometheus data as it stands is that it doesn't appear to split latency out by (eg) response code or http operation09:10
ttxthat glance_api_external does not seem to be on a good trends09:10
oneswigthe big red ascending saw-tooth looks bad.  To make it do that I was repeatedly creating and deleting images.09:11
oneswig(this is only a single-node control plane, it's a dev environment)09:11
ttxoneswig: so success latency is mixed with error latency?09:12
oneswigWhat it doesn't show is that this is a combination of POST, PUT, GET, DELETE09:12
oneswigttx: exactly, which isn't perfect.09:12
ttxyes because I read the golden signals chapter09:12
oneswigand brings us to the next part of the work - slide 509:12
oneswig:-)09:12
oneswigDoug noticed that haproxy can log copious amounts of useful data, and the log messages appear designed to be parsed into semi-structure ddata09:13
oneswigForgot to mention at the top - we use Kolla-Ansible, which standardises on a fluentd log aggregator container on each node09:13
oneswigAfter parsing the logs with some epic regex, we get json structured data about each api request09:14
oneswigThis goes into monasca's log pipeline.  The box in the bottom right corner can be used to convert log messages into dimensioned time series telemetry (monasca log metrics)09:15
oneswigThat gives us individual samples which can be aggregated at various points in the pipeline into histograms09:15
oneswigcurrently we do this in grafana, but it could be pushed further upstream, even to fluentd09:16
*** lajoskatona has left #openstack-meeting09:16
oneswigThe second grafana screenshot shows api responses for one service (keystone in this case, because the data's prettiest:-)09:17
ttxHmm... y is response time, but what is x in this graph?09:18
oneswigBut what we can see is data by operation, interface and response09:18
oneswigfrequency density, iirc09:18
oneswigit's binned into 10ms intervals09:18
ttxah ok09:18
oneswigUnfortunately there weren't errors for this service but if there were, we might see 500 response codes on the graph too.09:19
ttxKeystone never fails09:19
oneswigOne shortcoming I guess is that if the number of errors is small, or the timing of them scattered, they'd be lost in the noise along the x-xis09:20
ttxyeah for errors you might want to aggregate on longer periods of time09:20
ttx(or for other rare events)09:21
witekand create a separate dashboard for errors only09:21
dougszRe. the axis labelling, unfortunately the histogram plugin doesn't support it09:21
ttxdougsz: as long as the reader knows what's on them, I guess it does not matter that much09:22
oneswiga good sample would certainly be more useful.  We also have such detailed data here, we could potentially trace every datapoint to a single api request09:22
ttxdougsz, oneswig: That's interesting integration work! Thanks for sharing09:22
oneswigBTW all this work is going / has gone upstream09:22
oneswigIt should be useful at various levels - even the general principles for folks not using any of these components09:23
ttxIt shows that once you start reducing the parameters (like say you start from Kolla-Ansible so you can rely on fluentd/monasca being present), it simplifies things a lot09:23
ttx(in the telemetry gathering space)09:23
oneswigI think so.  One thing missing is a nice starting point in terms of dashboards.  It's pretty basic what you get as standard09:24
ttxquestions on this presentation?09:24
oneswigdoug did I miss anything?09:24
dougszIndeed, we have a goal to pre-configure monitoring out of the box in Kolla-Ansible09:24
dougszI think you captured it nicely, thanks oneswig09:25
ttxoneswig: do you mind if I include a link to your slides on the meeting summary sent to the ML?09:25
dougszIt might be worth mentioning that Prometheus users can take advantage of the log parsing via the Fluentd Prometheus plugin in Kolla09:25
oneswigBTW the glance API - I ran that test overnight, it reached a steady state around 3.5s :-)09:25
ttxOK, if no more questions we'll switch to our next topic...09:26
ttx#topic Progress on "Documenting large scale operations" goal09:26
*** openstack changes topic to "Progress on "Documenting large scale operations" goal (Meeting topic: large_scale_sig)"09:26
ttxamorin: around?09:26
ttx#link https://etherpad.openstack.org/p/large-scale-sig-documentation09:26
*** tetsuro has joined #openstack-meeting09:27
ttxNo amorin today, so we'll get how things are going on the config default documentation effort in a future meeting09:27
ttxWe also had a bunch a links added to the etherpad, which is great. I briefly scanned them and feel like they all belong.09:28
ttx#topic Progress on "Scaling within one cluster" goal09:28
*** openstack changes topic to "Progress on "Scaling within one cluster" goal (Meeting topic: large_scale_sig)"09:28
ttx#link https://etherpad.openstack.org/p/large-scale-sig-cluster-scaling09:28
ttxThe oslo.metric blueprint got its first round of reviews, mostly from outside the SIG09:28
ttx#link https://review.opendev.org/#/c/704733/09:28
ttxWould be great to get more feedback from the SIG participants themselves, before masahito does another round.09:29
ttxSo I propose to add a TODO for the group to review that spec ASAP09:29
ttx(as soon as possible)09:29
masahitoI don't have much update this week.  I'll update the patch without adding actual schema in this week.09:30
masahitos/patch/draft/09:30
ttx#action masahito to update spec based on initial feedback09:30
ttx#action everyone to review and comment on https://review.opendev.org/#/c/704733/09:30
ttxRegarding golden signals, did anyone read the recommended read ?09:31
ttx#link https://landing.google.com/sre/sre-book/chapters/monitoring-distributed-systems/#xref_monitoring_golden-signals09:31
ttxBasically the summary is that any monitoring system should watch latency, traffic, errors, and saturation as early detectors of impeding failure09:31
ttxSo making sure this group has a common understanding of those terms is useful.09:31
*** oneswig_ has joined #openstack-meeting09:32
ttxPlease read it (it's short) if you haven't had the chance yet09:32
ttxOn the scaling stories front, thanks to Albert Braden who posted to the doc recently09:32
ttx#link https://etherpad.openstack.org/p/scaling-stories09:32
ttxI feel like some of it should find its way to amorin's documentation efforts09:33
ttxcomments on that?09:33
ttxSounds like a no09:34
ttx#topic Other topics09:34
*** openstack changes topic to "Other topics (Meeting topic: large_scale_sig)"09:34
ttxSo... we have an "Opendev" event coming up in Vancouver, June 8-1109:34
ttxI wanted to talk briefly about it and how this group can get involved09:35
*** oneswig has quit IRC09:35
ttxFor those not familiar with the format, it's a workshop-style event where we deep-dive into a number of predefined topics, with lots of flexibility in the exact event format09:35
ttxOne of the 4 themes selected for the event is "Large-scale Usage of Open Source Infrastructure Software"09:35
ttxWhich is directly aligned with this SIG09:35
ttxSo I think we should definitely participate to the programming committee and help select the content that will be discussed there09:36
ttxLike make sure we have some part of the event discussing our "scaling one cluster" and "documenting large scale use defaults" goals09:36
ttxAnd also take the opportunity to recruit more people to this SIG.09:36
ttxI saw that Belmiro applied to be on the programming committee, I'll make sure to support that application. I myself will be focused on other tracks at the same event09:37
ttxSo if others (masahito? oneswig? amorin? jiaopingju?) are interested in driving the content that will be discussed there, please let me know09:37
masahitoThank. I plan to go to the Opendev. But not decided yet.09:38
mdelavergneI might be able to help, but I am not sure I will physically go there09:38
masahitoIf I can go, I'm okay to be a moderator.09:39
ttxThat would be great09:39
ttxOK, we still have some tie, but I  know the event organizers want to select the programming committees ASAP09:39
ttxsome time*09:39
masahitoIs there room or talk submission for the event now?09:40
ttxmasahito: It depends on the choice of each programming committee. The general idea is to have a limited number of formal presentations, so in most cases the programming committee will just invite a specific speaker09:41
ttxBut some tracks might do a more classic CFP09:41
masahitoGot it. Thanks.09:41
ttxand some others might do more of a short-presentations session09:41
ttx(this is why it's important to have members of this SIG in the programming committee)09:42
ttxmasahito: in case you can confirm your presence soon, I'd be happy to pass your name to be a part of the committee09:42
ttxif you'll know later, we can always have you moderate some topic09:43
ttxlike a workshop on gathering metrics on bottlenecks in your OpenStack clusters09:43
masahitookay.09:43
ttxOther questions on this event?09:44
ttxOther topics to discuss?09:44
mdelavergneNot from myself right now09:44
ttx#topic Next meeting09:44
masahitoNothing from my side.09:44
*** openstack changes topic to "Next meeting (Meeting topic: large_scale_sig)"09:44
ttxOur next meeting should be Feb 26, 9 utc09:44
ttxHopefully we'll have more people around09:44
ttxAnything else before we close the meeting?09:45
ttxIf not, thank you for attending!09:45
mdelavergneThanks everyone!09:46
ttx#endmeeting09:46
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"09:46
openstackMeeting ended Wed Feb 12 09:46:18 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)09:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-02-12-09.00.html09:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-02-12-09.00.txt09:46
openstackLog:            http://eavesdrop.openstack.org/meetings/large_scale_sig/2020/large_scale_sig.2020-02-12-09.00.log.html09:46
masahitothanks09:46
*** e0ne has joined #openstack-meeting09:54
*** ociuhandu has joined #openstack-meeting09:56
*** mdelavergne has quit IRC10:02
*** jiaopengju2 has joined #openstack-meeting10:04
*** TomStappaerts has quit IRC10:08
*** TomStappaerts has joined #openstack-meeting10:08
*** ykatabam has quit IRC10:22
*** rcernin|lunch has quit IRC10:22
*** kaisers has quit IRC10:27
*** kaisers has joined #openstack-meeting10:35
*** rcernin|lunch has joined #openstack-meeting10:36
*** vishalmanchanda has quit IRC11:12
*** armax has quit IRC11:14
*** armax has joined #openstack-meeting11:19
*** Lucas_Gray has joined #openstack-meeting11:27
*** oneswig_ has quit IRC11:31
*** rpittau is now known as rpittau|bbl11:33
*** hammad_ has quit IRC11:35
*** armax has quit IRC11:44
*** raildo has joined #openstack-meeting11:47
*** nicolasbock has joined #openstack-meeting12:06
*** ociuhandu has quit IRC12:09
*** ociuhandu has joined #openstack-meeting12:10
*** rfolco has joined #openstack-meeting12:10
*** jmasud has quit IRC12:13
*** jmasud has joined #openstack-meeting12:14
*** jiaopengju2 has quit IRC12:21
*** jiaopengju2 has joined #openstack-meeting12:22
*** TomStappaerts has quit IRC12:24
*** TomStappaerts has joined #openstack-meeting12:24
*** ianychoi has quit IRC12:25
*** masahito has quit IRC12:25
*** masahito has joined #openstack-meeting12:26
*** rfolco has quit IRC12:26
*** rfolco has joined #openstack-meeting12:26
*** masahito has quit IRC12:26
*** masahito has joined #openstack-meeting12:27
*** masahito has quit IRC12:27
*** TomStappaerts has quit IRC12:29
*** TomStappaerts has joined #openstack-meeting12:30
*** ykatabam has joined #openstack-meeting12:37
*** TomStappaerts has quit IRC13:03
*** TomStappaerts has joined #openstack-meeting13:03
*** Liang__ has quit IRC13:03
*** Liang__ has joined #openstack-meeting13:04
*** rpittau|bbl is now known as rpittau13:05
*** senrique_ has joined #openstack-meeting13:08
*** jamesmcarthur has joined #openstack-meeting13:09
*** ociuhandu has quit IRC13:11
*** manuvakery has quit IRC13:13
*** TrevorV has joined #openstack-meeting13:16
*** Lucas_Gray has quit IRC13:31
*** Lucas_Gray has joined #openstack-meeting13:34
*** jamesmcarthur has quit IRC13:35
*** rh-jelabarre has joined #openstack-meeting13:39
*** nicolasbock has quit IRC13:43
*** TomStappaerts has quit IRC13:44
*** TomStappaerts has joined #openstack-meeting13:44
*** jamesmcarthur has joined #openstack-meeting13:45
*** nicolasbock has joined #openstack-meeting13:47
*** ociuhandu has joined #openstack-meeting13:48
*** rcernin|lunch has quit IRC13:50
*** liuyulong has joined #openstack-meeting13:51
*** ociuhandu has quit IRC13:52
*** eharney has quit IRC13:55
liuyulong#startmeeting neutron_l313:58
openstackMeeting started Wed Feb 12 13:58:47 2020 UTC and is due to finish in 60 minutes.  The chair is liuyulong. Information about MeetBot at http://wiki.debian.org/MeetBot.13:58
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:58
*** openstack changes topic to " (Meeting topic: neutron_l3)"13:58
openstackThe meeting name has been set to 'neutron_l3'13:58
liuyulong#topic Announcements13:58
*** openstack changes topic to "Announcements (Meeting topic: neutron_l3)"13:58
slaweqhi13:59
liuyulonghi13:59
liuyulongUssuri-2 is this week.13:59
liuyulongAnd we have this list:14:00
liuyulong#link https://launchpad.net/neutron/+milestone/ussuri-214:00
*** Liang__ is now known as LiangFang14:00
*** sfernand has joined #openstack-meeting14:00
*** TomStappaerts has quit IRC14:01
liuyulongTwo RFE related bugs are not finished. So maybe we should move it to next U-314:02
*** TomStappaerts has joined #openstack-meeting14:02
*** lbragstad has joined #openstack-meeting14:02
liuyulongOVN migrations are quite good I guess.14:02
liuyulongOK, I just read the book, haha.14:03
liuyulongNo more from me now.14:03
liuyulongAny updates?14:03
*** senrique_ is now known as enriquetaso14:04
liuyulongOK, let's move on.14:04
liuyulong#topic Bugs14:04
*** openstack changes topic to "Bugs (Meeting topic: neutron_l3)"14:04
ralonsohhi14:04
liuyulong#link http://lists.openstack.org/pipermail/openstack-discuss/2020-February/012477.html14:04
liuyulongralonsoh, hi14:04
*** ociuhandu has joined #openstack-meeting14:04
liuyulongFirst one14:05
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186231514:05
openstackLaunchpad bug 1862315 in neutron "Sometimes VMs can't get IP when spawned concurrently" [High,New] - Assigned to Oleg Bondarev (obondarev)14:05
liuyulongIt has a fix now.14:05
liuyulong#link https://review.opendev.org/#/c/707077/14:06
*** lbragstad has quit IRC14:08
liuyulongsorry, a bit latency on networking...14:09
liuyulongYes, the fix is fine to me, we can go with that.14:09
*** jamesmcarthur has quit IRC14:11
*** vishalmanchanda has joined #openstack-meeting14:11
liuyulongWe have that original fix https://review.opendev.org/#/c/626830/ in our queens branch for a long time, in general it works fine.14:11
*** jamesmcarthur has joined #openstack-meeting14:12
liuyulongI will check our local logstash to see if it has such issue.14:13
liuyulongOK, no more bugs in the deputy list, let's give a quick scan of the the LP.14:14
liuyulong++,sorry, no more bugs related to L3 in the deputy list14:15
*** ociuhandu has quit IRC14:15
*** witek has left #openstack-meeting14:15
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186285114:17
openstackLaunchpad bug 1862851 in neutron "update_floatingip_statuses: StaleDataError: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched." [Undecided,New]14:17
*** jamesmcarthur has quit IRC14:17
haleybhi, sorry was in a downstream chat14:17
ralonsohthis is not the first time we have this bug14:17
liuyulongThis is a really common exception in DB related actions.14:18
haleybwe've seen those errors before ^^^, and that bug is against rocky14:18
ralonsohbtw, a patch for a previous bug related to this14:19
ralonsohhttps://review.opendev.org/#/c/503517/14:19
ralonsohhttps://bugs.launchpad.net/neutron/+bug/171632114:19
openstackLaunchpad bug 1716321 in neutron "StaleDataError: UPDATE statement on table 'standardattributes' expected to update 1 row(s); 0 were matched." [Undecided,Fix released]14:19
*** tesseract has quit IRC14:20
liuyulongYes, we have met this sometimes also, as far as we can see the exception does not have big effect to the neutron-api, the DB retry action could work.14:20
ralonsohexactly14:21
liuyulongOK, next14:22
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186187614:22
openstackLaunchpad bug 1861876 in neutron "[Neutron API] Neutron Floating IP not always have 'port_details'" [Critical,New]14:22
liuyulongA critical one, but I did not read the detail yet...14:22
slaweqI think it's fixed now (at least not so critical anymore)14:23
liuyulongI don't think floating IP has such "port_details" attribute. It is another L3 service_providers ?14:23
ralonsohthat was because OVN L3 pluging didn't have the correct mixin14:24
ralonsohthe nova bug is solved14:24
ralonsohand neutron one14:24
ralonsohhttps://review.opendev.org/#/c/705982/14:24
liuyulongAlright, maybe we can get it merged.14:26
liuyulongOK, that's all from me.14:27
liuyulongAny other bugs?14:27
slaweqI want to ask You to review https://review.opendev.org/#/c/702856/14:28
ralonsohsure14:28
slaweqliuyulong: I was playing with putting interface down on standby nodes but it didn't work as I wanted14:28
slaweqthere were some errors in keepalived logs during failover14:29
liuyulong: ), maybe I should submit our local fix.14:29
slaweqliuyulong: sure14:30
slaweqif You have something which really works without problems than we can review it14:30
liuyulongI will submit it today.14:30
slaweqliuyulong: thx14:31
liuyulongslaweq, np14:33
liuyulongOK, let's move on14:33
liuyulong#topic OVN_L314:33
*** openstack changes topic to "OVN_L3 (Meeting topic: neutron_l3)"14:33
*** anastzhyr has joined #openstack-meeting14:33
ralonsohmaciejjozefczyk, ping14:34
ralonsohlucasagomes,14:34
ralonsoh^^ any relevant update this week about OVN L3?14:34
lucasagomeshi there, not from my part14:34
liuyulongWe have a bug related to OVN gateway I remember.14:35
ralonsohbtw, we are still dealing with the CI14:35
liuyulong#link https://review.opendev.org/#/c/705660/14:35
liuyulongThis one14:35
*** Lucas_Gray has quit IRC14:35
lucasagomesyeah, specially on the func tests... I know maciejjozefczyk is looking into it. He's uploaded a new patch-set today14:35
maciejjozefczykliuyulong, Yes we have an OVN gateway related patch: https://review.opendev.org/#/c/705660/14:36
maciejjozefczykI needs to be on top of functional one, and those functional test failed on something else.14:37
maciejjozefczykI pushed today a fix to stablize part of functional tests related failures14:37
liuyulongYes, I noticed that, it is based on 3 parts of functional test fix.14:38
maciejjozefczykliuyulong, yes, actually the functional test that I needed to change is in the third part.14:39
liuyulongSo I wonder if the stable branch could have the fix reviewing in parallel ?14:40
liuyulongStable branch does not need to fix the functional test, right?14:40
maciejjozefczykliuyulong, potentially we could do a review in a stable networking-ovn branch and then apply it on master, but that breaks workflow a bit ;/14:41
*** eharney has joined #openstack-meeting14:41
maciejjozefczykliuyulong, or we can review this patch now, have agreement on its shape, then I can cherry-pick it, what do you think?14:42
maciejjozefczykliuyulong, actually tests that are failing are unrelated.14:42
*** jamesmcarthur has joined #openstack-meeting14:42
liuyulongBoth make sense for me, but IMO if it get merged first in networking-ovn, it will be more easily to backport to T/Q/R stable branches.14:44
liuyulongFor important patches, my idea is to quickly merge and benefits the end users.14:45
maciejjozefczykliuyulong, Ok, I'm gonna propose it in stalble/train first, we gonna have a discussion there. Then, if functional tests will be in place, we gonna merge it in Neutron master, agreed?14:46
slaweqI think that we should propose in master first and then do "cherry-pick" to networking-ovn14:47
*** masahito has joined #openstack-meeting14:47
*** jamesmcarthur has quit IRC14:47
slaweqI don't think we should change our normal workflow as maciejjozefczyk already said14:47
maciejjozefczykslaweq, liuyulong I'm ok with both, this change is important, but not a blocker.14:49
liuyulongSure, both works14:49
maciejjozefczykWould be great to have somebody eyes on it first :)14:50
liuyulong#link https://bugs.launchpad.net/neutron/+bug/186264814:51
openstackLaunchpad bug 1862648 in neutron "[OVN] Reduce the number of tables watched by MetadataProxyHandler " [High,Fix released] - Assigned to Lucas Alvares Gomes (lucasagomes)14:51
lucasagomesyeah that's an optimization to the ovn metadata anget14:52
lucasagomesagent*14:52
liuyulongAfter reading this bug, I have an idea, if we can ovn-metedata-agent someday by using some distributed proxies locally in the compute node.14:52
liuyulongsorry, my idea is to replace, "if we can replace"14:53
*** ociuhandu has joined #openstack-meeting14:53
liuyulonglet the ovn-controller do something instead of a python agent.14:54
lucasagomesit's something we could bring up with the OVN team itself, I've jsut heard of the idea so I don't know much about it atm14:56
liuyulongNp, we have a local topic which is trying to replace python neutron-metadata-agent with distributed proxies locally.14:57
*** ociuhandu has quit IRC14:58
liuyulongOK, time is up.14:58
liuyulongThank you guys, bye14:58
liuyulong#endmeeting14:58
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:58
openstackMeeting ended Wed Feb 12 14:58:56 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:58
ralonsohbye14:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-02-12-13.58.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-02-12-13.58.txt14:59
maciejjozefczykbye!14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_l3/2020/neutron_l3.2020-02-12-13.58.log.html14:59
*** jamesmcarthur has joined #openstack-meeting15:00
*** masahito has quit IRC15:10
*** artom has joined #openstack-meeting15:11
*** priteau has joined #openstack-meeting15:15
*** lbragstad has joined #openstack-meeting15:15
*** jamesmcarthur has quit IRC15:16
*** lpetrut has quit IRC15:24
*** ociuhandu has joined #openstack-meeting15:25
*** jamesmcarthur has joined #openstack-meeting15:31
*** rpittau is now known as rpittau|afk15:31
*** armax has joined #openstack-meeting15:45
*** ysandeep is now known as ysandeep|away15:50
*** jmasud has quit IRC15:50
*** jmasud has joined #openstack-meeting15:51
*** Trevor_V has joined #openstack-meeting15:55
*** TrevorV has quit IRC15:59
*** tesseract has joined #openstack-meeting16:02
*** jamesmcarthur_ has joined #openstack-meeting16:03
*** jamesmcarthur has quit IRC16:06
*** maciejjozefczyk has quit IRC16:06
*** jmasud has quit IRC16:12
*** jmasud has joined #openstack-meeting16:13
*** jiaopengju2 has quit IRC16:19
*** jiaopengju2 has joined #openstack-meeting16:20
*** ykatabam has quit IRC16:20
*** priteau has quit IRC16:38
*** priteau has joined #openstack-meeting16:39
*** macz has joined #openstack-meeting16:43
*** macz has quit IRC16:43
*** macz has joined #openstack-meeting16:44
*** jiaopengju2 has quit IRC16:46
*** jiaopengju2 has joined #openstack-meeting16:46
*** lucasagomes has quit IRC16:47
*** macz has quit IRC16:50
*** priteau has quit IRC16:51
*** gyee has joined #openstack-meeting16:52
*** jiaopengju2 has quit IRC17:00
*** jiaopengju2 has joined #openstack-meeting17:00
*** igordc has joined #openstack-meeting17:17
*** tesseract has quit IRC17:32
*** ociuhandu_ has joined #openstack-meeting17:32
*** ociuhandu has quit IRC17:36
*** ociuhandu_ has quit IRC17:37
*** anastzhyr has quit IRC17:43
*** jmasud has quit IRC17:43
*** jamesmcarthur_ has quit IRC17:47
*** vishalmanchanda has quit IRC17:51
*** dougsz has quit IRC17:59
*** igordc has quit IRC18:08
*** jamesmcarthur has joined #openstack-meeting18:18
*** eharney has quit IRC18:18
*** ijw has joined #openstack-meeting18:23
*** igordc has joined #openstack-meeting18:23
*** e0ne has quit IRC18:26
*** jamesmcarthur has quit IRC18:31
*** jamesmcarthur has joined #openstack-meeting18:31
*** jamesmcarthur has quit IRC18:42
*** jamesmcarthur has joined #openstack-meeting18:43
*** jamesmcarthur has quit IRC18:48
*** ijw has quit IRC18:53
*** jamesmcarthur has joined #openstack-meeting18:54
*** jamesmcarthur has quit IRC18:57
*** jamesmcarthur has joined #openstack-meeting18:58
*** yamamoto has quit IRC19:03
*** ralonsoh has quit IRC19:04
*** manuvakery has joined #openstack-meeting19:05
*** jamesmcarthur has quit IRC19:08
*** jamesmcarthur has joined #openstack-meeting19:09
*** jamesmcarthur has quit IRC19:13
*** eharney has joined #openstack-meeting19:17
*** jamesmcarthur has joined #openstack-meeting19:30
*** anastzhyr has joined #openstack-meeting19:31
*** jamesmcarthur_ has joined #openstack-meeting19:31
*** jamesmcarthur has quit IRC19:35
*** yamamoto has joined #openstack-meeting19:39
*** e0ne has joined #openstack-meeting19:40
*** e0ne has quit IRC19:51
*** yamamoto has quit IRC19:52
*** jamesmcarthur_ has quit IRC19:54
*** igordc has quit IRC19:58
*** LiangFang has quit IRC20:05
*** jmasud has joined #openstack-meeting20:37
*** armax has quit IRC20:45
*** armax has joined #openstack-meeting20:48
*** ChanServ has quit IRC20:50
*** zaitcev has joined #openstack-meeting20:50
*** artom has quit IRC21:12
*** ChanServ has joined #openstack-meeting21:13
*** orwell.freenode.net sets mode: +o ChanServ21:13
*** rfolco has quit IRC21:18
*** rcernin has joined #openstack-meeting21:18
*** sluna has quit IRC21:23
*** ociuhandu has joined #openstack-meeting21:37
*** zaitcev has left #openstack-meeting21:44
*** ociuhandu has quit IRC21:48
*** ociuhandu has joined #openstack-meeting21:49
*** ociuhandu has quit IRC21:52
*** manuvakery has quit IRC21:55
*** ykatabam has joined #openstack-meeting21:57
*** raildo_ has joined #openstack-meeting22:05
*** raildo has quit IRC22:08
*** jamesmcarthur has joined #openstack-meeting22:20
*** jamesmcarthur has quit IRC22:24
*** jamesmcarthur has joined #openstack-meeting22:25
*** slaweq has quit IRC22:26
*** slaweq has joined #openstack-meeting22:38
*** slaweq has quit IRC22:42
*** jamesmcarthur has quit IRC23:02
*** Trevor_V has quit IRC23:04
*** rh-jelabarre has quit IRC23:04
*** Adri2000 has quit IRC23:19
*** jmasud has quit IRC23:22
*** yamamoto has joined #openstack-meeting23:49
*** yamamoto has quit IRC23:54

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