Description of problem packaging tcmu-runner for gluster-block tcmu-runner is a daemon that handles the userspace side of the LIO TCM-User backstore. Background: TCM is another name for LIO, an in-kernel iSCSI target (server). As we know existing TCM targets run in the kernel. TCMU (TCM in Userspace) allows userspace programs to be written which act as iSCSI targets. These enables wider variety of backstores without kernel code. Hence the TCMU userspace-passthrough backstore allows a userspace process to handle requests to a LUN. TCMU utilizes the traditional UIO subsystem, which is designed to allow device driver development in userspace. One such backstore with best clustered network storage capabilities is GlusterFS Any TCMU userspace-passthrough can utilize the TCMU framework handling the messy details of the TCMU interface. One such passthrough is Tcmu-runner (Thanks to Andy Grover). Tcmu-runner has a glusterfs handler that can interact with the backed file in gluster volume over gluster libgfapi interface and can show it as a target (over network). Some responsibilities of userspace-passthrough include, Discovering and configuring TCMU UIO devices waiting for the events on the device and managing the command ring buffers. Info: gluster-block is dependent on this for exporting files in gluster volume(userspace) as block devices.
dist-git repo for tcmu-runner already exists at [1] and it was created with Bug#1383116 [2] which is ON_QA. Hence moving this Bug to "build" component. [1] http://pkgs.devel.redhat.com/cgit/rpms/tcmu-runner/log/?h=rhgs-3.2.0-rhel-7 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1383116
(In reply to Sreenath G from comment #2) > dist-git repo for tcmu-runner already exists at [1] and it was created with > Bug#1383116 [2] which is ON_QA. Hence moving this Bug to "build" component. > > [1] > http://pkgs.devel.redhat.com/cgit/rpms/tcmu-runner/log/?h=rhgs-3.2.0-rhel-7 > > [2] https://bugzilla.redhat.com/show_bug.cgi?id=1383116 Sreenath, BZ 1383116 is not an approved bug for rhgs-3.2.0. I think it's better to close this one as a duplicate of BZ 1383116 and target the latter for 3.3. *** This bug has been marked as a duplicate of bug 1383116 ***