[ovs-git] [ovn-org/ovn] 9ea1f0: Include OVS as a git submodule.

Mark Michelson noreply at github.com
Tue Feb 9 18:47:59 UTC 2021


  Branch: refs/heads/master
  Home:   https://github.com/ovn-org/ovn
  Commit: 9ea1f092d2ed6b90bc8c444a2c73f4e0fceebeff
      https://github.com/ovn-org/ovn/commit/9ea1f092d2ed6b90bc8c444a2c73f4e0fceebeff
  Author: Mark Michelson <mmichels at redhat.com>
  Date:   2021-02-09 (Tue, 09 Feb 2021)

  Changed paths:
    M .ci/linux-build.sh
    M .ci/osx-build.sh
    M .github/workflows/test.yml
    A .gitmodules
    M Documentation/intro/install/general.rst
    M Makefile.am
    M acinclude.m4
    M build-aux/initial-tab-whitelist
    A ovs
    M utilities/checkpatch.py

  Log Message:
  -----------
  Include OVS as a git submodule.

OVN developers have had isssues with the current method by which OVS
source code is used by OVN.

* There is no way to record the minimum commit/version of OVS to use
  when compiling OVN.
* When debugging issues, bisecting OVN commits may also requires
  simultaneously changing OVS commits. This makes for multiple moving
  targets to try to track.
* Performance improvements made to OVS libraries and OVSDB may benefit
  OVN. However, there's no way to encourage the use of the improved OVS
  source.

By using a submodule, it allows for OVN to record a specific commit of
OVS that is expected to be used.


  Commit: c5bd2ef3a5fdfd14f3830fcd966cd04641c60601
      https://github.com/ovn-org/ovn/commit/c5bd2ef3a5fdfd14f3830fcd966cd04641c60601
  Author: Mark Michelson <mmichels at redhat.com>
  Date:   2021-02-09 (Tue, 09 Feb 2021)

  Changed paths:
    M .github/workflows/test.yml

  Log Message:
  -----------
  Add weekly CI job that uses OVS master.


Compare: https://github.com/ovn-org/ovn/compare/022ea339c8e2...c5bd2ef3a5fd


More information about the git mailing list