Commit Graph

12 Commits

Author SHA1 Message Date
Liam Young
5fdde89be0 Tidyup docstring and method name 2020-02-04 12:48:00 +00:00
Liam Young
9c8a18b66f Fix path to get_unit_name_from_ip_address 2020-02-04 11:05:23 +00:00
Liam Young
5927878a03 Tidyup mojo cert unseal 2020-02-04 10:10:50 +00:00
Liam Young
cac2f4c4a7 Fix MOJO_LOCAL_DIR name 2020-02-03 16:03:42 +00:00
Liam Young
83982a7aec Add unseal function for mojo use.
* Add an unseal function for mojo to use.
* Switch mojo to use new function after series upgrade reboot.
* Add fallback if vip client is unavailable (the case if all
  hacluster units are paused for series upgrade).
2020-02-03 13:39:17 +00:00
Frode Nordahl
9108059f71 vault: Extend workaround for LP: #1826382
We also need to restart consumers of the placement API on the
'nova-cloud-controller' unit.
2019-11-12 17:40:25 +01:00
Frode Nordahl
8d676bf9fa Make non-existent tests/tests.yaml non-fatal where possible
Not all test environments or runners are equal, don't crash on
non-existent test config.
2019-11-05 16:38:06 +01:00
Frode Nordahl
a82979d145 vault: Await execution prior to validation step
Make it possible for consumers of the ``auto_initialize_no_validation``
function to execute subsequent setup and test code that require vault
and the consumers of the ``certificates`` relation to be ready.

With the current order of execution, it is not possible to use the
configure function in models where ``keystone`` application is not
present.
2019-10-18 11:05:18 +02:00
Liam Young
79a149bfc5 Facade for vault & basic_setup_and_unseal
Add a facade for interacting with vault and a function which
unseals vault units (useful when vault units have been rebooted).
2019-10-14 08:56:35 +00:00
Liam Young
025e1f4830 Ensure nova-compute is restarted when certs change
This is a temporary fix to work around a bug in nova-compute.
The bug causes nova-compute to cache the placement api endpoint
which causes placement api calls to fail when the endpoint switches
from http to https
2019-07-22 08:09:54 +00:00
Liam Young
11b55d5b4c Support initializing vault with no clients
Currently when vault auto_inititialize [sic] is called a validation
step is run at the end to check that clients connected to vault
have the correct setup. However in sometimes there are no clients
to run validation with (as with cross model relation testing). To
facilitate this expose a new method 'auto_initialize_no_validation'
which skip the client validation.

Also correct the spelling of auto_inititialize but add a partial
to support tests that are already using the old spelling.
2019-06-11 15:27:03 +00:00
Chris MacNaughton
dd434e281e Add zaza namespacing, starting with openstack 2019-04-25 17:46:03 +02:00