Bug 1680019
| Summary: | [RFE] [heketi] Expand feature for Block PVs | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Patric Uebele <puebele> | |
| Component: | heketi | Assignee: | John Mulligan <jmulligan> | |
| Status: | CLOSED ERRATA | QA Contact: | Vinayak Papnoi <vpapnoi> | |
| Severity: | high | Docs Contact: | Amrita <asakthiv> | |
| Priority: | unspecified | |||
| Version: | ocs-3.11 | CC: | aramteke, asakthiv, bkunal, hchiramm, jmulligan, knarra, kramdoss, madam, mmuench, olim, pasik, prasanna.kalever, rcyriac, rhs-bugs, rtalur, storage-qa-internal, susgupta | |
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened, ZStream | |
| Target Release: | OCS 3.11.z Batch Update 6 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 1822068 (view as bug list) | Environment: | ||
| Last Closed: | 2020-12-17 04:31:42 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: | 1507764, 1707789, 1822068, 1889299 | |||
| Bug Blocks: | 1716431 | |||
|
Description
Patric Uebele
2019-02-22 14:44:43 UTC
Status? 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? 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. *** Bug 1702847 has been marked as a duplicate of this bug. *** Opps! looks like all needinfo got cleared, reverting needinfo flag on puebele 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 |