| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2026-07-13 | |||
| 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 | |
| 08:59:38 | bauzas | I was thinking the cycle model was defined in https://opendev.org/openstack/governance/src/branch/master/reference/projects.yaml but alas no | |
| 08:59:50 | sean-k-mooney[m] | its set in 2 places, you can spcify it in the grovernace repo but tis also in the release repo in the deliverabvle | |
| 09:00:22 | sean-k-mooney[m] | bauzas: it can be yes we dont have it set which means its coming form a default adn or cofniguration in the release repo | |
| 09:00:38 | bauzas | found the definition | |
| 09:01:38 | bauzas | https://opendev.org/openstack/releases/src/branch/master/deliverables/hibiscus/placement.yaml | |
| 09:01:49 | sean-k-mooney[m] | where? the inline release-model: in the deliverable is set form somewhere else | |
| 09:01:54 | bauzas | that's why the release tool accepted b1 for placement | |
| 09:02:13 | sean-k-mooney[m] | that is genereate by the tool automaticly each cycle | |
| 09:02:27 | sean-k-mooney[m] | when we create the first deliberable for that release | |
| 09:02:51 | bauzas | ,o | |
| 09:02:52 | bauzas | no | |
| 09:02:54 | sean-k-mooney[m] | but where is the data for that coming form i tought it was coming form the governace repo | |
| 09:03:09 | bauzas | you can use the tool for generating optional milestone releases | |
| 09:03:20 | bauzas | please look at what we discussed just before | |
| 09:03:41 | bauzas | https://opendev.org/openstack/releases/src/branch/master/deliverables/hibiscus/os-vif.yaml os-vif is indeed cycle-with-intermediary | |
| 09:03:45 | sean-k-mooney[m] | i knwo you can your not answering my question | |
| 09:03:49 | bauzas | and os-traits is independent | |
| 09:04:12 | bauzas | are you asking me how the tool works ? I don't know | |
| 09:04:22 | sean-k-mooney[m] | the release model in the delverable file is set form somethign else or a human ahas been seting it for every proejct for every release and we have not been doing that | |
| 09:04:28 | sean-k-mooney[m] | i am not | |
| 09:04:42 | bauzas | are you asking who defines that model ? that's humans | |
| 09:04:45 | sean-k-mooney[m] | i am telling you that i know about the release-model in the release repo | |
| 09:04:49 | bauzas | that's us | |
| 09:04:58 | sean-k-mooney[m] | no | |
| 09:05:03 | sean-k-mooney[m] | i am not askign that either | |
| 09:05:46 | sean-k-mooney[m] | i am saying the release-model in the release repo is set form somewhere else, or a human has been seting it by hand for every new release for every project | |