On 04/06/2025 10:49, taketani.ryo@fujitsu.com wrote:
Thank you for replying, Sean.
you can start the discussion the one think i will say is that its unlikely that many will have time to implement this for you so you and your team will have to take lead on doing the work to run the third party ci on your own hardware and make the results available puhlicly. I understand that while meeting the all conditions is ultimately necessary, we should focus on preparing for and aligning our efforts with the community towards submitting a third-party CI [1] environment and the results. Is my understanding correct?
If so, I'm committed to setting up the third-party CI and making the results publicly available.
i used ot recommend the OVH Performance Hosting plan for this https://www.ovhcloud.com/en-ie/web-hosting/compare/ for about ~€150 a year you get 500GB of storage, multiple 1 GB dbs that you can use if you want to as part of your ci. and plenty of bandwidth that allows you to host the ci logs publicly outside your company firewall. when i was involved in the intel third party ci that what we used but since they the have added a Professional Hosting option with 250G of storage but you may not have enough space to retain logs for up to 30 days with that plan. it is half the cost however. if your using zuul or just the zuul playbooks you can pretty trivially scp the logs form the folder on the executor too the root of the web share since you have ssh access in both plans. i know when we spoke to our internal lab team being able to fully outsource the log storage out side our cooperate network made them very happy so if you can and your company does not have a fatality to do that already i would consider ovh ro similar.
In addition, regarding the phrase "on your own hardware", can I use our internally available hardware for CI testing?
yes if you lab security policy allows that then you can use any hard ware you have available when running a third party ci. i don't think we will have a way to use that hardware easily in the first party ci so that really only an option if you run the ci yourself.
in your case since you want toe test a hardware feature that likely cannot be emulated?
if you already have an internal jenkins system with your own provisioning system you can use that instead to set up Arm CCA environment can be emulated by QEMU[2]. Can this be leveraged for proceeding CI testing?
maybe, for third party ci yes, you could create vms to emulate the compute nodes and then install opentack on those emulated compute nodes the constraint there would be performance and the ability to use nested CCA. if it is supported by libvirt then nova could be enhanced to support enabling the emulation and the eventually once one of our first party open-stack providers supports this feature we could use that in the first party ci. That will likely take 1-2+ years to get in place so i would not recommend that as the initially approach.
For example, we could set up and run CI tests in an emulated environment before executing them on the actual hardware. Internally, we are planning to do this. Would it be valuable to share this environment and the results with the community? By doing this, we'd like to discuss how to provide CI in advance.
yes i can see a number of options. if you run a third party ci you can automate creating and deleting the vms to emulate CCA then you can allocate those vms too ci job as worker/compute nodes. i don't think providing access to the community would really be useful but if you provided documentation for how to deploy a vm that is capable of emullating CCA and installing devstack in that that would be useful.
[1] https://docs.openstack.org/infra/openstackci/third_party_ci.html [2] https://linaro.atlassian.net/wiki/spaces/QEMU/pages/29051027459/Building+an+...
Regards,
Ryo Taketani