Tuesday, 2024-02-20

opendevreviewMerged openstack/neutron-lib master: [S-RBAC] Add note about port:binding:profile field and SERVICE role  https://review.opendev.org/c/openstack/neutron-lib/+/90936601:05
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] "Logical_Router" pinned to chassis, OVN L3 scheduler  https://review.opendev.org/c/openstack/neutron/+/90919407:27
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] "Logical_Router" pinned to chassis, OVN L3 scheduler  https://review.opendev.org/c/openstack/neutron/+/90919407:45
opendevreviewRodolfo Alonso proposed openstack/neutron master: WIP === [OVN] Provide HA functionality to "Logical_Router" chassis pinning  https://review.opendev.org/c/openstack/neutron/+/90943707:45
opendevreviewArkady Shtempler proposed openstack/neutron-tempest-plugin master: Adds new Neutron Designate DNS integration test  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/85851807:58
*** mklejn_ is now known as mklejn10:33
opendevreviewMerged openstack/neutron-tempest-plugin master: Skip HA router tests when not meant for OVN driver  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90840811:00
*** dmellado74522 is now known as dmellado745211:06
opendevreviewRodolfo Alonso proposed openstack/neutron stable/zed: Change SG rules backref load method to "joined"  https://review.opendev.org/c/openstack/neutron/+/90858811:59
ralonsohslaweq, ykarel hi! if you have 2 mins: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90471011:59
ralonsohthanks in advance!11:59
*** dmellado74522 is now known as dmellado745212:00
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] "Logical_Router" pinned to chassis, OVN L3 scheduler  https://review.opendev.org/c/openstack/neutron/+/90919412:15
slaweq<ralonsoh> "slaweq, ykarel hi! if you have 2..." <- done12:16
ralonsohslaweq, thanks!12:17
ykarelack12:26
opendevreviewDr. Jens Harbott proposed openstack/neutron master: DNM: Testing netaddr bump  https://review.opendev.org/c/openstack/neutron/+/90931612:33
*** mklejn__ is now known as mklejn12:54
opendevreviewMerged openstack/ovn-octavia-provider master: [OVN][CI] Update OVS_BRANCH to be compatible with ovn main  https://review.opendev.org/c/openstack/ovn-octavia-provider/+/90832013:17
*** haleyb|out is now known as haleyb13:58
haleyb#startmeeting networking14:00
opendevmeetMeeting started Tue Feb 20 14:00:56 2024 UTC and is due to finish in 60 minutes.  The chair is haleyb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
opendevmeetThe meeting name has been set to 'networking'14:00
haleybPing list: bcafarel, elvira, frickler, mlavalle, mtomaska, obondarev, slaweq, tobias-urdin, ykarel, lajoskatona, jlibosva, averdagu, amotoki14:00
mlavalle\o14:00
slaweqo/14:01
ralonsohhello14:01
obondarevhi14:01
elvirao/14:01
frickler\o14:01
rubasovo/14:01
mtomaskacan't attend today :/14:01
ykarelo/14:01
haleybok, we can get started14:02
haleyb#topic announcements14:02
haleyb#link https://releases.openstack.org/caracal/schedule.html14:02
haleybGeneral libraries (except client libraries) need to have their last feature release this week14:03
lajoskatonao/14:03
haleybi have seen proposals for neutron-lib, etc14:03
haleybwe still had a few things in neutron-lib to merge i think14:03
haleyb#link https://review.opendev.org/q/project:openstack/neutron-lib+status:open14:03
ralonsohplease lets focus on these open reviews14:03
haleybyes, i will look right after meeting14:04
haleybClient libraries (think python-*client libraries) need to have their last feature release before Client library freeze (February 29, 2024)14:05
haleybi dont think that really affects us14:05
haleybFeb 26th-Mar 1st is C-3 milestone / feature freeze / requirements freeze14:05
haleybto complicate things (for me) i'm out this wednesday and friday, they didn't ask my kids school when to have break :)14:06
mlavallein regards to the neutron-lib reviews list. there are some that go as far as July of last year. Are those also priorities?14:07
ralonsohthe ones already reviewed and with zuul+114:07
mlavalleack14:08
lajoskatona+114:08
haleybi did have a question on the unmaintained core group after seeing a ML email on it14:12
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/message/ID6BUMR7XCGQQ6LPNLGYGPHCJAFYWJ5I/14:12
haleybTo summarize: you should only create your own separate group if you want 14:13
haleybto maintain the unmaintained branches yourself and don't want the larger 14:13
haleybgroup to do it for you.  Otherwise you have no such obligation.  If you 14:13
haleybare interested in helping with the unmaintained branches, it will help 14:13
haleybthe community more if you join the global team instead creating your own.14:13
haleybi haven't seen a follow-on to that yet14:13
lajoskatonathanks haleyb, so we have to ask permisison to that big group14:14
ralonsohwe should request a Neutron core vote for this14:14
lajoskatonaand we will have "root" permisison on all projects unmaintained/yoga now :-)14:14
fricklerwell ... "big" ;)14:14
lajoskatonafrickler: :-)14:14
ralonsohif 1) we want a independent group or 2) join the global one14:15
lajoskatonanot big by members but big by repsitiories?14:15
frickleryes, that may be true14:15
ralonsohif there is no quorum today, we can delay it to the next drivers meeting14:15
ralonsoh(but I think we have quorum)14:15
slaweqralonsoh neutron cores have (should have) nothing to do/vote here - unmaintained branches were created to free core groups from maintaining those old stuff14:16
ralonsohbut we are deciding if creating a neutron um group or not14:16
ralonsohshould this should be decided by neutron core14:16
slaweqIMO this should be decision of the people who wants to maintain those branches14:17
ralonsohok, then, I'll abandon the proposed patch https://review.opendev.org/c/openstack/project-config/+/908911 and leave to anyone independently to join the "big" group14:17
slaweqit is not neutron core group decision, can be if core team really wants to maintain it but the goal of unmaintained branches was different really14:17
haleybright, last week we started the process, but after that email i had a pause, since it would mean this core group would be the approvers14:17
slaweqso I want it to be clear here - neutron core team IS NOT responsible for unmaintained branches at all14:18
ralonsohyes, I know14:18
ralonsohbut the creation (or not) of this group is14:18
opendevreviewMerged openstack/ovsdbapp master: Update supported python versions  https://review.opendev.org/c/openstack/ovsdbapp/+/90399314:18
ralonsoh--> https://review.opendev.org/c/openstack/project-config/+/90891114:18
haleybslaweq: so if we create the group, it's only that group that can merge neutron* things, correct?14:21
slaweqhaleyb yes14:21
haleybwe then would each, if desired, need to join said group14:21
slaweqif anyone would be interested in doing so, then yes14:21
slaweqbut by default neutron core group or PTL shouldn't be core in that group automatically14:22
slaweqto not have any impression that core team is responsible for such branch14:22
frickleryou could also modify the acls to include openstack-unmaintained-core. but then the new group would be kind of redundant14:22
haleybslaweq: right, but it might just happen that way14:23
slaweqhaleyb yes, it can but not by default :)14:23
slaweqand I would really want to avoid doing it that way14:23
slaweqas then it will be no real change comparing to current EM thing14:24
mlavalleyeap, why make the change then14:24
slaweqmlavalle are You asking why is the "unmaintained" change done at all?14:25
haleybi think we have 6 (or 7?) cores here, do we want to vote?14:27
* haleyb was trying to wait for response there14:27
haleybif 1) we want a independent group or 2) join the global one14:27
frickleror 3) ignore unmaintained branches completely?14:28
mlavalleslaweq: I was just agreeing with you14:28
slaweqmlavalle ok :)14:28
ralonsoh2) is a personal option, option 3) is by default now14:29
haleybfrickler: last week we agreed there were some of us that didn't want that14:29
slaweqhaleyb are You asking if we as neutron cores want to join unmaintained group or create neutron unmaintained group and be part of it?14:29
ralonsohno14:29
ralonsohwe are not asking anyone to join this group14:29
ralonsohbut, of course, if no one is joinin it, it makes no sense14:29
haleybright, just if we wanted to make our own, i.e. merge that patch14:30
ralonsohok, let's finish this topic14:30
ralonsohanyone is able to join the "big" group if needed14:30
ralonsohI'll abandon the creation of this neutron um group14:30
lajoskatonaack, and unsetood14:30
ykarel+114:30
ralonsohwe'll retake it if needed14:30
haleyb+114:30
mlavalle+114:31
ralonsohdone14:31
haleybalright, anything else for announcements?14:31
haleyb#topic bugs14:31
haleybrubasov was bug deputy last week14:32
haleyb#link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/35WCRUGK3BD54NYJ2U6BEB5WHLJ5SHXO/14:32
rubasovthere's one unassigned bug14:32
slaweqhaleyb one thing to announcements14:32
slaweqquickly14:32
slaweqthere is nomination period of TC and PTLs open already14:32
slaweqif anyone is interested, please send Your nominations :)14:33
haleyboh right14:33
slaweqthat's all from me14:33
slaweqthx14:33
rubasovso, this ovn bug is unassigned: https://bugs.launchpad.net/neutron/+bug/205327414:33
haleybi was going to nominate myself for a second term14:33
slaweqhaleyb++ that's great14:34
lajoskatonahaleyb: cool, thanks14:34
haleybin case there was someone worried about next release14:34
mlavallehaleyb: thanks for your leadership. I wasn't worried just yet, but wondering14:35
opendevreviewMerged openstack/neutron-tempest-plugin master: Add router check, subnet attached gateway IP update or deletion  https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/90471014:35
haleybno problem, i've just been busy recently14:36
haleybrubasov: ack, i did see that mtu bug, seemed legit14:36
haleyband i think there is a way to address it, just a little complicated after looking at the code14:37
rubasovother than that the author of the rfe did not return yet, I don't know if he/she would want to contribute14:37
haleybdid anyone want to take that OVN bug? or i can ping the submittor to see if they have cycles?14:39
haleybalright, will drop a note in it14:40
ralonsohI can take it14:40
haleybralonsoh: ack, thanks14:41
haleyband just my weekly bug housekeeping14:41
haleybCurrent bug count this week: 745, down 25 from last week's 77014:42
haleybi spent some time closing some, as did ralonsoh i believe14:42
ralonsoh(I closed 15 yesterday)14:42
fricklersaw some pretty old ones fly by, good work14:42
haleybralonsoh: yes, thanks, when i noticed that i did the same14:43
haleybwill scrub some more once we go into freeze14:43
lajoskatona+1, I checked also some, but much lower than your numbers :-)14:43
haleybthe only good bug is a closed bug :)14:44
mlavalleindeed, LOL14:44
haleybthis weeks bug deputy is lucasagomes, next week is jlibosva14:45
haleyblucasagomes: you good triaging this week?14:45
haleybi don't see kuba here14:45
mlavalleI can ping both internally14:45
slaweqhaleyb I would go step further and say that the only good bug is invalid bug :P14:46
mlavallenaah, we want some feedback from the real world14:46
haleybslaweq: because we don't have bugs in our code, they're just using it wrong :)14:47
lajoskatona:D14:47
slaweqhaleyb exactly :D14:47
haleybalright, lets move on not much time left14:47
slaweqit's always PEBKAC14:47
haleybtopic #specs14:47
haleyb#link https://review.opendev.org/q/project:openstack%252Fneutron-specs+status:open14:47
haleybhmm, bad paste14:48
haleyb#link https://review.opendev.org/q/project:openstack-neutron-specs+status:open14:48
haleybstrange, still not working for me14:49
slaweqfirst link is ok for me14:49
ralonsohhttps://review.opendev.org/q/project:openstack/neutron-specs+status:open14:49
haleybthat's better14:49
haleybi realize we might not work on these this cycle, but if anyone has time can review14:50
haleyb#topic community_goals14:51
haleyb#link https://review.opendev.org/c/openstack/horizon/+/89120514:51
lajoskatonaI had some discussions with gtema from SDK team14:51
lajoskatonaand based on that I see better what is not working with tls_enabled, but there are still things I just guess there with SDK14:52
lajoskatonaso still fighting14:52
haleyblajoskatona: ack, thanks for the update14:53
haleybwill move on since we have two more items14:53
haleyb#topic on_demand14:53
haleybralonsoh: you had two things here14:53
ralonsohhttps://review.opendev.org/c/openstack/neutron-lib/+/90397114:53
ralonsohthis is incorrectly implementing an API extension14:54
ralonsohas commented in the patch14:54
ralonsohthe problem is that this is mimicing what was done before14:54
ralonsohthe question is: should we accept it as is now (again wrong) or request a correct (and more complex) implementation?14:54
ralonsohthis is affecting neutron-vpnaas14:55
haleybthat was my fault for approving14:55
lajoskatonaI was in it also14:55
ralonsohnot at all, there are many reviewers (me too)14:56
ralonsohwe are running out of time: please comment in the patch14:56
ralonsohsecond topic14:56
ralonsohhttps://bugs.launchpad.net/neutron/+bug/205420314:56
ralonsohbecause of a change in netaddr14:57
ralonsoh"101.12.13.00/24" is going to be considered as wrong14:57
ralonsohquestion here: is this an API regression or that was a previous bug14:57
frickleror any leading zeros in IP literals general14:57
ralonsohIMO: a previous bug, "101.12.13.00/24" should have never been a valid input14:57
haleybwhich i think is correct to be a bug, are you worried someone might have been using the api and relied on that?14:57
ralonsoh^^ exactly14:57
fricklerhaleyb: yes14:58
ralonsohyes, that's the point, if anyone is using it now 14:58
ralonsohagain, we are running out of time, please comment in the LP bug14:58
tkajinamthat 101.12.13.00 is a specific case which may look like invalid, but please note that the change would reject a few more different patterns like 10/814:59
ralonsohsorry, I don't understand that one14:59
tkajinamthat's the core concern and the reason why I said "at least"14:59
ralonsoh10/8?14:59
tkajinam10/8 is translated to 10.0.0.0/814:59
ralonsohand that was a valid input?15:00
haleybwe are out of time, please follow-up in the bug and/or review15:00
frickleryes. or just "1". see also https://bugs.launchpad.net/neutron/+bug/2054435 for an related issue that this discovered15:00
haleybbut i don't think 10/8 should be valid either15:00
tkajinamwill post a comment in a bug with some more details15:00
ralonsohthanks15:00
tkajinamjust wanted to highlight this may not be a trivial bug15:01
haleyb#endmeeting15:01
opendevmeetMeeting ended Tue Feb 20 15:01:13 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
opendevmeetMinutes:        https://meetings.opendev.org/meetings/networking/2024/networking.2024-02-20-14.00.html15:01
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/networking/2024/networking.2024-02-20-14.00.txt15:01
opendevmeetLog:            https://meetings.opendev.org/meetings/networking/2024/networking.2024-02-20-14.00.log.html15:01
haleybthanks for attending, have neutron-ci meeting right now15:01
lajoskatonao/15:01
ykarel#startmeeting neutron_ci15:01
opendevmeetMeeting started Tue Feb 20 15:01:54 2024 UTC and is due to finish in 60 minutes.  The chair is ykarel. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
opendevmeetThe meeting name has been set to 'neutron_ci'15:01
ykarelThis will be video meeting today: https://meetpad.opendev.org/neutron-ci-meetings15:02
ralonsohhello15:02
ykarelping bcafarel, lajoskatona, mlavalle, mtomaska, ralonsoh, ykarel, jlibosva, elvira15:02
mlavalleykarel: video this week?15:02
ykarelyeap15:02
lajoskatonao/15:03
ykarel#topic Actions from previous meetings15:04
ykarelralonsoh to send patch for functional failure for NetworkInterfaceNot found issue15:04
ykarel#link https://review.opendev.org/c/openstack/neutron/+/90938515:04
opendevreviewyatin proposed openstack/neutron master: Enable logging for scheduler functional tests  https://review.opendev.org/c/openstack/neutron/+/90959015:05
ykarelykarel to check failure in test_auto_schedule_router15:05
ykarelhttps://review.opendev.org/c/openstack/neutron/+/90959015:05
ykarel#topic Stable branches15:05
ykarelall good15:06
ykarel#topic Stadium projects15:06
ykarelperiodic green15:06
ykarel#topic Rechecks15:06
ykarel3/9 bare rechecks15:07
ykarel#topic fullstack/functional15:07
ykarelNetworkInterfaceNotFound15:07
ykarelhttps://36d827c3b1c315f941c5-25d2473a8435e86d2da970876b6bac73.ssl.cf1.rackcdn.com/909147/1/gate/neutron-functional-with-uwsgi/8f21c8a/testr_results.html15:07
ykarelhttps://d8e1d98dffdc278e1978-d367ceb2d3289c9a141d614bfa7b9335.ssl.cf1.rackcdn.com/908587/2/gate/neutron-functional-with-uwsgi/341f73b/testr_results.html15:07
ykarelhttps://4622e0f521fe7ef77d9d-3fa6c7b03298e65764ba8baf4a8a5f26.ssl.cf1.rackcdn.com/periodic/opendev.org/openstack/neutron/master/neutron-functional-with-sqlalchemy-master/b6b4c83/testr_results.html15:07
ykarelhttps://40435b1c258f5ac27bbf-77898a6eec3a425de21ff1866f14fdfb.ssl.cf5.rackcdn.com/periodic/opendev.org/openstack/neutron/master/neutron-functional-with-oslo-master/48e3773/testr_results.html15:07
ykarelhttps://11573cfdd1061b394e98-004d3431496c0f87d52b52d1bec387e7.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/neutron/master/neutron-functional-with-oslo-master/d47dd98/testr_results.html15:07
ykarelhttps://a8f58a33b71dbdbaeaf0-b8f5baac1536449624f55cad0c5791e8.ssl.cf2.rackcdn.com/periodic/opendev.org/openstack/neutron/stable/2023.1/neutron-functional/dfd5463/testr_results.html15:07
ykareltest_bw_limit_qos_no_rules_l2_agent_restart(ingress) timeout at _wait_for_bw_rule_applied15:07
ykarelhttps://28c7dba65a3263b7dc56-ac03866ed76044a5727f648521330347.ssl.cf2.rackcdn.com/873699/57/check/neutron-fullstack-with-uwsgi/179f96c/testr_results.html15:07
ykarel#action ykarel to check fullstack failure15:09
ykarel#topic Tempest/Scenario15:09
ykarelDetails: (ServerStableDeviceRescueTest:test_stable_device_rescue_disk_usb) Image 5003f8b5-2980-4aa2-af11-9be9573b4350 failed to reach ACTIVE state (current state SAVING) within the required time (300 s).15:09
ykarelhttps://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_a37/874760/56/check/neutron-ovn-tempest-ipv6-only-ovs-release/a37f9d3/testr_results.html15:09
ykarel#topic Periodic15:10
ykarel#topic Grafana15:10
ykarelhttps://grafana.opendev.org/d/f913631585/neutron-failure-rate?orgId=115:10
ykarel#action ykarel to check grenade status 15:12
ykarel#topic On Demand15:12
mlavallehttps://review.opendev.org/c/openstack/neutron/+/90151315:13
ykarelhttps://review.opendev.org/c/openstack/neutron-tempest-plugin/+/908408?usp=search15:14
ykarel#endmeeting15:15
opendevmeetMeeting ended Tue Feb 20 15:15:17 2024 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:15
opendevmeetMinutes:        https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-02-20-15.01.html15:15
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-02-20-15.01.txt15:15
opendevmeetLog:            https://meetings.opendev.org/meetings/neutron_ci/2024/neutron_ci.2024-02-20-15.01.log.html15:15
ralonsohbye15:15
lucasagomeshaleyb, sorry I was having lunch15:28
lucasagomeshaleyb, all good triaging it this week o/15:28
haleyblucasagomes: no problem, happy triaging! :)15:28
lucasagomeso/15:28
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for Static Routes  https://review.opendev.org/c/openstack/neutron/+/90748915:35
crohmannCould someone kindly help me understand why openstack cli does respond with "Floating ip pool operations are only available for Compute v2 network." when asking for "floating ip pool list"?15:55
crohmannThe error msg originates from https://github.com/openstack/python-openstackclient/blob/2eea916b35fd6f01947dce168c50c314ed9072db/openstackclient/network/v2/floating_ip_pool.py15:55
fricklercrohmann: because floating ip pools were a thing only for nova networking? now floating IPs are assigned from the "normal" allocation pool in a subnet16:01
opendevreviewJayce Houtman proposed openstack/neutron master: Change exception messages to error log messages for DNS integration.  https://review.opendev.org/c/openstack/neutron/+/90021216:18
tkajinamhaleyb, hi. I'm wondering how I can move https://review.opendev.org/c/openstack/neutron-lib/+/902133 forward. Unfortunately I've not heard any feedback frm the charm team about https://review.opendev.org/c/openstack/charm-octavia/+/902499 . I've left some comments in their irc channel to ask their attention but it'd be appreciated if you can help that conversation if you know these people.16:34
tkajinammy main concern is that the logic has been removed from neutron. if charm still relies on that lbaas v2 owner and associated settings which was previously done by neutron, then we should fix one of neutron or charm-octavia.16:35
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for Static Routes  https://review.opendev.org/c/openstack/neutron/+/90748917:00
haleybtkajinam: let me ping frode17:06
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for SNAT rules  https://review.opendev.org/c/openstack/neutron/+/90791517:26
crohmannfrickler: Understood. But I was just a little puzzled, because there is "floating ip list", kinda the same signature of commands. Maybe that whole command could actually be dropped (at some point)?20:47
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for Static Routes  https://review.opendev.org/c/openstack/neutron/+/90748920:49
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for SNAT rules  https://review.opendev.org/c/openstack/neutron/+/90791520:52
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for Static Routes  https://review.opendev.org/c/openstack/neutron/+/90748920:54
opendevreviewRoberto Acosta proposed openstack/neutron master: [ML2/OVN] Add external_ids key for SNAT rules  https://review.opendev.org/c/openstack/neutron/+/90791520:55
zambai want to bridge a physical layer 2 network into one of my instances, how can i do this?21:18
opendevreviewMerged openstack/neutron master: [S-RBAC] Change policies for port's binding:profile field  https://review.opendev.org/c/openstack/neutron/+/90907521:36
opendevreviewMerged openstack/neutron master: Enable logging for scheduler functional tests  https://review.opendev.org/c/openstack/neutron/+/90959022:14
opendevreviewRodolfo Alonso proposed openstack/neutron master: [OVN] Provide HA functionality to "Logical_Router" chassis pinning  https://review.opendev.org/c/openstack/neutron/+/90943722:41
opendevreviewMerged openstack/neutron master: Fix invalid IP address representation in unit test  https://review.opendev.org/c/openstack/neutron/+/90931723:14

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!