need a charm upgrade path from ceph to ceph-mon

[Ryan Beisner]

We need a charm upgrade path and procedure from ceph to ceph-mon. Until that happens, the classic ceph charm will need to be tested along with its replacement ceph-mon, which essentially doubles the test efforts and system resource impact.

[James Page (james-page)]

https://review.openstack.org/#/c/504235

[James Page (james-page)]

https://review.openstack.org/#/q/topic:bp/charm-ceph-migration

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/504235
Committed: https://git.openstack.org/cgit/openstack/charm-ceph/commit/?id=71390fe0cf8778c42b691389d2c4fca78a9447e0
Submitter: Zuul
Branch: master

commit 71390fe0cf8778c42b691389d2c4fca78a9447e0
Author: James Page <email address hidden>
Date: Thu Sep 14 14:44:22 2017 -0600

    Add support for ceph-mon bootstrap

    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

[James Page (james-page)]

ceph-mon part lacked a bug reference:

https://github.com/openstack/charm-ceph-mon/commit/e7964d40c8e6a908373abd8642ac47eae9f876a4