David Ames ae257a0955 Functionality to enable mojo's use of zaza ...

Without introducing mojoisms into zaza there are some changes that are
required to enable mojo's use of zaza.

The goal is to keep mojo specific utilities in openstack-mojo-specs and
to move any generalized tools here in zaza.

This change updates some generalized zaza tools to enable mojo to use
them.

2018-04-30 16:13:50 +00:00

..

utilitites

Rename get_net_info to get_network_config

2018-04-25 15:51:33 -07:00

__init__.py

initial commit framing out stuff

2017-12-04 17:01:33 +01:00

test_zaza_charm_lifecycle_configure.py

Fix unit tests

2018-03-28 11:56:29 +00:00

test_zaza_charm_lifecycle_deploy.py

Add the ability to wait for bespoke statuses (#38)

2018-04-25 09:48:31 +01:00

test_zaza_charm_lifecycle_destroy.py

s/charm_testing/charm_lifecycle/ and unit tests

2018-03-27 12:35:38 +00:00

test_zaza_charm_lifecycle_func_test_runner.py

Merge pull request #35 from thedac/issue/34

2018-04-21 07:32:01 +01:00

test_zaza_charm_lifecycle_prepare.py

Ensure we use default model constraints

2018-04-20 08:25:04 +02:00

test_zaza_charm_lifecycle_test.py

Fix unit tests

2018-03-28 11:56:29 +00:00

test_zaza_charm_lifecycle_utils.py

Functionality to enable mojo's use of zaza

2018-04-30 16:13:50 +00:00

test_zaza_model.py

Functionality to enable mojo's use of zaza

2018-04-30 16:13:50 +00:00

utils.py

s/charm_testing/charm_lifecycle/ and unit tests

2018-03-27 12:35:38 +00:00