Test websocketproxy with TLS in the nova-next job

Depends-on: Ib29d3f5f18533115b9c51e27b373e92fc0a28d1a

Change-Id: I203163b09613734b3e792bee7e5a931f0888378e
This commit is contained in:
melanie witt 2017-10-18 18:28:54 +00:00 committed by Matt Riedemann
parent bb3ded3537
commit 4d5e370b8f
2 changed files with 8 additions and 1 deletions

View File

@ -95,7 +95,8 @@
Pike, the service user token functionality was added. This job is also
unique in that it runs the post_test_hook from the nova repo, which runs
post-test scripts to ensure those scripts are still working,
e.g. archive_deleted_rows.
e.g. archive_deleted_rows. In Queens, this job started testing the
TLS console proxy code in the libvirt driver.
# TODO(mriedem): Make this voting once bug 1747511 is fixed.
voting: false
run: playbooks/legacy/nova-next/run.yaml

View File

@ -26,12 +26,16 @@
- shell:
# TODO(mriedem): Consider setting USE_PYTHON3=True here to make this
# job run under python 3.5 which is a "next" type thing.
# Enable TLS between the noVNC proxy & compute nodes; this requires
# the tls-proxy service to be enabled.
cmd: |
set -e
set -x
cat << 'EOF' >>"/tmp/dg-local.conf"
[[local|localrc]]
NOVA_USE_SERVICE_TOKEN=True
NOVA_CONSOLE_PROXY_COMPUTE_TLS=True
EOF
executable: /bin/bash
@ -42,6 +46,8 @@
cmd: |
set -e
set -x
# tls-proxy is needed to initialize the CA and cert.
export ENABLED_SERVICES=tls-proxy
export PYTHONUNBUFFERED=true
# Yes we want to run Tempest.
export DEVSTACK_GATE_TEMPEST=1