Thank you for replying, Sean.
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.
I understand that I need to scp CI test logs to external storage and retain them. I will use the suggested methods for selecting the appropriate approach.
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.
I understand that providing publicly accessible testing result logs from an emulated environment would not be useful. Instead, I should commit documentation on how to emulate a CCA environment and build OpenStack within it. We cannot run ci tests on actual hardware in the immediate future. So, we will proceed ci testing with the following steps: 1. Run CI tests on an emulated environment and contribute documentation on how to emulate a CCA environment and build DevStack. 2. Run CI tests on actual hardware and commit CI environment configurations and logs.
you can however start setting up third party testing and and testing before all of the component are available in ubuntu
I'd like to seek clarification on an above comment, specifically the one received two turns ago. Is it correct that "you can however start setting up third party" refers to the possibility of doing internal preparation for CI testing? 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? Regards, Ryo Taketani