Bug 1370050 - [doc] [RFE] Warning message for conflicting OSD options
Summary: [doc] [RFE] Warning message for conflicting OSD options
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: 2.1
Assignee: Aron Gunn
QA Contact: ceph-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-25 07:40 UTC by James Biao
Modified: 2016-09-30 17:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-30 17:19:27 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description James Biao 2016-08-25 07:40:15 UTC
Description of problem:

https://access.redhat.com/documentation/en/red-hat-ceph-storage/2/single/installation-guide-for-red-hat-enterprise-linux#configuring_ceph_osd_settings

Adding warning message at the end of this chapter would be helpful.

Some osd options are conflicting each other. As in /usr/share/ceph-ansible/roles/ceph-common/tasks/checks/check_mandatory_vars.yml

~~~
name: verify only one osd scenario was chosen
  fail:
    msg: "please select only one osd scenario"
  when:
    osd_group_name is defined and
    osd_group_name in group_names and
    ((journal_collocation and raw_multi_journal) or
    (journal_collocation and osd_directory) or
    (raw_multi_journal and osd_directory) or
    (bluestore and journal_collocation) or
    (bluestore and raw_multi_journal) or
    (bluestore and osd_directory))
~~~

bluestore is tech preview so we don't need to worry about here.

(journal_collocation and raw_multi_journal) or
(journal_collocation and osd_directory) or
(raw_multi_journal and osd_directory) or

These are 3 scenario we need to avoid when enabling osd options


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:


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