Description of problem: As of now when user tries to create a RAID0 volume there is no way for him to specify a stripe size. User should be given an option to specify the stripe size. Version-Release number of selected component (if applicable): ovirt-engine-webadmin-portal-3.6.0-0.0.master.20150406175153.gite240701.el6.noarch How reproducible: Steps to Reproduce: 1. Add a rhel7 node to console which has JBODS configured with 0. 2. Now sync all the devices in UI. 3. click on the create brick dialog. 4. For RAID0, user is not asked to provide the stripe size. Actual results: UI should does not provide a way for the user to specify the stripe size Expected results: UI should provide a way for the user to specify the stripe size for RAID0 and that should be used to tune lvm parameters while creating a brick. Additional info:
We don't need to ask the strip size for RAID0 volume from the user. We can default the data alignment value to 256K internally. Refer the Redhat Storage Admin Guide for more info : https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html/Administration_Guide/Brick_Configuration.html
Aggregation of disks in RAID0 volume is not recommended by gluster. So we can expect the user to create RAID0 volume using only one disk.
Patch sent to upstream for review: https://gerrit.ovirt.org/40890
Earlier assumption of the default alignment value is zero. But now its changed to 256. Alignment value plays an important role for calculation and design making while pvcreate, vg, pool & lv create process. This requires lot of changes in the code and might need to do lot of testing. The patch is under review. We will sent it to downstream after the review is complete and merged upstream.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
oVirt 3.6.0 has been released on November 4th, re-targeting to 4.0 since this bug has been marked with severity < high
This bug is flagged for 3.6, yet the milestone is for 4.0 version, therefore the milestone has been reset. Please set the correct milestone or add the flag.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
The patch fixing this is merged in master. Moving to ON_QA to verify with 4.0 build
Closing due to capacity reasons, if still happen, please reopen.