openstack
/
charm-designate-bind
Code Issues Proposed changes
Juju Charm - Designate Bind Backend
23 Commits 33 Branches 0 Tags 2.1 MiB
Python 100%
Go to file
James Page 4c662a92a0 Add yakkety to supported series 
Change-Id: I3a012a452d729480c7967fa2276065f86895c498
 		2016-09-14 09:26:48 +01:00
src Add yakkety to supported series 2016-09-14 09:26:48 +01:00
unit_tests Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
.bzrignore Initial charm 2016-02-11 10:05:16 +00:00
.gitignore Add unit tests 2016-07-08 12:35:52 +01:00
.gitreview Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
.testr.conf Add unit tests 2016-07-08 12:35:52 +01:00
LICENSE Add functional tests 2016-07-13 14:07:13 +00:00
README.md Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
requirements.txt Allow all master dns nodes to send notifys 2016-07-27 15:25:31 +00:00
test-requirements.txt Add .gitreview and clean up repo 2016-07-22 14:53:32 +00:00
tox.ini Update tox.ini files based on release-tools gold copy 2016-09-08 23:04:05 +00:00

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