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

The ceilometer charm was assuming grizzly before the ceilometer-common
package was installed to determine the OS release. On queens deploys
this breaks due packages not being installed.

If ceilomter-common is not installed return empty configs.

Change-Id: Ib8bc1b7be3595bd8e64a25d0444dd768b80de881
Closes-Bug: #1759301

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

As of pip 10.0, --allow-unverified is not permitted.

Use of the flag in this repo was previously used to force
installation of python-apt to accommodate certain unit tests.

The unverified package, python-apt, is no longer necessary
for test execution.

Related-Bug: #1760720

Change-Id: I4d7cb93e41256ef6b75be3a8acd83303b32ac6bd

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

When >= queens ceilometer uses the identity-credentials relation
rather than the identity-service relation. When using HTTPS
ceilometer still needs the CA certificate from keystone.

This change sets up the CA when using the identity-credentials
relation.

Please merge https://github.com/juju/charm-helpers/pull/124 first.

Change-Id: I7c6ca1d913ad8b8123685a064933031f322869df

For OpenStack versions >= Queens the Ceilometer Charm
requires a 'identity-credentials' relation to Keystone
and not a 'identity-service' relation.

Log a warning-level verbose message when 'identity-service'
relation is detected on a >= Queens deployment.

Change-Id: I8e3ff1b899b877cd2870f4bbaaea155e4433c4f4
Closes-Bug: #1751772

Queens ceilometer requires a number of different services and
relations, the amulet functional tests have been updated for
that. Also move to using charmhelper keystone v3 api helpers.

Change-Id: I432c8937693fb47e7ca52e6dafe143a0143c437d
Requires: https://github.com/juju/charm-helpers/pull/119

When there are multiple mongodb peers but replset has not yet been set
on the relation, do not complete the MongoDBContext. This causes the
template to be rendered incorrectly and leads to the following error:

ERROR ceilometer ValueError: Port must be an integer between 0 and
65535:

Closes-Bug: #1750639
Change-Id: Ifb9424ac5e175d788fa21de0ee332c0a13e61a9f

Ceilometer-upgrade is in a race with the keystone catalog for the
metric entry. The function already has a retry on error loop. Bump up
the delay between retries to mitigate the race with keystone.

Change-Id: I7fdf36a1cf480607744dcfed9628f0bf9e6daac0

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

Change-Id: Ia846fe377366315d93fc08b8382d01631b25ecc0

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

Sync charm-helpers to pick up the updated InternalEndpointsContext
which removes the need to provide a package.

This essentially reverts commit f76d0755 in favor of an alternative
approach to selecting the volume catalog endpoint information.

Change-Id: I4a985fe1b8885b14aefdfeda9a8c2c4914c5fc93
Related-Bug: #1733566

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

The default HAProxy timeout values are fairly strict. On a busy cloud
it is common to exceed one or more of these timeouts. The only
indication that HAProxy has exceeded a timeout and dropped the
connection is errors such as "BadStatusLine" or "EOF." These can be
very difficult to diagnose when intermittent.

This charm-helpers sync pulls in the change to update the default
timeout values to more real world settings. These values have been
extensively tested in ServerStack. Configured values will not be
overridden.

Partial Bug: #1736171

Change-Id: I2474ba8abbd77d89b82d2fefb51aef463c45169b

Change-Id: Ie361b9a43a6a45b3c3fcd8ac87fdfaad599b2639
Partial-Bug: 1733566

Make xenial-pike the func27-smoke test

Change-Id: Ia5d12cff44cd29dc7b96fd41d155cfc94dd26abd

Bionic, being the next LTS, is important to enable for dev
and test as early as possible ahead of 18.02.

Zesty goes EOL in Jan 2018. The next stable charms release (18.02)
will not provide Zesty series support, as it was an interim
(non-LTS) release.

Change-Id: Ie15ffb42b8381601917e8d3a96cca3628d422357

Change-Id: I96674f2d5a8573a5e6fc4800108adca74bdd406c

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

Change-Id: Iad4d5dc187894c1a67d5b95cf75cb5e2fd82eecf

Change-Id: I02dd12ae127870747175237d9b7c998e0c2ac0cd