Bug 1540461
Summary: | [RFE] Support configuring lvmcache during brick creation | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Sahina Bose <sabose> |
Component: | rhhi | Assignee: | Sahina Bose <sabose> |
Status: | CLOSED ERRATA | QA Contact: | Mugdha Soni <musoni> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | rhhiv-1.5 | CC: | bugs, dchaplyg, dfediuck, rcyriac, rhs-bugs, sabose, sasundar |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | RHHI-V 1.5 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: |
Administrators can now select a faster device to use as a cache when configuring a brick for RHHI for Virtualization. This enables better performance when using hard disk drives as bricks.
|
Story Points: | --- |
Clone Of: | 1539636 | Environment: | |
Last Closed: | 2018-11-08 05:37:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1539636 | ||
Bug Blocks: | 1520833, 1548985 |
Description
Sahina Bose
2018-01-31 06:20:08 UTC
Tested with the following-: 1. RedHat-release-virtualization-host-4.2-2.1.el7.x86_64 2. Cockpit-ovirt-dashboard-0.11.20-1 Lvm cache device was attached to the thinpool during the creation of bricks from the storage device. Following were the steps performed to test:- 1. Login to the cockpit UI and in gluster deployment configure hosts,package and volume tabs. 2. Configure the brick tab . Configure the LVM cache with the size and proceed to gluster deployment. 3. Gluster deployment was successful. Could see the LVM cache attached to the thinpool during the creation of bricks from the storage device. 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-2018:3523 |