libdmmp is build on top of libmpathcmd, which is a more general library interface to multipathd, that simply sends the commands and receives the data, formatted just like it would be if you ran the command at the commandline. I'm also packaging this library as well.

Actually, the device-mapper-multipath package will now have 3 new subpackages, device-mapper-multipath-devel, libdmmp, and libdmmp-devel. I'm not adding libdmmp to device-mapper-multipath-libs (which is getting libmpathcmd, and already has the libmpathpersist libraries) because it requires json-c to work, and I don't want to add that dependency to all multipath users.

device-mapper-multipath-devel will include the headers and library files for using the libmpathcmd libaray, as well as the libmpathpersist library (which were previously installed with device-mapper-multipath-libs). libdmmp with just include that library, and libdmmp-devel will include all the
files necesary to write programs that use it.

Patches backported.

Ben:

I did a little bit of rearranging here to fit the release note format. Does this seem ok to you?

Steven

Looks good.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1961