Red Hat Bugzilla – Bug 829356
Transport options need better docs
Last modified: 2012-06-07 03:03:27 EDT
Description of problem:
values for the transport option are not well described. The only possible options listed in man page are udp, updu and iba.
In cluster RNG (back in rhel6) the options are as follows:
udp (multicast default), udpb (broadcast), udpu (unicast) and rdma (Infiniband)
I'd like you to make sure the description in the man page is up to date.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. man corosync.conf (look for transport)
all options documented and matching current state
corosync man page is up to date. Cluster RNG will go (because it's part of cman and that will go) and there will be corosync RNG. Only difference I see is udpb which is udp + broadcast (and internally by cman this is converted to broadcast: yes and transport: udp). Both udp and broadcast are documented and can be used without any problems by user.
I'm closing bug as notabug. If you will feel there should be some kind of additional info, please reopen bug.
Thanks for the explanation. The iba and rdma options are also "translated" in a similar way?
rdma (in cman) = iba (in corosync). Plan (in corosync) is not use rdma, but rather directly iba (ibverbs) to achieve higher network throughput (iba should be like UDP, rdma is like TCP), but it's not sure if we will be able to finish such support in FC18 / RHEL 7 GA. But this is reason for different names in cman vs. corosync (cman describes real state (because of no future of it), corosync describes future (because it hopefully has some ;) ).