Description of problem: Integrate the flow as per http://www.ovirt.org/develop/release-management/features/gluster/gluster-dr/ for gluster based storage domains in engine Version-Release number of selected component (if applicable): How reproducible: NA
Agreed with the Gluster team we can move Gluster bugs to ON_QA on engine build.
Tested with oVirt-4.1.0-3 There exists the 'Remote Data Sync Setup' tab for the gluster data domain and, if that gluster data domain is created with the gluster volume that is managed in the same cluster, then geo-rep have to setup explicitly on that volume and schedule could be created from 'Remote Data Sync Setup' UI