Bug 1674083
| Summary: | [RFE] centralize config settings in monitor | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Josh Durgin <jdurgin> |
| Component: | RADOS | Assignee: | Neha Ojha <nojha> |
| Status: | CLOSED ERRATA | QA Contact: | Manohar Murthy <mmurthy> |
| Severity: | medium | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | high | ||
| Version: | 4.0 | CC: | ceph-eng-bugs, dzafman, hnallurv, kchai, nojha, pasik, pdhiran, tserlin |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 4.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ceph-14.2.4 | Doc Type: | Enhancement |
| Doc Text: |
.Configuration is now stored in Monitors accessible by using `ceph config`
In this release, {product} centralizes configuration in Monitors instead of using the Ceph configuration file (`ceph.conf`). Previously, changing configuration included manually updating `ceph.conf`, distributing it to appropriate nodes, and restarting all affected daemons. Now, the Monitors manage a configuration database that has the same semantic structure as `ceph.conf`. The database is accessible by the `ceph config` command. Any changes to the configuration are applied to daemons or clients in the system immediately and restarting them is no longer needed. Use the `ceph config -h` command for details on the available set of commands. Note that a Ceph configuration file is still required to identify the Monitors nodes.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-01-31 12:45:38 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: | 1730176 | ||
|
Description
Josh Durgin
2019-02-09 01:50:15 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri 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/RHBA-2020:0312 |