| Summary: | Director: document how to define custom configuration option for Ceph | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Alexandre Marangone <amarango> |
| Component: | documentation | Assignee: | Dan Macpherson <dmacpher> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | RHOS Documentation Team <rhos-docs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 10.0 (Newton) | CC: | dmacpher, gfidente, jomurphy, srevivo |
| Target Milestone: | --- | ||
| Target Release: | 10.0 (Newton) | ||
| 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: | 2017-01-17 16:22:37 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: | |
|
Description
Alexandre Marangone
2016-12-06 17:44:44 UTC
We have some docs about this upstream at [1], more specifically not the example describing how to override puppet-ceph settings but the one about arbitrary stanza/key/value lines 1. http://tripleo.org/advanced_deployment/ceph_config.html That's pretty much exactly what I think we need to add to our downstream doc. However, there's a mistake in the upstream doc. the resulting ceph.conf file should be populated with the following: [global] max_open_files: 131072 my_setting: my_value should be [global] max_open_files = 131072 my_setting = my_value (In reply to Alexandre Marangone from comment #2) > That's pretty much exactly what I think we need to add to our downstream doc. > > However, there's a mistake in the upstream doc. > > the resulting ceph.conf file should be populated with the following: > [global] > max_open_files: 131072 > my_setting: my_value > > should be > [global] > max_open_files = 131072 > my_setting = my_value hi Alexandre, we should fix that upstream yes :) thanks. I think I understand. It's not an either/or situation, but more "Use Method 1. If it's not covered by Method 1, use Method 2." |