Description of problem:
This BZ is for bringing in userspace RBD changes required for LIO HA support being requested in
More info can also be found here:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Josh, can you comment on feasibility for 1.3? Was this already taken care of as part of the RHEL 7.1 effort perchance?
1.3 isn't feasible. The kernel portions are planned for 7.3. See:
Mike, I assume we need to package and ship https://github.com/SUSE/lrbd ? I think that's the only userland change needed here - does that match your understanding?
(In reply to Ken Dreyer (Red Hat) from comment #3)
> Mike, I assume we need to package and ship https://github.com/SUSE/lrbd ? I
> think that's the only userland change needed here - does that match your
lrbd package up for review in Fedora: bug 1303245
Still need to create an Ubuntu package.
Here are is info on how to use lrbd:
The difference between upstream and RHEL will be that we use iblock and upstream uses target_core_rbd.
However, in the RHEL version, I made iblock the default and only usable option, so you can't and do not need to pass in -I. Just run lrbd like described in the doc and it will use iblock.
And then of course if you run targetcli ls, the rbd device will show up in the iblock backend interface instead of the rbd backend one like in the pics on that page.
Ping. We are still missing a QA ack on this one.
See how you can run this tests,
Eventually this should become part of our regression tests.
Thanks Mike and Vasu, for providing the information.
Note that this bug pertains to RHEL-only, not Ubuntu. The Ubuntu kernel does not have the features we need.
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
I'm guessing we should rebase to a newer lrbd version, now that this is off the 2.0 schedule. Moving back to ASSIGNED in the meantime.
*** This bug has been marked as a duplicate of bug 1367182 ***