54c3f21221
The charm has had the capability to automatically handle fsid in deployments for several cycles. Explicitly setting the fsid can lead to unpredictable behavior when data from previous deployments remains on block devices, and when the fsid is explicitly static across those separate deployments. ex. Ceph would see the fsid match and attempt to use the block device from a previous deployment as-is and unsuccessfully. This primarily affects legacy development and CI environments, which may be in place from a time before the charm autoatically handled fsids. The recommendation is for both test and production deployments to defer fsid generation to the charm. Change-Id: I0b87576810faa08a81dc2d559ef925ea02f58db0 Partial-bug: #1698154 |
||
---|---|---|
.. | ||
charmhelpers | ||
README.md | ||
basic_deployment.py | ||
dev-basic-xenial-queens | ||
gate-basic-artful-pike | ||
gate-basic-bionic-queens | ||
gate-basic-trusty-icehouse | ||
gate-basic-trusty-mitaka | ||
gate-basic-xenial-mitaka | ||
gate-basic-xenial-ocata | ||
gate-basic-xenial-pike | ||
gate-basic-xenial-queens | ||
tests.yaml |
README.md
Overview
This directory provides Amulet tests to verify basic deployment functionality from the perspective of this charm, its requirements and its features, as exercised in a subset of the full OpenStack deployment test bundle topology.
For full details on functional testing of OpenStack charms please refer to the functional testing section of the OpenStack Charm Guide.