Bug 1296171
Summary: | Require API to Create/update/Del Crush Rule | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Nishanth Thomas <nthomas> |
Component: | Calamari | Assignee: | Christina Meno <gmeno> |
Calamari sub component: | Back-end | QA Contact: | Harish NV Rao <hnallurv> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | unspecified | CC: | ceph-eng-bugs, flucifre, gmeno, hnallurv, icolle, yweinste |
Version: | 1.3.1 | Flags: | icolle:
needinfo+
|
Target Milestone: | rc | ||
Target Release: | 2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | calamari-server-1.4.0-rc4 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-23 19:29:25 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: | 1291304 |
Description
Nishanth Thomas
2016-01-06 14:06:14 UTC
This work is really just following the template of work that exists for updating crush nodes. I expect that this is at least two weeks of effort. I don't agree that this is top priority though. The need in MVP-011 could be satisfied in using the crush map endpoint as it has the ability to update rules. http://calamari.readthedocs.org/en/latest/calamari_rest/resources/resources.html#crush-map Retrieve is implemented here already http://calamari.readthedocs.org/en/latest/calamari_rest/resources/resources.html#crushruleviewset I recommend coming back to this one after closing other 2.0.0 bugs. Harish yes it will This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions able to create, delete and modify the crush rule using the 'crush_rule' api. 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-2016:1755 |