Juju Charm - Neutron Gateway
Go to file
Aurelien Lourot 7c01bada1d Updates for stable branch creation
Set default branch for git review/gerrit.

Switch tests to stable.

Switch to using stable charm-helpers branch.

Switch to using stable charm.openstack branch.

Change-Id: I8bc2651e1db546ebe0fa6c944494ea37dc509a9c
2020-11-02 11:49:49 +01:00
actions Add cleanup action and OVS to OVN migration test 2020-09-11 19:11:32 +00:00
files Merge "fix the spelling mistakes" 2019-12-19 12:56:31 +00:00
hooks Batch update to land Ubuntu Groovy support into the charms 2020-10-12 11:23:09 +02:00
lib Update tox.ini files from release-tools gold copy 2016-09-09 19:43:18 +00:00
templates Add keepalived-healthcheck-interval config option 2020-08-20 13:23:57 +01:00
tests Updates for stable branch creation 2020-11-02 11:49:49 +01:00
unit_tests Add cleanup action and OVS to OVN migration test 2020-09-11 19:11:32 +00:00
.gitignore Update for Python 3 execution 2017-11-16 11:19:58 -08:00
.gitreview Updates for stable branch creation 2020-11-02 11:49:49 +01:00
.project Rename project 2015-09-15 09:30:01 +01:00
.pydevproject Rename project 2015-09-15 09:30:01 +01:00
.stestr.conf Replace ostestr with stestr in testing framework. 2019-03-07 17:12:21 -05:00
.zuul.yaml Switch to Ussuri jobs 2019-12-03 16:41:50 +08:00
Makefile Sync helpers for 20.05 2020-05-18 14:46:36 +02:00
README.md Mark OVS bridges and ports as managed by charm-neutron-gateway 2020-08-27 12:00:32 +02:00
actions.yaml Add cleanup action and OVS to OVN migration test 2020-09-11 19:11:32 +00:00
charm-helpers-hooks.yaml Updates for stable branch creation 2020-11-02 11:49:49 +01:00
config.yaml Merge "Add keepalived-healthcheck-interval config option" 2020-09-04 15:07:56 +00:00
copyright Add missing copyright file 2012-12-07 08:39:53 +00:00
hardening.yaml Add hardening support 2016-03-31 15:01:54 +01:00
icon.svg Update charm icon 2017-08-02 18:03:36 +01:00
metadata.yaml Updates for 20.08 cycle start for groovy and libs 2020-06-02 14:34:07 +01:00
requirements.txt Sync libraries & common files prior to freeze 2020-09-26 18:36:44 +01:00
revision added postgresql 2014-03-28 12:02:09 +01:00
setup.cfg Add Python 3 Train unit tests 2019-07-30 10:18:50 -04:00
test-requirements.txt Sync libraries & common files prior to freeze 2020-09-26 18:36:44 +01:00
tox.ini Sync libraries & common files prior to freeze 2020-09-26 18:36:44 +01:00

README.md

Overview

Neutron provides flexible software defined networking (SDN) for OpenStack.

This charm is designed to be used in conjunction with the rest of the OpenStack related charms in the charm store to virtualize the network that Nova Compute instances plug into.

Neutron supports a rich plugin/extension framework for propriety networking solutions and supports (in core) Nicira NVP, NEC, Cisco and others...

See the upstream Neutron documentation for more details.

Usage

In order to use Neutron with OpenStack, you will need to deploy the nova-compute and nova-cloud-controller charms with the network-manager configuration set to 'Neutron':

nova-cloud-controller:
    network-manager: Neutron

This decision must be made prior to deploying OpenStack with Juju as Neutron is deployed baked into these charms from install onwards:

juju deploy nova-compute
juju deploy --config config.yaml nova-cloud-controller
juju deploy neutron-api
juju add-relation nova-compute nova-cloud-controller
juju add-relation neutron-api nova-cloud-controller

The Neutron Gateway can then be added to the deploying:

juju deploy neutron-gateway
juju add-relation neutron-gateway mysql
juju add-relation neutron-gateway rabbitmq-server
juju add-relation neutron-gateway nova-cloud-controller
juju add-relation neutron-gateway neutron-api

The gateway provides two key services; L3 network routing and DHCP services.

These are both required in a fully functional Neutron OpenStack deployment.

Configuration Options

Port Configuration

All network types (internal, external) are configured with bridge-mappings and data-port and the flat-network-providers configuration option of the neutron-api charm. Once deployed, you can configure the network specifics using neutron net-create.

If the device name is not consistent between hosts, you can specify the same bridge multiple times with MAC addresses instead of interface names. The charm will loop through the list and configure the first matching interface.

Basic configuration of a single external network, typically used as floating IP addresses combined with a GRE private network:

neutron-gateway:
    bridge-mappings:         physnet1:br-ex
    data-port:               br-ex:eth1
neutron-api:
    flat-network-providers:  physnet1

neutron net-create --provider:network_type flat \
    --provider:physical_network physnet1 --router:external=true \
    external
neutron router-gateway-set provider external

Alternative configuration with two networks, where the internal private network is directly connected to the gateway with public IP addresses but a floating IP address range is also offered.

neutron-gateway:
    bridge-mappings:         physnet1:br-data external:br-ex
    data-port:               br-data:eth1 br-ex:eth2
neutron-api:
    flat-network-providers:  physnet1 external

Alternative configuration with two external networks, one for public instance addresses and one for floating IP addresses. Both networks are on the same physical network connection (but they might be on different VLANs, that is configured later using neutron net-create).

neutron-gateway:
    bridge-mappings:         physnet1:br-data
    data-port:               br-data:eth1
neutron-api:
    flat-network-providers:  physnet1

neutron net-create --provider:network_type vlan \
    --provider:segmentation_id 400 \
    --provider:physical_network physnet1 --shared external
neutron net-create --provider:network_type vlan \
    --provider:segmentation_id 401 \
    --provider:physical_network physnet1 --shared --router:external=true \
    floating
neutron router-gateway-set provider floating

This replaces the previous system of using ext-port, which always created a bridge called br-ex for external networks which was used implicitly by external router interfaces.

Note: if the 'data-port' config item is set, then the 'ext-port' option is ignored. This is to prevent misconfiguration of the charm. A warning is logged and the unit is marked as blocked in order to indicate that the charm is misconfigured.

Instance MTU

When using Open vSwitch plugin with GRE tunnels default MTU of 1500 can cause packet fragmentation due to GRE overhead. One solution is to increase the MTU on physical hosts and network equipment. When this is not possible or practical the charm's instance-mtu option can be used to reduce instance MTU via DHCP.

juju set neutron-gateway instance-mtu=1400

Note that this option was added in Havana and will be ignored in older releases.