Description of problem: RHEV is not aware about existing LVM or prepared mountpoints inside RHS. If a RHEV admin create volumes in the wild, the root filesystem of RHS will most likely easily fill up to 100%. Version-Release number of selected component (if applicable): 3.1.0-32.el6ev How reproducible: Create brick on RHS host from within RHEV-M Gui Steps to Reproduce: 1.logon to the rhev-m gui 2.Select RHS datacenter\cluster\host 3.Create a new volume, add brick(s) Actual results: Brick is created on the RHS host. It doesn't care about the location where it is placed, can eventual be place inside the root filesystem of the RHS host Expected results: New brick should only be place on a LVM logical volume XFS filesystem. Additional info: In preparation, a Logical volume XFS formatted should be available for placing brick directories in here. Recommendation: integrate RHS Logical Volume Management inside RHEV GUI.
Please also note Bug 887311, opened by Patric Uebele.
Provisioning of bricks given a storage device is available since oVirt 3.6. Brick provisioning follows the recommended steps to create a Logical volume and mounts it at the brick path provided