Use Case Overview: As a ROBO Operator, I want to deploy my RHHI 2.0 system with data reduction to reduce the volume of disk/SSD capacity required to operate my workloads so that I can reduce capital and operating expenses. This use case requires the following information: (a) specific requirements related to VDO deployment -RHHI 2.0 -RHGS 3.4 -RHV 4.2 -RHEL 7.5 or later -RHHI 1.x does not support upgrade paths for VDO -additional caveats as identified by Eng and/or QE (b) task information that informs the ROBO operator how to specify compression/de-duplication during deployment via gdeploy
This is supported only in RHHI-2.0 with RHV-4.2 We need to specify below configuration for "vdo" in gdeploy conf file: [vdo] ction: 'create', devices: "" names: "" logicalsize: "GB"
Vdo configuration need to add in gdeployConfig.conf which will be located (RHHI-2.0) at "/var/lib/ovirt-hosted-engine-setup/gdeploy/gdeployConfig.conf" but in (RHHI-1.x) it is located at "/tmp/gdeployConfig.conf" And the command is: gdeply -c gdeployConfig.conf
The actual config will be like: [vdo] action=create devices=sdb,sdb names=data,vmstore logicalsize=2000,2000 Here I have selected vdo for two devices.
Hi, We have done cockpit enhancement with two new feature. 1- We can expand cluster by adding additional hosts where we can configure vdo. 2- We can create new volume in existing deployment where we can configure vdo as well. But there is now way to update existing volumes from cockpit right now. Note: These features are in testing phase right now. Coming to you doc update, There are lot of changes required for gdeploy conf file as RHHI-2.0 has Asymmetric brick concept.i.e. we can configure bricks per host.So per host device and sizes may change. If vdo configured then pv and vg will change means both will use vdo name instead of device. Let me know when you will have time so that will sit and finish.
Went through the doc. The updated section looks good. Moving the bug as verified