f1788f3ac6
The current cirros image version is 0.4.0. As we have the image name hard-coded, it is required that we update it manually. See [1] for reference. [1] https://review.openstack.org/#/c/521825/ Change-Id: I99a49975c5674991d84932ebd2c7ab6599d343ea Migrate Dragonflow from Ryu to os-ken This change causes Dragonflow to stop consuming Ryu in favor of os-ken. os-ken becomes the reference implementation for BGP services and Dragonflow no longer has a dependency on Ryu. See [1] for reference in Neutron. [1] https://review.openstack.org/607008/ Change-Id: Ifbf294f2f586cf765d20cfa60774c45aa735ca62 Force delete of VM on close There are tests that fail because we are waiting for the VM to complete shutdown In tests, we do not mind destroying the machine forcefully as there is no reason to wait for it. Change-Id: I5f8e4928ceb7b467af891835600cd8096ec88d2b use payloads for SECURITY_GROUP BEFORE_DELETE events This patch switches over to the payload style callbacks for BEFORE_DELETE events of SECURITY_GROUP resources. Co-Authored-By: Boden R <bodenvmw@gmail.com> Depends-On: https://review.openstack.org/#/c/597599/ Change-Id: Ie9163ad7baecf85e234e4253160f30015b43166b |
||
|---|---|---|
| devstack | ||
| doc | ||
| dragonflow | ||
| etc | ||
| rally-jobs | ||
| releasenotes | ||
| tools | ||
| vagrant | ||
| zuul | ||
| .coveragerc | ||
| .gitignore | ||
| .gitreview | ||
| .mailmap | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| CONTRIBUTING.rst | ||
| Dockerfile | ||
| Dockerfile.fedora | ||
| HACKING.rst | ||
| LICENSE | ||
| README.rst | ||
| babel.cfg | ||
| lower-constraints.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
README.rst
Team and repository tags
Distributed SDN-based Neutron Implementation
- Free software: Apache license
- Homepage: https://launchpad.net/dragonflow
- Source: https://git.openstack.org/cgit/openstack/dragonflow
- Bugs: https://bugs.launchpad.net/dragonflow
- Documentation: https://docs.openstack.org/dragonflow/latest/
- Release notes: https://docs.openstack.org/developer/dragonflow/releasenotes.html
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
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