Includes fix for failed sysctl tuning with lxdbr0.

Change-Id: I53de0d6dd9e9c4035f02405d172e1e2e5224daf0
Closes-Bug: 1735070

Change-Id: I7521ba297ab6a9d23246ca39b7cf508fd0b50f48

As of Ceph Luminous, bucket keys within the CRUSH map must be
unique; The root bucket is always called 'default' so remap
Juju and configuration provided bucket keys to
'default-{row,rack}' ensuring that keys are unique.

Change-Id: I7fa3dd9e001cca40e678e8983a1d7ed19d51e2fe
Closes-Bug: 1729911

* Synced version of charm-helpers
* Synced version of charms.ceph to bring in Py3 compatible library
  methods.

Change-Id: I5ac45740f48a71d9cb0c5943472fc8590a723514

The blacklist actions allow for adding and removing devices
to a unit-local list of devices to be skipped during osd
initialization. This list will be used to override the
application level, and thereby deployment wide, 'osd-devices'
configuration option on a individual unit basis.

The pre-existing list-disk action is extended to return
list of blacklisted devices under the 'blacklist' key.

Change-Id: I28a3c5d6076fb496dead3fe3387d9bbbbe9ec083
Closes-Bug: #1730267

Upstream Ceph removed the `osd crush location` option in
commit f9db479a14d9103a2b7c0a24d958fe5fff94100e [0]. This
causes new clusters deployed from the Pike UCA (Luminous)
using the customize-failure-domain option to not create or
move the OSD to the correct spot in the OSD tree. The end
result is that placement groups will fail to peer because
there are no racks to select hosts and OSDs from.

Instead, the charm should set the more generic `crush
location` option in the ceph.conf file. It is and has been
supported since the Firefly (trusty-icehouse) version of
Ceph.

[0] https://github.com/ceph/ceph/commit/f9db479a14d9103a2b7c0a24d958fe5fff94100e

Change-Id: I0b7055b20f54096a2f33583079326aee17726355
Closes-Bug: 1730839

Change-Id: I78ea1d1c861070e4d4b1d171ded7286ebb636600

Added options for osd_max_backfills and osd_recovery_max_active, if we
should want to override the default.

Change-Id: Iaeb93d3068b1fab242acf2d741c36be5f4b29b57
Closes-bug: #1661560

During ceph to ceph-osd/ceph-mon migrations, the bootstrap keyring
for the cluster will be in place as the ceph-osd units are started
alongside existing ceph units.

Switch this check to look for the upgrade keyring, which won't be
in place until the ceph-osd <-> ceph-mon relation is complete, at
which point in time a) the unit has the correct access to perform
the upgrade and b) the previous/current version check code will
not trip over due to the previous value of the source option
being None, resulting in a fallback to 'distro' as the previous
source of ceph.

Change-Id: I10895c60aeb543a10461676e4455ed6b5e2fdb46
Closes-Bug: 1729369

Change-Id: Ic8612eb123ec8335a6a867f0775116dba3a68dce
Signed-off-by: Marian Gasparovic <marian.gasparovic@canonical.com>

Essentially, we want to avoid doing:

    from module import f1, f2, f2

and instead doL

    import module

    module.f1()

This helps with reading the code and understanding where the functions
come from.

Change-Id: I1bc06441dc5595e8a0c84a5b5c3db5d88b68a4f2

Commit 4bcdddc4 code cleanup did
not address actions.

Fixed.

Change-Id: Ic5de38e4d56022e3f72e5dcb08f6a4253e3306ee
Closes-bug: #1726275

Change-Id: I2d441da31e8e3b6570bf237661bf22c294d8ee73
Related-Bug: #1719742

Change-Id: I8b66ca368dcf6ec55d4c558e96f156c4859bad63

Change-Id: I7bd5b62d3bfdd11334b3a8ce25692c1343a5c515

Change-Id: I8a83e15a77306cca4baa665c31cb9363f7cbde83
Depends-On: I483ee9dae4ce69c71ae06359d0fb96aaa1c56cbc

In small clusters, adding OSDs at their full weight causes massive IO
workload which makes performance unacceptable.  This adds a config
option to change the initial weight, we can set it to 0 or something
small for clusters that would be affected.

Closes-Bug: 1716783
Change-Id: Idadfd565fbda9ffc3952de73c5c58a0dc1dc69c9

Drop explicit global configuration of keyring, supporting
installation of the ceph/ceph-mon/ceph-osd charms in the
same machine.

Change-Id: Ib4afd01fbcc4478ce90de5bd464b7829ecc5da7e
Closes-Bug: 1681750

the 'experimental' option is no longer needed as of Luminous release
https://github.com/ceph/ceph/blob/luminous/src/common/legacy_config_opts.h#L79

Change-Id: Idbbb69acec92b2f2efca80691ca73a2030bcf633

Change-Id: Iaa2ddfa4db639db1a142e7b025a26012fb45e3de

juju_availability_zone is not a valid configuration setting, let's use
'rack' instead.

Change-Id: I6763377f253e6feb92d7c4c31eefc600cce3a8b8
Closes-Bug: #1684330

Explain that for Ceph Luminous, which uses Bluestore
as the default backend for OSDs, if the bluetsore
option is set to false then OSDs will continue to use
Filestore.

Change-Id: I0cb65310f98562ec959018fad538e9006f1c41f6

Change-Id: I12b0ba1b814cbba2dbb3474de5c0b180df03628a

Change-Id: I7f7eb751b1996415ede24ac61f51bad685735da0

Closes-Bug: #1709962
Closes-Bug: #1710645
Change-Id: I1b6d91f0f09f0142f4470d8ae3eea650165a0575

- ensure filestore is used by default
- allow upgrades to luminous

Change-Id: I00aa4fcba53d9bd28592b9ba1b89f74d869148c2
Depends-on: I8205f7c7c63ec30900c4afdc76df174d3d9a8466

Merge "Modify tests.yaml which specifies bundletester config params with the following key:value pairs:"

Also had to fix some imports due to changes
implemented as part of the cleanup.

Change-Id: Ie232828056a7f15525f820e8e106264b22697168

with the following key:value pairs:

- reset_timeout: 600

Change-Id: I8a35d5ec734663bc48932a9ee142fb433d540bc9

Change-Id: I542e169004123635683b0e24a015885d43007a7e
Closes-bug: #1686739