30bde6129c
Introduce the CephExtraKeys parameter which may be used
have the newly deployed Ceph cluster create additional
keys which may be used by clients to access the cluster.
This parameter will useful for the multiple-external-ceph
blueprint because an operator would use CephExtraKeys to
create a cluster with a new key and that same key could
then be passed to a subsequent deployment to access the
same Ceph cluster. The alternative is to require the
operator to create this key manually between doing split
control plane deployments.
Change-Id: Ic47c2ad47e15e7e7bf56b300517e333f7ebd4013
Implements: blueprint multiple-external-ceph
(cherry picked from commit
|
||
---|---|---|
.. | ||
network | ||
README.rst | ||
ceph-min-osds.yaml | ||
disable-unbound.yaml | ||
multinode-3nodes-registry.yaml | ||
multinode-3nodes.yaml | ||
multinode-containers.yaml | ||
multinode-core.yaml | ||
ovb-ha.yaml | ||
scenario000-multinode-containers.yaml | ||
scenario001-multinode-containers.yaml | ||
scenario001-standalone.yaml | ||
scenario002-multinode-containers.yaml | ||
scenario002-standalone.yaml | ||
scenario003-multinode-containers.yaml | ||
scenario003-standalone.yaml | ||
scenario004-multinode-containers.yaml | ||
scenario004-standalone.yaml | ||
scenario006-multinode-containers.yaml | ||
scenario006-multinode.yaml | ||
scenario007-multinode-containers.yaml | ||
scenario007-standalone.yaml | ||
scenario010-multinode-containers.yaml | ||
scenario010-standalone.yaml | ||
scenario012-multinode-containers.yaml | ||
scenario012-standalone.yaml |
README.rst
This directory contains environments that are used in tripleo-ci.
They may change from release to release or within a release, and should
not be relied upon in a production environment. The top-level
environments
directory in tripleo-heat-templates contains
the production-ready environment files.