
Enable the ovsdb-subordinate interface to provide chassis certificates to principal. This is useful for related charms providing payloads that expect direct communication with the OVN databases. While a principal and subordinate charm executes in the same environment, the payload usually execute under different service accounts and as such it is impractical and may be less secure to attempt to provide direct on-disk file access. Related-Bug: #1918271 Change-Id: I867817dfa7dd43cdb9035af87cbac3371dff13a5
Overview
This repository contains a set of similar interfaces with common code broken out to a separate module.
This interface facilitates a provider charm to publish connection properties of a OVSDB and a requirer charm to consume a remote OVSDB.
Usage
No explicit handler is required to consume this interface in charms that consume this interface.
In addittion to the states automatically set based on relation data by
charms.reactive.Endpoint
, the interface provides the
ovsdb.available
state.
metadata
To consume this interface in your charm or layer, add the following to layer.yaml
:
includes: ['interface:ovsdb']
and add a provider or requires interface of type ovsdb
to your charm or
layers metadata.yaml
:
requires:
ovsdb:
interface: ovsdb
Bugs
Please report bugs on Launchpad.
For development questions please refer to the OpenStack Charm Guide.