On 01/28/2016 04:15 AM, Hannes Reinecke wrote: > > I would very much advocate to use the IPC interface into multipathd; > we can easily define a stable ABI for that. Do you have a preference for the format of the API? Are you thinking JSON, JSON-RPC, YAML, XML, XML-RPC? The user of the API would write a command to the netlink socket that multiapthd already listens? the command would be something like: multipathd show map topology JSON Just looking to confirm I understand. > ATM it's just being use for the userland CLI, and hence it'll return > human-readable output. But I don't have any issues to define a > machine-readable output, too, so that it can be easily parsed from > other programs. I've abandoned the approach of putting a d-bus thread in multipathd. But, I'm still hoping to help higher level tools understand the multipath picture (and help users manage/monitor it). Thanks for any help, Todd -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
