Project

General

Profile

Actions

Documentation #4227

closed

networks section still doesn't explain global vs specific

Added by Dan Mick about 11 years ago. Updated about 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
% Done:

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

The network section implies that you must set both the [global] and the [<daemon>] settings for network addresses, and doesn't talk about the "search for a NIC on the subnet" algorithm at all. It also doesn't answer a question I have right now, which is "what happens if you specify global settings, but need to use only
one net for a specific host? can you set the per-daemon public and cluster addresses identically?"

Actions #1

Updated by Sage Weil about 11 years ago

the sections behave in the usual way, where [type.foo] overrides [type] overrides [global].

Actions #2

Updated by John Wilkins about 11 years ago

  • Assignee set to John Wilkins
Actions #3

Updated by Dan Mick about 11 years ago

Sage: yeah, that wasn't the question; the question was, say you have public/cluster nets
in global; can you specify an OSD on only the public net? (presumably by specifying
a specific public address for that daemon only, but maybe a specified public and cluster
address, set to the same public address, so that when it attempts to connect to "cluster"
it doesn't search and fall through to trying to find an address on cluster that it doesn't have)?

Actions #4

Updated by John Wilkins about 11 years ago

  • Status changed from New to Resolved

Added a new network configuration section. http://ceph.com/docs/master/rados/configuration/network-config-ref/ and covered the 1-NIC two networks use case in a topic under http://ceph.com/docs/master/rados/configuration/network-config-ref/#ceph-daemons

Actions

Also available in: Atom PDF