RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 829356 - Transport options need better docs
Summary: Transport options need better docs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: corosync
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Friesse
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-06 14:33 UTC by Jaroslav Kortus
Modified: 2012-06-07 07:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 14:59:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Kortus 2012-06-06 14:33:27 UTC
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):
corosync-2.0.0-2.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. man corosync.conf (look for transport)
2.
3.
  
Actual results:
corosync-2.0.0-2.el7.x86_64

Expected results:
all options documented and matching current state

Additional info:

Comment 1 Jan Friesse 2012-06-06 14:59:07 UTC
Jardo,
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.

Comment 2 Jaroslav Kortus 2012-06-06 16:52:16 UTC
Thanks for the explanation. The iba and rdma options are also "translated" in a similar way?

Comment 3 Jan Friesse 2012-06-07 07:03:27 UTC
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 ;) ).


Note You need to log in before you can comment on or make changes to this bug.