Host network configuration tool
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Zuul 905c23dd89 Merge "Publish documents" 1 day ago
doc Update docs testing 2 days ago
etc/os-net-config/samples Merge "Add ovs_options and ovs_extra parameters to VLAN object" 1 month ago
os_net_config Modify udev rule for VF representor rename 2 weeks ago
releasenotes Update master for stable/stein 1 month ago
zuul.d Publish documents 2 days ago
.coveragerc Update .coveragerc after the removal of respective directory 1 year ago
.gitignore Switch to stestr 10 months ago
.gitreview OpenDev Migration Patch 1 month ago
.mailmap Initial commit 5 years ago
.stestr.conf Switch to stestr 10 months ago
CONTRIBUTING.rst Publish documents 2 days ago
HACKING.rst Replacing the link in HACKING.rst 6 months ago
LICENSE Initial commit 5 years ago
README.rst Publish documents 2 days ago
babel.cfg Initial commit 5 years ago
requirements.txt Uncap jsonschema 1 month ago
setup.cfg Change openstack-dev to openstack-discuss 5 months ago
setup.py Updated from global requirements 2 years ago
test-requirements.txt Update docs testing 2 days ago
tox.ini Update docs testing 2 days ago

README.rst

Team and repository tags

image

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.

Release Notes

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

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.