Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1482424

Summary:	Ensure we document use of CephPoolDefaultSize for tests or POCs with less than 3 Ceph OSDs.
Product:	Red Hat OpenStack	Reporter:	Giulio Fidente <gfidente>
Component:	documentation	Assignee:	RHOS Documentation Team <rhos-docs>
Status:	CLOSED DUPLICATE	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	12.0 (Pike)	CC:	jjoyce, srevivo
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-20 09:47:28 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:

Description Giulio Fidente 2017-08-17 09:03:11 UTC

We switched the default replica size for Ceph from 1 to 3 which is a better value for production environments (see BZ #1404459) but test and POC deployments with less than 3 OSDs will fail as Ceph pools are not usable (not accepting writes).

We should add into documentation a comment about the usage of:

parameter_defaults:
  CephPoolDefaultSize: 1

in the various examples related to Ceph, to make sure readers are aware of the param.

NOTE: it is possible to change the replica size for a pre-existing pool after the deployment is completed and such a change is effective immediately (bringing the cluster back in working state), I am documenting it here hoping it can be helpful but I don't think we should document these bits. For example, to change the size of the "images" pool:

# ceph osd pool set images size=1

Comment 1 Red Hat Bugzilla Rules Engine 2017-08-17 09:03:34 UTC

This bugzilla has been removed from the release since it has not been triaged, and needs to be reviewed for targeting another release.

Comment 2 Giulio Fidente 2018-02-20 09:47:28 UTC


*** This bug has been marked as a duplicate of bug 1545383 ***