659403d17c
This adds the assess_status functionality, but without any tests yet. It also adds a register function to enable the release to be specified before an OpenStackCharm class is instantiated, thus providing the mechanism to choose the class to use for a release (or series of releases). This was missing from earlier commits. |
||
---|---|---|
charms_openstack | ||
unit_tests | ||
.gitignore | ||
.testr.conf | ||
.travis.yml | ||
MANIFEST.in | ||
Makefile | ||
README.md | ||
copyright | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.md
charms.openstack
Helpers for building layered, reactive OpenStack charms.
Support and discussions
We use the openstack-charmers mailing-lists for developer and user discussions, you can find and subscribe here: https://lists.ubuntu.com/openstack-charmers.
If you prefer live discussions, some of us also hang out in #juju on irc.freenode.net.
Bug reports
Bug reports can be filed at https://bugs.launchpad.net/charms.openstack/+filebug