mfsipmap.cfg
MooseFS chunkserver and master IP mappings.
This page reproduces the manual page mfsipmap.cfg(5) as the product ships it: the text man mfsipmap.cfg prints on a machine where the packages are installed. It is not edited here, and where it disagrees with the rest of this documentation, the documentation is the side kept against the sources. What the subject is: mfsipmap.cfg.
Description
The file mfsipmap.cfg contains MooseFS chunkserver and master server IPs mapping lists.
SYNTAX
General file format: the content is one or more different LAN remappings. Each LAN remapping consists of first the list of client IPs that will have the server's IPs remapped and then the server's remappings themselves. Proper file is build like this: client IP list - mapping list - client IP list - mapping list etc.
Clients' IPs can be defined as classes in two formats: IP/MASK or IP/BITS:
n.n.n.n/m.m.m.m
n.n.n.n/b
Class definitions can use shortened IP, for example a.b.c.0/24 is the same as a.b.c/24, and a.b.0.0/255.255.0.0 is the same as a.b/255.255.0.0.
Clients' IPs can also be defined as ranges in format IP - IP:
f.f.f.f-t.t.t.t
And lastly, clients' IPs can be defined as single IPs, one IP per line:
n.n.n.n
x.x.x.x
Server's IP mappings are always defined in one format IP:IP:
n.n.n.n:r.r.r.r
If a client's IP is defined in the list directly preceding this mapping, the server with IP on the left side of the mapping will be presented to this client with the IP on the right side of the mapping.
Lines starting with # character are ignored as comments.
Notes
This file allows to define LAN mappings in cases where there is no common scheme of numbering in LANs, i.e. where the same servers have different IP suffixes in each LAN. If machines have common suffixes, use MULTILAN_BITS and MULTILAN_CLASSES options from mfsmaster.cfg file instead.
Examples
File content:
192.168.1/24
192.168.2.1-192.168.2.24
192.168.3.20
10.10.10.3:10.20.30.7
10.10.10.4:10.20.33.19
Behaviour:
Any client having IP starting with 192.168.1, starting with 192.168.2 and ending in 1 to 24, or with IP 192.168.3.20, if it wants to communicate with server with IP 10.10.10.3, will instead do so using IP 10.20.30.7, with server with IP 10.10.10.4 it will use IP 10.20.33.19.
File content:
192.168.1/24
10.10.10.3:10.20.30.7
10.10.10.4:10.20.33.19
192.168.2.1-192.168.2.24
10.10.10.3:10.20.38.8
10.10.10.5:10.20.38.37
Behaviour:
Any client having IP starting with 192.168.1, if it wants to communicate with server with IP 10.10.10.3, will instead do so using IP 10.20.30.7, with server with IP 10.10.10.4 it will use IP 10.20.33.19. Any client having IP starting with 192.168.2 and ending in 1 to 24, if it wants to communicate with server with IP 10.10.10.3, will instead do so using IP 10.20.38.8, with server with IP 10.10.10.5 it will use IP 10.20.38.37. Notice, that the same server (with IP 10.10.10.3) will be presented to clients from different IP lists with different remapped IP.
Note: empty lines between sections are not necessary, they are used in the above examples only for ease of reading.