Support for using external Ceph clusters
authorDan Prince <dprince@redhat.com>
Wed, 1 Jul 2015 20:44:15 +0000 (16:44 -0400)
committerGiulio Fidente <gfidente@redhat.com>
Thu, 13 Aug 2015 14:19:04 +0000 (16:19 +0200)
commitbc9368fd91ca29b5c86caa3ddc88d8ff76009250
tree11bdb9b4e4404ca31589e4e42b5fdce3e93f82dd
parente96c087509193d5ad63caa3014977a2baf0db0d3
Support for using external Ceph clusters

This patch adds support for using an externally managed Ceph
cluster with the TripleO Heat templates.

For an externally managed Ceph cluster we initially
only deploy the Ceph client tools, install the 'openstack' user
keyring, and generate the ceph.conf. This matches what we do
for managed Ceph installations and is a good first start.
No other Ceph related services are installed or managed.

To enable use of a Ceph external cluster simply add
the custom Heat environment file environments/puppet-ceph-external.yaml
to your heat stack create/update command and make sure to
set the required CephClientKey, CephExternalMonHost, and CephClusterFSID
variables.

Change-Id: I0a8b213ce9dfa2fc4e62ae1e7631466e5179fc2b
ceph-cluster-config.yaml
environments/puppet-ceph-external.yaml [new file with mode: 0644]
overcloud-without-mergepy.yaml
puppet/ceph-cluster-config.yaml
puppet/extraconfig/ceph/ceph-external-config.yaml [new file with mode: 0644]
puppet/manifests/overcloud_controller.pp
puppet/manifests/overcloud_controller_pacemaker.pp