- Feb 02, 2018
-
-
Giuseppe Attardi authored
-
- Jan 25, 2018
-
-
Giuseppe Attardi authored
-
Giuseppe Attardi authored
-
Giuseppe Attardi authored
-
Giuseppe Attardi authored
-
- Jan 24, 2018
-
-
Giuseppe Attardi authored
-
- Jan 22, 2018
-
-
Alex Barchiesi authored
-
- Jan 19, 2018
-
-
Ryan Beisner authored
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: I86b23f0be2e5098696833996ca807d354fe72751
-
- Jan 10, 2018
-
-
James Page authored
Pickup fixes for upgrade from Jewel -> Luminous. Change-Id: I3ffeebc38464096724ca0fd40f1cf29cf3e7fe4f Closes-Bug: 1742082 Closes-Bug: 1742083 Closes-Bug: 1742120 Closes-Bug: 1742079 Closes-Bug: 1742408
-
- Dec 20, 2017
-
-
Dmitrii Shcherbakov authored
Adds bluestore-specific options related to the metadata-only journal. The options allow a user to control: 1. path to a bluestore wal (block special file or regular file) 2. path to a bluestore db (block special file or regular file) 3. size of both Their configuration works similarly to the FileStore journal. If paths are not specified both WAL and DB will be collocated on the same block device as data. Other options can be configured via an existing config-flags option if needed. http://docs.ceph.com/docs/master/rados/configuration/bluestore-config-ref/ Closes-Bug: #1710474 Change-Id: Ia85092230d4dcb0435354deb276012f923547393 Depends-On: I483ee9dae4ce69c71ae06359d0fb96aaa1c56cbc Depends-On: Idbbb69acec92b2f2efca80691ca73a2030bcf633
-
James Page authored
Ensure that netaddr and netifaces are installed on upgrade from older py2 based charms to the newer py3 based execution. Change-Id: I1c7b2eb545e5ef5b40ab2db5a1a968ceb7d916e1 Closes-Bug: 1738979
-
- Dec 06, 2017
-
-
Andrew McLeod authored
Make default func27-smoke xenial-pike Charm-helpers sync Review and merge https://github.com/juju/charm-helpers/pull/69 first. Change-Id: I32a04dfc995929840f8c544e1d5ed58066515210
-
- Dec 05, 2017
-
-
David Ames authored
Charm-helpers sync for python3 fixes. Update Exception.message to use str(Exception) Change-Id: I0e354d0d07f220e3285eb3e863498918c82df2ca
-
Ryan Beisner authored
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: If8d82e92a6768af127e68d18c65dfbc3b97f49f9
-
- Dec 01, 2017
-
-
Liam Young authored
Change-Id: Id0add7b995e424a5a1c77c80e242fc6ffca54c87 Partial-Bug: #1735720
-
- Nov 29, 2017
-
-
James Page authored
Includes fix for failed sysctl tuning with lxdbr0. Change-Id: I53de0d6dd9e9c4035f02405d172e1e2e5224daf0 Closes-Bug: 1735070
-
- Nov 22, 2017
-
-
Ryan Beisner authored
Change-Id: I7521ba297ab6a9d23246ca39b7cf508fd0b50f48
-
- Nov 21, 2017
-
-
Zuul authored
-
- Nov 17, 2017
-
-
James Page authored
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
-
Alex Kavanagh authored
* Synced version of charm-helpers * Synced version of charms.ceph to bring in Py3 compatible library methods. Change-Id: I5ac45740f48a71d9cb0c5943472fc8590a723514
-
- Nov 10, 2017
-
-
Zuul authored
-
- Nov 09, 2017
-
-
Zuul authored
-
Frode Nordahl authored
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
-
- Nov 08, 2017
-
-
Zuul authored
-
Billy Olsen authored
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
-
- Nov 07, 2017
-
-
Frode Nordahl authored
Change-Id: I78ea1d1c861070e4d4b1d171ded7286ebb636600
-
- Nov 06, 2017
-
-
Xav Paice authored
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
-
- Nov 01, 2017
-
-
James Page authored
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
-
- Oct 26, 2017
-
-
Marian Gasparovic authored
Change-Id: Ic8612eb123ec8335a6a867f0775116dba3a68dce Signed-off-by:
Marian Gasparovic <marian.gasparovic@canonical.com>
-
- Oct 25, 2017
-
-
Alex Kavanagh authored
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
-
- Oct 23, 2017
-
-
Frode Nordahl authored
Commit 4bcdddc4 code cleanup did not address actions. Fixed. Change-Id: Ic5de38e4d56022e3f72e5dcb08f6a4253e3306ee Closes-bug: #1726275
-
Frode Nordahl authored
Change-Id: I2d441da31e8e3b6570bf237661bf22c294d8ee73 Related-Bug: #1719742
-
- Sep 26, 2017
-
-
Ryan Beisner authored
Change-Id: I8b66ca368dcf6ec55d4c558e96f156c4859bad63
-
Frode Nordahl authored
Change-Id: I7bd5b62d3bfdd11334b3a8ce25692c1343a5c515
-
- Sep 25, 2017
-
-
Dmitrii Shcherbakov authored
Change-Id: I8a83e15a77306cca4baa665c31cb9363f7cbde83 Depends-On: I483ee9dae4ce69c71ae06359d0fb96aaa1c56cbc
-
- Sep 20, 2017
-
-
Jenkins authored
-
Xav Paice authored
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
-
- Sep 14, 2017
-
-
James Page authored
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
-
- Sep 06, 2017
-
-
Jenkins authored
-
- Aug 31, 2017
-
-
Jenkins authored
-