Tuesday, 2023-08-15

gibisean-k-mooney: as we really like shelve/unshelve to clean up messy situations this bugfix probably very useful https://review.opendev.org/q/topic:bug%252F202548010:01
kevkoHi everyone, i would like to ask if someone can approve this blueprint proposed by my colleaguage Viktor Krivak, we already have a code implemented but waiting for specs approval , so we can send patches to gerrit...could someone look into please ? https://review.opendev.org/c/openstack/nova-specs/+/890779 , thank you very much 10:12
kevko^^ it's solution for az-affinity and anti-az-affinity which can be also used by octavia to reach better high-availability as amphoras will be spread across AZs10:13
gibikevko: we reached nova spec freeze for 2023.2 (bobcat) on 6th of July https://releases.openstack.org/bobcat/schedule.html#b-nova-spec-freeze 10:14
gibithis is why you don't get attention on the spec10:14
kevkohmm, does it mean that this can be approved for caracal only right ? 10:14
gibikevko: yes10:15
gibikevko: you can see the caracal schedule here https://releases.openstack.org/caracal/schedule.html10:15
kevkohmm, can we push patchsets for this to gerrit and mark as DNM for example, we would like to see zull results etc ... 10:16
gibikevko: yes, you can do that10:16
kevko(because i read somewhere that it's "forbidden" to push the code if spec is not approved ... so i am better asking )10:16
gibikevko: that will help the spec reviewers as well to see not just the spec proposal but the resulting implementation10:16
gibikevko: if you can point me to the place where it was written then I will be happy to fix that10:17
kevkolet me find it 10:18
kevkohttps://github.com/openstack/nova-specs/blob/master/specs/2023.2-template.rst10:35
kevkoGibi, so question is when we can except that new directory for caracal release will be available for specs repo to move spec for caracal ? 10:39
kevkoGibi, can we create directory for 2024.1 specs  now ? 10:45
gibikevko: which part of the spec template suggested that you should not push code for review? 11:36
gibiI see 11:36
gibi"You should aim to get your spec approved before writing your code. While you are free to write prototypes and code before getting your spec approved, its possible that the outcome of the spec review process leads you towards a fundamentally different solution than you first envisaged."11:37
kevkoyep ..maybe misunderstood ..11:37
gibikevko: it is basically a warning that we might ask you during the spec review to change the direction of the spec and therefore you might need to rewrite the code11:39
gibion the directory question. Technically we could propose the directory right now11:40
gibikevko: you can propose a similar patch to https://review.opendev.org/c/openstack/nova-specs/+/872068 to create the 2024.1 directory11:46
kevkogibi Thank you, I really appreciate it :),  then if the spec will be in right directory, can we expect that someone will check the spec even if now it's bobcat cycle ? or we will wait until december ? 11:49
opendevreviewMichal Arbet proposed openstack/nova-specs master: Create specs directory for 2024.1 Caracal  https://review.opendev.org/c/openstack/nova-specs/+/89146812:17
opendevreviewMichal Arbet proposed openstack/nova-specs master: Add availability zone-aware affinity filter to the scheduler  https://review.opendev.org/c/openstack/nova-specs/+/89077912:20
gibikevko: to be honest right now is vacation period, then we will be busy finishing the content for the bobcat release. So I would not expect much review on caracal spec until the bobcat release is done in early october.12:32
kevkogibi understand, that's apity12:46
kevkoa pity 12:46
sean-k-mooneykevko: i would expect it to get attention in mid september13:11
sean-k-mooneyit wont be december13:11
sean-k-mooneybut we will be busy with release work for then ext 3-4 weeks and thats where most of the attention will be focused until rc1 is released13:11
sean-k-mooneygibi: like i s a strong statement for using shelve to recover but it works surpising well in may siturations13:13
kevkosean-k-mooney: well, it would be nice if you just read it and leave some comment ...but on the other side ...i understand 13:19
kevkopoint is that my colleguage as implementator can work on it ...and it will not work on it until some comment will be left in review :D 13:20
sean-k-mooneyi can try and take a look in general i dont think we can do what you want however13:22
sean-k-mooneykevko: we cant do az affintiy or anti affintiy at the sechduelr filter level without some majoyr chages as the az is already select before the scheduler runs13:22
sean-k-mooneydoing this in the filters has been rejected in the past on 2 ocations for that very reason13:23
sean-k-mooneythe az is set in the build request in the api before the rpc to the schduler 13:23
sean-k-mooneyso unless the spec adresses that it wont work13:23
opendevreviewBence Romsics proposed openstack/nova master: Do not untrack resources of a server being unshelved  https://review.opendev.org/c/openstack/nova/+/89040613:29
opendevreviewDan Smith proposed openstack/nova master: Log excessive lazy-loading behavior  https://review.opendev.org/c/openstack/nova/+/89134014:21
opendevreviewDan Smith proposed openstack/nova master: Avoid lazy-loading in resize and rebuild/evacuate  https://review.opendev.org/c/openstack/nova/+/89133614:21
opendevreviewDan Smith proposed openstack/nova master: Remove a lazy load on every server show  https://review.opendev.org/c/openstack/nova/+/89135214:21
gibinova meeting will start in 30 mins here. I will be your host stoday in bauzas' absense and I will not try to do a full meeting if not needed :)15:31
gibi#startmeeting nova16:00
opendevmeetMeeting started Tue Aug 15 16:00:41 2023 UTC and is due to finish in 60 minutes.  The chair is gibi. 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
gibio/16:00
dansmitho/16:00
elodilleso/16:01
gibiOK, lets get started16:02
gibithis will be a sort meeting16:02
gibi#topic Bugs (stuck/critical)16:02
gibiI don't see any critical bugs16:02
gibi#link https://bugs.launchpad.net/nova/+bugs?search=Search&field.status=New 40 new untriaged bugs (+0 since the last meeting)16:03
gibibased on the roster elodilles had the baton for a long time16:03
elodillesyepp o:) i've tried to triage some bugs :)16:04
gibithanks16:04
elodillesnp16:04
gibiI think we can let that baton be on PTO until bauzas is back16:04
elodilles++16:04
gibiat least I don't know where to assign it16:05
gibiso16:05
gibi#info bug baton is PTO16:05
gibi#info bug baton is on PTO16:05
gibido we have any bugs that needs discussion?16:05
gmanno/16:06
elodillesi don't have any to mention (though feel free to look for the bugs if i misjudged any of them)16:06
gibi#topic Gate status16:07
dansmithhoo boy16:07
dansmiththings are definitely improving but we still have work to do16:07
dansmiththis isn't really gate status, but one thing I've noticed while looking at countless gate logs is that we've had a bunch of lazy-loads sneak in,16:08
dansmithup to five per object one after another for several operations16:08
gmannat least less timeout and oom i think16:08
dansmithI started work on making them visible and have been squashing them here: https://review.opendev.org/q/topic:reduce-lazy-loads16:08
gibidansmith: nice16:09
gibiis there any specific issue we need to discuss?16:09
dansmithI dunno how others feel, but I think 1 lazy load per object per service should be enough, and any time we need to lazy-load more than one thing, we probably should have pre-queried for the thing16:09
gibidansmith: in general I agree16:09
gibiespecially if we always do the two lazy loads unconditionally16:10
dansmithso while it's not really clearly stability-related, doing this will reduce our load on rabbit, the db, and conductor which I'm sure will help gate performance16:10
dansmithyeah16:10
gibiI agree16:10
dansmiththe other gate failure I know of, which I haven't seen much since discussing with melwitt, was the ceph job seeming to hang n-cpu16:10
dansmithI think she was looking at it but I don't know if there was any outcome16:10
gibiOK16:11
gibithanks for the update16:11
dansmithand then aside from that, plenty of small things but nothing large enough to be specifically noteworthy on its own that I know of16:11
gibiI started to look into https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_1fe/889992/2/gate/nova-tox-functional-py39/1fefb65/testr_results.html on Friday but no real breakthrough yet16:12
dansmithcool16:12
gmannone thing to note, rebuild tests have refactored which was failing more. it work on its own server now and should be less on disturbing the thing on class level server16:13
gibigmann: thanks for the heads up16:13
gmannand py3.11 testing started, this is fix from frickler for nova https://review.opendev.org/c/openstack/nova/+/891256/216:14
gmannand in child patch we can see job is passing 16:14
gmannidea is to add py3.11 unit test job as non voting in this cycle and make it voting in next cycle16:14
gibisounds good16:15
gibiI approved the bindep change now as that was simple enough :)16:15
gmannthanks16:16
gibianything else about our gate?16:16
gmannnothing else from me16:16
gibi#topic Release Planning16:17
gibi3 weeks left until Feature Freeze16:17
gibianything to raise here?16:17
gibi#topic Stable Branches16:18
gibielodilles: your turn :)16:19
elodilleso716:19
elodillesthere was not much activity on stable branches16:19
elodillesif the gate issues did not cause any problem on stable gates, then16:19
elodilles#info all stable gates should be OK16:19
elodilles:)16:19
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:19
elodillesand that's all from me16:19
gibithanks16:20
gibiothers, any comment on stable?16:20
gibi#topic Open discussion16:21
gibiany other business?16:21
dansmithnay16:21
sean-k-mooneyi havent really looked at the sabel brances in a a few weeks and no other business form me16:22
elodilles-16:22
gibiOK. Then thanks for joining. :)16:22
gibi#endmeeting16:22
opendevmeetMeeting ended Tue Aug 15 16:22:24 2023 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:22
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2023/nova.2023-08-15-16.00.html16:22
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2023/nova.2023-08-15-16.00.txt16:22
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2023/nova.2023-08-15-16.00.log.html16:22
elodillesthanks o/16:22
-opendevstatus- NOTICE: Zuul job execution is temporarily paused while we rearrange local storage on the servers16:54
sean-k-mooneykevko: i left comments on https://review.opendev.org/c/openstack/nova-specs/+/890779 but that approch will not work17:01
opendevreviewDan Smith proposed openstack/nova master: WIP: Avoid lazy-loads on server create  https://review.opendev.org/c/openstack/nova/+/89152017:33
opendevreviewDan Smith proposed openstack/nova master: Avoid lazy-loads on server create  https://review.opendev.org/c/openstack/nova/+/89152017:34
-opendevstatus- NOTICE: Zuul job execution has resumed with additional disk space on the servers17:44
dansmithgibi: another functional failure, but this looks different: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_240/889740/1/check/nova-tox-functional-py39/240dccc/testr_results.html18:12
dansmithsurely seems like the 3.9 job is the one we always see trouble with...18:12
sean-k-mooneywe coudl just test 3.8 and 3.10 :P18:13
sean-k-mooney oh the db coursor thing18:13
sean-k-mooneyso 3.9 is runing on focal with a non default python i.e. that default to 3.818:15
dansmithyup18:15
sean-k-mooneyso i dont know if there could be a bug in that interperter18:15
dansmiththat's why I was pointing it out18:16
sean-k-mooneyi dont see this often but we could always try using debian for this job18:16
sean-k-mooneyof centos 9 stream18:16
sean-k-mooneythat default to 3.918:16
sean-k-mooneywe woudl jsut need to suppy a diffent nodeset but im not sure if that will help or not18:18
sean-k-mooneyam is zuul ok at th moment18:19
sean-k-mooneyi pushed a patch almost 2 hours ago and its still queueed to start running18:20
dansmithsee the notices above?18:21
sean-k-mooneyoh ok18:21
sean-k-mooneyso there is proably a backlog18:22
sean-k-mooneyill check tomorrow18:22
opendevreviewDan Smith proposed openstack/nova master: Avoid lazy-loads on server create  https://review.opendev.org/c/openstack/nova/+/89152021:19

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