a1070dd259
We provide our own systemd service files with this change. To be able to pass the correct command line arguments to ``ovn-nortrhd`` we need to create a ``/etc/openvswitch/ovn-northd-db-params.conf`` which has the side effect of profoundly changing the behaviour of the ``ovn-ctl`` tool that the ``ovn-central`` init script makes use of. The systemd service files should be upstreamed. Also fix the ``ovn-remote`` setting in the local OVSDB, handy for executing management tools on the units. Update documentation. Depends-On: I86b530db330d59c7e31d75b05aeaa99415b59324 Change-Id: I0cc74e2fd45e13d8b3e279ebb3de73117aac3e76
Overview
This charm provides the Northbound and Southbound OVSDB Databases and the
Open Virtual Network (OVN) central control daemon (ovn-northd).
Note
: The OVN charms are considered preview charms.
Usage
OVN makes use of Public Key Infrastructure (PKI) to authenticate and authorize
control plane communication. The charm requires a Certificate Authority to be
present in the model as represented by the certificates relation.
There is a OVN overlay bundle for use in conjunction with the OpenStack Base bundle which give an example of how you can automate certificate lifecycle management with the help from Vault.
Please refer to the Open Virtual Network section of the OpenStack Charms Deployment Guide for information about deploying OVN with OpenStack.
Network Spaces support
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 ovn-central --bind "''=oam-space ovsdb=data-space"
Bugs
Please report bugs on Launchpad.
For general questions please refer to the OpenStack Charm Guide.