Add support for the charm to request and receive certificates from
the tls-certificates relation.

Add missing direct ``amqp`` relation between ``ceilometer-agent``
and ``rabbitmq-server``

Change-Id: I931f5d3fcbf28e85b1a8e3e7cf24d13cf741e4bd
Closes-Bug: #1818546

The previous attempt at addressing Bug#1811108 was a bit naive.
It was not HA aware and it failed to handle upgrade-charm.

This change moves from kv to leader-set as only the leader needs to run
the action and then inform the other nodes.

Note: on upgrade-charm we must assume the deployment has run
ceilometer-upgrade as there is no mechanism to determine this
independently. If we do not do this, the charm is in blocked state after
charm-upgrade. A warning is logged that this assumption has occurred.

Partial-Bug: #1811108
Change-Id: Idcc26df53542e78f0671942c99edfcbf61eccf6c

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

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: 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

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

There is a use-case to forward events received by ceilometer from
OpenStack services to an external system via http/udp. It comes
from the fact that aodh does not include all information about an
event alarm into POSTed data. Raw event data can be published by
ceilometer via http/udp to an external system without giving a
user direct access to rabbitmq.

This patch adds a context generator, associated templates, and
configuration entry for configuring multiple event-sinks in
/etc/ceilometer/event_pipeline.yaml. This also modifies the
ceilometer.conf templates to reflect the correct naming of the
same file to align with upstream Ceilometer.

Also adds support for a future Panko charm event consumer using
the event-service interface in the above context with associated
metadata and hook symlinks.

This change will only effect Mitaka and later clouds.

Closes Bug: 1763321

Change-Id: I931438c720272bd9a3d2b958ebabcd3584790bd0

The ceilometer-upgrade command needs to be run to update back end
ceilometer data stores. When attempting to run this command during
deploy time due to the number of required relations many inherent
race conditions exist leading to Bug#1749280.

This change allows the ceilometer-upgrade command to be run as an action
post-deploy.

Change-Id: I64a56d9a38532476b8a01df6227231a1276c708f
Closes-Bug: #1749280

For queens, only the identity-credentials relation is required
as ceilometer no longer registers endpoints; ensure the correct
relation name is used when checking to see if the ceilometer
upgrade process can be executed.

Change-Id: I8482e97f4f60e019b0225f67c568965adbb034cb

Align ceilometer charm with worker-multiplier usage as found
across the majority of OpenStack Charms.  Worker configuration
values are set for API, Notification and Collector services
as needed for each release. Note that for Ocata or later, API
services are executed as WSGI apps under Apache which was
already plugged into the standard worker calculation logic
in charm helpers.

This includes dropping of the existing api-worker configuration
option in preference to a calculated approach.

Change-Id: Idba7c3012d9d24b7ae6ef8eade4a5261ef1cbddc
Closes-Bug: #1745189

Notable issues resolved:

openstack_upgrade_available() broken for swift
https://bugs.launchpad.net/charm-swift-proxy/+bug/1743847

haproxy context doesn't consider bindings
https://bugs.launchpad.net/charm-helpers/+bug/1735421

regression in haproxy check
https://bugs.launchpad.net/charm-helpers/+bug/1743287

Change-Id: I50e8b24c4e9404f81a4b782f414171d5ded31dfb

Update charm to support Ceilometer@Queens; specifically:

 - Removal of Ceilometer API service
 - Removal of ceilometer-collector service

Most of this change is related to dropping of these
services; In addition its now possible to complete a
ceilometer-upgrade without mongodb being configured.

As this charm no longer provides any endpoints to
keystone, for Queens the identity-credentials relation
is required instead of the identity-service relation.

Change-Id: I3cefc24ffc9a0e60f446fbbdff603dfad37f7baa

When an existing cluster of the service is scaled out the new unit
will join with keystone before it is fully clustered. In identity
joined hook the charmhelpers function canonical_url is called which
in turn uses another charmhelpers function, resolve_address.
resolve_address will only return the vip if the vip is set in config
AND the unit is clustered. This means that the units local address
is returned and that is then registered with keystone.

This change gates registering an endpoint if the cluster is
partially formed.

Change-Id: Icf2753b6b21347af8106ebad03d81309177d09f2
Partial-Bug: #1544959

The OpenStack OCF resource definitions for Ceilometer have proven
to be quite brittle, and we can achieve much the same end by just
using the lsb module to track ceilometer-agent-central directly.

Drop all use of ocf:openstack and delete res_ceilometer_polling
which is a) broken for Pike and b) complete misnamed.  Configure
'lsb:ceilometer-agent-central' for all deployments irrespective
of release.

Change-Id: I7b02065cf245ae480c04d5db235866e879c14002
Closes-Bug: 1718830

According to http://docs.python.org/2/library/unittest.html
assert(Not)Equals is a deprecated alias of assert(Not)Equal.

Change-Id: Ib96a90d6e4c4e8c72ddd62820ca794d29f8dbfae
Closes-Bug: #1329757

Ensure that the os_release cache is cleared during the openstack
upgrade process, ensuring that package list and configuration
options are correctly set for the new OpenStack version.

Change-Id: Ie685854952527f59ee344bfda8e49250c248150a
Closes-Bug: 1715624

Add new metric-service interface to support use of
Gnocchi as a storage backend for resource and metric
data.

Configure ceilometer to use the gnocchi dispatcher
in the event that ceilometer is related to gnocchi.
This has the side effect of disabling the ceilometer
API - Aodh and Gnocchi API's should be used directly
in this deployment topology.

Note that Gnocchi is only supported in OpenStack
Mitaka or later; 'metrics-service' is added to the
required interfaces configuration as an alternative
to 'mongodb' for >= Mitaka.

Change-Id: Ia31dfefd5efa3fb5ec2ba5d132ee865c567bd8df

Use the get_relation_ip function for selecting addresses for the
cluster relationship. Including overrides for the admin, internal,
and public config settings or extra bindings.

Partial-Bug: #1687439

Change-Id: I3e651e32a970a427597cc485b8549d51442919cd

- sync charmhelpers with fix-alpha helpers
- fix up code where the alpha comparisons are done
- fix tests which assumed mocks would just work on os_release()

Change-Id: I3d142f04bedc7dde12f3c079534cd43841fa8401
Related-Bug: #1659575

For large integer values, Juju can choose to return the number
in scientific notation. This causes the python code loading the
config data to return a floating point number instead of an
integer. Floating point values in ceilometer's configuration file
will prevent ceilometer from starting.

This change forces the type to an integer, allowing users to
specify large ttl values.

Change-Id: I8e29e6868b4c4a4ae20ad87ab585508fd321261c
Closes-Bug: #1651645

By providing openstack network relation data during cluster join we
allow haproxy backends to be configured in the corresponding os networks
should a 'public-address' not be available.

Change-Id: Ie370552410fffb859d236a011844427d8b3aff45
Closes-Bug: #1669044

This change aligns with the Ocata ceilometer package, which has
moved the ceilometer-api to run under mod_wsgi with apache2.

Change-Id: I0f13f3bcb346182541376843a65d07f570f89442

'alarm-listener' in Aodh would be deployed if you use charm-aodh.
It expects that ceilometer publish events with 'alarm.all' topic,
then it can evaluate alarm criteria pre-configured by users.

This patch makes ceilometer publish events for event-driven alarm
evaluation in Aodh.

Change-Id: Id536c9d847ac9c08b9d7d309b4639606e6860a17

With the release of 4.2.0 of keystonemiddleware using the
in-process token cache is no longer recommended. It is recommended
that a memcache backend to store tokens is used instead,

This installs and configures memcache and configures neutron-server
to use memcache for token caching.

http://docs.openstack.org/releasenotes/keystonemiddleware/mitaka.html#id2

Change-Id: I1f7764afb24b511508432fa758596cc9ab40aba8

The ceilometer-agent-central and ceilometer-agent-compute
services are now completely removed from the liberty release
of ceilometer. The new implementation is to use
ceilometer-polling and call the respective pollsters by
namespace.

Change-Id: I3af6fe9cc9c5b0fcf0406f89f402cbd1a31f66c4
Closes-Bug: 1606787

If the charm enables https then apache is used to terminate ssl. As
part of this Apache listens on the port that the ceilometer API port
was listening on and the API service shuffles down to a lower port. If
the services are restarted one at a time and Apache goes first then
Apache will try and bind to the port the API service is listening on
because the API service has not yet been restarted to pick up its
new port.

Change-Id: Ied3224660948a9775c8000369cba0c287944cde5
Closes-Bug: 1632287

Ceilometer switched to using wsgi_script to generate the
ceilometer-api binary; this resulted in a few packaging changes,
including one which means the listen port for Ceilometer API is
set via the systemd unit, rather than the ceilometer.conf
configuration file.

Add systemd override file handling for ceilometer-api, including a
small workaround which ensures that the systemd daemon loads the
override configuration file when it changes (only possible during
config-changed with enabling SSL support).

This charm should switch to using Apache + mod_wsgi next cycle, at
which point all of that can just be dropped.


Change-Id: Ic8b359d0b91fda144925f5c75044f919e73aadd9
Closes-Bug: 1629796

Juju 2.0 provides support for display of the version of
an application deployed by a charm in juju status.

Insert the os_application_version_set function into the
existing assess_status function - this gets called after
all hook executions, and periodically after that, so any
changes in package versions due to normal system updates
will also be reflected in the status output.

This review also includes a resync of charm-helpers to
pickup hookenv and contrib.openstack support for this
feature.

Change-Id: I4cf3c3389def2a0dc9d0cd286aa8190cbfa59f9a

ceilometer.conf template >= Kilo does not contain metering-time-to-live
and event-time-to-live parameters. Add these options so we can control
ceilometer database growth.

Change-Id: Id5831280daeb582586bfa615268309c4abec5d63
Closes-Bug: 1561220

All contributions to this charm where made under Canonical
copyright; switch to Apache-2.0 license as agreed so we
can move forward with official project status.

Change-Id: I15bca9b973b61e408e25c113035702a596c45268

Implement DNS high availability. Pass the correct information to
hacluster to register a DNS entry with MAAS 2.0 or greater rather
than using a virtual IP.

Charm-helpers sync to bring in DNS HA helpers

Change-Id: I543095a210e668f30c3617990b3ee668a3143dd9

Add charmhelpers.contrib.hardening and calls to install,
config-changed, upgrade-charm and update-status hooks. Also
add new config option to allow one or more hardening
modules to be applied at runtime.

Change-Id: I7752d72cc5a3f47fe66bca23aac730d76af8556a

Adds improved pause and resume unit to the charm such tha the
charm stays paused during maintenance operations.  Updates the
basic_deployment.py to use the the new version of
python-ceilometerclient (that's available in xenial, but works
back to icehouse/precise.

Change-Id: I869e467d0e4d9fecd661a6f946d45e31535ea11e

Rework ceilometer.conf to remove use of deprecated groups and options.

Don't install aodh alarming services for Mitaka; this will be handled in
a new aodh charm.

Rework upgrade tests from precise-havana -> trusty-kilo.

Change-Id: I74112fd6206665bbb7a20eaa5be15ac85116ae03