6266312fa1
There is currently no coverage of upgrades in CI, which leaves us open to regression in this infrequently tested but crucial area. This change adds the required scripts and Zuul configuration. A control plane is first deployed using the Kayobe stable/pike branch and associated default configuration. The control plane is tested by deploying then deleting a server instance. An upgrade to Queens is performed, using the Kayobe master branch, or code in review if applicable. The upgraded control plane is tested by deploying then deleting a second server instance. A workaround was required to restart the nova_compute service after the upgrade, since the SIGHUP sent to it by Kolla Ansible during upgrade appeared to be putting it into a degraded state. A future improvement to this test could be to leave a server instance running during the upgrade. Change-Id: I0e595524e39d1131fe3ec6aaf2aeec3ff3d6a536 Story: 2003472 Task: 24732
10 lines
395 B
Django/Jinja
10 lines
395 B
Django/Jinja
---
|
|
# The Queens kayobe configuration uses the fernet token provider. To avoid
|
|
# issues during upgrade, set the provider to fernet in the Pike deployment
|
|
# also.
|
|
keystone_token_provider: 'fernet'
|
|
|
|
# Most development environments will use nested virtualisation, and we can't
|
|
# guarantee that nested KVM support is available. Use QEMU as a lowest common
|
|
# denominator.
|
|
nova_compute_virt_type: qemu |