openstack/os-net-config
Code Issues Proposed changes
RETIRED, Host network configuration tool
154 Commits 3 Branches 29 Tags 10 MiB
f79d534c3e
Go to file
Saravanan KR f79d534c3e Supporting numbered nics for DPDK Port and DPDK Bond 
Modified the sample code to use numbered nics instead of physical
device name and added test code for testing the numbered nic usecases.

Implements: blueprint tripleo-ovs-dpdk
Depends-On: If1c91402d2d393140dc1b4a678e68a1bcdbe81e4

Change-Id: Ifadb495be57fcef56a97250de0c52fd03f2dd817
2016-08-26 15:30:58 +05:30
doc/source Initial commit 2014-06-06 12:27:50 -04:00
etc/os-net-config/samples Supporting numbered nics for DPDK Port and DPDK Bond 2016-08-26 15:30:58 +05:30
os_net_config Supporting numbered nics for DPDK Port and DPDK Bond 2016-08-26 15:30:58 +05:30
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:41:51 +00:00
.gitignore Initial commit 2014-06-06 12:27:50 -04:00
.gitreview Add a .gitreview file for os-net-config 2014-09-18 15:53:03 -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 Workflow documentation is now in infra-manual 2014-12-05 03:30:38 +00: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
README.rst Updated description in README.rst 2014-09-04 09:51:05 -04:00
requirements.txt Remove deprecated references to oslo-incubator 2015-02-24 09:21:04 +00:00
setup.cfg Correct the setup.cfg OS. 2014-09-04 10:29:12 -04:00
setup.py Add interface, address, and route objects 2014-06-09 10:42:19 -04:00
test-requirements.txt Remove discover from test-requirements 2016-07-22 06:44:12 +00:00
tox.ini py26 is no longer supported by Infra's CI 2015-12-26 14:21:47 +05:30

README.rst

os-net-config

host network configuration tool

An implementation of 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 CLI (os-net-config) which provides configuration via a YAML or JSON file formats. By default os-net-config uses a YAML config file located at /etc/os-net-config/config.yaml. This can be customized via the --config-file CLI option.
  • A python library which provides configuration via an object model.

YAML Config Examples

  • Configure an OVS bridge with a single attached interface (port)
network_config:
  - 
    type: ovs_bridge
    name: br-ctlplane
    use_dhcp: true
    ovs_extra:
      - br-set-external-id br-ctlplane bridge-id br-ctlplane
    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
         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
    use_dhcp: true
    members:
      - 
        type: interface
        name: em1
      - 
        type: vlan
        vlan_id: 16
        addresses:
          - 
            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... (implementation in progress)

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.