fd98fa0722
The charm didn't work unless a mandatory bind-rndc interface was present. However, the dns-slaves option was supposed to provide an alternative to needing to relate the unit to the (say) designate-bind charm. This change allows dns-slaves and/or a bind-rndc relation and configures the underlying service accordingly. Also some fixups to the tests to simplify handler verification using more recent charms.openstack features. Also note that the bind-rndc interface needed a fix (the depends-on) for if/when a bind-rndc relation is removed; the interface incorrectly maintained that the relation was present when it was not. Change-Id: Ib2c883e623292520224f882aef09d3710e1e1348 Closes-Bug: #1693162 Depends-On: I523fecff4e80734772872a8a6d2507f1e2162ae3 |
||
---|---|---|
src | ||
unit_tests | ||
.gitignore | ||
.gitreview | ||
.testr.conf | ||
LICENSE | ||
README.md | ||
rebuild | ||
requirements.txt | ||
test-requirements.txt | ||
tox.ini |
README.md
Overview
This is a "source" charm, which is intended to be strictly the top layer of a built charm. This structure declares that any included layer assets are not intended to be consumed as a layer from a functional or design standpoint.
Test and Build
Building, pushing and publishing to the charm store is automated by CI to ensure consistent flow. Manually building is useful for development and testing, however.
tox -e pep8
tox -e py34 # or py27 or py35
tox -e build
Contact Information
Freenode IRC: #openstack-charms