Bug 1497624
| Summary: | OSP director sets Ceph's pool min_size to 1 by default | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Giulio Fidente <gfidente> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Giulio Fidente <gfidente> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 11.0 (Ocata) | CC: | acanan, dbecker, dcadzow, gfidente, jefbrown, jomurphy, mburns, mlopes, morazi, nlevine, rhel-osp-director-maint, yrabl |
| Target Milestone: | --- | Keywords: | Triaged, ZStream |
| Target Release: | 11.0 (Ocata) | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-6.2.1-2.el7ost | Doc Type: | Enhancement |
| Doc Text: |
This enhancement allows the Ceph cluster to determine the pool's minimum replica size, by reference to the desired replica size. The director will no longer enforce a minimum replica size of 1 for the Ceph pools; you can instead configure a desired replica size using the `CephPoolDefaultSize` parameter (defaulted to `3`), based upon which the Ceph cluster will identify the optimal minimum replica size.
This was changed because enforcing a minimum replica size of 1 is dangerous, as it allows for writes in the Ceph pools when only one copy of the data is available. As a result, the minimum replica size for the Ceph pools is determined by the Ceph cluster, based on the desired replica size of each pool.
|
Story Points: | --- |
| Clone Of: | 1481826 | Environment: | |
| Last Closed: | 2018-02-13 16:31:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1481826 | ||
|
Description
Giulio Fidente
2017-10-02 08:38:29 UTC
verified Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0310 |