1freight-network-config(1)   General Commands Manual  freight-network-config(1)
2
3
4

NAME

6       freight-network-config - Configuration file format for freight networks
7

CONFIG FILE FORMAT

9       The network config file has the following format
10
11       ---------------------------------------------
12       # These are comments
13
14
15       # The leading config block starts with network=
16       network = {
17               type = "<network type>";
18       };
19
20       address_config = {
21            ipv4_aquisition = "dhcp|static";
22            ipv6_aquisition = "dhcpv6|slaac|static";
23       };
24
25       <type>_config = {
26            # see network type sections for config options
27       };
28
29
30       static_address = [
31            {
32                 cname = "container name";
33                 ipv4_addr="192.168.1.1";
34                 ipv6_addr="fe80::fc54:ff:fe84:f6f0/64";
35            },
36            {
37                 cname = "container name"'
38                 ipv4_addr="192.168.1.2";
39                 ipv6_addr="fe80::fc54:ff:fe84:f6f1/64";
40            },
41            ...
42       ];
43
44
45

NETWORK TYPES

47       bridged
48
49       Bridged  networks  are  just  that,  simple  straight  layer 2 bridges.
50       Freight nodes running containers attached to networks of this type will
51       create  a  bridge,  attach a physical interface to the bridge, create a
52       veth pair, attach one end to the bridge and pass the other end  to  the
53       container.
54
55
56

ADDRESS CONFIG

58       The  address config section ennumerates how a container on this network
59       will obtain an address.  Current supported formats are dhcp, and slaac
60
61

NETWORK TYPE CONFIGURATIONS

63       bridged_config
64
65       There are no bridge specific config options
66
67

<NAME> STATIC ADDRESSES

69       This section allows for the configuration to  specify  a  per-container
70       static  address override.  If a container with the instance name <name>
71       is attached to the network, the host running that container will assign
72       the   provided   static   address  to  the  container,  overriding  the
73       address_config section.  This is useful in creating networks that  have
74       a  'controlling'  container - a container on an isolated tunnel network
75       perhaps that serves dhcp and dns to the other containers on the network
76       for example.
77
78
79
80
81
82Neil Horman                        Apr 2015          freight-network-config(1)
Impressum