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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Pick up the latest features, including compatability with the latest
DPDK as well as bug fixes.
The patches for TARGET_PYTHON and TARGET_PERL can be dropped as
configure now lets us pass these in the env (which we set).
The systemd service files have been shuffled some upstream and we make
adjustments in the recipe to accomodate these. The sysvinit scripts
remain functional as they are.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Upstream commit a489b16854b5 [conntrack: New userspace connection
tracker.] classified new files under existing licenses in COPYING,
resulting in no change to the overall licenses but requires a new
checksum.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
netns is a runc hook for setting up simple bridge networking within containers.
See README.md (or https://github.com/jfrazelle/netns/blob/master/README.md) for
instructions on how to use netns.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
error: file /var/run from install of openvswitch-2.1.3-r0.x86_64
conflicts with file from package base-files-3.0.14-r89.ubinux_x86_64
Signed-off-by: Dai Caiyun <daicy.fnst@cn.fujitsu.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Set PYTHON to TARGET_PYTHON for running on target
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
- 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 <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Uprev to git rev bb429e09f7783f1ba23ac0682ed9edf424f0cfbb (based on 2.5.0)
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <rongqing.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
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 <bruce.ashfield@windriver.com>
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 <bruce.ashfield@windriver.com>
The dpdk recipes are not commonly available, so we shouldn't have
dpdk in the PACKAGECONFIG by default.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Add openvswitch.inc, removing common parts out of openvswitch*.bb
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This revision corresponds to git rev 1667bb34988358aaf1c92d0d21fad4b1c8698780
(based on 2.3.90)
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
v2.1.3 is listed upstream as "contains only bug fixes for the 2.1.2
release". The only update to the recipe is updated checksums.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
meta-networking layer includes a newer version (0.2.3) of netcf recipe.
Since meta-virtualization layer depends on meta-oe/meta-networking layer,
we can avoid duplication by removing this recipe.
Signed-off-by: Maxin B. John <maxin.john@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Updating to the latest OVS 2.x. Only minor patch refreshes required, and
no regressions were found during sanity testing.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
For now adding netcf to the list of "brokensep" packages. The install
phase fails when autotools split directories are used, so we inherit
brokensep to get things building again.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Install openvswitch test suite and run it as ptest.
Signed-off-by: Radu Patriu <radu.patriu@enea.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The TARGET_PYTHON variable is used for script
substitutions to ensure the scripts will be able to properly execute
if the target system has a different path for the python.
Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
openvswitch requires pkgconfig or you may see an error:
configure.ac:53: error: Please install pkg-config.
during configure.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Bitbake was properly detecting a dependency on libpcap but since it
was not an explicit RDEPENDS the libpcap package was not being built
in all cases which had the potential to break rootfs image building.
The obvious solution was to add libpcap to the RDEPENDS but looking
upstream it was found that they have removed the use of this library
for all but FreeBSD since for other systems it is unused. So using the
upstream patch here eliminates the dependency and in turn the issue
described above.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
right or wrong, we shouldn't have a mix of tabs or spaces, so in this
cleanup, we'll make them all tabs.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
We update to the latest 2.0 OVS, but we'll keep the existed (better tested)
version around until this proves to be stable.
As part of this update the openvswitch-add-target-perl-handling.patch has
been refreshed, since one of the scripts it patched is no longer part
of the package.
Finally, we drop PR from the recipe as part of the larger move to PRSERVER
based revision numbers.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
An updated version of the openflow recipe has been added to meta-openembedded
in the meta-networking layer.
commit: 37660c [openflow: import and tweak] in git://git.openembedded.org/meta-openembedded
So we can safely remove the meta-virt variant of this recipe.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Make sure openvswitch has all the runtime dependencies defined.
Without e.g. sed, an installer may calculate dependencies and order
packages based on the deps, which may install openvswitch before sed.
This would result in an install failure, when the post install step
calls ovs-pki, which uses sed.
Signed-off-by: Paul Barrette <paul.barrette@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
In a systemd based build, /var/run is translated to /run. Since ovs doesn't
currently package this directory, it results in a QA error. Adding it to the
main ovs package fixes the QA issue and provides the proper runtime support.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
RPM doesn't guarantee the order in which postinstalls are ran.
Added code to ensure the pki directory is initialized.
Signed-off-by: Mihai Prica <mihai.prica@intel.com>
Openvswitch is built with the assumption that the PYTHON and PERL
variables are common between the host and target. This can result in
improper paths used for script substitutions which in turn causes
scripts which will fail to run on the target and the generated
packages to have improper REQUIRES, making them impossible to
install. These are usually not an issue since python and perl are
found in the same location on the host and target, but there is no
guarantee of this so the possibility of failure exists. By explicitly
defining the location of the python and perl on the target we can
avoid these assumptions and possibility of failure.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The OVS 1.10 integration has soaked for long enough to be stable, so
we can remove the old 1.9 recipe.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
-Uprev to 1.10
-removed vswitch_test.sh
-added openvswitch.txt.
Signed-off-by: Paul Barrette <paul.barrette@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Update recipe to version 1.9.0. Refer to docs/vswitch_test.sh
for a sanity test. This package will not be functional unless
the openvswitch kernel module is configured into the kernel.
Signed-off-by: Joe Slater <jslater@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
When I define the bridge, I get below error
root@intel_5500_server:~# ovs-vsctl add-br ovsbr0
Jan 25 17:34:07|00002|stream_unix|ERR|/tmp/stream-unix.1487.0: connection to /var/run/openvswitch/db.sock
failed: No such file or directory
........
........
This is because openvswitch damon isn't running,so we'd better start it at
the boot time. The split-package ${PN}-switch ${PN}-controller provide us
to start necessary daemon with update-rc.d so we add them to the RDEPENDS.
Since openvswitch depends on openvswtich kernel module, so auto load the
kernel module too.
Signed-off-by: Lei Yang <lei.yang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
