Bug 1631010

Summary:	batch: allow journal+block.db sizing on the CLI
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Alfredo Deza <adeza>
Component:	Ceph-Volume	Assignee:	Andrew Schoen <aschoen>
Status:	CLOSED ERRATA	QA Contact:	Vasishta <vashastr>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.2	CC:	aschoen, ceph-eng-bugs, ceph-qe-bugs, edonnell, gmeno, kdreyer, tchandra, tserlin, vashastr
Target Milestone:	rc
Target Release:	3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	RHEL: ceph-12.2.12-8.el7cp Ubuntu: ceph_12.2.12-6redhat1	Doc Type:	Enhancement
Doc Text:	.The `ceph-volume` tool can now set the sizing of journals and block.db Previously, sizing for journals and block.db volumes could only be set in the `ceph.conf` file. With this update, the `ceph-volume` tool can set the sizing of journals and block.db. This exposes sizing right on the command line interface (CLI) so the user can use tools like `ceph-ansible` or the CLI directly to set or change sizing when creating an OSD.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-08-21 15:10:24 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:	1726135

Description Alfredo Deza 2018-09-19 17:13:47 UTC

Description of problem: 

Because there is tooling (e.g. ceph-ansible) that may not have a configured cluster that ceph-volume can work with to use these values


ceph-ansible is unable to properly calculate the osd max memory setting otherwise.


Steps to Reproduce:
This is adding 2 new flags.

Expected results: block.db and journal sizing is affected when these flags are used

Comment 11 errata-xmlrpc 2019-08-21 15:10:24 UTC

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/RHSA-2019:2538

Comment 12 Red Hat Bugzilla 2023-09-14 04:38:42 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days