Bug 1790479
Summary: | [RFE] [ceph-ansible] : FS to BS migration - reuse journal partition / journal vm for bluestore OSDs for db/wal | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Vasishta <vashastr> |
Component: | Ceph-Ansible | Assignee: | Dimitri Savineau <dsavinea> |
Status: | CLOSED ERRATA | QA Contact: | Vasishta <vashastr> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | aschoen, ceph-eng-bugs, ceph-qe-bugs, dsavinea, gabrioux, gmeno, hyelloji, jbrier, knortema, nthomas, rmandyam, tserlin, ykaul |
Target Milestone: | rc | Keywords: | FutureFeature |
Target Release: | 4.1 | Flags: | hyelloji:
needinfo-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | ceph-ansible-4.0.16-1.el8, ceph-ansible-4.0.16-1.el7 | Doc Type: | Enhancement |
Doc Text: |
.The dedicated journal devices retain their configuration when migrating from Filestore OSD to Bluestore
Previously, dedicated journal devices for Filestore OSD could not be reused when migrating to Bluestore OSD DB. An example of a dedicated device configuration is using a HDD for data and an SSD for journaling.
With this update, dedicated journal devices retain their configuration during the migration, so that they can be reused with the Bluestore OSD DB.
For more information, see link:{admin-guide}#how-to-migrate-the-object-store-from-filestore-to-bluestore[How to Migrate the Object Store from FileStore to BlueStore] in the link:{admin-guide}[Administration Guide].
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-05-19 17:31:40 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: | 1733577, 1816167 |
Description
Vasishta
2020-01-13 13:10:44 UTC
Working as expected with ceph-ansible-4.0.19-1.el7cp.noarch Moving to VERIFIED state. 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/RHSA-2020:2231 |