Bug 1741687 - BETA - RHCS4 Installation docs - Last Updated: 2019-08-01 - Misc (Structure, parameters, question etc)
Summary: BETA - RHCS4 Installation docs - Last Updated: 2019-08-01 - Misc (Structure, ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 4.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: 4.0
Assignee: Ranjini M N
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks: 1708370
TreeView+ depends on / blocked
 
Reported: 2019-08-15 20:00 UTC by Heðin
Modified: 2020-03-09 15:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-09 15:23:48 UTC
Embargoed:


Attachments (Terms of Use)

Description Heðin 2019-08-15 20:00:12 UTC
Page 13:
Firewalld config - Isn't this handled by ceph-ansible in rhcs-4 ?
If it is, then it should be explained how to enable it in ceph-ansible instead of how to set it up manually.

Page 32-35: filestore, bluestore, filestore, both, both
It's cluttered. Should be one of 'filestore', 'bluestore', 'both' but not mixed together.

Page 52: Cluster name: Some time ago talks were about deprecating custom cluster names, will this be supported in RHCS-4 ?

Appendix J: ansible paramenters
It's not specified what deployment scenarios the parameters are valid for.
a "Used by" string under "Required" etc. would clarify the use of the parameters.

General:
Parts of the installation guide would be much cleaner to read, if it stuck to bluestore and referenced a filestore document or appendix. (writing this with the expectation that bluestore is the default)

I haven't seen any ref. to how ansible tags work, but they are used in multiple places.

Comment 3 Ranjini M N 2020-01-07 16:12:51 UTC
3 Jan 2020
Had a call with Vasishta

remove filestore and retain only bluestore

Comment 10 Heðin 2020-01-23 20:59:34 UTC
Is it possible to get access to the updated documentation on google docs ?


Note You need to log in before you can comment on or make changes to this bug.