openstack
/
charm-designate
Code Issues Proposed changes
Juju Charm - Designate
99 Commits 33 Branches 0 Tags 17 MiB
Python 99.6%
Shell 0.4%
Go to file
Jenkins f492591c08 Merge "Re-enable v1 API for charm compatibility" 2017-09-06 16:44:11 +00:00
src Merge "Re-enable v1 API for charm compatibility" 2017-09-06 16:44:11 +00:00
unit_tests Do less work in the update-status hook 2017-08-31 10:28:58 +01:00
.gitignore Delete *.pyc files from repo and add ignore to .gitignore 2016-08-26 10:34:07 +00:00
.gitreview Add .gitreview and clean up repo 2016-07-22 12:01:10 +00:00
.testr.conf Unit tests and lint fixes 2016-07-07 09:36:22 +01:00
LICENSE Add License info 2016-07-13 14:02:28 +00:00
README.md Add .gitreview and clean up repo 2016-07-22 12:01:10 +00:00
rebuild Rebuild for IPv4/IPv6 Dualstack changes 2017-08-22 13:20:01 -07:00
requirements.txt Render configs always needs the cluster relation 2016-07-27 15:24:14 +00:00
test-requirements.txt Add .gitreview and clean up repo 2016-07-22 12:01:10 +00:00
tox.ini Update tox.ini for py27 requirement 2016-11-28 18:21:06 -06: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