RETIRED, Host network configuration tool
Go to file
Dan Prince 3b5e878987 A vlan on an OVS bridge doesn't require a device
Updates the object model so that a VLAN on top of a bridge
(an OVS int port) doesn't require a physical device to
be set in the object model.
2014-08-21 13:25:38 -04:00
doc/source Initial commit 2014-06-06 12:27:50 -04:00
etc/os-net-config/samples A vlan on an OVS bridge doesn't require a device 2014-08-21 13:25:38 -04:00
os_net_config A vlan on an OVS bridge doesn't require a device 2014-08-21 13:25:38 -04:00
.coveragerc Initial commit 2014-06-06 12:27:50 -04:00
.gitignore Initial commit 2014-06-06 12:27:50 -04:00
.mailmap Initial commit 2014-06-06 12:27:50 -04:00
.testr.conf Initial commit 2014-06-06 12:27:50 -04:00
babel.cfg Initial commit 2014-06-06 12:27:50 -04:00
CONTRIBUTING.rst Initial commit 2014-06-06 12:27:50 -04:00
HACKING.rst Initial commit 2014-06-06 12:27:50 -04:00
LICENSE Initial commit 2014-06-06 12:27:50 -04:00
MANIFEST.in Initial commit 2014-06-06 12:27:50 -04:00
openstack-common.conf Import processutils from oslo-incubator. 2014-06-09 17:13:57 -04:00
README.rst Add README example docs, etc. 2014-07-09 16:05:56 -04:00
requirements.txt Add support for parsing YAML 2014-08-20 21:46:46 -04:00
setup.cfg Add os-net-config CLI 2014-07-01 16:54:25 -04:00
setup.py Add interface, address, and route objects 2014-06-09 10:42:19 -04:00
test-requirements.txt Add interface, address, and route objects 2014-06-09 10:42:19 -04:00
tox.ini Initial commit 2014-06-06 12:27:50 -04:00

os-net-config

host network configuration tool

This is an initial implementation towards the 'network configuration' spec @ https://review.openstack.org/#/c/97859/ The intention is for this code to be moved under the tripleo project in due course.

Features

The core aim of this project is to allow fine grained (but extendable) configuration of the networking parameters for a network host. The project consists of:

  • A python library which provides configuration via an object model.
  • A CLI (os-net-config) which provides configuration via a JSON file format. By default os-net-config uses a JSON config file located at /etc/os-net-config/config.json. This can be customized via the --config-file CLI option.

JSON Config Examples

  • Configure an OVS bridge with a single attached interface (port)
{ "network_config": [
        {
            "type": "ovs_bridge",
            "name": "br-ctlplane",
            "use_dhcp": "true",
            "members": [
                {
                    "type": "interface",
                    "name": "em1"
                }
            ]
        }
    ]
}
  • Configure an OVS bridge on top of an OVS bond
{ "network_config": [
        {
            "type": "ovs_bridge",
            "name": "br-ctlplane",
            "use_dhcp": "true",
            "members": [
                {
                    "type": "ovs_bond",
                    "name": "bond1",
                    "use_dhcp": "true",
                    "members": [
                        { "type": "interface", "name": "em1" },
                        { "type": "interface", "name": "em2" }
                    ]
                }
            ]
        }
    ]
}
  • Configure a tagged VLAN interface on top of an OVS bridge
{ "network_config": [
        {
            "type": "ovs_bridge",
            "name": "br-ctlplane",
            "members": [
                {
                    "type": "vlan",
                    "device": "em1",
                    "vlan_id": "16",
                    "addresses": [{
                        "ip_netmask": "192.0.2.1/24"
                    }],
                    "routes": [{
                        "next_hop": "192.0.2.1",
                        "ip_netmask": "192.0.2.1/24"
                    }]
                }
            ]
        }
    ]
}

Provider Configuration

Providers are use to apply (implement) the desired configuration on the host system. By default 3 providers are implemented:

  • Ifcfg: persistent network config format stored in /etc/sysconfig/network-scripts
  • ENI: persistent network config format stored in /etc/network/interfaces
  • iproute2: non-persistent provider which implements the config using iproute2, vconfig, etc...

When using bin/os-net-config the provider is automatically selected based on the host systems perferred persistent network type (ifcfg or ENI). This can be customized via the --provider CLI option.