[Bug 2076312] [NEW] The ovn-ctl script supports only one remote for joining cluster

[Frode Nordahl]

Public bug reported:

Depending on arguments, the `ovn-ctl` script can take care of clustered
database life cycle operations such as creating and joining a cluster.

Indication to whether to create or join a cluster is provided to `ovn-
ctl` through the `--db-nb-cluster-remote-addr` and `--db-sb-cluster-
remote-addr` arguments.  When empty, and other prerequisites are met, a
new cluster will be created. When containing an IP address, an attempt
will be made to join an existing cluster.

The problem is that only a single IP address is accepted/provided.  A
cluster typically consists of an odd number of nodes, 3 or more.  Now
imagine if the one member that happens to be provided in the above
mentioned argument is down at the time the join operation is attempted?

Under the hood, `ovn-ctl` makes use of `ovsdb-tool join-cluster` to
prepare the on-disk database file for consumption by `ovsdb-server`, and
the `join-cluster` command accepts multiple remotes.

Downstream tooling has had to work around this [0], and it would be nice
to get proper support for joining clusters using multiple remotes in the
upstream scripts.

0: https://opendev.org/x/charm-ovn-
central/src/commit/74f2aa702cf11c597d74a915a5e8d626d2241912/src/lib/charm/openstack/ovn_central.py#L500-L540

** Affects: ovn (Ubuntu)
     Importance: Wishlist
         Status: Triaged


** Tags: good-first-bug

** Changed in: ovn (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ovn (Ubuntu)
       Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to ovn in Ubuntu.
https://bugs.launchpad.net/bugs/2076312

Title:
  The ovn-ctl script supports only one remote for joining cluster

Status in ovn package in Ubuntu:
  Triaged

Bug description:
  Depending on arguments, the `ovn-ctl` script can take care of
  clustered database life cycle operations such as creating and joining
  a cluster.

  Indication to whether to create or join a cluster is provided to `ovn-
  ctl` through the `--db-nb-cluster-remote-addr` and `--db-sb-cluster-
  remote-addr` arguments.  When empty, and other prerequisites are met,
  a new cluster will be created. When containing an IP address, an
  attempt will be made to join an existing cluster.

  The problem is that only a single IP address is accepted/provided.  A
  cluster typically consists of an odd number of nodes, 3 or more.  Now
  imagine if the one member that happens to be provided in the above
  mentioned argument is down at the time the join operation is
  attempted?

  Under the hood, `ovn-ctl` makes use of `ovsdb-tool join-cluster` to
  prepare the on-disk database file for consumption by `ovsdb-server`,
  and the `join-cluster` command accepts multiple remotes.

  Downstream tooling has had to work around this [0], and it would be
  nice to get proper support for joining clusters using multiple remotes
  in the upstream scripts.

  0: https://opendev.org/x/charm-ovn-
  central/src/commit/74f2aa702cf11c597d74a915a5e8d626d2241912/src/lib/charm/openstack/ovn_central.py#L500-L540

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ovn/+bug/2076312/+subscriptions