Bug 1142485
| Summary: | ability to set osd pool default size in ceph.conf | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Crag Wolfe <cwolfe> |
| Component: | rubygem-staypuft | Assignee: | Brad P. Crochet <brad> |
| Status: | CLOSED ERRATA | QA Contact: | Alexander Chuzhoy <sasha> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.0 (RHEL 7) | CC: | ajeain, brad, jguiditt, mburns, mlopes, morazi, rhos-maint, sasha, yeylon |
| Target Milestone: | z2 | Keywords: | ZStream |
| Target Release: | Installer | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ruby193-rubygem-staypuft-0.4.0-1.el6ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the 'OSD Pool' default size was not visible in the Advanced Configuration of a deployment. As a result, the default pool size could not be set for Ceph.
With this update, the Ceph default pool size has been added to the Advanced Configuration screen and is available for modification.
|
Story Points: | --- |
| Clone Of: | 1142483 | Environment: | |
| Last Closed: | 2014-11-04 17:02:34 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: | 1142483 | ||
| Bug Blocks: | |||
|
Description
Crag Wolfe
2014-09-16 21:12:23 UTC
PR submitted https://github.com/theforeman/staypuft/pull/324 Verified: ruby193-rubygem-staypuft-0.4.0-2.el6ost.noarch rhel-osp-installer-0.4.1-2.el6ost.noarch In the "Advanced Configuration" tab of the deployment, there's "Ceph Storage (OSD) (node) Service Configuration". Previously you couldn't set any parameters, it said: "No configuration needed for this service." Now, you can set/override parameters for the service and one of them is "Osd pool default size". 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://rhn.redhat.com/errata/RHBA-2014-1800.html |