openstack
/
charm-designate
Code Issues Proposed changes
Juju Charm - Designate
128 Commits 33 Branches 0 Tags 17 MiB
Python 99.6%
Shell 0.4%
Go to file
Dmitrii Shcherbakov 269ba2bb1d reintroduce designate_notifications topic 
Change I709a6aca1843918a67d43bc4808a0013168fbc55, commit hash
1879b16ea5 introduced a
backwards-incompatible change in the fact that designate stopped
consuming messages using designate_notifications topic from nova and
neutron.

While designate.conf change in the mentioned commit is needed to make
sure Designate emits its own notifications on the topic that ceilometer
uses ("notifications"), for nova and neutron to designate notifications
a separate topic should be used as before.

A revert of the previous commit is not done as it addresses the previous
issue but introduces a new one.

Change-Id: I6b5fd1b5f9bae1cd4a1683fd476b456e81d6c79e
Related-Bug: #1710831
 		2018-02-05 14:22:54 +03:00
src reintroduce designate_notifications topic 2018-02-05 14:22:54 +03:00
unit_tests Designate - Neutron integration 2018-01-18 13:49:27 -08:00
.gitignore Enable designate to list on all interfaces 2017-11-29 11:58:36 +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 sync charm-helpers 2018-01-19 10:18:47 -08: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 Add memcache as the coordinator backend 2017-11-02 14:10:30 +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