| Age | Commit message (Collapse) | Author |
|---|
|
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>
|
|
Signed-off-by: David Nyström <david.nystrom@enea.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>
|
|
The install and nice programs from coreutils are required by openvswitch.
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>
|
|
Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
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>
|
|
Signed-off-by: Ting Liu <b28495@freescale.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>
|
|
Signed-off-by: David Nyström <david.nystrom@enea.com>
|
|
Signed-off-by: David Nyström <david.nystrom@enea.com>
Reviewed-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: David Nyström <david.nystrom@enea.com>
Reviewed-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: David Nyström <david.nystrom@enea.com>
Reviewed-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
|
Signed-off-by: David Nyström <david.nystrom@enea.com>
Reviewed-by: Bruce Ashfield <bruce.ashfield@windriver.com>
|
