Bug 1523603 - [RFE] Configure dedupe&compression on gluster brick devices
Summary: [RFE] Configure dedupe&compression on gluster brick devices
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhhi
Version: rhhi-1.1
Hardware: x86_64
OS: Linux
high
medium
Target Milestone: ---
: RHHI-V 1.5
Assignee: Sahina Bose
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1510857 1518537 1523562
Blocks: 1520833 1548985
TreeView+ depends on / blocked
 
Reported: 2017-12-08 11:30 UTC by Sahina Bose
Modified: 2018-11-08 05:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Configuring VDO at deployment time lets you reduce the amount of storage space required for data. You can configure Gluster bricks to use deduplication and compression, and monitor and configure notifications for VDO capacity usage in Cockpit, so that you know when your storage is running out of space.
Clone Of:
Environment:
Last Closed: 2018-11-08 05:37:25 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:3523 0 None None None 2018-11-08 05:38:50 UTC

Description Sahina Bose 2017-12-08 11:30:53 UTC 
Description of problem:

Configure dedupe & compression (using VDO) on devices used as gluster bricks - for vmstore & data gluster volumes during cockpit deployment.
This should also be available for the brick creation via Cockpit


How reproducible:
NA
Comment 3 SATHEESARAN 2018-02-28 11:44:51 UTC 
This can't be ON_QA, as the dependent bug BZ 1523562  is in assigned state.
Comment 4 SATHEESARAN 2018-04-04 11:57:07 UTC 
Verified with RHV 4.2.2-6 and cockpit-ovirt-dashboard-0.11.19 with gdeploy-2.0.2-22.el7rhgs

Dedupe and compression features could be enabled for the gluster bricks
Comment 10 errata-xmlrpc 2018-11-08 05:37:25 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.