Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1494647

Summary: Documentation update for changed vdo commands
Product: Red Hat Enterprise Linux 7 Reporter: Joe Shimkus <jshimkus>
Component: doc-Storage_Administration_GuideAssignee: Marek Suchánek <msuchane>
Status: CLOSED CURRENTRELEASE QA Contact: Zhang Kexin <kzhang>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: rhel-docs
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-13 18:49:51 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: 1495322, 1552784    

Description Joe Shimkus 2017-09-22 17:58:36 UTC
Describe the issue: 
The following vdo command line utility commands have been changed.

"disable" has been renamed to "deactivate".
No other changes have been made to it.

"enable" has been renamed to "activate".
No other changes have been made to it.

Comment 2 Joe Shimkus 2017-10-18 15:12:14 UTC
Further options that have been renamed for the vdo management command (vdo).
Any references in Bugzilla prior to the date of this comment are superseded.

--albireoMem has been renamed to --indexMem
    --indexMem=<gigabytes>
                        Specifies the amount of index memory in gigabytes; the
                        default is currently 0.25 GB. 0 requests the default.
                        The special decimal values 0.25, 0.5, 0.75 can be
                        used, as can any positive integer.

--volumeGroup has been renamed to --device
    --device=<devicepath>
                        Specify the path of the device to use for VDO storage.

Comment 3 Joe Shimkus 2017-10-18 18:53:30 UTC
Please note that the change of --volumeGroup to --device represents a change from anything LVM-related.  That is to say, the --device option represents storage that has been made available (by whatever manner) by the administrator and that storage will be used "as is" as block storage.
Consequently, any references to LVM-related activities (creation, etc.) in relation to --volumeGroup (now --device) should be removed from the documentation.

Comment 4 Marek Suchánek 2017-11-16 18:09:42 UTC
Thanks.

I'm setting this bug as a blocker for the VDO docs tracking bug.

Comment 5 Marek Suchánek 2018-02-08 12:55:23 UTC
All occurrences of the above mentioned commands and options should now be fixed in the Integration Guide:

* 29.4. Integrating VDO
  https://access.qa.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/integrating-vdo

* 29.7. VDO Commands
  https://access.qa.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/commands

Comment 6 Marek Suchánek 2018-03-13 18:49:51 UTC
Content from the VDO Integration Guide has been published on the Customer Portal:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/storage_administration_guide/vdo-integration

Therefore, I'm closing this bug as CURRENTRELEASE.