Add new relation to support bootstrapping a new deployment
of the ceph-mon charm from an existing ceph charm deployment,
supporting migration away from the deprecated ceph charm.
Each member of the existing ceph application will present
the required fsid and monitor-secret values, as well as its
public address so that the related ceph-mon units can
correctly seed from the exisitng MON cluster.
Provide stop hook implementation, which will leaves OSD
services running but will remove the ceph.conf provided
directly from this charm, falling back to ceph.conf provided
by other charms installed on the same machine. MON and MGR
services will be shutdown and disabled.
Closes-Bug: 1665159
Change-Id: I9bd1d7630a8eff53c65cb0f07d17e095fc7f32a9
Depends-On: Iac34d1bee4b51b55dfb3d14d315aae8526a0893c
- Add Zesty as a supported series to metadata.yaml.
- Turn on Xenial-Ocata Amulet test definitions.
- Sync charm helpers to get Juju 2.x amulet compatibility.
- Keeping Zesty-Ocata Amulet test definitions turned off until the
metadata.yaml changes propagate to the charm store.
- Resync tox.ini to resolve amulet test failures.
Change-Id: Id0c204f273caa9f0f585dcf505975ba685349ad0
This stops an error that happens when size is not
specified when adding storage via Juju storage hooks.
Without a set minimum, Juju will give 1G to a disk
which will cause ceph-disk to fail when connecting
the new disk.
Change-Id: Id959ee65ded03b95933a1deb099f492fccc0c182
This optimizes the publication process to the charm store, and
ensures that the charm code and version is consistent across all
supported Ubuntu series.
Change-Id: I0d0ef5530f035c1773ab3f3f616088a028e6a26c
Juju 2.0 provides support for network spaces, allowing
charm authors to support direct binding of relations and
extra-bindings onto underlying network spaces.
Add public and cluster extra bindings to this charm to
support separation of client facing and cluster network
traffic using Juju network spaces.
Existing network configuration options will still be
preferred over any Juju provided network bindings, ensuring
that upgrades to existing deployments don't break.
Change-Id: I4df75a40f5308f701f15c45d3d7b1df1e03832ad
Add the "osd-devices" block-type storage, with
minimum of 0 and no maximum. Volumes assigned to
a unit will be added as OSDs.
Also, add the "osd-journal" block-type storage,
with minimum of 0 and maximum of 1. The osd-journal
storage, if supplied, will be used in favour of
osd-journal configuration if supplied.
For now, handling of osd-journal is static, just
as the configuration method was before. Removing
or adding the journal after deployment is not
currently supported. This is possible with further
changes, but requires stopping Ceph and migrating
the existing journal, and so out of scope here.
James Page