aboutsummaryrefslogtreecommitdiff
path: root/docker/fluentd
diff options
context:
space:
mode:
authorMichael Still <mikal@stillhq.com>2026-06-03 13:10:47 +1000
committerMichael Still <mikal@stillhq.com>2026-06-03 13:10:47 +1000
commit118541d5b3de5290d64a1e137d7bfb59afd8db4e (patch)
tree6bc4664f0c61a24e1a37d725bcc5df1c58701859 /docker/fluentd
parentcbdbd894b06b049e36ecd4fab4d0ecc3a49e0c00 (diff)
downloadkolla-118541d5b3de5290d64a1e137d7bfb59afd8db4e.tar.gz
kolla-118541d5b3de5290d64a1e137d7bfb59afd8db4e.zip
Implement container image build for kerbside.
This change adds images for Kerbside. Kerbside is a SPICE protocol native proxy used to expose the new spice-direct console type provided by Openstack Compute. This allows high fidelity virtual desktop experiences without requiring transcoding of the console into HTML5 in Horizon, or allowing users direct access to the console ports on your hypervisors. Sadly, Red Hat chose to remove SPICE support from qemu in RHEL9, and Rocky Linux has followed along. You therefore _must_ run the Debian or Ubuntu container images if you wish to use the ``spice-direct`` console type. Architecturally Kerbside has two components -- an API service which turns console access URLs from Nova into URLs to ``.vv`` files, and a proxy service which actually proxies the SPICE traffic. These are handled as separate container images here because they're quite different. One is a WSGI REST API, and the other is a daemon. It is also likely that deployers would choose to host these on different machines. Finally, the proxy service needs to be special cased in load balancing because it strongly expects to terminate TLS itself. The haproxy is therefore configured as a layer 4 proxy in this case. Depends-On: https://review.opendev.org/c/openstack/kolla/+/991249 Change-Id: If60a70745462e1360cfadaab1a5a8d75b7fdeb21 Partial-Bug: #2131793 (spice-direct consoles) Signed-off-by: Michael Still <mikal@stillhq.com>
Diffstat (limited to 'docker/fluentd')
0 files changed, 0 insertions, 0 deletions