Tuesday, 2023-04-04

opendevreviewliang jiechao proposed openstack/nova-specs master: Generic vdpa spec  https://review.opendev.org/c/openstack/nova-specs/+/87933802:09
opendevreviewliang jiechao proposed openstack/nova-specs master: Generic vdpa spec  https://review.opendev.org/c/openstack/nova-specs/+/87933802:15
opendevreviewliang jiechao proposed openstack/nova-specs master: Generic vdpa spec  https://review.opendev.org/c/openstack/nova-specs/+/87933804:45
*** elodilles_pto is now known as elodilles08:04
opendevreviewKonrad Gube proposed openstack/nova-specs master: Re-propose using extend volume completion action for 2023.2  https://review.opendev.org/c/openstack/nova-specs/+/87723308:38
kgubeHi bauzas, could you have a look at my spec? https://review.opendev.org/c/openstack/nova-specs/+/87723308:50
kgubeYou had some issues with the implemtentation for Antelope that might be better to discuss at the spec level: https://review.opendev.org/c/openstack/nova/+/87356008:50
bauzaskgube: ack, will try to do todaty08:50
kgubethanks!08:51
sahidlajoskatona: o/ if that sounds right for you I'm taking the lead to migrate nova on openstacksdk https://etherpad.opendev.org/p/python-neutronclient_deprecation11:20
lajoskatonasahid: cool, thanks for checking it11:54
opendevreviewAlexey Stupnikov proposed openstack/nova stable/xena: Add debug log for scheduler weight calculation  https://review.opendev.org/c/openstack/nova/+/87940412:23
opendevreviewAlexey Stupnikov proposed openstack/nova stable/wallaby: Add debug log for scheduler weight calculation  https://review.opendev.org/c/openstack/nova/+/87940512:24
dansmithbauzas: what regression do you think the long-wait change introduced?13:33
bauzasdansmith: well, I don't really know but the test you modified was hit13:33
dansmithuh, okay :)13:34
dansmithbauzas: it's failing on create server, I only modified the attach volume line13:36
dansmithso I think it's not likely related13:36
bauzasok13:36
wangrongdansmith: hello Dan, based on our previous agreement, we have prepared the relevant spec and would like you to review them. If you have any questions, please contact with us anytime. Thank you! 13:50
wangrong https://review.opendev.org/c/openstack/nova-specs/+/87729113:50
dansmithwangrong: that's my spec that I showed you as an example.. did you paste the wrong link?13:51
wangrongdansmith: oh, sorry, my bad...13:53
wangrongdansmith: https://review.opendev.org/c/openstack/nova-specs/+/87933813:53
wangrongdansmith: I think this the one we posted13:54
dansmithwangrong: cool, sean-k-mooney is the one that needs to do most of the review, but I'll try to take a first stab later today as well13:54
dansmithbauzas: also cc ^ as discussed maybe you can provide some early feedback like we promised13:54
bauzascool13:54
wangrongsure, thank you very much, so appreciate your help, dansmith, bauzas and sean-k-mooney .13:57
bauzasas a reminder, due to European DST change one week before, the nova meeting will be in ~2 hours14:02
bauzas(still the same UTC time, in case you're not in Europe)14:03
TheJuliaAre there any known issues on grenade from 2023.1 to master in regards to flavors? Specifically we're seeing a ~40% failure rate for grenade jobs on ironic, nova is specifically reporting the flavor baremetal is not found when it was added 5+ minutes earlier in the logs.  Looks like post-create (200 response code), a lookup for it immediately fails with a 404. 15:11
TheJuliahttps://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_b1d/879215/3/check/ironic-grenade/b1d6cf4/controller/logs/screen-n-api.txt15:11
TheJuliaand the returned flavor does indicate it is public, btw.15:17
sean-k-mooneyit might be related to srbac15:37
sean-k-mooneytempest need to be using proejct scoped tokens15:37
sean-k-mooneybut im not really aware of anythng that woudl cause that other then srbac15:37
sean-k-mooneyand i would not expect it to be flaky in that case15:38
sean-k-mooneyso im not sure what explains the 40% rate15:38
bauzasgentle reminder : nova meeting in 10 mins here15:50
fricklerTheJulia: I think that 404 is a red herring, it is OSC first trying to use the name_or_id parameter as ID. you should see the same in passing runs15:59
bauzas#startmeeting nova16:00
opendevmeetMeeting started Tue Apr  4 16:00:04 2023 UTC and is due to finish in 60 minutes.  The chair is bauzas. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
opendevmeetThe meeting name has been set to 'nova'16:00
bauzashey folks16:00
bauzashope you had a good PTG16:00
Ugglao/16:00
bauzas#link https://wiki.openstack.org/wiki/Meetings/Nova#Agenda_for_next_meeting16:00
elodilleso/16:00
* bauzas again misses all of you16:00
TheJuliasean-k-mooney: I looked at the query on the db, just looks like it is not there based upon the error. Only option I have is to attempt local reproduction most likely.16:00
auniyalo/16:01
bauzasTheJulia: sorry but we just started our weekly meeting16:01
TheJuliaI'm aware16:01
* bauzas awaits for folks to be arriving16:01
dansmitho/16:01
gibio/16:02
bauzasok, let's start then16:03
bauzas#topic Bugs (stuck/critical) 16:03
bauzas#info No Critical bug16:03
bauzas#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 22 new untriaged bugs (+5 since the last meeting)16:03
bauzassorry I didn't had time to look at all the bugs 16:03
bauzasthat said, I think we could quickly close some of them when I just opened ^16:04
bauzasso,16:04
bauzasI'll continue to have the bug baton for this weeek16:04
bauzas#info Add yourself in the team bug roster if you want to help https://etherpad.opendev.org/p/nova-bug-triage-roster16:04
bauzas#info bug baton is being passed to bauzas16:04
bauzasany bug to discuss before we move ?16:04
bauzaslooks not16:05
bauzas#topic Gate status 16:06
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:06
bauzas#link https://etherpad.opendev.org/p/nova-ci-failures16:06
bauzasI need to look again on the ci failures16:06
dansmithI haven't had anything in the gate since before PTG, but it sounds like things are sucking a gain?16:06
bauzasI saw some other issues so I'll try to verify whether they are a lot16:06
bauzasdansmith: unfortunately yes, see for example https://review.opendev.org/c/openstack/nova/+/875621 and https://review.opendev.org/c/openstack/nova/+/87869316:07
bauzasanyway, let's move on16:08
bauzas#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&pipeline=periodic-weekly Nova&Placement periodic jobs status16:08
bauzasall greens :)16:09
bauzas#info Please look at the gate failures and file a bug report with the gate-failure tag.16:09
bauzas#info STOP DOING BLIND RECHECKS aka. 'recheck' https://docs.openstack.org/project-team-guide/testing.html#how-to-handle-test-failures16:09
bauzasthat's it16:09
bauzasmoving on ?16:09
bauzaslooks so16:11
bauzas#topic Release Planning 16:11
bauzas#link https://releases.openstack.org/bobcat/schedule.html16:11
bauzas#link https://review.opendev.org/c/openstack/releases/+/877094 Proposed deadlines for Bobcat16:11
gmanno/16:11
bauzasas I said on Friday, I eventually provided a new revision 16:11
bauzas#link https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_2b8/877094/3/check/openstack-tox-docs/2b8febf/docs/bobcat/schedule.html Generated HTML for proposed deadlines16:11
bauzasplease review those dates16:12
bauzasbefore tomorrow16:12
bauzas#info Nova contributors should review this change before tomorrow 1600UTC.16:12
bauzasI added one stable review day16:12
bauzasand I added a second feature review day16:12
bauzason milestone-1 we could review the stable branches16:13
elodilles++16:13
bauzasthen we'll have one spec review day *before* the summit16:13
bauzasand another one two weeks after the summit (one week before spec feature freeze)16:13
bauzasspec approval freeze sorry16:14
bauzasthen, on the day after the spec approval freeze, we could review some series from accepted blueprints16:14
bauzasand eventually, a second implementation review day the last week of July16:15
bauzas(which would be 5 weeks before FF)16:15
bauzasthat's it.16:16
bauzaswe could review some series on the week before FF, but honestly, I think it's late (and also I'll just be back from PTO)16:16
bauzasso I'd prefer to tell the blueprints owners to provide their series one month before (as we also discussed during the PTG)16:17
bauzasanyway, as a reminder, please review https://review.opendev.org/c/openstack/releases/+/877094 before tomorrow 1600UTC16:17
bauzasagain, that's it on this topic for me16:18
bauzasmoving on, I guess16:19
bauzasoh, last point16:19
bauzas#info Bobcat-1 is in 5 weeks.16:19
opendevreviewMerged openstack/nova master: Update min support for Bobcat  https://review.opendev.org/c/openstack/nova/+/87562116:19
bauzaswoooohoooooooooooooooooooooooo16:19
bauzas^16:19
bauzasso, next topic16:20
bauzas#topic vPTG feedback 16:20
bauzas#link https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033124.html16:20
bauzasI provided an email summary ^16:20
bauzasbtw. heh, sorry about s/NFV/NFS :p16:20
bauzas-ETOOMANYNETWORKINGDISCUSSIONS16:21
elodilles:)16:21
bauzasanyway, it was more a FYI16:21
bauzas#topic Review priorities 16:21
bauzas#link https://review.opendev.org/q/status:open+(project:openstack/nova+OR+project:openstack/placement+OR+project:openstack/os-traits+OR+project:openstack/os-resource-classes+OR+project:openstack/os-vif+OR+project:openstack/python-novaclient+OR+project:openstack/osc-placement)+(label:Review-Priority%252B1+OR+label:Review-Priority%252B2)16:21
bauzas#info As a reminder, cores eager to review changes can +1 to indicate their interest, +2 for committing to the review16:21
bauzasnext topic16:22
bauzas#topic Stable Branches 16:22
bauzaselodilles: before I'm asking you, let me first add something :)16:22
elodillessure :)16:22
bauzas#link https://review.opendev.org/c/openstack/releases/+/878860 Xena stable branche EM proposal16:22
bauzasso,16:22
bauzasI said last week we should discuss the Xena EM approval this week16:22
bauzas#link https://review.opendev.org/q/project:openstack/nova+branch:stable/xena+is:open16:23
bauzasthose are the open changes we have16:23
bauzasso, question16:23
opendevreviewRajesh Tailor proposed openstack/nova master: Fix trivial doc issues  https://review.opendev.org/c/openstack/nova/+/87877916:23
bauzasdoes anyone want to have their series be merged in xena before we EM ?16:24
*** iurygregory_ is now known as iurygregory16:24
bauzasas a reminder, we can continue to merge patches in that branch16:24
bauzasthis is just we won't have an upstream .z or .y release after EM tag16:25
bauzasanyone ?16:25
auniyalthis is a clean backport for xena https://review.opendev.org/c/openstack/nova/+/87406616:25
elodillesjust an addition to what bauzas said: anyone see any patch that "would be good to get merged & released as final"?16:26
elodillesin xena16:26
bauzaselodilles: maybe we could wait for https://review.opendev.org/c/openstack/nova/+/866156 to be merged16:26
bauzassince it's a bit of a regression16:26
bauzasand yoga was merged16:27
elodillesbtw, we have a tracking pad if needed: https://etherpad.opendev.org/p/nova-stable-xena-em16:27
elodillesso we can add these patches there ^^^16:27
sean-k-mooneyill review that backport now16:27
bauzasauniyal: the problem is that the patch you proposed needs to have its yoga backport approved before16:27
elodillesand (stable) cores could review them when they have time16:27
elodillesi can also help with some reviews hopefully16:28
bauzaselodilles: remind me when the deadline for Xena EM is ?16:28
auniyalyeah my bad its not merged in yoga16:28
elodilleswell, the transition date is April 20th16:28
elodillesshould be good to release earlier though16:29
bauzasok, then we'll track the progress every week16:29
bauzasand every week, I'll ask the question16:29
elodillesmaybe we can see if next week we can cut a release16:29
bauzasin the meantime, people can merge whatever they want16:29
bauzaselodilles: yup16:29
bauzasdon't disagree16:29
elodillesnote also, that we had a xena release around end of january (24.2.0)16:30
bauzas#link https://etherpad.opendev.org/p/nova-stable-xena-em Tracking etherpad for Xena 16:30
elodillesso really the open patches is mostly the ones that we need to consider16:30
sean-k-mooneybauzas: i have approved the mdev patch16:31
bauzas#info please tell the nova community which patches you want to have to be released before next week by pinging bauzas on IRC16:31
sean-k-mooneyjust skimin gthe open ones now16:31
bauzascool thanks16:31
bauzasanyway, elodilles, add your points now16:31
elodilles++16:31
elodilleswell, there is nothing left just the usual16:31
elodilles#info stable gates seem to be OK - though it's hard to merge patches due to intermittent failures16:31
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:31
bauzascool16:33
bauzaslast topic then16:33
bauzas#topic Open discussion 16:33
bauzasthe agenda is empty16:33
auniyalso I was looking for backports in 2023.1, zed and yoga16:33
bauzasanyone wants to discuss about something that we missed at the PTG ?16:33
gibibauzas: the lower constraint job discussion was punted last week16:34
bauzasgibi: yup, I haven't asked you if you wanted to discuss about it today16:35
gibibauzas: I have not much to add to what was in the current or in the previous PTG etherpad just that I have the intention to add a limited lower constraint job16:35
bauzasgibi: do you want now ?16:35
gibiwe can16:35
bauzascool16:35
bauzas(we also have other punted topics, but again, those were not prioritary for this week)16:36
bauzasgibi: so, shoot16:36
gibiyeah, this is not priority either16:36
bauzaswe discussed your topic briefly16:36
bauzasconcerns were coming from any potential transitive dependencies and the scope 16:36
gibiso I see that sean-k-mooney prefer not to have it16:37
bauzaswe said this was for unittests and functionaltests16:37
dansmithgmann also had comments I think16:37
gibiso the scope is intentionally limited16:37
bauzascorrect16:37
sean-k-mooneyi do not wnat nova to be the only ones to have it if we do i would prefer it to be a perodic16:37
gibiso run unit and functional test, only with the some of our direct depds pinned to lowest16:37
bauzasand if I'm not wrong, this wouldn't be having transitive deps in the filez16:37
bauzasfile16:37
gibino transitives yes16:37
sean-k-mooneyim more or less ok with that but limitation 16:38
bauzasok, then I wasn't wrong16:38
dansmithI didn't hear the pitch about why we should, but I too am a bit skeptical16:38
bauzasdansmith: it was due to a regression we had with os-traits16:38
bauzaswe modified the code by using the new traits16:38
gibidansmith: in Zed we released nova code that depended on os-traits versions but we forgot to bump the version16:38
gmanngibi: did you try how it will run with nova as lower bound and other deps's deps as upper bound ?16:38
bauzasthat yeah16:38
gibigmann: not yet, I had some local trials but mostly got sidetracked 16:38
gmannI am ok to run unit test lower bound job but just wondering how complex it will be to setup and keep green16:39
dansmithtraits is kinda weird though right? we sort of always need that to move in lockstep with our usage of it yeah/16:39
gmanngibi: ack16:39
dansmithso requirements and the lower constraint is always the same?16:39
dansmithit's not like libvirt where we actually want to support a range of older and newer versions16:39
gibidansmith: yeah, in case of os-traits we have a fairly hard connection16:40
gmannI think we need to keep lower constraint file as requirements.txt constraints might be higher than lowest supported versions16:40
dansmithso was the miss that we always get the latest os-traits from other stuff and we didn't notice we needed a bump?16:40
sean-k-mooneygmann: they should not be16:40
gmannor gibi you want to test what we have in requirements.txt as lower bound and not actual lower bound ?16:40
gibigmann: I thought that the minimum in requiremenets.txt is the lowest we need to test with16:40
gmannok16:40
sean-k-mooneyrequirements has our lower bound16:40
sean-k-mooneywhile lower version might work if you dont use all features16:41
gmannsean-k-mooney: yeah but they are no guaranteed to be lowest bound, we can have b>8 where it might work b==6 also16:41
gibidansmith: os-vif is a bit softer, i.e. lower != higher, but we can break the dep the same way16:41
dansmiththat's true of libvirt but probably less so os-traits16:41
sean-k-mooneygmann: if you use somthing older then in in requiremtns i would say thats an unsupported config16:41
dansmithso is the proposal to maintain a separate list, or to sed the >= out of requirements.txt?16:42
bauzasdo people say we shall pin our versions in reqs.txt ?16:42
gmannthat is why there are two things 1. test what we have lower bound in requirements.txt 2. test actual lower(st) bound work for nova16:42
gibidansmith: basically sedding the requirements.txt16:42
dansmithgibi: okay if it's that, and periodic, then I'm okay with it.. what I don't want is a second list and pre-merge testing (just because of the load)16:42
sean-k-mooneywe dont want to do 216:42
bauzashah16:42
bauzasso, s/>=/== then ?16:43
sean-k-mooneywe could do 1 16:43
gibidansmith: ack, I'm OK to make it periodic16:43
gmannyeah, doing 2 is difficult 16:43
bauzasautomatically from reqs.txt ?16:43
dansmithbauzas: yeah, I think that's reasonable16:43
sean-k-mooneyi would say 2 is a non goal16:43
gibibauzas: that is the idea16:43
gmannI am ok to doing 1 and even in check pipeline as unit test also ok16:43
gmannsean-k-mooney: yes16:43
bauzasso a specific tox target ?16:43
gibibauzas: yepp16:43
bauzasto -epy38-min ?16:43
gmannyeah, that will be helpful to check locally also16:44
bauzasok, then I don't disagree the idea16:44
dansmitha specific tox target that runs both in a single go would be nice to avoid needing separate unit/functional jobs yeah16:44
bauzasI see16:44
dansmithand I'd prefer periodic until/unless we see it breaking more often16:44
gibisean-k-mooney, gmann : I agree to aim for 1. If somebody want to find the real lower bound (i.e 2) then that person can play with the requirements.txt and with the new job16:44
bauzasso the tox target would call out a script that would copy/sed reqs.txt by pinning to the mins 16:44
gmanngibi: agree16:45
gibibauzas: yeah16:45
bauzasand the gate would periodically run a job that would call this target 16:45
bauzasthen I don't disagree16:45
gibicool16:45
gibiI see an agreement forming :)16:45
bauzasanyone having concerns ?16:45
gibi(now I need to find the time to do the scripting)16:46
bauzassay it now or forever hold your peace16:46
bauzascrickets, all cool16:46
gibithanks16:46
gibiand sorry again for missing the firday sessions16:46
gibiFriday even16:46
bauzas#agreed gibi to work on a new tox target that would run unittests with a pinned min version of reqs.txt, with a periodic job testing it weekly16:47
bauzasgibi: I guess you may want to do it as well for functional tests but this doesn't harm to me16:47
gibibauzas: yeah, lets see the unit first, adding functional to it is easy then16:48
bauzascool16:48
bauzasI think dust is settled now16:48
bauzasanything else before I call it a wrap ?16:48
auniyalbauzas, I dont have anything w.r.t PTG missing item, can we discuss few backports ?16:48
gibiI've updated the etherpad with the link to this meeting log16:48
bauzasgibi: excellent for tracking decisions16:49
bauzasauniyal: are you asking for specific change reviews ?16:49
auniyalI have few backports which can be merged mostly for zed and yoga, I have reviewed them from my end, I would like to request cores to review them 16:49
bauzasif so, I'd prefer if you could ping folks off the meeting16:49
bauzas(we generally try to avoid review requests during the meeting, for obvious reasons)16:50
auniyalokay16:50
bauzas(the main one is brevity)16:50
bauzasok, so, last call ?16:50
bauzasthanks all16:51
bauzas#endmeeting16:51
opendevmeetMeeting ended Tue Apr  4 16:51:56 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:51
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2023/nova.2023-04-04-16.00.html16:51
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-04-04-16.00.txt16:51
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2023/nova.2023-04-04-16.00.log.html16:51
gibio/16:51
elodillesthanks o/16:52
bauzasthat's also it for me today16:53
bauzassee ya folks16:53
bauzasfor the fun, I want to test virtiofs on my laptop with a windows guest :)16:54
bauzaswaaah that works with winfcp16:57
dansmithgibi: sean-k-mooney: can ya'll hit this at some point: https://review.opendev.org/c/openstack/nova/+/87823817:01
dansmithrelated to a recent conversation we had17:01
gibidansmith: added to my list17:04
dansmiththanks17:04
opendevreviewDan Smith proposed openstack/nova master: Add compute_id column to instances table  https://review.opendev.org/c/openstack/nova/+/87949917:42
opendevreviewDan Smith proposed openstack/nova master: Add compute_id to Instance object  https://review.opendev.org/c/openstack/nova/+/87950017:42
dansmithanyone else having trouble with the fast8 target? it's complaining about python not being in the list of allowed externals, presumably because of the install_command override17:45
dansmithadding it causes it to fail install because it tries to install nova to my /usr/local instead of the venv17:46
dansmithother targets don't seem to have any problems17:46
clarkbpython shouldn't be in externals because it is in the venv17:48
dansmithI know that's how it should work17:48
dansmithokay I blew away .tox and it may be working17:50
dansmithI cleaned a(n apparently very old) .tox/fast8 before and it didn't fix it, but I think because flake8 now uses .tox/shared17:50
dansmithso removing that seems to have fixed it up17:50
dansmithI dunno how it got confused about that, but it was the python pip install on the nova package that it was failing with that error17:51
dansmithso maybe something to do with me recently upgrading to py311 on my system17:51
dansmithyeah, that worked17:51
dansmiththe pep8 target worked, but I guess it doesn't use the shared venv so I guess it got rebuilt and the one fast8 uses didn't trigger it or soemthing17:54
sean-k-mooneyit could be related to the fact we now dont set useddevelop17:59
sean-k-mooneyor what ever17:59
dansmithwe still do for all the regular venvs, AFAICT18:01
dansmithI think it's more likely a stale bin/python link in that venv pointing to the old python3.10 on my system or something18:01
sean-k-mooneyas in i cant fine the sepcific thing i was likign for18:01
sean-k-mooneyit might be related to this https://github.com/openstack/nova/commit/5e5b6751d32aa50dc372c55b5c2044d0dade51f418:02
sean-k-mooneybut i toug we change how ew used sdigts18:02
sean-k-mooneyi tought we did somethign for tox 418:02
dansmithyeah, that added isntall_command which was the problem18:02
sean-k-mooneyok ya that was the tox 4 change https://review.opendev.org/c/openstack/nova/+/86954518:03
sean-k-mooneyi tought thact actully bumped the min version to 4 but it did not18:04
sean-k-mooneyjust made it compatible18:04
sean-k-mooneydansmith: im going to call it a day but this is the youtube link i added to the vdpa spec https://www.youtube.com/watch?v=zyDSUU0TLB4 its not that long but it answered some of my questions18:55
dansmithI saw the link but haven't watched it18:55
dansmithcool18:55
sean-k-mooneyi think we are going to want two flags hw_disk_bus=vdpa-blk and then a second flag for if it requires hardware offload18:56
sean-k-mooneyif we want to supprot the software and hardware backends eventually18:56
dansmithhmm okay I guess I don't know why we'd need two flags, but I'm sure it's ignorance.. I'll watch, we can chat tomorrow or later18:57
sean-k-mooneywell its vdpa-blk in the guest in either caes but ya watch the vid and we can chat about it whenever18:57
sean-k-mooneyo/18:57
dansmitho/18:58
opendevreviewMerged openstack/nova stable/yoga: db: Resolve additional SAWarning warnings  https://review.opendev.org/c/openstack/nova/+/87406519:34

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