
Due to a build problem with the reactive plugin, this change falls back on overriding the steps and doing a manual build, but it also ensures the CI system builds the charm using charmcraft. Changes: - add a build-requirements.txt - modify charmcraft.yaml - modify osci.yaml -> indicate build with charmcraft - modify tox.ini -> tox -e build does charmcraft build/rename -> tox -e build-reactive does the reactive build - modify bundles to use the <charm>.charm artifact in tests. and fix deprecation warning re: prefix - tox inception to enable tox -e func-test in the CI func-test-pr: https://github.com/openstack-charmers/zaza-openstack-tests/pull/708 Change-Id: I4652834f5a4dd681563488cd340dac27dbf70075 Co-authored-by: Aurelien Lourot <aurelien.lourot@canonical.com>
19 lines
407 B
Django/Jinja
19 lines
407 B
Django/Jinja
applications:
|
|
keystone:
|
|
num_units: 3
|
|
options:
|
|
vip: {{TEST_VIP00}}
|
|
nova-cloud-controller:
|
|
num_units: 3
|
|
options:
|
|
vip: {{TEST_VIP01}}
|
|
keystone-hacluster:
|
|
charm: ch:hacluster
|
|
channel: latest/edge
|
|
nova-hacluster:
|
|
charm: ch:hacluster
|
|
channel: latest/edge
|
|
relations:
|
|
- ["keystone:ha", "keystone-hacluster:ha"]
|
|
- ["nova-cloud-controller:ha", "nova-hacluster:ha"]
|