mfsipmap.cfg(5)

NAME
mfsipmap.cfg - MooseFS chunkserver IP mappings

DESCRIPTION
The file mfsipmap.cfg contains MooseFS chunk 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 chunk server's IPs remapped and then the chunk server's remmapings 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 lasty, clients' IPs can be defined as single IPs, one IP per line:
n.n.n.n
x.x.x.x

Chunk 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 preceeding this mapping, the chunkserver 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 chunkserver with IP 10.10.10.3, will instead do so using IP 10.20.30.7, with chunkserver 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 chunkserver with IP 10.10.10.3, will instead do so using IP 10.20.30.7, with chunkserver with IP 10.10.10.4 it will use IP 10.20.33.1. Any client having IP starting with 192.168.2 and ending in 1 to 24, if it wants to communicate with chunkserver with IP 10.10.10.3, will instead do so using IP 10.20.38.8, with chunkserver with IP 10.10.10.5 it will use IP 10.20.38.37. Notice, that the same chunkserver (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.

COPYRIGHT
Copyright (C) 2025 Jakub Kruszona-Zawadzki, Saglabs SA This file is part of MooseFS. MooseFS is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, version 2 (only). MooseFS is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with MooseFS; if not, write to the Free Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02111-1301, USA or visit http://www.gnu.org/licenses/gpl-2.0.html

SEE ALSO
mfsmaster(8), mfsmaster.cfg(5)