Bug 1680019 - [RFE] [heketi] Expand feature for Block PVs
Summary: [RFE] [heketi] Expand feature for Block PVs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 3.11.z Batch Update 6
Assignee: John Mulligan
QA Contact: Vinayak Papnoi
Amrita
URL:
Whiteboard:
: 1702847 (view as bug list)
Depends On: 1507764 1707789 1822068 1889299
Blocks: 1716431
TreeView+ depends on / blocked
 
Reported: 2019-02-22 14:44 UTC by Patric Uebele
Modified: 2023-03-24 14:35 UTC (History)
17 users (show)

Fixed In Version: heketi-9.0.0-11.el7rhgs
Doc Type: Enhancement
Doc Text:
With this update, Heketi can expand block volumes. As long as there is sufficient space in the Block hosting volumes, Heketi can expand block volumes similar to how standard volumes can be expanded. In cases where the original size of a block volume is insufficient for the continued use of the volume, the ability to expand a block volume avoids the need to create a new and larger block volume and migrate the data between volumes.
Clone Of:
: 1822068 (view as bug list)
Environment:
Last Closed: 2020-12-17 04:31:42 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1702847 1 None None None 2024-09-18 00:50:42 UTC
Red Hat Product Errata RHBA-2020:5602 0 None None None 2020-12-17 04:32:12 UTC

Internal Links: 1716431

Description Patric Uebele 2019-02-22 14:44:43 UTC 
Description of problem:
Block volume expansion is not supported in OpenShift Container Storage 3.11.. With the support of application workloads on gluster-block in OCS 3.11.1, this limitation will affect customers more now, as most modern storage solutions allow at least online expansion.

The request is to enable online expansion of block PVs acroass the whole stack (gluster-block provisioner, heketi, gluster-block).

Version-Release number of selected component (if applicable): 3.11


How reproducible: Every time


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Customer asking for it: PWC
Comment 3 Yaniv Kaul 2019-04-14 19:19:19 UTC 
Status?
Comment 4 Michael Adam 2019-04-15 23:11:28 UTC 
The resize/expand functionality is done at the gluster-block level (BZ 1507764).

Steps TODO:

- expand the heketi block-volume api/cli for the blockvolume expand operation
- change the kubernetes (out-of-tree) block-volume-provisioner to know expansion
- NOT SURE: how the (kubernetes in-tree) iscsi mount plugin deals with expansion!
  (The above just expands the block device, but we also need to expand the file system and possibly unmount the client(s) before and remount them afterwards...)

==> John can you provide more info? Maybe Humble is the right person to answer?
Comment 5 John Mulligan 2019-04-16 12:52:49 UTC 
Yeah the heketi part would mostly be fairly straightforward but I do need to know how we'd implement clean/rollback for expand in gluster-block. If it's fully atomic, just checking if the volume is expended or not at the g-block level should be sufficient. Adding needinfo on prasanna for that.

I agree that we need to know more about the iscsi side as well. Adding a needinfo on Humble. and perhaps Prasana with have an opinion about that as well.
Comment 8 Oonkwee Lim 2019-05-10 17:32:46 UTC 
*** Bug 1702847 has been marked as a duplicate of this bug. ***
Comment 20 Prasanna Kumar Kalever 2019-05-30 10:30:00 UTC 
Opps! looks like all needinfo got cleared, reverting needinfo flag on puebele
Comment 38 errata-xmlrpc 2020-12-17 04:31:42 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 (OpenShift Container Storage 3.11.z bug fix update), 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-2020:5602
Note You need to log in before you can comment on or make changes to this bug.