[ovs-build] Passed: booxter/ovn#39 (multi-bridge - 36ff2eb)

Travis CI builds at travis-ci.com
Wed Jul 29 03:06:45 UTC 2020


Build Update for booxter/ovn
-------------------------------------

Build: #39
Status: Passed

Duration: 18 mins and 2 secs
Commit: 36ff2eb (multi-bridge)
Author: Ihar Hrachyshka
Message: Allow to run multiple controllers on the same machine

User stories:
1) NFV: an admin wants to run two separate instances of OVN controller
   using the same database but configuring ports on different bridges.
   Some of these bridges may use DPDK while others may not.

2) Parallel OVN instances: an admin wants to run two separate
   instances of OVN controller using different databases. The
   instances are completely independent and serve different consumers.
   For example, the same machine runs both OpenStack and OpenShift
   stacks, each running its own separate OVN stack.

To serve these use cases, several features should be added to
ovn-controller:

- use different database configuration for multiple controllers;
- customize chassis name used by controller.

=====

For each of the following database configuration options, their
extended chassis specific counterparts are introduced:

external_ids:ovn-remote -> external_ids:ovn-remote-<chassis-name>=
external_ids:ovn-encap-type -> external_ids:ovn-encap-type-<chassis-name>=
external_ids:ovn-encap-ip -> external_ids:ovn-encap-ip-<chassis-name>=
external_ids:ovn-bridge -> external_ids:ovn-bridge-<chassis-name>=

Priority wise, <chassis-name> specific options take precedence.

=====

For system-id,

You can now pass intended chassis name via CLI argument:

  $ ovn-controller ... -n <chassis_name>

Alternatively, you can configure a chassis name by putting it into the
${ovs_sysconfdir}/system-id file before running the controller.

The latter option may be more useful in container environment where
the same image may be reused for multiple controller instances, where
ovs_sysconfigdir/system-id is a volume mounted into this generic
image.

Priority wise, this is the order in which different means to configure
the chassis name are used:

- external_ids:system-id= ovsdb option;
- ${ovs_sysconfdir}/system-id file;
- ovn-controller ... -n <chassis_name> CLI argument.

Signed-off-by: Ihar Hrachyshka <ihrachys at redhat.com>

View the changeset: https://github.com/booxter/ovn/compare/0970d82b1b18...36ff2ebfebd0

View the full build log and details: https://travis-ci.com/github/booxter/ovn/builds/177545890?utm_medium=notification&utm_source=email

--

You can unsubscribe from build emails from the booxter/ovn repository going to https://travis-ci.com/account/preferences/unsubscribe?repository=12736311&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.com/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-build/attachments/20200729/f36638ca/attachment-0001.html>


More information about the build mailing list