Go to file

David Ames addee58dd8 Do set DNS on overcloud subnets

It turns out we do need to set DNS on the overcloud subnet. It should be
the .2 of the CIDR under test and not the _admin_net's .2. There seems
there are security group rules in the way.

2019-10-22 16:12:26 -07:00

doc/source

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

tests

Add zaza namespacing, starting with openstack

2019-04-25 17:46:03 +02:00

unit_tests

Unit test fix

2019-10-21 16:19:42 -07:00

zaza

Do set DNS on overcloud subnets

2019-10-22 16:12:26 -07:00

.gitignore

modify base zaza poackage into zaza.openstack package

2019-05-08 13:38:33 +02:00

.travis.yml

Fix lint

2019-06-27 11:33:52 +02:00

Add license, copyright and update package info

2018-08-08 16:11:04 -05:00

LICENSE

Add license, copyright and update package info

2018-08-08 16:11:04 -05:00

README.md

update readme

2019-05-09 10:53:24 +02:00

requirements.txt

Pin pydocstyle

2019-07-16 11:57:34 +02:00

setup.cfg

modify base zaza poackage into zaza.openstack package

2019-05-08 13:38:33 +02:00

setup.py

Saml tests rely on lxml

2019-10-11 11:30:16 +00:00

tox.ini

More debugging in the test

2019-09-25 14:43:10 +01:00

README.md

Zaza OpenStack Tests

This is a test library designed to be shared between the OpenStack Charms to improve code-reuse among the various components.

Usage

This example is taken from the pacemaker-remote charm's tests.yaml:

charm_name: pacemaker-remote
tests:
  - zaza.openstack.charm_tests.pacemaker_remote.tests.PacemakerRemoteTest
configure:
  - zaza.openstack.charm_tests.noop.setup.basic_setup
gate_bundles:
  - basic
smoke_bundles:
  - basic

test-requirements.txt:

git+https://github.com/openstack-charmers/zaza.git#egg=zaza
git+https://github.com/openstack-charmers/zaza-openstack-tests.git#egg=zaza.openstack