linux/meta-virtualization.git/recipes-networking/openvswitch, branch krogoth

openvswitch: ptest: Fix python path

2016-04-19T19:51:17+00:00

Set PYTHON to TARGET_PYTHON for running on target Signed-off-by: He Zhe Signed-off-by: Bruce Ashfield

openvswitch: Fix ptest for v2.5

2016-04-05T15:12:37+00:00

- Copy certain files from srcdir since it has been different from build directory. - Copy more necessary files for new added test cases. - Modify config files for running on target. - Add necessary RDEPENDS Signed-off-by: He Zhe Signed-off-by: Bruce Ashfield

openvswitch: Uprev to latest version 2.5.0

2016-03-31T13:15:25+00:00

Uprev to git rev bb429e09f7783f1ba23ac0682ed9edf424f0cfbb (based on 2.5.0) Signed-off-by: He Zhe Signed-off-by: Bruce Ashfield

openvswitch: enable systemd support

2015-12-15T13:47:25+00:00

Make the necessary updates to get openvswitch to be compatible with systemd. Up to now if you built a systemd supported image openvswitch was using the systemd sysvinit wrappers, by making these changes we now support systemd natively. Note that there is no equivalent systemd support for openvswitch-testcontroller. Following the lead of upstream this is not something that should be run by the init system. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: rename openvswitch-controller

2015-12-15T13:47:25+00:00

As of version 2.4.0 openvswitch-controller has been renamed to openvswitch-testcontroller. This was documented in the upstream 'NEWS': - test-controller has been renamed ovs-testcontroller at request of users who find it useful for testing basic OpenFlow setups. It is still not a necessary or desirable part of most Open vSwitch deployments. Our initscripts and such have continued to reference the old name despite the application name name changing and so openvswitch-controller packaging has been broken for some time now. We rename the openvswitch-controller package to reflect the upstream name change and apply this name change throughout. We also drop the RDEPENDS as the upstream comments also indicate that this package is not needed for a normal openvswitch deployment. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: drop version 1.10.0 and 2.1.3

2015-12-15T13:47:25+00:00

There are some changes that we need to make in the .inc file to properly support more recent releases of openvswitch. These changes are not compatible with these older versions of openvswitch, so rather than make accommodations in the .inc file to continue to support this version we will simply drop them. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

openvswitch: Uprev to latest stable version 2.4.0

2015-11-03T09:51:05+00:00

Uprev to git rev bb429e09f7783f1ba23ac0682ed9edf424f0cfbb (based on 2.4.0) - Remove non_reproducible_builds_cleanup.patch since it have been in the version 2.4.0. Signed-off-by: Jianchuan Wang Signed-off-by: Bruce Ashfield

openvsitch: set CONFIGUREOPT_DEPTRACK to empty

2015-08-26T12:52:07+00:00

compilation failed since the needed dirs maybe not created when make ".in" target, fix it by creating the needed dirs before, but mainstream thinks the needed dirs should be created when do configuration. at last, find CONFIGUREOPT_DEPTRACK disable the creation, so empty it http://openvswitch.org/pipermail/dev/2015-August/059189.html set CONFIGUREOPT_DEPTRACK to empty, is lower effective, but harmless, and can fix the parallel building issue; see oe-core 970e0ae6108[autotools: Disable dependency tracking Signed-off-by: Roy Li Signed-off-by: Bruce Ashfield

openvswitch: add bash rdepends

2015-02-23T04:48:09+00:00

Fix the following QA warning: WARNING: QA Issue: openvswitch requires /bin/bash, but no providers in its RDEPENDS [file-rdeps] Signed-off-by: Bruce Ashfield

openvswitch: don't pass kernel source or build artifacts

2015-02-21T04:33:20+00:00

Like the previous versions of OVS, we rely on the virtual/kernel provider to build the appropriate modules. Passing the --with-linux and --with-linux-source breaks builds when the split source/build/build-artifacts are not as expected (and modules are attempted to be built from the wrong directory). To fix this, we simply don't enable those options, and all is well. Signed-off-by: Bruce Ashfield