The payload containers sb, nb and northd have a shared db dir. The join wrapper skips the join command if it detects an existing ovn db. But the regex used by the join command is not specific enough. So the sb would skip the join if the nb db was present. This patch tightens the regex so that the join wrappers look for their own db. Change-Id: I20b139244664a5218c236ec28756fefd617cc668
ovn-central-k8s is an operator to manage the OVN central services (northd, ovsdb-nb, ovsdb-sb) on a Kubernetes based environment.
ovn-central-k8s is deployed using below command:
juju deploy ovn-central-k8s ovn-central
Now connect the ovn-central operator to Vault to generate certificates for secure authentication and communication:
juju relate vault:certificates ovn-central:certificates
This section covers common and/or important configuration options. See file
config.yaml for the full list of options, along with their descriptions and
default values. See the Juju documentation for details
on configuring applications.
This section covers Juju actions supported by the charm.
Actions allow specific operations to be performed on a per-unit basis. To
display action descriptions run
juju actions ovn-central. If the charm is not
deployed then see file
ovn-central-k8s requires the following relations:
certificates: To retrieve generated certificates from vault
ovn-central-k8s provides the following relations:
ovsdb-cms: Used by Neutron to get ovn-central IPs.
The charm by default uses following images:
`registry.jujucharms.com/charm/kau2b145zhaeuj5ly4w4m30qiq8qzspf93tnd/ovn-northd-image` `registry.jujucharms.com/charm/kau2b145zhaeuj5ly4w4m30qiq8qzspf93tnd/ovn-nb-db-server-image` `registry.jujucharms.com/charm/kau2b145zhaeuj5ly4w4m30qiq8qzspf93tnd/ovn-sb-db-server-image`
Please report bugs on Launchpad.