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 |
||
|---|---|---|
| .. | ||
| cli | ||
| devrefs | ||
| multi-node-conf | ||
| sfc-example | ||
| single-node-conf | ||
| specs | ||
| conf.py | ||
| configuration.rst | ||
| containers.rst | ||
| contributing.rst | ||
| distributed_dhcp.rst | ||
| distributed_dragonflow.rst | ||
| docker_install.rst | ||
| features.rst | ||
| gmr.rst | ||
| index.rst | ||
| installation.rst | ||
| manual_deployment.rst | ||
| osprofiler.rst | ||
| pipeline.rst | ||
| pluggable_db.rst | ||
| pluggable_pubsub.rst | ||
| readme.rst | ||
| releasenotes_create.rst | ||
| reviewers_guide.rst | ||
| testing_and_debugging.rst | ||
| usage.rst | ||
readme.rst
Installation guide for Dragonflow, Keep in mind that Dragonflow is still in beta.
Prerequisites
Require Open vSwitch 2.5.0
Quick Installation
Clone Devstack
git clone https://git.openstack.org/openstack-dev/devstackCopy one of the following as your
local.confto your devstack folder
DevStack Single Node Configuration
DevStack Multi Node Configuration
- Edit local.conf according to your configuration, See Detailed Installation for more details, or the Devstack configuration manual
DHCP configuration (IPv4 Only Environment)
no configuration needed
DHCP configuration (mixed IPv4/IPv6 or pure IPv6)
enable_service q-dhcp
If the q-dhcp is installed on a different Node from the q-svc
Please add the following flag to the neutron.conf on the q-svc node
use_centralized_ipv6_DHCP=True
Meta data and cloud init
In order to enable the VMs to get configuration like public keys, hostnames, etc.. you need to enable meta service. You can do it by adding the following lines to local.conf file (before running 'stack.sh' command):
enable_service q-meta enable_service q-dhcp
For the meta service to work correctly, another "hidden" service must be started. It is called meta-service-proxy and it is used to forward meta data client requests to real meta service. By default, it is started by regular q-dhcp service for each tenant. As a result 'q-meta' and 'q-dhcp' services must be enabled.
Database configuration
Choose one of the following Database drivers in your local.conf
Etcd Database:
enable_service df-etcd
Ram Cloud Database:
enable_service df-ramcloud
enable_service df-rccoordinator
enable_service df-rcmaster
Zookeeper Database:
enable_service df-zookeeper
enable_service df-zookeeper-server
Redis Database:
enable_service df-redis
enable_service df-redis-server
Detailed Installation
Important parameters that needs to be set in local.conf
:
HOST_IP <- The management IP address of the current node
FIXED_RANGE <- The overlay network address and mask
FIXED_NETWORK_SIZE <- Size of the overlay network
NETWORK_GATEWAY <- Default gateway for the overlay network
FLOATING_RANGE <- Network address and range for Floating IP addresses (in the public network)
Q_FLOATING_ALLOCATION_POOL <- range to allow allocation of floating IP from (within FLOATING_RANGE)
PUBLIC_NETWORK_GATEWAY <- Default gateway for the public network
SERVICE_HOST <- Management IP address of the controller node
MYSQL_HOST <- Management IP address of the controller node
RABBIT_HOST <- Management IP address of the controller node
GLANCE_HOSTPORT <- Management IP address of the controller node (Leave the port as-is)You can find example configuration files in the multi-node-conf or the single-node-conf directories.
Automated setup using Vagrant + Virtualbox
Troubleshooting
You can check northbound database by using db-df utility, see details in Testing and Debugging.