The charm currently configures events to be published to
rabbit on both the config.event_topic (event.sample queue)
and alarm topic but as of Queens Ceilometer no longer
consumes event.sample. This patch makes the event_sink
publishers configurable and defaults to publishing to
aodh to retain backwards compatibility.

Change-Id: I5b55f31adcf2b069ff51e387a416f9f1ac4099f8
Partial-Bug: #1676586

Currently it is unclear that ceilometer is not actually ready when it
is related to gnocchi until the ceilometer-upgrade action has run. The
status will show active Unit is ready when it is not.

When gnocchi is related, check that the ceilometer-upgrade action has
been run. If not set workload status to prompt the administator to run
the action.

Please merge the charm-helpers change first:
https://github.com/juju/charm-helpers/pull/270

Partial-Bug: #1811108
Change-Id: Id778ed3f59e4bcde9c6586aad46be2b5b9ccb531

Commit 3838010a added code that was subsequently made redundant
by commit 668a2898 but never removed. This patch cleans things
up.

Change-Id: I59fcea6f5bb19e0bc57856600a85a18419cf8730

Change-Id: Iac4b963eef9de40938c98053c9d7cab30dbb0500

Change-Id: Ife58c6e14465b6f93fa46bd1968936a79d1b97d1

Change-Id: I5ab5d72ab5a312205275b2478abb402627f5a21a

Change-Id: Id6fea2f6805e59d976f44a2318ddac7c7bd95e78

Use the generate_ha_relation_data helper from charmhelpers to
generate the data to send down the relation to the hacluster
charm.

This results in a few changes in behaviour:

1) The charm will no longer specify a nic name to bind the vip. This
   is because Pacemaker VIP resources are able to automatically
   detect and configure correct iface and netmask parameters based
   on local configuration of the unit.
2) The original iface named VIP resource will be stopped and deleted
   prior to the creation of the new short hash named VIP resource.

Change-Id: I6c10762e4f3367684f19852d03d5e5b84cf37600

This change adds polling.yaml to the list of managed config files, for
Queens and above.  Two new config items are added alongside the
template, to take into account a choice between the two polling.yaml
files supplied with the Ceilometer source, one which has a small list of
pollsters and the other which has all pollsters.  Additionally the
change adds the option to set the polling interval.

Change-Id: Ifff72870cf79bea23dbd21586857dd832c9e1405
Closes-Bug: 1785933
Closes-Bug: 1652848

On charm upgrade the charm may switch to py3 packages. If so, ensure
the old py2 packages are purged. If the purge occurs then restart
services.

Change-Id: I23812e518d5d0ba64dff33ac8d704b8b0f829b7e
Closes-Bug: 1803451

Change-Id: Idfc2d473bcb76552e8f280e795cae02cffafa865

We want to default to running all tox environments under python 3, so
set the basepython value in each environment.

We do not want to specify a minor version number, because we do not
want to have to update the file every time we upgrade python.

We do not want to set the override once in testenv, because that
breaks the more specific versions used in default environments like
py35 and py36.

Change-Id: Iaf0db51532f8397529cb603815baecff90cb0e88
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

Change-Id: I0921c5508a64e986fe9ad943700276e68fe7e4ba

This change adds the ability to listen for events across multiple
rabbit queues. Nova cells v2 has a message broker per cell and
the charms already support having a separate message broker for
neutron, in both these topologies ceilometer needs the ability to
listen to multiple brokers.

To achieve this a new relation 'amqp-listener' has been introduced.
The existing 'amqp' relation should be used for the broker that
ceilometer listens to and publishes to. 'amqp-listener' should be
used for additional brokers that ceilometer just listens on.

Update functional tests to satisfy relation with
nova-cloud-controller.

Change-Id: Ifdade3f7814620f4cd4a1d35a584cbc099bb6d88

Charmhelpers is now installed via pip for unit tests so stop
'Make sync' from pulling it down.

Change-Id: I605e431fea9d57eac431a83c3347058c73384710

Implement the series-upgrade feature allowing to move between Ubuntu
series.

Change-Id: I4fadff9ff740b37f19fac47c68131f0128bf24bc

Change-Id: I78010884bce5c025901aa16bc32d123ac1d33c9d

The configuration file /etc/ceilometer/pipeline.yaml will be managed by
juju, currently it is not. On every change of this file
ceilometer-collector daemon is restarted.

Change-Id: Ie18a5284812f4f698b929b9e17b34289e7732bf7
Closes-Bug: 1715672

Switch package install to Python 3 for OpenStack Rocky or later.

When upgrading, remove any python-* packages that where explicitly
installated and then autoremove --purge any dependencies that are
no longer required.

Change-Id: I120ed44988f9e86a27f464dc879acdc1b8926dd8

Add a tactical change which is already merged into charm-helpers.

This needs to go into all charms to solve the chicken:egg issue
where cosmic is untestable until this change exists.

Reference:

https://github.com/juju/charm-helpers/commit/4835c6c167c429527ef0a0291d17cf559c9cf880

Change-Id: If8339ef341188d8daf50a692bd125b7f3305884b

This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.

Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.

Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.

See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html

Change-Id: Ia7c13ed8ffbba0bbf64d2d8a169785a62dee6d99
Story: #2002586
Task: #24317

Change-Id: I6ef5624c5cfeabc81c74e9e078df83e461321a5a

Change-Id: I8014e4b9c174e91f547cba689c05266fb4ef0fa7

Change-Id: I9ad9e7668a2664a0ac9fde680869737e76ed87b6
Closes-Bug: #1713807

Change-Id: I3b58874e67cf98ff2d3913b6f19df8048c820b4b

Python 3.6 is installed by default in Ubuntu 18.04 LTS.
Therefore, according to Transition Plan [1],
it'll be handy to have py36 testenv.

For more details, please check Python2 Deprecation Timeline [2]
and Python3-first Goal - Completion Criteria [3].

[1] https://wiki.ubuntu.com/Python/Python36Transition
[2] https://governance.openstack.org/tc/resolutions/20180529-python2-deprecation-timeline.html
[3] https://review.openstack.org/#/c/575933/8/goals/stein/python3-first.rst@42

Change-Id: I219e5015ebddb56e2f1c38d6ba83bc1057e56f86

Ensure that EOL releases are removed from metadata
and tests, and that the current dev release is enabled
in metadata.  Dev release tests are enabled separately
because of chickens and eggs.

Change-Id: If1acd82a6e351947ab03aeb4415b17a81186aa4a

Due to changes to the ceph-osd charm, it is
suggested to use Juju storage for testing.

Change-Id: Ie92c503dd8aaf1fb43920792a676c98bfc222cc9
Related-Bug: #1698154

A bug was causing the events yaml from being rendered on quuens+
deploys. This change adds it to the quuens+ configs.

Closes-Bug: 1773355
Change-Id: I309107da609e186638332d3a9bca00a86ccd6010

Change-Id: I443241fcd096c594ef11d83c9033e64ff5b74b2c

Change bionic test from dev to gate for 18.05.

Change-Id: I62ce9734a406f97b8199255d722577a23cc68cab