Juju Charm - Open Virtual Network - Central components
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Frode Nordahl 9d04f1f487
Remove incorrect check and return from states_to_check
1 week ago
src Remove incorrect check and return from states_to_check 1 week ago
unit_tests Improve messaging for required relations 1 week ago
.gitignore Initial commit of charm skeleton 10 months ago
.gitreview Add gerrit and zuul bits 8 months ago
.stestr.conf Initial commit of charm skeleton 10 months ago
.travis.yml Fix remote clustering after moving local addr code to interface 8 months ago
.zuul.yaml Add gerrit and zuul bits 8 months ago
LICENSE Initial commit of charm skeleton 10 months ago
README.md Fix DB connection configuration for ``ovn-northd`` 8 months ago
rebuild Updates for 20.08 cycle start for groovy and libs 1 month ago
requirements.txt Enable Ussuri and Focal 4 months ago
test-requirements.txt Enable Ussuri and Focal 4 months ago
tox.ini Enable Ussuri and Focal 4 months ago

README.md

Overview

The ovn-central charm provides the Northbound and Southbound OVSDB Databases and the Open Virtual Network (OVN) central control daemon (ovn-northd). It is used in conjunction with either the ovn-chassis subordinate charm or the ovn-dedicated-chassis principle charm.

Note: The OVN charms are supported starting with OpenStack Train.

Usage

The OpenStack Base bundle gives an example of how you can deploy OpenStack and OVN with Vault to automate certificate lifecycle management.

OVN makes use of Public Key Infrastructure (PKI) to authenticate and authorize control plane communication. The charm therefore requires a Certificate Authority to be present in the model as represented by the certificates relation.

Refer to Open Virtual Network (OVN) in the OpenStack Charms Deployment Guide for details, including deployment steps.

Note: The ovn-central charm requires a minimum of three units to operate.

Network spaces

This charm supports the use of Juju network spaces.

By binding the ovsdb, ovsdb-cms and ovsdb-peer endpoints you can influence which interface will be used for communication with consumers of the Southbound DB, Cloud Management Systems (CMS) and cluster internal communication.

juju deploy -n 3 --series focal \
    --bind "''=oam-space ovsdb=data-space" \
    ovn-central

OVN RBAC and securing the OVN services

The charm enables RBAC in the OVN Southbound database by default. The RBAC feature enforces authorization of individual chassis connecting to the database, and also restricts database operations.

In the event of an individual chassis being compromised, RBAC will make it more difficult to leverage database access for compromising other parts of the network.

Note: Due to how RBAC is implemented in ovsdb-server the charm opens up a separate listener at port 16642 for connections from ovn-northd.

The charm automatically enables the firewall and will allow traffic from its cluster peers to port 6641, 6643, 6644 and 16642. CMS clients will be allowed to talk to port 6641.

Anyone will be allowed to connect to port 6642.

Bugs

Please report bugs on Launchpad.

For general questions please refer to the OpenStack Charm Guide.