| Age | Commit message (Collapse) | Author | Files | Lines | |
|---|---|---|---|---|---|
| 2015-11-05 | Allow customization of Ceph client user |   Giulio Fidente | 1 | -1/+13 | |
| Previously we enforced the Ceph user used by the OpenStack clients to be named 'openstack', this change allows for customization of such a name. Change-Id: Idef3e1ed4e8e21b645081869b8d6fad2329bdc60 | |||||
| 2015-11-05 | Allow customization of the Ceph pool names | Giulio Fidente | 1 | -2/+20 | |
| This is useful in those scenarios were we want to use an external Ceph deployment with multiple overclouds. Change-Id: I1749d2a6547f6ce25843709e46a1447e8d42cfff | |||||
| 2015-08-13 | Support for using external Ceph clusters |   Dan Prince | 1 | -0/+65 | |
| 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 | |||||
 |
index : apex-tripleo-heat-templates | |
| Unnamed repository | Grokmirror user |
| aboutsummaryrefslogtreecommitdiffstats |