openstack
/
charm-placement
Code Issues Proposed changes
Juju Charm - Placement
11 Commits 19 Branches 0 Tags 15 MiB
Python 98.1%
Shell 1.9%
Go to file
David Ames b4166e949c Update peers with API addresses 
Use default_update_peers which will publish admin, internal and public
addresses to peers.

Change-Id: Iaa3fc3f2401981f6f0a2130a277a6da7439cff52
Closes-Bug: #1858132
 		2020-03-27 15:03:07 -07:00
src Update peers with API addresses 2020-03-27 15:03:07 -07:00
unit_tests Initial Commit 2019-10-15 18:13:51 +00:00
.gitignore Initial Commit 2019-10-15 18:13:51 +00:00
.gitreview Added .gitreview 2019-10-09 15:08:24 +00:00
.stestr.conf Initial Commit 2019-10-15 18:13:51 +00:00
.zuul.yaml [ussuri][goal] Updates for python 2.7 drop 2020-03-24 17:30:42 +00:00
LICENSE Initial Commit 2019-10-15 18:13:51 +00:00
README.md Add top-level README.md 2019-10-28 10:17:10 -04:00
rebuild Rebuild for updates to charms.openstack 2020-03-11 09:24:41 +01:00
requirements.txt Update charm build requirements 2020-03-03 09:58:26 +01:00
test-requirements.txt Initial Commit 2019-10-15 18:13:51 +00:00
tox.ini Initial Commit 2019-10-15 18:13:51 +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 py37
tox -e build

Contact Information

Freenode IRC: #openstack-charms