Earlier  
Posted Nick Remark
#openstack-nova - 2026-07-10
14:21:20 sean-k-mooney gibi: sorry i just didnt get as far with the futurist work as i hoped for today. im going to wrap up shortly but ill take a look at it again on monday
14:21:55 gibi sean-k-mooney: no worries. Have a nice weekend
14:23:44 sean-k-mooney i might push what i have before i leave i need to pack a bag and trun on the ac in my car to cool it down or ill melt when i get into it
14:24:27 sean-k-mooney i plugged it in to charge ealer and the temperture in the car was 35c which is what i get for parking it facing uphil and south on a nice day
14:27:42 sean-k-mooney oh i was under estermating it say its at 44c right now. i am happy it also has a remote ac feature
15:32:48 opendevreview Mike Lowe proposed openstack/nova master: Fix PCI cleanup when a move claim is aborted https://review.opendev.org/c/openstack/nova/+/996822
17:57:15 opendevreview Merged openstack/nova master: tests: use file-backed Placement SQLite in functional threading https://review.opendev.org/c/openstack/nova/+/992581
19:47:29 gmaan gibi: sean-k-mooney[m] stuck on other things downstream but I will check and reply on bug/gerrit. most probably today otherwise Monday
#openstack-nova - 2026-07-11
01:51:11 opendevreview Takashi Kajinami proposed openstack/nova master: libvirt: Use native DictOpt for disk_cachemode https://review.opendev.org/c/openstack/nova/+/915390
01:51:11 opendevreview Takashi Kajinami proposed openstack/nova master: libvirt: Validate valid cache mode at config input layer https://review.opendev.org/c/openstack/nova/+/933327
01:52:34 opendevreview Takashi Kajinami proposed openstack/nova master: Remove unused default argument https://review.opendev.org/c/openstack/nova/+/922073
10:25:05 opendevreview Takashi Kajinami proposed openstack/nova master: Remove unused default argument https://review.opendev.org/c/openstack/nova/+/922073
13:21:41 opendevreview Takashi Kajinami proposed openstack/nova stable/2026.1: Return 400 for invalid properties for locked memory https://review.opendev.org/c/openstack/nova/+/996878
15:20:42 opendevreview Takashi Kajinami proposed openstack/nova master: doc: Update cursive repository path https://review.opendev.org/c/openstack/nova/+/996880
16:07:10 opendevreview Takashi Kajinami proposed openstack/nova master: Remove tempest-pg-full https://review.opendev.org/c/openstack/nova/+/996887
17:12:50 opendevreview Takashi Kajinami proposed openstack/placement master: tox: Use constraints option https://review.opendev.org/c/openstack/placement/+/996893
#openstack-nova - 2026-07-13
03:19:05 opendevreview yaguang proposed openstack/nova master: libvirt: enable Hyper-V evmcs on Intel VMX hosts https://review.opendev.org/c/openstack/nova/+/995620
06:37:02 opendevreview Bhavana proposed openstack/nova master: Add Minimal Displacement Solver for MIG GPU Repartitioning https://review.opendev.org/c/openstack/nova/+/996058
06:42:09 opendevreview Bhavana proposed openstack/nova master: Add Minimal Displacement Solver for MIG GPU Repartitioning https://review.opendev.org/c/openstack/nova/+/996058
08:16:03 gibi sean-k-mooney[m] gmaan: I think we need to tweak the functional-py313-threading job as it pulls placement from pypi but we needed to land a fix in placement master that is not release yet.
08:16:24 gibi https://zuul.opendev.org/t/openstack/build/fdefa3b20f4f471cb6f0ef9b29ccd241/log/job-output.txt#870
08:18:05 sean-k-mooney[m] We can use tox siblings and required projects I think to pull master
08:18:17 sean-k-mooney[m] Or we can just release placement
08:24:27 gibi I assuem that zuul's required-projects only work with devstack based jobs not tox based ones
08:24:30 bauzas gibi: good call
08:24:39 gibi I'm trying to find an example of tox siblings
08:24:41 bauzas we can do a placement release indeed
08:24:50 bauzas that looks to me the simpliest
08:24:59 gibi can we release from master randomly even if placement is expected to be release at milestones?
08:25:06 gibi elodilles: ^^ cc
08:25:18 bauzas gibi: we can do a rc2
08:25:28 bauzas lemme check the release cycle
08:25:40 gibi we are not in an rc period
08:25:45 bauzas we can do milestones
08:25:47 gibi M2 is in a week or se
08:25:50 gibi so
08:25:54 bauzas oh sorry, I meant milestone-2
08:26:03 gibi can we do an M2 early/
08:26:05 gibi ?
08:26:07 bauzas yes
08:26:13 bauzas or any milestone
08:26:14 bauzas sec
08:26:40 bauzas https://releases.openstack.org/reference/release_models.html#cycle-with-rc
08:26:43 gibi OK, if we can that is indeed the cheapest
08:27:00 bauzas "The “cycle-with-rc” model describes projects that produce a single release at the end of the cycle, with one or more release candidates (RC) close to the end of the cycle and optional development milestone betas published on a per-project need."
08:27:22 bauzas we can create any optional milestone release if we wantr
08:27:25 gibi ^^ that means to me that we need to push an rc1 now
08:27:45 bauzas no
08:27:48 gibi that description does not talk about milestone releaes
08:27:52 bauzas we will need to publish a rc1
08:27:53 elodilles gibi: yes we can release a 16.0.0.0b1 or 0b2 release anytime
08:27:56 gibi OK
08:27:57 bauzas that ^
08:28:01 gibi I will propose a b1 now
08:28:05 gibi thanks
08:28:36 bauzas we have to create a RC1 at least, yes
08:28:44 elodilles not many project do that, but some do release beta releases (milestone releases)
08:29:03 bauzas but as elodilles said, we can create *any* milestone releases
08:29:03 elodilles just merged a couple of neutron related beta release patches in the morning ;)
08:29:18 bauzas we did created m1, m2 and m3 before :)
08:29:28 bauzas like 10 years before
08:29:35 gibi yeah but not in the last couple of years
08:29:51 gibi but it seems the release tooling correctly chose b1 if I ask for a hibiscus milestone release
08:29:56 gibi so all seems good
08:30:19 elodilles :]
08:30:38 bauzas lovely
08:31:17 bauzas gibi: given Uggla is on PTO, please ping me the release change and I'll +1
08:33:11 gibi https://review.opendev.org/c/openstack/releases/+/996992
08:33:54 gibi bauzas: elodilles: ^^ please take a look
08:35:27 elodilles gibi: LGTM, just need a Verified+1 and a release-liaison CR+1 o:)
08:35:47 gibi bauzas will do that :)
08:37:34 elodilles :]
08:38:06 opendevreview Balazs Gibizer proposed openstack/nova master: Speed up functional test in threading mode https://review.opendev.org/c/openstack/nova/+/996500
08:38:06 opendevreview Balazs Gibizer proposed openstack/nova master: Check service_ref before destroy https://review.opendev.org/c/openstack/nova/+/996793
08:38:30 gibi this is two small stability / performance fixes for the functional test in threading mode
08:38:49 gibi if somebody want to look :)
08:38:52 opendevreview Takashi Kajinami proposed openstack/nova master: Update documentations for AMD SEV-SNP support https://review.opendev.org/c/openstack/nova/+/995090
08:39:02 bauzas gibi: I can take a look
08:39:08 opendevreview Takashi Kajinami proposed openstack/nova master: Remove [libvirt] num_memory_encrypted_guests https://review.opendev.org/c/openstack/nova/+/995120
08:39:14 opendevreview Takashi Kajinami proposed openstack/nova master: Use domain capabilities to detect SEV-SNP support https://review.opendev.org/c/openstack/nova/+/996316
08:40:00 gibi this is more involved https://review.opendev.org/q/topic:%22bug/2160224%22 but also needed evetually for the functional test as it is failing intermittently due to this race
08:44:31 bauzas gibi: ok let's merge the two ones first then
08:44:45 gibi sure
08:44:50 gibi thanks
08:45:06 gibi I got gmaan looking at the 3rd one as that is a slight API change
08:49:39 sean-k-mooney[m] gibi: sorry hadnat actully started yet. i though placement like now was release-with-intermediary not release-with-rc
08:50:49 sean-k-mooney[m] i didnt think we had any proejct that were not https://releases.openstack.org/reference/release_models.html#cycle-with-intermediary as part of the upstream compute team
08:54:24 gibi sean-k-mooney[m]: no worries. the release tooling allowed me to push 16.0.0b1 for placement and it seem the release team is OK with it
08:54:34 sean-k-mooney[m] i feel like that got incrrectly change in the release repo at some poitn
08:54:45 sean-k-mooney[m] well to me this is a bigger problem then that
08:55:38 sean-k-mooney[m] when we moved from cycle-with-milestones i tought we moved to cycle-with-intermediary
08:56:35 sean-k-mooney[m] cycle-with-rc project should not have release at milestone 1 or 2 like we have been doing for nova
08:57:22 sean-k-mooney[m] hum or maybe we havnt done that for nova
08:58:21 gibi i need to defer to the release team :)
08:58:24 sean-k-mooney[m] hum i see
08:58:31 sean-k-mooney[m] elease-model: cycle-with-intermediary is there for os-vif
08:58:39 bauzas sean-k-mooney[m]: I can't remember where we do set the cycle models for each of the repos but I'm pretty sure placement is cycle-with-rc
08:58:40 sean-k-mooney[m] and we are usign that for our libs
08:58:50 sean-k-mooney[m] but we have cycle-with-rc for the service projects
08:59:13 bauzas some of our libs are cycle-with-intermediary and some are independent yes

Earlier   Later