openstack
/
os-net-config
Code Issues Proposed changes
RETIRED, Host network configuration tool
223 Commits 3 Branches 125 Tags 10 MiB
Go to file
Cédric Jeanneret 9ce34d529d Allow to pass more than two DNS while putting 2 DNS 
Until now, when we pass more than 2 DNS, only the first one is added in
the ifcg-* config files.

This patch-set proves the issue, and proves the correction actually works.

Change-Id: I70a779782ab87cd4f74f3c50b0e649f503b386e3
Closes-Bug: #1716171
(cherry picked from commit 8ddab87c6e)
 		2017-09-15 00:14:20 +02:00
doc/source Initial commit 2014-06-06 12:27:50 -04:00
etc/os-net-config/samples Merge "Multiqueue support for OvsDpdkBond" 2017-06-09 10:56:12 +00:00
os_net_config Allow to pass more than two DNS while putting 2 DNS 2017-09-15 00:14:20 +02:00
.coveragerc Change ignore-errors to ignore_errors 2015-09-21 14:41:51 +00:00
.gitignore Fix 'tox -e cover' 2017-07-09 11:15:41 +02:00
.gitreview Update .gitreview for stable/pike 2017-08-17 21:21:54 +00:00
.mailmap Initial commit 2014-06-06 12:27:50 -04:00
.testr.conf 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 There is no documentation for os-net-config 2017-07-19 17:26:07 +05:30
babel.cfg Initial commit 2014-06-06 12:27:50 -04:00
requirements.txt Add schema-based config data validation 2017-07-12 22:57:34 +02:00
setup.cfg Remove unused Babel setup 2017-05-16 14:54:58 +02:00
setup.py Updated from global requirements 2017-03-31 17:45:11 +00:00
test-requirements.txt Updated from global requirements 2017-03-31 17:45:11 +00:00
tox.ini Fix 'tox -e cover' 2017-07-09 11:15:41 +02:00

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.

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.