Red Hat Bugzilla – Bug 1311657
[Docs] "Configuring Ceph with Custom Config Settings"
Last modified: 2017-03-13 11:37:16 EDT
Description of problem:
The TripleO heat templates for Ceph only support a limited number of parameters for inclusion in the ceph.conf file. The following parameters need to be supported in order to properly manage and tune the Ceph cluster:
max open files
osd op threads
osd mkfs options
osd mount options
filestore max sync interval
filestore xattr use omap
Ideally, the heat template syntax would support adding any parameter to the ceph.conf file. That way the heat template itself wouldn't need to change, but additional entries could be added to the ceph.conf file by adding the data to the ceph.yaml hieradata file.
Additional parameters can be added to ceph.conf
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
It should be possible to provide arbitary config params for ceph by passing the following via environment file:
which should result in ceph.conf being populated with something like:
This isn't working for me. Here is what I added to an environment file that is part of our solution:
Note: Deployments failed until I determined the proper ceph_classes name is "ceph::conf" (not "ceph::confg" or "ceph::config").
The overcloud deployment succeeds, but no additional entry appears in ceph.conf. The hiera data appears to be correct:
[heat-admin@overcloud-cephstorage-0 ~]$ sudo hiera ceph_classes
[heat-admin@overcloud-cephstorage-0 ~]$ sudo hiera ceph::conf
I expected to find a "max_open_files" entry in the [global] section of ceph.conf, but there isn't one.
hi Alan, please excuse me but the syntax I suggested in comment #4 is indeed wrong; if I remember correctly we wrote it down together during a session at the summit but I didn't test it. My bad.
The correct syntax is:
which in your use case ( comment #6 ) would become:
I tested it this time and it works as intended.
As a side note, with OSP8 templates we also don't need to pass ::conf as an additional class (in ceph_classes) because it's included by default so one could remove:
(In reply to Alan Bishop from comment #5)
> This isn't working for me. Here is what I added to an environment file that
> is part of our solution:
> - ceph::conf
> value: 131072
this should be:
Giulio, I confirmed the corrected syntax you provided works as you describe. Thanks!
On one hand, this RFE is not needed because the capability already exists. On the other hand, I have not seen any documentation that explains how to use the capability.
I recommend adding a write-up to an appropriate section in the Red Hat OpenStack Platform Partner Integration guide (https://access.redhat.com/documentation/en/red-hat-openstack-platform/8/partner-integration/partner-integration).
Alan, I am adding some docs in tripleo.org to document this feature .
Do you think we can move the BZ to docs and do something similar with the official RH OSP documentation?
That sounds like a good idea to me.
Since the feature exists, and this is now a docs bug, I'm changing the flags back to rhos-9.0? to match the Target Release "9.0 (Mitaka)"
*** Bug 1319328 has been marked as a duplicate of this bug. ***
It looks like this BZ fell through the cracks.
There's a page for this content here:
Same content appears on OSP10 and OSP11 branches.
@Giulio, is there anything further we need for this content?
thanks Dan, I think the example in the link you posted is fine, Alan do you think it is sufficient? Maybe we can close this as CURRENTRELEASE?
I reviewed the documentation at the link Dan provided, and feel it does a very good job of explaining things. I agree this BZ can be closed.