Bug 1269271
| Summary: | Object Map & Erasure Coding documentation | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | monti lawrence <mlawrenc> |
| Component: | Documentation | Assignee: | ceph-docs <ceph-docs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ceph-qe-bugs <ceph-qe-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.3.1 | CC: | agunn, kdreyer, ngoswami, poelstra |
| Target Milestone: | rc | ||
| Target Release: | 1.3.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-12-18 09:59: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: | |||
Added content for Object Map in the following commit: https://gitlab.cee.redhat.com/jowilkin/red-hat-ceph-storage-architecture/commit/8624d1d194571e38cd465e358cc16e7d160bd589 See: https://gitlab.cee.redhat.com/jowilkin/red-hat-ceph-storage-architecture/blob/v1.3/architecture.adoc#object-map Provided the doc link to concerned devels for review. As per devel review, updated the content in the following commit: https://gitlab.cee.redhat.com/jowilkin/red-hat-ceph-storage-architecture/commit/9798667f832cddb0bba069c332f837bcd04a91df See: https://gitlab.cee.redhat.com/jowilkin/red-hat-ceph-storage-architecture/blob/v1.3/architecture.adoc#object-map The Object Map content is now reviewed and finalized. Fixed for 1.3.1 Release. |
**Object Map** Resizing/Exporting/Importing/Flattening Index of objects that actually exist. Valuable against clones that don't have actual objects, but gets object from parent. Reads and writes that do copy ups. Improves performance, because map has data already. Off by default. **Erasure coding** Can't do omap on erasure coded pool Placement policies Admin sets default user for placement/region/zone Should have a hierarchy set up for different pools. Add to Architecture Guide