* Support OVN charms in automated OpenStack upgrade
* Add ovn-dedicated-chassis to the list of control plane principal charms
Change-Id: I857513f130091e218a60eaf54eaf63527c00f5e5
Functional test for multi zone deployment was added.
The functional test removes the devices in region1 zone3 then uploads a new object. The check is to return object header data.
Add a method which will init vault if its present and skip if it
is not. This allows much simpler tests.yaml if all test and
config steps are the same for TLS and non-TLS test cases apart
from initialising vault.
This dict is used in the OpenStack upgrade tests in
order to automatically determine the next release and
set the openstack-origin accordingly.
Also taking the opportunity to extend neighboring
lists.
If the V3 volume endpoint is available, use it for tempest testing.
The V2 volume endpoint is removed in OpenStack Xena, so this allows
us to use the latest available endpoint.
This adds a new setup function that will setup a VLAN provider network.
It can be called by tests.yaml after basic_overcloud_network:
- zaza.openstack.charm_tests.neutron.setup.basic_overcloud_network
- zaza.openstack.charm_tests.neutron.setup.vlan_provider_overcloud_network
Since the charm is now marked stateful, the 'host' attribute
of a volume is mangled differently. This change makes the test
more robust against future changes as well.
* Set timeout on juju_wait()
* Remove leftover traces
Traces should be made with logging.debug(). These traces
are probably leftovers from the development phase.
Instead of introducing a new decorator to temporarily change the
configuration, use the existing infrastructure. Furthermore, avoid
passing the model name in some calls since it's implied already.
Hard-coding the manila-ganesha application names makes
these tests fail in bundles that are using the manila-
ganesha application with it's default name. This change
updates the tests to try to restart the desired
services on any applications named *ganesha*.
Add setup step for the dashboard which will block until the
certificates are present and the model is idle. This is to prevent
the tests from continuing when the certificates are not ready.
Also up CephDashboardTest to use standard tools for collecting
ca cert.