| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2023-11-21 | |||
| 16:15:20 | elodilles | np :) | |
| 16:15:28 | bauzas | I'll upload a new rev | |
| 16:15:39 | elodilles | thx | |
| 16:16:13 | bauzas | #info Caracal-2 (and spec freeze) milestone in 7 weeks | |
| 16:16:41 | bauzas | as a reminder, we'll have another spec review day | |
| 16:17:13 | bauzas | now, I have a question | |
| 16:17:41 | bauzas | we said necxt week that we could add a caracal-1 tag for nova | |
| 16:17:53 | bauzas | but then I looked at all the releases we did from yoga | |
| 16:18:01 | bauzas | and none of them have any milestone tag | |
| 16:18:10 | bauzas | hence my question | |
| 16:18:16 | bauzas | should we create a specific milestone for Nova and Placement? | |
| 16:18:19 | bauzas | I don't think so | |
| 16:18:21 | sean-k-mooney | we are not required to create them. we are just required to have 1 rlease before the final release | |
| 16:18:29 | sean-k-mooney | so the RC-1 release covers that | |
| 16:18:31 | bauzas | this is rc1 | |
| 16:18:36 | bauzas | yeah | |
| 16:18:58 | sean-k-mooney | i dont personlly think milestone release make sense for nova | |
| 16:18:58 | bauzas | and I very quickly looked at cinder, they don't add a milestone too | |
| 16:19:03 | sean-k-mooney | or non lib projects | |
| 16:19:07 | bauzas | yup | |
| 16:19:11 | elodilles | no need for Caracal-1 (.b01) release (which is not rc1) | |
| 16:19:23 | elodilles | for nova & placement | |
| 16:19:27 | elodilles | imo | |
| 16:19:34 | bauzas | the only usecase would be for operators if they want to test milestones | |
| 16:19:52 | elodilles | (it's just a possibility, but we don't need) | |
| 16:19:54 | bauzas | but we haven't had any operators doing this from a long time | |
| 16:19:59 | bauzas | okay | |
| 16:20:01 | sean-k-mooney | they could just deploy a commit at that point | |
| 16:20:21 | sean-k-mooney | googing though the release process for that has very little return | |
| 16:20:36 | sean-k-mooney | we do it for libs since we do not install libs form git as the default | |
| 16:20:40 | bauzas | #action bauzas to not provide a caracal-1 tag actually (compared to what we said on the previous weekly meeting) | |
| 16:20:42 | sean-k-mooney | unlike service projects which we do | |
| 16:20:49 | bauzas | I'm fine | |
| 16:21:00 | bauzas | I just wanted to remove the action item that we agreed last week | |
| 16:21:01 | elodilles | +1 | |
| 16:21:20 | bauzas | I don't know how many people read our meeting minutes but... :) | |
| 16:21:33 | bauzas | anyway, moving on | |
| 16:21:46 | bauzas | #topic Review priorities | |
| 16:21:51 | bauzas | #link https://etherpad.opendev.org/p/nova-caracal-status | |
| 16:21:53 | bauzas | hehe | |
| 16:22:21 | bauzas | so, folks who want to add some bugfixes can now add them in ^ | |
| 16:22:41 | bauzas | we have a specific section | |
| 16:22:55 | bauzas | and cores, please look at this etherpad in order to know what to review | |
| 16:23:05 | gibi | aye sir :) | |
| 16:23:34 | bauzas | nay, I'm not a sir :) | |
| 16:23:43 | gibi | :) | |
| 16:23:43 | bauzas | :D | |
| 16:23:51 | bauzas | #topic Stable Branches | |
| 16:24:00 | bauzas | elodilles: please | |
| 16:24:02 | gibi | monsieur ? :) | |
| 16:24:07 | elodilles | :) | |
| 16:24:15 | elodilles | #info stable gates don't seem blocked | |
| 16:24:25 | elodilles | except now yoga with nova-emulation job :D | |
| 16:24:41 | elodilles | which is almost constantly failing as it looks... | |
| 16:24:44 | sean-k-mooney | do we want to nuke that | |
| 16:24:59 | bauzas | +1 | |
| 16:25:03 | elodilles | is it needed for yoga? | |
| 16:25:04 | sean-k-mooney | we woudl not be running it on unmaintaed anyway | |
| 16:25:18 | sean-k-mooney | and if its brokekn im not sure it worth fixing | |
| 16:25:19 | bauzas | unless we want to unmaintan yoga | |
| 16:25:27 | bauzas | *now* I think | |
| 16:25:30 | sean-k-mooney | elodilles: it was ment to be in perodic-weekly | |
| 16:25:37 | sean-k-mooney | not in check | |
| 16:25:46 | sean-k-mooney | so while it shoudl work its not required | |
| 16:25:56 | elodilles | sean-k-mooney: ACK, i'll check and try to remove from the check pipeline then | |
| 16:26:25 | bauzas | +1 | |
| 16:26:28 | elodilles | bauzas: we'll unmaintain yoga soon, but let's fix that for now if that is possible by eliminating that job o:) | |
| 16:27:25 | elodilles | it's also needed if we want a final release off yoga before it gets unmaintained | |
| 16:27:47 | elodilles | btw, stable releases: | |
| 16:27:51 | elodilles | #info stable release patches still open for review: https://review.opendev.org/q/project:openstack/releases+is:open+intopic:nova | |
| 16:28:17 | elodilles | do we still want to wait for patches? | |
| 16:28:30 | elodilles | a couple of stable bug fix have landed meanwhile | |
| 16:28:39 | bauzas | I think I clicked +2 on a yoga change | |
| 16:29:07 | sean-k-mooney | the one from tobias-urdin | |
| 16:29:08 | bauzas | elodilles: what's the deadline ? | |
| 16:29:10 | elodilles | (and that failed due to the nova-emulation) | |
| 16:29:12 | bauzas | sean-k-mooney: yup | |
| 16:29:24 | sean-k-mooney | we should include that in the final release | |
| 16:29:51 | elodilles | bauzas: no strict deadline planned, as we (community) are already late, so just ASAP :) | |
| 16:30:49 | sean-k-mooney | we can quickly update the jobs after the meeting and then recheck the patch | |
| 16:30:54 | elodilles | i mean the EM transition deadline was Nov 2nd, but meanwhile the process is changing and now we need to move to Unmaintained instead | |
| 16:31:02 | elodilles | sean-k-mooney: +1 | |
| 16:31:24 | bauzas | okay | |
| 16:31:34 | elodilles | then the general message then: | |
| 16:31:35 | bauzas | cool enough | |
| 16:31:37 | elodilles | #info stable branch status / gate failures tracking etherpad: https://etherpad.opendev.org/p/nova-stable-branch-ci | |
| 16:31:56 | elodilles | add here stable gate issues if you encounter one ^^^ | |
| 16:32:09 | elodilles | and that's it i think | |
| 16:33:45 | bauzas | ++ | |
| 16:33:52 | bauzas | moving on then | |
| 16:34:06 | bauzas | #topic Open discussion | |
| 16:34:09 | bauzas | there was one item | |
| 16:34:13 | bauzas | in the agenda | |
| 16:34:22 | bauzas | (fwiesel) vmwareapi driver deprecation/removal: SAP wants to step up provide the resources to keep the driver maintained (CI, tests coverage, code changes, ...?). what would be needed? | |
| 16:34:27 | fwiesel | Hi, that would be me. | |
| 16:34:35 | bauzas | yes indeed | |
| 16:35:13 | fwiesel | So, essentially me and my colleagues talked to our management, and we have the commitment from them to dedicate 1FTE just for upstream work. | |
| 16:35:55 | fwiesel | My understanding is, the most pressing issue would be to have a working stable CI worker for the vmware api, followed by cleanup work, test-coverage, etc... | |
| 16:36:10 | fwiesel | Is that correct? | |
| 16:36:52 | bauzas | we basically deprecated the virt driver by Bobcat | |