d11e256eed
Add docker profiles to deploy Ceph in containers via ceph-ansible. This is implemented by triggering a Mistral workflow during one of the overcloud deployment steps, as provided by [1]. Some new service-specific parameters are available to determine the workflow to execute and the ansible playbook to use. A new `CephAnsibleExtraConfig` parameter can be used to provide arbitrary config variables consumed by `ceph-ansible`. The pre-existing template params consumed up until the Pike release to drive `puppet-ceph` continue to work and are translated, when possible, into the equivalent `ceph-ansible` variable. A new environment file is added to enable use of ceph-ansible; the pre-existing puppet-ceph implementation remains unchanged and usable for non-containerized deployments. 1. https://review.openstack.org/#/c/463324/ Change-Id: I81d44a1e198c83a4ef8b109b4eb6c611555dcdc5
14 lines
755 B
YAML
14 lines
755 B
YAML
---
|
|
prelude: >
|
|
Deployment of Ceph in containers is implemented using a Mistral workflow.
|
|
other:
|
|
- |
|
|
It is possible to deploy Ceph in docker containers in the overcloud. This
|
|
is implemented by triggering `ceph-ansible` via a Mistral workflow. A new
|
|
`CephAnsibleExtraConfig` parameter has been added to the templates and can
|
|
be used to provide arbitrary config variables consumed by `ceph-ansible`.
|
|
The pre-existing template params consumed by the TripleO Pike release to
|
|
drive `puppet-ceph` continue to work and are translated, when possible, into
|
|
their equivalent `ceph-ansible` variable. To enable the deployment of Ceph
|
|
in containers use `environments/ceph-ansible/ceph-ansible.yaml` when
|
|
deploying the overcloud. |