Bug 1420861
| Summary: | [RFE] Add Support for a Second Ceph Storage Tier deployment capability through director | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Paul Needle <pneedle> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Giulio Fidente <gfidente> |
| Status: | CLOSED ERRATA | QA Contact: | Yogev Rabl <yrabl> |
| Severity: | high | Docs Contact: | Derek <dcadzow> |
| Priority: | high | ||
| Version: | 10.0 (Newton) | CC: | asimonel, brault, cylopez, gcharot, gfidente, jamsmith, jefbrown, johfulto, jraju, lmarsh, mariel, mburns, nsatsia, pneedle, racedoro, rhel-osp-director-maint, sclewis, scohen, seb, shan, sputhenp |
| Target Milestone: | Upstream M2 | Keywords: | FutureFeature, Triaged |
| Target Release: | 14.0 (Rocky) | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-9.0.0-0.20180710202746.d2994ca.el7ost | Doc Type: | Enhancement |
| Doc Text: |
You can now use different Ceph crush rules for different node, to optimize performance of Ceph pools. You configure crush rules in ceph-ansible with the `CephAnsibleExtraConfig` Heat parameter. You can then assign nodes to a specific rule with the `osd_crush_location` for each node. For example:
CephAnsibleExtraConfig:
crush_rule_config: true
NodeDataLookup: |
{"1B535751-93B6-4673-8A02-2D4F8FA3431E": {"osd_crush_location": "\"root=HDD host=overcloud-ceph-0\""}}
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-11 11:47:00 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: | 1476900, 1625008, 1654792, 1714227 | ||
|
Description
Paul Needle
2017-02-09 16:31:01 UTC
Verified 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/RHEA-2019:0045 |