linux/meta-virtualization.git/recipes-networking/openvswitch/openvswitch.inc, branch hardknott-next

openvswitch: drop LSB bits

2019-09-15T03:51:16+00:00

openembedded-core commit fb064356af61 [Remove LSB support] dropped the 'lsb' recipe which caused openvswitch to throw a dependency fail for both sysvinit and systemd builds. LSB init functions for log_begin_msg, log_end_msg and others were being used. We now use the functions from ovs-lib which are part of OVS and supply the remaining ones directly. This allows us to regain the functionality and drop the dependency on 'lsb'. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: install ovs-systemd-reload

2019-08-30T04:29:15+00:00

Install ovs-systemd-reload as openvswitch.service uses it. openvswitch.service:ExecReload=/usr/share/openvswitch/scripts/ovs-systemd-reload Signed-off-by: Chen Qi Signed-off-by: Bruce Ashfield

openvswitch: do not use 'exit 1' to postpone to first boot

2018-09-05T20:25:03+00:00

Since `229f4e9 package.bbclass: add support for pkg_postinst_ontarget()' applied in oe-core, use pkg_postinst_ontarget to run postinst at first boot. Signed-off-by: Hongxu Jia Signed-off-by: Bruce Ashfield

openvswitch: uprev to v2.9.2

2018-06-04T03:26:54+00:00

This brings us up to date with the latest upstream release. I suspect there will be an upcoming release to add compatibility with DPDK v18.05 (the DPDK release is due out any day now) but getting this fairly large release bump out of the way first will facilitate any upcoming uprev. We are able to drop they python3 patches as they have been merged upstream. Some scripts which needed to be updated to use python3 disappeared, new ones appeared so the 'use python3' patches are updated accordingly. Beyond this the biggest change is related to the systemd unit files, the ovsdb-server has been updated upstream to be generated on the fly via the spec file, we mimic this in the install_prepend. We also add the various configuration files which the unit files source before launching the services. As usual this was tested against out typical usecases including usage in meta-overc. As well the ptests have been run and the results are no better or worse. Previous version: ERROR: 2332 tests were run, 21 failed unexpectedly. 3 tests were skipped. New version: ERROR: 2527 tests were run, 29 failed unexpectedly. 3 tests were skipped. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: Fix compile problems with i586-nlp

2017-08-29T12:43:11+00:00

If you have in your $CC from the compiler template any kind of directive which contains a comma character it is going to cause ovs to not build due to the macro expansion in the Makefile: CC = $(if $(C),env REAL_CC="'"$CC"'" CHECK="$(SPARSE) -I $(top_srcdir)/include/sparse $(SPARSEFLAGS) $(SPARSE_EXTRA_INCLUDES) " cgcc $(CGCCFLAGS),'"$CC" Put more simply: CC = $(if $(C), CONFIGURE_CC_DEFINITION, cgcc args CONFIGURE_CC_DEFINITION) The CONFIGURE_CC_DEFINITION for the i585-nlp definition had "-Wa,-momit-lock-prefix=yes". The comma there caused a strings to "break" in the wrong place in the $(if) macro and the build of recipe will fail with the error shown below: /bin/sh: -c: line 1: unexpected EOF while looking for matching `"' /bin/sh: -c: line 3: syntax error: unexpected end of file The solution is to transform the "-Wa," -> "-Xassembler ". Signed-off-by: Jason Wessel Signed-off-by: Bruce Ashfield

openvswitch: force PYTHON to python3

2017-08-22T15:25:28+00:00

Openvswitch has been created to search for and use both py2 and py3, with a preference for py2. There is no configure option to force the use of py3 only, and many of the scripts only use the value of PYTHON and not PYTHON3 (again there is a general preference for py2). In order to force this issue we set PYTHON to 'python3'. This isn't ideal but allows for the desired outcome without us having to carry changes against upstream OVS. During our py3 work with OVS this change was identified but for some reason was not included as part of the already merged changes. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: backport py3 fixups

2017-07-13T14:54:49+00:00

While attempting to get ovs to be built and run with py3 (completely free of py2) host contamination was found (builds on hosts without python-six installed would fail). It was also determined that pyc files were still being generated with py2 and not py3. This resulted in more work being done to achieve the desired results. This work was sent upstream and subsequently merged. Unfortunately this didn't make v2.7.1 and may not be available until the next major release, so here we backport these commits and adjust the recipe to get a clean py3 only build. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: switch to depending on python3

2017-06-21T18:25:14+00:00

As far as I can tell openvswitch has been updated to work with python3 as well as with python(2). Switch to depend on python3 and use python3 for associated scripts. For the most part openvswitch will bind at runtime to either py2 or py3 regardless of these changes, with these changes we just do a better job of setting up the dependencies to facilitate py3 bindings. The openvswitch autotests results are mostly identical before and after this switch (failures move from python3 to python(2) test cases as expected, with some exceptions see below). When running the autotests/ptest with python(2) vs python3 we see a slightly higher failure rate (334 failures vs. 284 failures). I do not believe this higher fail rate reflects actual errors in the runtime, rather the tests are not adapted to python3. At any rate like the rest of openvswitch it is fairly straightforward to hack the logic for autotests to be run using py2 as long as it is available in the image, so these changes don't prevent falling back to py2 for autotests. This should facilitate any debugging we need to do based on us switching to favor py3. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: add missing depends on coreutils-native

2017-03-13T13:25:01+00:00

I was getting the following error when building the latest master: ../git/build-aux/calculate-schema-cksum: cksum: not found ../git/build-aux/calculate-schema-cksum: cksum: not found Adding coreutils-native which supplies 'cksum' resolved this. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: fix build host contamination

2017-01-15T00:26:17+00:00

There is only a single PYTHON variable for configure and yet python is used for the build as well as scripts installed on the target. If we set a path in PYTHON as we had we end up using this same path during the build and since it isn't to the sysroot we end up with host contamination (as demonstrated by python failing to import 'six' on build hosts without python-six installed. The best approach is to set PYTHON to "python" when calling configure, ie. without a path. This will use 'python' from the path during build time and by ensuring all the installed scripts use '/usr/bin/env' we can ensure python will be found on the target when the scripts are run. Since 'six' is used as part of the build we have to ensure it is -native'ly buildable and we set all the required build and runtime dependencies. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield