Tuesday, 2025-06-24

*** ykarel_ is now known as ykarel04:18
opendevreviewJohannes Beisiegel proposed openstack/nova master: feat: compute created weigher  https://review.opendev.org/c/openstack/nova/+/94750306:28
opendevreviewJohannes Beisiegel proposed openstack/nova master: feat: compute created weigher  https://review.opendev.org/c/openstack/nova/+/94750306:36
opendevreviewJohannes Beisiegel proposed openstack/nova master: feat: compute created weigher  https://review.opendev.org/c/openstack/nova/+/94750307:19
opendevreviewJohannes Beisiegel proposed openstack/nova master: feat: compute created weigher  https://review.opendev.org/c/openstack/nova/+/94750307:23
opendevreviewStephen Finucane proposed openstack/python-novaclient master: tests: Remove use of ddt  https://review.opendev.org/c/openstack/python-novaclient/+/95319307:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for services APIs  https://review.opendev.org/c/openstack/nova/+/95319608:13
*** LarsErik1 is now known as LarsErikP10:30
opendevreviewJohannes Beisiegel proposed openstack/nova master: feat: compute created weigher  https://review.opendev.org/c/openstack/nova/+/94750311:29
opendevreviewStephen Finucane proposed openstack/nova master: tests: Use valid UUIDs for cinder resources  https://review.opendev.org/c/openstack/nova/+/95293513:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Only apply "soft" additionalProperties validation to requests  https://review.opendev.org/c/openstack/nova/+/95293613:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for volumes APIs  https://review.opendev.org/c/openstack/nova/+/95234813:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for snapshots APIs  https://review.opendev.org/c/openstack/nova/+/95234913:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for volume attachments APIs  https://review.opendev.org/c/openstack/nova/+/95235013:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for floating IP APIs  https://review.opendev.org/c/openstack/nova/+/95297213:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for security group APIs  https://review.opendev.org/c/openstack/nova/+/95297313:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for services APIs  https://review.opendev.org/c/openstack/nova/+/95319613:24
opendevreviewStephen Finucane proposed openstack/nova master: api: Add response body schemas for server usage audit log APIs  https://review.opendev.org/c/openstack/nova/+/95320913:25
UgglaNova meeting in ~1h15:01
opendevreviewJohannes Beisiegel proposed openstack/nova master: feat: compute created weigher  https://review.opendev.org/c/openstack/nova/+/94750315:24
gmaanUggla: Due to board meeting at same time, I will not be able to attend nova meeting today.15:52
Ugglagmaan, ok so I'll skip "your" topic.15:53
Ugglagmaan thx for warning me.15:53
UgglaMeeting in ~5mn15:54
fungii'll be lurking here in case there are more questions about the btg topic from last week, but also mostly on the board ai policy discussion conference call15:56
Uggla#startmeeting nova16:01
opendevmeetMeeting started Tue Jun 24 16:01:44 2025 UTC and is due to finish in 60 minutes.  The chair is Uggla. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
opendevmeetUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
opendevmeetThe meeting name has been set to 'nova'16:01
UgglaHello everyone16:01
bauzaso/16:02
elodilleso/16:02
* bauzas hopes that one day, AI bubble will just explode16:02
andreykurilinO/16:02
bauzasthe quickier being the better16:02
gibio/16:03
bauzas(sorry, was a rant)16:03
gibibauzas: it will16:03
Ugglabauzas ;)16:03
Uggla#topic Bugs (stuck/critical)16:03
Uggla#info No Critical bug 16:03
gibithe question is where we will be when that bubble bursts16:04
Uggla#topic Gate status 16:04
Uggla#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs 16:04
Uggla#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:04
Uggla#link https://zuul.openstack.org/builds?project=openstack%2Fnova&project=openstack%2Fplacement&branch=stable%2F*&branch=master&pipeline=periodic-weekly&skip=0 Nova&Placement periodic jobs status16:04
Uggla#info Please look at the gate failures and file a bug report with the gate-failure tag.16:04
Uggla#info Please try to provide meaningful comment when you recheck16:05
Ugglajumping to next topic because gmaan is not available.16:05
Uggla#topic Release Planning 16:05
Uggla#link https://releases.openstack.org/flamingo/schedule.html16:05
Uggla#info Nova deadlines are set in the above schedule 16:05
Uggla#info Nova Spec review day was last week.16:06
bauzaswe have one week before the spec freeze16:06
bauzaslet's be productive :)16:06
UgglaI'm not sure we managed to review a lot of them. As I think everybody was busy.16:07
Ugglabauzas, You are right spec freeze is July 3rd 16:07
gibido we want to impose a limit how much we approve based on how much bandwidth we have to review implementation?16:07
bauzasgood call, last time (Epoxy) I was figuring this wasn't needed due to the low level of approved ones16:07
bauzaswhat's the current state of approved specs ?16:08
Ugglabauzas, I'm not up2date with it. :(16:08
ratailorHow can I get reviews for https://review.opendev.org/q/topic:%22bp/show-instance-action-finish-time%22 which is already completed.16:08
fungithat did seem like one of the upshots of the btg topic discussion too, approving a reasonable number of specs helps to not set unrealistic expectations for the people who might submit changes to implement them16:08
bauzashttps://specs.openstack.org/openstack/nova-specs/specs/2025.2/16:10
bauzasI see 7 approved16:10
bauzasbut I can't recall whether we approved specless bps16:10
sean-k-mooneywe have16:11
sean-k-mooneynot a lot but one or two16:11
gibieventlet removal is a specless bp 16:11
sean-k-mooneyi think thsoe are all done16:11
Ugglawe have also some specless BP.16:11
sean-k-mooneywell expcte eventlet16:11
bauzasthat would put the number to a small 1016:11
sean-k-mooneyim not sure we shoudl set a numerical limit16:11
bauzasI'd assume that we have a room for not more than 5 or 6 but usually we only merge ~12 features per cycle16:11
sean-k-mooneyi prefered gibis suggestion last week or +1 isntead of +216:12
sean-k-mooneyif you dont plan to review16:12
bauzasso that's really a messaging16:12
bauzasmessaging question16:12
gibiyeah I applied that last week on some specs16:12
bauzasthe real ask here is whether we want to paperwork some capacity limits while we never did before16:13
bauzasbut about the btg discussion, it has a cost : people could consider that we're committed to review their implementation, which isn't the case16:13
sean-k-mooneyif we had one i woudl likely be forece to downgrade some of my +2s to +1s we can condier it next cycle16:13
sean-k-mooneybut i dont want to chagne things this cycle at this point16:14
gibiI think if each core is only +2 a spec if they promise to review the impl then there will be a natural emergent limt16:14
bauzasI still want to review a couple of left specs that I got interested by 16:14
bauzasgibi: we somehow approached that on the previous PTG but we never enforced such rule yet16:15
UgglaI agree gibi, that's probably a good method.16:15
bauzasbut we're in the middle of the acceptance process16:15
gibisure I don't suggest to go back and change +2s (but could be if you want) but going forward we can be limiting +2s16:17
bauzasI mean, I'm not opposed to that, but there are precedent specs that we approved 16:17
bauzasanyway, if you feel so, do so16:18
bauzasI'll personnally follow that rule too16:18
sean-k-mooneyi really dont want to change the rules this cycle16:19
sean-k-mooneythis is all valid for next cycle but i think its unfair to change the critiria mid way. (removing +2s)16:20
sean-k-mooneythat up to each reviewer16:20
sean-k-mooneybut i htink taht would send lot of mixed messages16:21
sean-k-mooneywe only have 9? days till spec freeze16:21
sean-k-mooneyif folks want to not add a +2 or +1 to open spec that totally fair16:21
bauzasthat's why I'm saying : as we don't have quorum now, let's just leave that to each core's opinion16:22
sean-k-mooney+116:22
Uggla+1, I think it will be ok, based on the time left.16:23
UgglaMoving on.16:23
gibiOK16:23
Uggla#topic Review priorities 16:23
Uggla#link https://etherpad.opendev.org/p/nova-2025.2-status16:23
UgglaI think we should pay attention to this one: https://review.opendev.org/c/openstack/nova-specs/+/95163616:24
Uggla#topic OpenAPI 16:26
Uggla#link: https://review.opendev.org/q/topic:%22openapi%22+(project:openstack/nova+OR+project:openstack/placement)+-status:merged+-status:abandoned16:26
Uggla#info 25 increase +5, there are new ones from Stephen.16:27
sean-k-mooneyyep16:27
sean-k-mooneyim making my way through them16:27
sean-k-mooneyseveral are fixu ups form minor issues earlier in the series16:28
Ugglasean-k-mooney, you are right there are FUP in the list.16:28
sean-k-mooneythere are currnetly about 10 queued to merge16:29
sean-k-mooneyim kind of brunt on them for tosay but im planning to loop back again later in the week16:29
Ugglasean-k-mooney 👍16:30
UgglaMoving on because time is flying.16:30
sean-k-mooneyi think gmaan  has done a first pass on all the currently open ones or most of them and Uggla  has reviewds many fo them too16:30
Uggla#topic Stable Branches 16:30
sean-k-mooneyso ya good progress but we can move on16:30
Ugglaelodilles, the mic is yours16:30
elodillesthanks Uggla 16:30
elodillesas in the past weeks, there's nothing special to report16:31
elodilles#info stable branches (stable/2025.1 and stable/2024.*) seem to be in OK state16:31
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:31
elodillesthat's all, back to you Uggla 16:31
Ugglathx elodilles16:31
UgglaSkipping next topic because fwiesel is not available16:32
Uggla#topic Gibi's news about eventlet removal. 16:32
Uggla#link Blog: https://gibizer.github.io/categories/eventlet/16:32
Uggla#link nova-scheduler series is ready for core review, starting at https://review.opendev.org/c/openstack/nova/+/94796616:32
Ugglagibi, something you want to share.16:32
gibihm16:33
gibisorry16:33
gibithanks for the feedback on the series16:33
gibiI spent time on https://review.opendev.org/c/openstack/nova/+/95312116:33
gibithat was triggered by the discusson on the spawn_on patch16:33
gibiI have local changes to apply some of those to the eventlet series itself16:33
gibibut downstream priorities stole my time16:34
bauzasgibi: I saw the -W, can I start to review it tho ?16:34
bauzas(I mean the spawn_on patch)16:34
gibibauzas: you can it is not broken. There is a missing piece that I will add 16:34
gibiall noted in the review comments16:34
gibito be precise I will add a missing test piece16:35
gibinot production code piece16:35
bauzasack16:35
gibiand16:35
gibithere is the governance discussion about when to drop eventlet16:35
gibihonestly I'm a bit lost how to move that forward16:36
gibihttps://review.opendev.org/c/openstack/governance/+/952903/1/goals/selected/remove-eventlet.rst16:36
gibiI hope the tc has plans to reconcile the discussion there ;)16:36
gibithat is it form me16:36
Ugglathx gibi16:36
Uggla#topic Open discussion 16:37
UgglaWe have 2 topics16:37
Uggla#topic (andreykurilin) Expansion of "servers:detail:get_all_tenants" policy to other server read-only APIs (example: https://review.opendev.org/c/openstack/nova/+/952896)16:37
Ugglaandreykurilin, please go ahead16:37
andreykurilinHi folks!16:37
andreykurilinI, as an operator, have a need to provide readonly access to compute resources for third-party teams16:38
andreykurilinWhile list api works fine, get api provides much better UX16:38
andreykurilinWhat do you think about extending current readonly apis to reuse existing policy?16:38
andreykurilinDoes it need new api micro version ? Spec? Blueprint?16:39
sean-k-mooneyone of the latter two but policy change generally dont need micro verions16:40
sean-k-mooneywe do have a spec, two in fact for the intorduction fo the manager role and service role to nova16:41
sean-k-mooneyif i recall form the mailing list dicussion you only wanted to expose 1 endpoint correct16:42
sean-k-mooneyif it was many then i would say it needs a spec16:42
andreykurilinYes, I need get server api exposed. Maybe server actions in future, but not at this moment16:42
UgglaIt seems gmann is not opposed to the change, which is a good sign.16:43
andreykurilinI’m happy to commit some resources to cover more than is needed for my company, if you want, but not sure that I have enough resources to work on a big spec16:44
UgglaI think the question is  if we are ok to fix it as bug16:45
Ugglasean-k-mooney any thought about that ?16:46
sean-k-mooneyi dont consider it a bug in teh backport sense. we could treat it as an RFE bug i.e. a bug with the rfe tag instead of a specless bluepirnt16:47
sean-k-mooneyi would suggest that if we want to do somethign this clcye we keep it small and targeted16:48
sean-k-mooneyand we can dicuss larger changes but in the context of next cycle16:48
sean-k-mooneyjust being practical we hae several large api serises in flight16:49
sean-k-mooneyopenapi scemea, service role and manger role16:49
sean-k-mooneywe may be ableo to review a targed patch but if you want to do many endpoint we will need more time to discss it then we have before m216:50
UgglaTbh, I would rather have a specless BP. Easier to track on my side. 16:50
andreykurilinI’m ok to have only one endpoint “fixed” this cycle16:50
andreykurilinCreating a specless BP works for me16:50
UgglaSo andreykurilin, if you can open a specless BP so I could track it.16:50
sean-k-mooneythen i woudl suggest filing a specless blueprint for server show16:50
Uggla👍16:51
sean-k-mooneyand then asking for it to be approved on the mailing list or next meeting16:51
sean-k-mooneyto give gmaan  or other type to respond16:51
andreykurilinOk, got it. Thank you16:51
sean-k-mooneys/type/time/16:51
gmaanI am ok for the spec-less BP and agree that it does not need microversion16:52
sean-k-mooneyim ok with that direction too16:52
sean-k-mooneyjust for the metting ^16:52
gmaanI tried to search history why we did not do for SHOW server when doing for details and could not find any reason16:52
gmaanit was just not needed by anyone till now16:53
andreykurilinIt was “workaroundable”. We lived with list + id filter for several years already and finally I found time to ask you guys about this16:53
gmaan++, thanks for bringing that16:54
Ugglaandreykurilin++16:54
Ugglamoving on to next topic.16:55
Uggla#topic (ratailor) spec and implementation for show-instance-action-finish-time (https://review.opendev.org/q/topic:%22bp/show-instance-action-finish-time%22) 16:55
Ugglaratailor please go ahead.16:55
ratailorAs the implementation is also completed, just a request to provide feedback on spec so that it gets merged before FF.16:56
opendevreviewMerged openstack/nova master: api: Add response body schemas for server IPs APIs  https://review.opendev.org/c/openstack/nova/+/93760816:56
ratailorThat's all from my side re this.16:57
sean-k-mooneyratailor: do you have tempest coverage showing that this works ?16:58
sean-k-mooneyspecificly it would be nice to see the test that orginally demponstrated this did not work passing16:59
ratailorsean-k-mooney, don't have tempest tests yet, but I can try to submit chagne for that.16:59
ratailorsean-k-mooney, yes, sure. I will try with that one.16:59
sean-k-mooneyhttps://review.opendev.org/c/openstack/tempest/+/90513016:59
sean-k-mooneyit woudl be nice to update that and have it depend on your seriese to show ti workign end to end17:00
ratailorsean-k-mooney, sure. Thansk!17:00
Ugglasean-k-mooney, I agree it might also help on an escalation we have internaly17:00
UgglaWe have 2 more topics, but we are also at the top of the hour. So gibi, jonnyb if you don't mind we would be able to discuss next week. Except if it's urgent.17:03
jonnybhi, fine for me17:03
Ugglajonnyb, thx for your understanding17:03
Ugglagibi ?17:03
sean-k-mooneyjonnyb: you wanted to add a tiny weigher right?17:04
jonnybyeah right17:04
sean-k-mooneyif you have the patch it woudl be good for other to at least condier it before the next meeting17:04
sean-k-mooneyor perhaps start a mailing list thread on the topic17:04
sean-k-mooneytl;dr is it weighs host by how old they are 17:05
sean-k-mooneyand prefers the newer ones17:05
jonnybits a pretty simple patch17:05
sean-k-mooneywhich is similer but differnt to the hyperviors_version weigher and they both complement each other17:05
sean-k-mooneyim generally ok with this as a specless blueprint by the way but we can disscuss that outside teh meeting or next week17:06
gibiUggla: no worries my topic was touched during the eventlet block17:07
jonnybI can move this to the mailing list to not drag this out here. thanks17:07
Ugglajonnyb, that will be ok next week, I guess it will not take long.17:07
Ugglaanyway time to close.17:07
UgglaThanks all17:08
Uggla#endmeeting17:08
opendevmeetMeeting ended Tue Jun 24 17:08:16 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:08
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2025/nova.2025-06-24-16.01.html17:08
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-06-24-16.01.txt17:08
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2025/nova.2025-06-24-16.01.log.html17:08
gibisorry I mixed up my topic17:30
gibiwe need to discuss https://review.opendev.org/c/openstack/nova/+/95296617:30
gibithis is pretty much needed by debian and ubuntu to be able to release on top of 3.13 while cpython 3.13 fixing a GC bug17:30
gibiso I need core reviews, pretty please17:30

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