| Posted | Nick | Remark | |
|---|---|---|---|
| #openstack-nova - 2025-01-28 | |||
| 16:16:01 | bauzas | the periodics are in a good shape | |
| 16:16:10 | bauzas | any gate failure you wanna talk ? | |
| 16:16:55 | sean-k-mooney | i havent really been looking at the gate in a while but the only fialures i notices were the usual volume or kernel panic issues | |
| 16:17:08 | bauzas | ditto here | |
| 16:17:09 | sean-k-mooney | with that said tehree was a fix for some of the volume tests in tempest | |
| 16:17:17 | sean-k-mooney | so that may help | |
| 16:17:19 | bauzas | and I definitely need to do a round of reviews | |
| 16:17:50 | sean-k-mooney | https://review.opendev.org/c/openstack/tempest/+/939663/2 and https://review.opendev.org/c/openstack/tempest/+/939633/11 for context | |
| 16:18:09 | sean-k-mooney | that shoudl help with some of the volume failures in test_instances_with_cinder_volumes | |
| 16:18:57 | sean-k-mooney | tl;dr those tests were not waiting for the vm to be sshabel ebfore trying to attach the voluems | |
| 16:18:59 | bauzas | good call, we can give them a shot | |
| 16:19:29 | sean-k-mooney | we can move on unless anyone else what to raise something | |
| 16:19:32 | bauzas | yup | |
| 16:19:36 | bauzas | #topic Release Planning | |
| 16:19:42 | bauzas | #link https://releases.openstack.org/epoxy/schedule.html | |
| 16:19:48 | bauzas | #info Nova deadlines are set in the above schedule | |
| 16:19:54 | bauzas | #info 4 weeks before Feature Freeze | |
| 16:19:57 | bauzas | the clock is ticking | |
| 16:20:29 | bauzas | as I said, I'll try to do a round of reviews as soon as my availability raises once I'm done with implementing a few things | |
| 16:20:49 | bauzas | as a reminder: | |
| 16:20:52 | bauzas | #info we'll try to create as os-traits release by this week, please provide your os-traits patches sooner than later. | |
| 16:21:00 | bauzas | Uggla: still volunteering for the release ? | |
| 16:21:08 | Uggla | sure | |
| 16:21:19 | sean-k-mooney | are there pending patches | |
| 16:21:24 | sean-k-mooney | that need review | |
| 16:21:48 | gibi | I think we need the vtpm one | |
| 16:22:05 | gibi | https://review.opendev.org/c/openstack/os-traits/+/940191 | |
| 16:22:05 | sean-k-mooney | https://review.opendev.org/c/openstack/os-traits/+/940191 | |
| 16:22:21 | sean-k-mooney | ok ill try and do a pass on the open patcher after the meeting | |
| 16:22:36 | Uggla | yes you were faster than me. | |
| 16:22:53 | sean-k-mooney | actully that look like the only relevent one | |
| 16:23:00 | sean-k-mooney | https://review.opendev.org/q/project:openstack/os-traits+status:open | |
| 16:23:11 | sean-k-mooney | the rest are not requried | |
| 16:23:22 | Uggla | btw I'm waiting this patch to be merged, then I'll go ahead with the release. | |
| 16:23:47 | sean-k-mooney | i have +2'd it | |
| 16:24:06 | sean-k-mooney | the traits alinght to what we dicussed in the spec and follow our naming convention | |
| 16:24:12 | sean-k-mooney | so looks good to me | |
| 16:24:17 | bauzas | I just +wd it, I was just reading the spec | |
| 16:24:20 | Uggla | \o/ | |
| 16:24:37 | bauzas | so yeah, it was a nobrainer | |
| 16:24:49 | gibi | awesome | |
| 16:24:59 | Uggla | yep reviewing that one was not difficult. ;) | |
| 16:25:40 | bauzas | #action Uggla to release os-traits this week | |
| 16:25:47 | bauzas | moving on | |
| 16:25:57 | bauzas | #topic Review priorities | |
| 16:26:05 | bauzas | #link https://etherpad.opendev.org/p/nova-2025.1-status | |
| 16:26:22 | bauzas | I'll be honest, I have some cleanup to do on that etherpad | |
| 16:29:00 | bauzas | I guess we can move on | |
| 16:29:09 | bauzas | #topic Stable Branches | |
| 16:29:38 | gibi | elodilles is out | |
| 16:29:42 | bauzas | ah ok | |
| 16:29:53 | bauzas | I guess we can discuss that next week then | |
| 16:29:56 | gibi | sure | |
| 16:30:06 | bauzas | #topic vmwareapi 3rd-party CI efforts Highlights | |
| 16:30:10 | bauzas | fwiesel: around ? | |
| 16:30:37 | fwiesel | Hi, I discovered another regression in the networking driver and investigating that. | |
| 16:30:47 | fwiesel | So, any failures are due to that. | |
| 16:30:52 | fwiesel | (In master that is) | |
| 16:30:59 | fwiesel | That's from my side. | |
| 16:31:16 | bauzas | oh sad newds | |
| 16:31:33 | bauzas | good luck then and thanks for your report | |
| 16:31:39 | fwiesel | Thanks. | |
| 16:31:42 | bauzas | #topic Open discussion | |
| 16:31:53 | bauzas | we have one item for today | |
| 16:31:58 | bauzas | (r-taketn) Request for comments on the following - Discussion of ArmCCA feature merge | |
| 16:32:01 | bauzas | r-taketn: around ? | |
| 16:32:04 | r-taketn | Hi, thanks for adding this to the agenda. | |
| 16:32:09 | bauzas | #link https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/thread/244U52T3HINVWUFSMPMA45A67BUPAQGK/ | |
| 16:32:24 | r-taketn | Please review the above mailing list about an Arm CCA new feature. | |
| 16:32:33 | r-taketn | In particular, We would like to discuss the feature merging timeline mentioned at the beginning with nova core developers. | |
| 16:32:57 | opendevreview | Merged openstack/os-traits master: Add vTPM secret policy traits https://review.opendev.org/c/openstack/os-traits/+/940191 | |
| 16:32:57 | r-taketn | We are proposing development for a feature (ArmCCA) targeting hardware not yet released to the market. | |
| 16:33:21 | r-taketn | We would appreciate your comments on the feasibility of merging a feature for unreleased hardware. | |
| 16:33:43 | sean-k-mooney | r-taketn: we do not allow meging enabling code for unreleased hardware | |
| 16:33:54 | sean-k-mooney | wwe are also passed the spec approveal deadline for this cycle | |
| 16:34:14 | sean-k-mooney | but it can be proposed for next cycle if the hardware is aviable | |
| 16:34:47 | sean-k-mooney | we only merge hardware enabling code after the hardware is generally aviabel in teh market not before | |
| 16:34:51 | bauzas | yes indeed, there are a few limitations that you should be aware | |
| 16:35:17 | r-taketn | To our knowledge, no products currently support Arm CCA. FUJITSU-MONAKA [1], scheduled for release by Fujitsu in 2027, may be the first such product. | |
| 16:35:20 | bauzas | usually, we would want to make sure that our upstream CI can test specific hardware | |
| 16:35:46 | bauzas | if specific hardware can't be tested on upstream CI, then there are two possibilities : | |
| 16:36:35 | bauzas | 1/ either you're able to test nova against fake hardware that reproduces the hardware behaviour | |
| 16:36:49 | bauzas | 2/ or you have to provide third-party CI | |
| 16:38:37 | sean-k-mooney | while 2 is preferd it much more overhead btu actull tests that the feature works end to end | |
| 16:38:46 | r-taketn | Does this mean that if we submit third-party CI and comprehensive test results, there is a possibility that they will be merged before the hardware release? | |
| 16:38:55 | sean-k-mooney | no | |
| 16:39:28 | sean-k-mooney | we have strictly applied the requriemetn that hardware is released before its enabeld in the past. we coudl change that | |
| 16:39:34 | sean-k-mooney | but it would eb a break with precedent | |
| 16:39:52 | sean-k-mooney | we also require that any kernel/qemu/libivrt supprot is in a public offcial release | |
| 16:40:02 | sean-k-mooney | so if this requires qemu changes | |
| 16:40:08 | sean-k-mooney | or libvirt | |
| 16:40:23 | sean-k-mooney | those must be in a public offical release formr that upstream proejct before we can enabel it in nova | |
| 16:41:07 | r-taketn | ok, i understood. | |
| 16:41:08 | sean-k-mooney | is arm CCA supported in the kernel, qemu and libvirt today | |
| 16:41:56 | r-taketn | no. LinuxKernel, qemu and libvirt are being developed now. | |
| 16:42:22 | sean-k-mooney | if you want to propose poc patches and prepare them that is fine | |
| 16:42:41 | sean-k-mooney | but we cant merge them until the deps are resolved | |
| 16:42:56 | bauzas | indeed, nothing blocks you to create a feature branch that you could use for your own testing | |
| 16:44:17 | bauzas | what I could suggest you is to come back to us as soon as kernel, QEMU and libvirt versions are released upstream so then we can discuss the alternatives | |
| 16:44:49 | sean-k-mooney | just looking at https://patchwork.kernel.org/project/qemu-devel/cover/20240419155709.318866-2-jean-philippe@linaro.org/ | |