Oh hello, For the last couple of years I've been working on trying to improve the VDI experience in OpenStack by enriching our SPICE capabilities. A series of patches has now landed in Nova that enable SPICE native console sessions from outside the cloud, I have a working (but probably not completely finished) SPICE native proxy, and the next step is adding deployment support to Kolla-Ansible so that I can start demoing an end to end implementation. I have a draft of those changes, but don't feel quite ready to push them to Gerrit just yet. As part of that I've been building my own Kolla images in my homelab CI environment for a couple of years now. I don't know about others, but for me by far the most common reason for these builds to fail is because of intermittent connectivity to upstream package repositories -- either flaky networking, random noise, or rate limiting. Increasingly I find myself carrying private patches to use local mirrors instead of the upstream sources. It occurs to me I might not be the only one with this sort of use case. I therefore wonder how the Kolla team would feel about abstracting the upstream sources of various build dependencies so that they were defined centrally? That would make it much easier both to override sources with local mirrors, as well as define exactly what upstream sources are required to conduct a build. If that's a reasonable thing to do, where would people see that list sitting? My initial thought is in the defaults for the kolla-build ansible role, but I am definitely not a Kolla expert so I am open to guidance here. Cheers, Michael -- Person on the internet. https://madebymikal.com. He / his / him.