RETIRED, SDN based Distributed Virtual Router for OpenStack Neutron
Go to file
Li Ma fe8bc32be9 Delete the tap-metadata device when it exists in the system
The existing tap-metadata device causes failure of service
startup. We first check its existance and re-initialize the
environment when necessary.

Change-Id: I9d6f1262909ee461e5891a023f7394565a12f91b
Closes-Bug: #1656500
2017-01-17 08:39:29 +00:00
devstack Merge "dpdk: could not bind or unbind nic in the latest release" 2017-01-11 13:25:53 +00:00
doc [TrivialFix] Fix dir specs comment typo error 2017-01-11 09:38:20 +08:00
dragonflow Delete the tap-metadata device when it exists in the system 2017-01-17 08:39:29 +00:00
etc/oslo-config-generator Moved config options of metadata_service_app 2016-11-23 12:27:34 +00:00
rally-jobs Use neutron rally job 2016-11-30 05:00:56 +00:00
releasenotes Enable release notes translation 2016-10-06 20:26:17 +02:00
tools Fix etcd driver requirement 2016-10-17 02:44:51 +00:00
vagrant Vagrant: Add support for parallels and libvirt 2016-05-22 20:20:25 -05:00
.coveragerc Update .coveragerc after the removal of openstack directory 2016-10-17 16:53:51 +05:30
.gitignore Remove df-ext-services 2016-11-02 14:36:52 +08:00
.gitreview Update .gitreview file for project rename 2015-06-12 23:12:30 +00:00
.mailmap Initial Cookiecutter Commit. 2015-01-29 16:46:27 +02:00
.testr.conf Seperate unit and fullstack testing in dragonflow 2015-12-08 08:40:54 +02:00
CONTRIBUTING.rst Initial Cookiecutter Commit. 2015-01-29 16:46:27 +02:00
HACKING.rst Initial Cookiecutter Commit. 2015-01-29 16:46:27 +02:00
LICENSE Initial Cookiecutter Commit. 2015-01-29 16:46:27 +02:00
README.rst Show team and repo badges on README 2016-11-25 16:39:09 +01:00
babel.cfg Initial Cookiecutter Commit. 2015-01-29 16:46:27 +02:00
requirements.txt Updated from global requirements 2017-01-02 16:08:59 +00:00
setup.cfg Moved config options of metadata_service_app 2016-11-23 12:27:34 +00:00
setup.py Updated from global requirements 2015-09-17 16:38:13 +00:00
test-requirements.txt Updated from global requirements 2016-11-02 15:31:05 +00:00
tox.ini Enable coverage report in console output 2017-01-11 10:17:43 +08:00

README.rst

Team and repository tags

image

Distributed SDN-based Neutron Implementation

Solution Overview

Overview

Dragonflow implements Neutron using a lightweight embedded SDN Controller.

Our project mission is to Implement advanced networking services in a manner that is efficient, elegant and resource-nimble

Distributed Dragonflow

Comprehensive agentless implementation of the Neutron APIs and advanced network services, such as fully distributed Switching, Routing, DHCP and more.

This configuration is the current focus of Dragonflow. Overview and details are available in the Distributed Dragonflow Section

Solution Overview

Mitaka Version Features

  • L2 core API

    IPv4, IPv6 GRE/VxLAN/STT/Geneve tunneling protocols L2 Population

  • Distributed L3 Virtual Router

  • Distributed DHCP

  • Distributed DNAT

  • Security Groups Using OVS and Connection tracking

  • Pluggable Distributed Database

    Supported databases:

    Stable:

    ETCD, RAMCloud, Redis, Zookeeper

    In progress:

    RethinkDB

  • Pluggable Publish-Subscribe

    ZeroMQ, Redis

  • Selective DB Distribution

    Tenant Based Selective data distribution to the compute nodes

Experimental Mitaka Features

  • Local Controller Reliability

In progress

  • IGMP Distributed application
  • Allowed Address Pairs
  • Port Security
  • DHCP DOS protection
  • Distributed Meta Data Service
  • Kuryr integration
  • Local Controller HA
  • ML2 Driver, hierarchical Port Binding
  • VLAN L2 Networking support
  • Smart broadcast/multicast

In planning

  • Distributed Load Balancing (East/West)
  • DNS service
  • Port Fault detection
  • Dynamic service chaining (service Injection)
  • SFC support
  • Distributed FWaaS
  • Distributed SNAT
  • VPNaaS

Configurations

To generate the sample dragonflow configuration files, run the following command from the top level of the dragonflow directory:

tox -e genconfig

If a 'tox' environment is unavailable, then you can run the following script instead to generate the configuration files:

./tools/generate_config_file_samples.sh