bc9368fd91
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 |
||
---|---|---|
.. | ||
cinder-netapp-config.yaml | ||
mongodb-nojournal.yaml | ||
net-bond-with-vlans.yaml | ||
net-single-nic-with-vlans.yaml | ||
network-isolation.yaml | ||
overcloud-steps.yaml | ||
puppet-ceph-devel.yaml | ||
puppet-ceph-external.yaml | ||
puppet-pacemaker.yaml | ||
puppet-tenant-vlan.yaml | ||
README.md | ||
storage-environment.yaml |
This directory contains Heat environment file snippets which can be used to enable features in the Overcloud.
Configuration
These can be enabled using the -e [path to environment yaml] option with heatclient.
Below is an example of how to enable the Ceph template using devtest_overcloud.sh:
export OVERCLOUD\_CUSTOM\_HEAT\_ENV=$TRIPLEO\_ROOT/tripleo-heat-templates/environments/ceph_devel.yaml