Tuesday, 2025-04-29

opendevreviewmelanie witt proposed openstack/nova master: live migration: Avoid volume rollback mismatches  https://review.opendev.org/c/openstack/nova/+/94660001:18
melwittlooks like nova-tox-functional-py39 is failing 100% due to a package dependency conflict https://zuul.opendev.org/t/openstack/builds?job_name=nova-tox-functional-py39&project=openstack/nova01:53
melwittI also notice cyborg-tempest and barbican-tempest-plugin-simple-crypto started failing recently, 1-2 days ago01:54
opendevreviewIvan Anfimov proposed openstack/nova master: Remove deprecated [workarounds] enable_numa_live_migration  https://review.opendev.org/c/openstack/nova/+/90542607:00
gibimelwitt: the cyborg-tempest failure is caused by cyborg-api not starting: --- no python application found, check your startup logs for errors ---07:00
gibimelwitt: reported bug https://bugs.launchpad.net/openstack-cyborg/+bug/210958307:06
gibimelwitt: barbican has very similar failure and similar data of breakdown07:07
gibiso there should be a common cause07:07
gibifiled a barbican bug too https://bugs.launchpad.net/barbican/+bug/210958407:10
gibiit all started on 04-27 but I don't see devstack/tempest changes merged around that time07:12
gibithere are requirements changes but nothing suspicious to me07:12
gibimelwitt: but I think the reason functional-py39 fails is that we dropped that python version from global requirements. I will propose a patch to remove the job from nova07:15
opendevreviewBalazs Gibizer proposed openstack/nova master: Remove python 3.9  support  https://review.opendev.org/c/openstack/nova/+/94839207:23
gibimelwitt, bauzas, sean-k-mooney ^^07:23
opendevreviewBalazs Gibizer proposed openstack/nova master: Remove python 3.9  support  https://review.opendev.org/c/openstack/nova/+/94839207:24
gibithis is needed to unblock the nova gate07:25
opendevreviewBalazs Gibizer proposed openstack/nova master: Remove python 3.9  support  https://review.opendev.org/c/openstack/nova/+/94839207:32
fricklerthe former looks similar to what ralonsoh found https://bugs.launchpad.net/designate/+bug/210957707:32
gibifrickler: indeed07:33
gibiand also started failing on the 27th07:34
gibiso probably the same common but unknown cause07:34
fricklerwell setuptools==80 released on the 27th, looks very likely07:35
gibiohh07:35
ralonsohin designate, the wsgi binary is not being created07:38
ralonsohbut I can´t reproduce it locally07:38
gibiis it the missing pyproject.toml?07:39
gibi2025-04-29 05:43:24.960850 | controller |   DEPRECATION: Legacy editable install of keystone==27.1.0.dev20 from file:///opt/stack/keystone (setup.py develop) is deprecated. pip 25.3 will enforce this behaviour change. A possible replacement is to add a pyproject.toml or enable --use-pep517, and use setuptools >= 64. If the resulting installation is not behaving as expected, try using 07:39
gibi--config-settings editable_mode=compat. Please consult the setuptools documentation for more information. Discussion can be found at https://github.com/pypa/pip/issues/1145707:39
gibi701007:39
gibihttps://zuul.opendev.org/t/openstack/build/af7efda68d204f1c99f8eeef77359ebf/log/job-output.txt#700907:40
gibias setuptool 80 changelog says07:40
gibiDevelop command no longer uses easy_install, but instead defers execution to pip (which then will re-invoke Setuptools via PEP 517 to build the editable wheel). Most of the options to develop are dropped. This is the final warning before the command is dropped completely in a few months. Use-cases relying on ‘setup.py develop’ should pin to older Setuptools version or migrate to modern build 07:40
gibitooling. (#4955)07:40
gibihttps://setuptools.pypa.io/en/stable/history.html07:40
gibiyeah barbican does not have pyproject.toml but nova has07:41
gibidesignate neither07:42
ralonsohneutron doesn't have it07:42
ralonsohbut seems to run fine07:42
gibimaybe neutron does not use setup.py develop 07:43
gibihttps://review.opendev.org/c/openstack/nova/+/899753 this added pyproject.toml to nova07:44
ralonsohbut, if I'm not wrong, we use editable installs in neutron, at least in neutron-tempest-plugin07:45
ralonsohmaybe I'm wrong07:45
johnsomhttps://review.opendev.org/c/openstack/designate/+/90284607:56
ralonsohjohnsom, can you add this info in the designate bug?07:57
ralonsohjohnsom, also this is blocking now the Neutron CI. Could be possible to have it rebased and reviewed?07:58
johnsomYea, I am about to turn in for the night, but can add a comment07:58
johnsomI would hope so. Maybe also ping in the designate channel07:58
ralonsohjohnsom, thanks a lot!07:59
fricklerI can take a look after a bunch of meetings that I've got coming up07:59
ralonsohgibi, ok, now I realize that Neutron is actually using the wsgi module and no longer using the script. This is why is working07:59
gibithanks folks08:03
opendevreviewBalazs Gibizer proposed openstack/nova master: WIP: allow service to start with threading  https://review.opendev.org/c/openstack/nova/+/94831108:46
opendevreviewBalazs Gibizer proposed openstack/nova master: Print ThreadPool statistics  https://review.opendev.org/c/openstack/nova/+/94834008:46
elodillesUggla: just a quick double check: do you want to wait for reviews with the schedule patch (review + freeze days) or is it ready to merge already? https://review.opendev.org/c/openstack/releases/+/94807708:52
gibielodilles: Uggla is on PTO the whole week as far as I remember09:02
elodillesahh, right.09:04
elodillesthen I'll wait maybe until the meeting :)09:04
opendevreviewSylvain Bauza proposed openstack/nova master: Add mtty/mdpy support for testing fake mdevs  https://review.opendev.org/c/openstack/nova/+/89810009:21
opendevreviewSylvain Bauza proposed openstack/nova master: WIP : Add mtty support to nova-next  https://review.opendev.org/c/openstack/nova/+/92214009:21
opendevreviewKamil Sambor proposed openstack/nova master: Replace eventlet.queue.LightQueue with queue.SimpleQueue  https://review.opendev.org/c/openstack/nova/+/94841710:05
gibisean-k-mooney: bauzas: we need this to unblock the nova gate https://review.opendev.org/c/openstack/nova/+/94839210:57
sean-k-mooney...10:58
sean-k-mooneydamb i new trhis was going to happen but i hoped we would have a few more months10:59
sean-k-mooney+2... i was hoping to keep watcher compaitble with 3.9 until we have an alternitive but if the requiremetns repo has droped validation fo 3.9 deps we are going to have to do something similar11:03
gibiyeah unfortunately they pulled the trigger11:03
gibinot having a py39 upper constraints causes version conflict in py39 jobs11:04
sean-k-mooneyya so for wathcer ill create a patch to do the same. im not going to bump required_python initally but ill do that in a followup patch11:05
sean-k-mooneythat we will have to merge before the end of the cycle11:05
sean-k-mooneyour downstream container build does not use the latest version of lib that UC allows so i want to see if it can still build on 3.9 with those deps before i fully block it11:06
sean-k-mooneybut that is only a tempory hack.11:06
sean-k-mooneyactully by downstrema in this context i just mean the operator jobs whcih are technially upstream using continers built form rdo content11:06
sean-k-mooneywe are working on moving those to centos 10 stream instead which will upgrade them to 3.1211:07
sean-k-mooneyi was hoping ot have another month or two to finish that but its fine11:07
opendevreviewBalazs Gibizer proposed openstack/nova master: WIP: allow service to start with threading  https://review.opendev.org/c/openstack/nova/+/94831111:15
opendevreviewBalazs Gibizer proposed openstack/nova master: Print ThreadPool statistics  https://review.opendev.org/c/openstack/nova/+/94834011:15
gibisean-k-mooney: yeah11:16
opendevreviewBalazs Gibizer proposed openstack/nova master: Print ThreadPool statistics  https://review.opendev.org/c/openstack/nova/+/94834011:29
opendevreviewBalazs Gibizer proposed openstack/nova master: WIP: allow service to start with threading  https://review.opendev.org/c/openstack/nova/+/94831111:29
sean-k-mooneyhttps://review.opendev.org/c/openstack/devstack/+/948408/1/lib/nova#b1118 is fine but it still might be cleaner to have either the nova devstack plugin or the job create a droping file for the systemd serivce in the long term11:51
sean-k-mooneygibi: if we ever land your patch to make the [[post-config|path]] thing work for non exisitent directories11:52
sean-k-mooneywe coudl do that via that in the job too11:52
gibisean-k-mooney: yeah the current devstack patch is a hardocded hack. I planning to have a devstack local conf variable to list the nova services that should run in threading mode then use that to pass the env var to systemd11:54
sean-k-mooneywhat im kind of hoping we can avoid si a patch to devstack for every binary we need to swap between modes so im hopign we can come up with somethign generic and reusable11:54
sean-k-mooneyya that woudl work. i was thinking more generic have a map of systemd unit name to a list of extr env vars11:55
sean-k-mooneyso it can work for any of the services so it woudl work for neutron or glance too11:55
sean-k-mooneybut we can keep it nova speicifc not to inflate the scope too much11:56
gibiI will look into the generic mapping, that sounds useful12:16
opendevreviewBalazs Gibizer proposed openstack/nova master: Print ThreadPool statistics  https://review.opendev.org/c/openstack/nova/+/94834012:25
opendevreviewBalazs Gibizer proposed openstack/nova master: WIP: allow service to start with threading  https://review.opendev.org/c/openstack/nova/+/94831112:25
sean-k-mooneyby the way could we land https://review.opendev.org/c/openstack/placement/+/945487 i would like to get that off my list of open patches while its not in merge conflict12:28
gibi+2 from me12:31
opendevreviewSylvain Bauza proposed openstack/nova master: WIP : Add mtty support to nova-next  https://review.opendev.org/c/openstack/nova/+/92214012:34
gibidansmith: sean-k-mooney: I had some local stress testing of the threaded scheduler. In the happy path scatter-gather worker threads are properly returned to the pool and reused (I scheduled 120 VMs with the pool of 20 threads x 2 worker processes).12:35
sean-k-mooneycool and did that taek a lot of ram and or time or was it reasonable 12:37
sean-k-mooneyim just askign for a gut feeling by the way12:37
sean-k-mooneyi assume that was not one multi create by the way12:37
sean-k-mooneyyou did parallel requests12:38
gibithe nova-scheduler workers are at 130MB RSS each 12:40
gibiI did parallel create requests not a single multicreate12:40
*** haleyb|out is now known as haleyb13:00
gibiaand we have the first CI result where n-sch run with threading https://zuul.opendev.org/t/openstack/build/c2ec6bc4ae4946468d5b2b4f8468d12a/log/controller/logs/screen-n-sch.txt#2855-285613:04
dansmithgibi: nice13:26
sean-k-mooneygibi: that all sounds pretty reasonable.  out side of a small number of thread local varablie and stack frames we woudl not expect the worker size to grow much as we increase the thread outside of the data needed for the schduler ot schdule13:40
sean-k-mooneyso 130MB RSS per worker does not sound bad at all13:40
opendevreviewKamil Sambor proposed openstack/nova master: Replace eventlet semaphores with threading one  https://review.opendev.org/c/openstack/nova/+/94843713:43
gibithe nova-lvm job run 70 worker https://zuul.opendev.org/t/openstack/build/b5d70ad645514181a1fda52bba8187ce/log/controller/logs/screen-n-sch.txt#5099-5100 and n-sch had 120MB RSS https://zuul.opendev.org/t/openstack/build/b5d70ad645514181a1fda52bba8187ce/log/controller/logs/screen-memory_tracker.txt#2507-2508 on the gate13:58
gibi70 task with 20 worker threads13:58
gibi2 worker processes13:59
sean-k-mooney how are you calulating the defautl therad pool size by the way. are you jsut levaing futurist decide currently14:00
sean-k-mooney (failures=0, executed=70, runtime=1.90, cancelled=0)>14:01
sean-k-mooneydoes that mean it ran for 1.9 sconds total?14:02
sean-k-mooneyi gues not14:02
sean-k-mooney 0x7cab7c4de4c0 (failures=0, executed=69, runtime=2.33, cancelled=0)>14:02
sean-k-mooneyperhaps its since the last tiem you got the stats14:02
gibifuturist decides today14:03
gibibut we can have a config 14:03
sean-k-mooneyi belvie it default to 2.5*nproc14:04
gibiI can run some tests to see what is the runtime stats there14:04
sean-k-mooneyi reused one fo the existing config option but i would proably default this to 414:04
sean-k-mooneyand allow peopel to overried if needed14:04
gibihttps://docs.openstack.org/futurist/latest/reference/index.html#futurist.ExecutorStatistics.runtime doc says total runtime of the pool14:04
sean-k-mooneyhum well it went down form 69 to 7014:05
gibiwe have two worker processes so you need to check the pid to see if this is the same worker14:06
sean-k-mooney oh good point14:06
sean-k-mooneyare you usign https://docs.openstack.org/futurist/latest/reference/index.html#futurist.periodics.Watcher14:06
gibifuturist creates cpu * 5 threads per executor by default https://github.com/openstack/futurist/blob/master/futurist/_utils.py#L12614:06
sean-k-mooneygibi: ack thats proably more then we need14:06
gibiI don't use periodics, I log the stats when new work is submitted and if the last report was older than 60 sec14:08
gibiwe can change it to periodic14:08
gibiand or we can have a config option for the age14:08
gibiyeah, 20 worker for scatter gather is too much, we can aim for 4 ish, but it depeds on the amount of parallel scheduling we need to serve14:09
sean-k-mooneyright but we have 2 ways to scale workers and treads in each workser thread pool. and we can make it configurable14:11
sean-k-mooneywell technially 3 you can just run more schdulers14:11
sean-k-mooneyi think tying the count to the cpu cores will bit ues down the line espcially if this is deployed on k8s as that could change based on where the pod runs so that why i would prefer to have a small integer default14:12
gibiyeah I will expose a config option with a small default14:16
gibiand document that you can ask for more worker processes as well as a scaling mechanism14:17
dansmithI think it will take some time to figure out what the real default should be14:19
dansmithgreenthreads are nice, but they also kinda avoid the resource exhaustion question such that we don't really have a good idea of what it needs to be, IMHO14:20
gibiyepp14:54
sean-k-mooneygibi: https://zuul.opendev.org/t/openstack/buildset/f495c3661ca346a198c80a01387d6ba4 so that not terible for a first run14:54
gibinova-next is green that is enough for me to declare success14:55
sean-k-mooneyim not sure why grenade is unhappy14:55
sean-k-mooneymaybe the devstack change14:55
gibisome tempest jobs does not have oslo.service as required project hence the oslo.service depends on is ignored14:55
sean-k-mooneyah ya that too14:55
gibialso nova-multi-cell is green 14:56
sean-k-mooneyyep most of them are14:57
opendevreviewDan Smith proposed openstack/nova master: WIP Example NVMe cleaning script for one-time-use  https://review.opendev.org/c/openstack/nova/+/94844614:57
sean-k-mooneygibi: the cyborg job is broken because they do not have pyproject.toml supprot so there wsgi script are not gerneated14:57
gibinova-multi-cell executed the most scatter-gathers and the nova-scheduler RSS is still around 122MB14:57
gibisean-k-mooney: yeah I ended up at the same conclusion this morning, as well as barbican and designate14:58
sean-k-mooneyim fixing that on watcher but that will impact other proejct shortly14:58
gibiI filed bugs for barbican and cyborg, ralonsoh has bug for designate14:58
sean-k-mooneyack there was a pip release 3 days ago 14:58
gibiyeah frickler pointed out that setupstools=80 is the root cause14:59
sean-k-mooneywell kind of 14:59
ralonsohjust for information: https://review.opendev.org/c/openstack/designate/+/90284614:59
ralonsohthe designate fix (along with another fix for the CI)14:59
sean-k-mooneythe actual root causae is we have been relying on a compatibality fallbac that was added 2 years ago and then deprecated for removal a year ago15:00
sean-k-mooneyralonsoh: this is the watcher fix but im respining it now https://review.opendev.org/c/openstack/watcher/+/948438 to fix the mistakes15:00
sean-k-mooneyralonsoh: i was going to defer the removal of the wsgi_script until next cycle15:01
ralonsohwell, now is mandatory I think15:02
sean-k-mooneybut i guess if we backported this to epoxy we coudl remove it this cycle maybe15:02
sean-k-mooneyno it will still work with older pip15:02
sean-k-mooneyon editbale installs15:02
sean-k-mooneyralonsoh: nova still has supprot for them15:02
johnsomI worry about backporting these patches given there is package/deployer impact. I was considering pinning setuptools in 2025.115:03
sean-k-mooneyif you build the whelie in non editable mode the extenion we have also work i belive15:03
sean-k-mooneyjohnsom: ya im trying to avoid backporting it too15:03
sean-k-mooneyjohnsom: that why  im intentially not removing the old way fo usign the console scrit in the intial patch15:04
opendevreviewBalazs Gibizer proposed openstack/nova master: Print ThreadPool statistics  https://review.opendev.org/c/openstack/nova/+/94834015:05
opendevreviewBalazs Gibizer proposed openstack/nova master: WIP: allow service to start with threading  https://review.opendev.org/c/openstack/nova/+/94831115:05
opendevreviewBalazs Gibizer proposed openstack/nova master: DNM:Run nova-next with n-sch in threading mode  https://review.opendev.org/c/openstack/nova/+/94845015:05
johnsomWell, if we don't pin, it's still likely to break people. That is why I was pushing to do it all at once and get the pain overwith15:05
sean-k-mooneyya its unfortuent we dint get this done in carical liek we orgianlly wanted to do 15:06
johnsom+115:06
sean-k-mooneyin theory if you use an old enough pip/setuptoosl nova still supprot setup.py directly too but nothing tests that15:07
johnsomWe plan to land the designate patch today (there is a typo to fix)15:07
bauzasnova meeting in 20 mins here15:40
* bauzas will chair the meeting for 20 mins only15:41
haleybwe noticed a failure in the neutron periodic jobs today with the oslo.utils master branch, but seems more a nova issue - https://bugs.launchpad.net/nova/+bug/210959215:45
haleybi'm assuming that would eventually get caught in an integration job somewhere15:46
dansmiththat looks more like an oslo, requirements, etc thing15:46
dansmith(could be nova requirements.txt)15:46
sean-k-mooneyya i was going ot say the same15:47
sean-k-mooneywhat branch was this on "master" i assume15:47
haleybdansmith: could be just didn't seem neutron-specific15:47
dansmithhaleyb: yes :D15:47
fricklerfrom the timing when this started failing, I was assuming setuptools==80 to be related15:47
haleybyes, we have a job that uses most (all) of the oslo master branches15:47
sean-k-mooneyactully thi si from a neutorn job that is testing with oslo master15:47
haleybit's a canary job15:48
sean-k-mooneyso that may also be a regression in oslo15:48
sean-k-mooneyi.e. they moved the module15:48
fricklerbecause from sunday to monday no changes were merged in oslo, neutron or nova15:48
gmaanyeah it is not yet released so will not be visible in other jobs but oslo master one15:48
sean-k-mooneyno its where we expect15:49
haleybwe noticed today, started seeing yesterday according to build logs15:49
haleybhttps://zuul.openstack.org/builds?job_name=neutron-ovn-tempest-ovs-release-with-oslo-master&job_name=neutron-ovs-tempest-with-oslo-master&skip=015:49
sean-k-mooneythe module is still in the same place https://github.com/openstack/oslo.utils/blob/master/oslo_utils/imageutils/format_inspector.py15:51
sean-k-mooneyso its a little od15:51
sean-k-mooneyoh15:51
sean-k-mooney/usr/lib/python3/dist-packages/oslo_utils/imageutils.py15:52
sean-k-mooneythat look wrong15:52
sean-k-mooneyit is using setup tools 80 Requirement already satisfied: setuptools in /opt/stack/data/venv/lib/python3.12/site-packages (from pbr>=6.1.0->oslo.utils==8.3.0.dev7) (80.0.0)15:53
opendevreviewBalazs Gibizer proposed openstack/nova master: DNM:Run nova-next with n-sch in threading mode  https://review.opendev.org/c/openstack/nova/+/94845016:00
bauzas#startmeeting nova16:01
opendevmeetMeeting started Tue Apr 29 16:01:04 2025 UTC and is due to finish in 60 minutes.  The chair is bauzas. 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
gibio/16:01
bauzasguys, we have a meeting now16:01
sean-k-mooneyo/16:01
elodilleso/16:01
bauzasdo you want to discuss ?16:01
gmaano/16:01
bauzasI can chair it for the next 20/30 mins 16:01
fwieselo16:01
gibiI have one gate topic16:01
bauzasand then I'll need to go offline16:01
bauzasokay, let's start16:01
bauzas#topic Bugs (stuck/critical) 16:02
bauzas#info No Critical bug16:02
bauzas#topic Gate status 16:02
bauzas#link https://bugs.launchpad.net/nova/+bugs?field.tag=gate-failure Nova gate bugs16:02
bauzas       Nova gate is blocked until we land https://review.opendev.org/c/openstack/nova/+/94839216:02
gibiyepp that is my point^^16:02
bauzasjust +wd it16:03
gibipy3.9 are dropped from global req causing version conflict 16:03
bauzas#link https://etherpad.opendev.org/p/nova-ci-failures-minimal16:03
bauzascool16:03
gibibauzas: thankls16:03
bauzasI saw the failures indeed16:03
bauzasgibi; no thanks to you for the fix16:03
bauzasanything else to say about it ?16:04
gibinope16:04
bauzasall good16:05
bauzasmoving on quickly then16:05
bauzas#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:05
bauzas#info Please look at the gate failures and file a bug report with the gate-failure tag.16:05
bauzas#info Please try to provide meaningful comment when you recheck16:05
bauzasperiodics are green, moving on16:06
bauzas#topic tempest-with-latest-microversion job status 16:06
bauzas#link https://zuul.opendev.org/t/openstack/builds?job_name=tempest-with-latest-microversion&skip=016:06
gmaanI will make it periodic as logs are not visible in experimental run16:07
bauzasmoving on while I'm awaiting the result 16:07
gmaanand will see how many tests need adjustment16:07
bauzasgmaan: ack thanks16:07
bauzas#topic Release Planning 16:07
opendevreviewMerged openstack/placement master: Add pyproject.toml to support pip 23.1  https://review.opendev.org/c/openstack/placement/+/93239916:07
bauzas#link https://releases.openstack.org/flamingo/schedule.html16:07
bauzas#info Nova deadlines are set in the above schedule16:07
bauzaswell, technically, those deadlines aren't set AFAICS16:08
elodillesactually they are not: https://review.opendev.org/c/openstack/releases/+/94807716:08
bauzaselodilles yeah16:08
elodilleso:)16:08
bauzasmoving on, that'll be Uggla's responsibility to check those deadlines every week :p16:08
elodillesthe above needs some review (at least from nova release liaisons)16:08
bauzas#topic Review priorities16:09
bauzas#link https://etherpad.opendev.org/p/nova-2025.2-status16:09
bauzaselodilles +1d16:09
gibielodilles: +1d16:09
bauzasapparently Uggla did a work on creating a tracking etherpad, noice16:09
bauzas#topic Stable Branches 16:10
elodillesthanks all o/16:10
bauzaselodilles: shoot your topic16:10
elodillesah, ok16:10
elodilles#info not aware of any stable gate blocking thing16:10
elodillesi haven't seen any setuptools related issue yet :)16:10
elodillesbut there were not much activity in the past days16:11
elodilles#info stable/2023.2 (bobcat) EOL patch for nova: https://review.opendev.org/c/openstack/releases/+/94819616:11
elodillesanother patch that needs some nova release liaison review ^^^16:11
elodilles#info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci16:11
elodillesthat's all from me16:11
elodillesbauzas: back to you16:12
bauzascool16:12
bauzas#topic vmwareapi 3rd-party CI efforts Highlights 16:12
bauzasfwiesel: around ?16:12
fwieselYes, finally.16:12
fwiesel#info fwiesel reports back to duty16:12
fwieselSo to say16:12
fwiesel#info fwiesel will involve more people from SAP for redundancy16:13
fwieselWhen I had my sick leave, I just dropped a short message on slack, hoping someone will take over, but that didn't work.16:13
fwieselI'll try to make that more formal.16:13
fwieselThat's from my side.16:13
bauzascool16:13
bauzas#topic Gibi's news about eventlet removal.16:14
bauzasgibi: shoot16:14
gibiack16:14
gibiwe saw the first nova-scheduler run with native threading16:14
gibiactually multiple green CI jobs16:14
gibie.g. https://zuul.opendev.org/t/openstack/build/636bdbb6ad494ef0b49415034842a640/log/controller/logs/screen-n-sch.txt nova-multi-cell16:14
gibinothing needs immediate review attention. The ball is on my side to clean up the series that is open16:15
gibithat is it16:15
gibibauzas: back to you16:16
bauzasnoted16:16
bauzasI'll skip the bug scrub as I don't have time to lead this16:16
bauzasand given Uggla is on PTO16:17
bauzas#topic Open discussion 16:17
bauzasanything anyone ?16:17
fwieselYes, me then.16:17
fwieselI was curious about what you think about enabling resize between hypervisors? I mean, a full discussion obviously means a blueprint.16:18
bauzasI'll need to disappear shortly16:18
bauzasdo people have opinions about ^ ?16:18
gibifwiesel: yeah probably a spec16:18
bauzasnot sure what you mean by an "hypervisor resize"16:19
fwieselQuestion there is is it worthwile to open one16:19
bauzasresizing all the instances on that host ?16:19
fwieselAh, the idea is we have a flavor for one hypervisor (i.e vmware), and the user wants to migrate to another one, say libvirt.16:19
bauzasor some hardware change for an hypervisor, like a new memory card ?16:20
fwieselThe user can then call a resize from one flavor to another16:20
bauzasah16:20
bauzaswe don't bubble up that to the users because $cloud16:20
fwieselI can write a spec, but I wanted to know if anyone would even be willing to look at it :)16:21
bauzasbut, operators can do multiple scheduling usages for that16:21
bauzaseg. aggregates, traits or anything else decorating16:21
bauzasnot sure I want to disclose which hypervisor runs by a flavor16:21
fwieselLet's turn it the other way around. Is it desireable that a resize should work between two different nova drivers?16:23
bauzasI need to go offline now16:23
bauzasagain, anyone want to discuss this ?16:23
bauzasor we could discuss this next week16:23
gibifwiesel: at least it worth dicussing it. I'm not against it at a first glance16:23
fwieselI can bring it up next week again. I want to avoid writing a spec, if there is a strong opposition to it.16:24
bauzasthanks, let's then discuss this again nextweek16:25
bauzasthanks all16:25
bauzas#endmeeting16:25
opendevmeetMeeting ended Tue Apr 29 16:25:21 2025 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:25
opendevmeetMinutes:        https://meetings.opendev.org/meetings/nova/2025/nova.2025-04-29-16.01.html16:25
opendevmeetMinutes (text): https://meetings.opendev.org/meetings/nova/2025/nova.2025-04-29-16.01.txt16:25
opendevmeetLog:            https://meetings.opendev.org/meetings/nova/2025/nova.2025-04-29-16.01.log.html16:25
fwieselthanks everyone16:25
elodillesthanks o/16:25
gibifwiesel: yeah I understand that you don't want a full blown spec. Maybe start a spec and only fill the up until the Use Case section16:26
gibiso define the what and keep the how empty16:26
gibiwhat and why16:26
* gibi thinks that this was the speediest nova meeting ever :)16:27
gmaanbauzas: latest-microversion job in periodic-  https://review.opendev.org/c/openstack/tempest/+/94845816:27
opendevreviewDan Smith proposed openstack/nova master: WIP Example NVMe cleaning script for one-time-use  https://review.opendev.org/c/openstack/nova/+/94844616:39
melwittgibi: cool thanks for fixing it!16:45
sean-k-mooneyif by resize between diffent hyperviors that actully means between differnt virt driver then that woudl need a full spec16:56
sean-k-mooneybecause that bring up the qustion what do you do with things like the disk format16:57
sean-k-mooneyeven if we do it via shelve liek we do for cross cell i expect there to be dragons16:57
dansmithon the one hand, it shouldn't be a problem at all,17:02
dansmithexcept for the disk format, the metadata that might make it not a candidate for the other hypervisor, etc17:02
dansmithso I expect there are dragons, but not fundamental ones17:02
sean-k-mooneywell even simple things like libvirt expect to be able to scp the disks17:03
dansmitheither way, I'm not sure how anyone could argue that a spec isn't warranted :)17:03
sean-k-mooneyim sure vmware/hypver/ironic woudl have optinons about that17:03
dansmithsean-k-mooney: I meant for the shelve-based approach, which I think would be the best for something17:03
dansmithlike cross-cell resize does17:03
sean-k-mooneyoh right 17:03
sean-k-mooneyya shelve is likely mortly ok17:04
sean-k-mooneyalthoguh windows may be unhappy if the mosther board that is virutalise and all the periferals 17:04
sean-k-mooneychange form whatevver vmware provides to q3517:04
dansmithsure, that's all under the metadata umbrella I meant above17:04
sean-k-mooneyah17:05
sean-k-mooneyi tought you ment the instnace metadata 17:05
sean-k-mooneybut ya liek it might work17:05
dansmithno, image meta17:05
sean-k-mooneybut im not sure if thaty is what they ment about hypervior above17:05
dansmithlike requesting something libvirt- or vmware-specific that just makes the scheduler not even willing to send it to another host, etc17:05
sean-k-mooneyoh no it is17:05
dansmithright17:05
sean-k-mooneyanyway i guess they may have jost wanted to avoid a spec initall to get some high level input17:06
sean-k-mooneyi.e. is this somethign we woudl ever want to supprot17:06
sean-k-mooneyi dont think its unreasonable but alos not a high on my wishlist17:06
dansmithhard to say if we could/would without knowing the dragons, which is what a spec is for :D17:06
dansmithagreed17:07
sean-k-mooneyif you had a vmware backed openstack17:07
dansmithI wonder if the ask is coming from an escape-the-20x-license-increase thing17:07
sean-k-mooneyand wanted to move to libvirt i guess it woudl be nice to jsut rezie the vms to do that17:07
dansmiththere are also community and commercial migration functions, so..17:07
sean-k-mooneyya that what im wondering too because fwiesel has been trying to maintain the vmware dirver bcause sap use it internally17:08
sean-k-mooneyso this may be realted to enabling them to move to libvirt goign forward17:08
sean-k-mooneyso migratekit or os-migrate might help there17:08
opendevreviewSylvain Bauza proposed openstack/nova master: Add mtty/mdpy support for testing fake mdevs  https://review.opendev.org/c/openstack/nova/+/89810017:10
opendevreviewSylvain Bauza proposed openstack/nova master: WIP : Add mtty support to nova-next  https://review.opendev.org/c/openstack/nova/+/92214017:10
*** benj_2 is now known as benj_17:39
opendevreviewMerged openstack/nova master: Remove python 3.9  support  https://review.opendev.org/c/openstack/nova/+/94839218:28
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179219:43
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179219:43
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179219:43
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179219:43
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179219:47
opendevreviewsean mooney proposed openstack/nova master: Add admin docs to cover limitations of OTU devices  https://review.opendev.org/c/openstack/nova/+/94849222:13
sean-k-mooneydansmith: i have tired to capture some fo the design constratis and limiation around OTU device and what a cleaning script, process shoudl do in terms of pre/post constratis22:15
sean-k-mooneydansmith: ^ im not sure if you had anything similar planned as a follow up but hopefully this will be useful for folks.22:16
sean-k-mooneyi have tired to spellcheck it but i dint pass it though grammerly. hopefully it pretty readable 22:17
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179222:19
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179222:26
opendevreviewIvan Anfimov proposed openstack/placement master: Remove tags from README  https://review.opendev.org/c/openstack/placement/+/94179222:26

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