I wonder if we can apply the same policies which we agreed with for AMD SEV or SEV-ES. - All required features have been implemented in kernel/qemu/libvirt (or any other dependent software) and we know exactly what should be checked/configured by nova (from documentations). - Do not require 3rd party CI due to limited availability of hardware - Require functional tests with fake libvirt driver (and a few more mocks) which simulates the behavior of kernel/qemu/libvirt with ARM-CCA features enabled. - Actual functionality with actual hardware(*1) needs to be tested locally by the developer IIUC this was one of the suggestions bausas mentioned when this topic was first discussed in the past nova meeting (If I understand what he means by "fake hardware") and I didn't find actual specific concern discussed to make third party CI a strict blocker. I know that having CI which can actually test the functionality is preferred but as you was mentioned earlier it may require a lot of overheads. [1] https://meetings.opendev.org/meetings/nova/2025/nova.2025-01-28-16.00.log.ht... (*1) Note that actual CPU with ARM CCA feature is not currently available. All development of ARM CCA support features in kernel/qemu/libvirt use a simulated CPU (which is actually a emulated CPU provided by forked QEMU) and the initial development in OpenStack may follow the same approach. On 6/18/25 7:03 PM, taketani.ryo@fujitsu.com wrote:
Hi all and Sean,
Is the ultimate goal to store CI test results from real hardware running upstream versions of OS/libvirt/QEMU/LinuxKernel, and will approval of those results be required for merging?
I apologize for the lack of clarity in my previous question. I'd like to rephrase and clarify my question.
For merging and releasing the nova CCA code, is it mandatory to have Third Party CI running on bare metal (non-emulated) environments? Or is Third Party CI on emulated environments also acceptable?
Furthermore, how long should the Third-Party environment be maintained? Are there any policies (e.g., "X number of years after the CCA feature is released")?
Regards, Ryo Taketani