openstack/charm-designate-bind
Code Issues Proposed changes
Juju Charm - Designate Bind Backend
20 Commits 33 Branches 0 Tags 2.1 MiB
Python 99.5%
Shell 0.5%
7505e62e2b
Go to file
Liam Young 7505e62e2b Populate built charm README.md 
Change-Id: I29e110b575285b918b6beee23f6197645c1e2a14
2016-07-28 16:26:04 +00:00
src Populate built charm README.md 2016-07-28 16:26:04 +00: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 Add .gitreview and clean up repo 2016-07-22 14:53:32 +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