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>
Finding the libprotobuf.* incorrectly if the host have pkgconfig
Signed-off-by: Jianchuan Wang <jianchuan.wang@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>
V1.1.4 includes a fix for CVE-2015-1335:
lxc-start in lxc before 1.0.8 and 1.1.x before 1.1.4 allows local container
administrators to escape AppArmor confinement via a symlink attack on a (1)
mount target or (2) bind mount source.
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2015-1335
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Some of the cgo variables were pointing to host paths and not target
Fix install rules - binaries can be installed to a subdirectory.
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Since we need go 1.3 to co-exist with later versions (ie 1.4),
package go-cross_1.3 as go-cross-1.3_1.3.
go 1.3 will be installed to a different path than go-cross, this requires
go packages needing go 1.3 to set its PATH to:
export PATH=${STAGING_BINDIR_NATIVE}/${HOST_SYS}/go-1.3:$PATH
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
submitted to upstream https://github.com/errordeveloper/oe-meta-go
go-cross: set alignment for the .rel.plt section on 32-bit architectures
This patch is cherry picked from golang's upstream, and this patch will
fix the package of etcd's following build error:
ERROR: debugedit failed with exit code 256 (cmd was 'bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit' -b 'bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi' -d '/usr/src/debug' -i -l 'bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/etcd/git-r0/debugsources.list' 'bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/etcd/git-r0/package/usr/bin/etcd'):
bitbake_build/tmp/sysroots/x86_64-linux/usr/lib/rpm/bin/debugedit: elf_update: invalid section alignment
ERROR: Function failed: split_and_strip_files
ERROR: Logfile of failure stored in: bitbake_build/tmp/work/cortexa7t2hf-vfp-neon-wrs-linux-gnueabi/etcd/git-r0/temp/do_package/log.do_package.109414
ERROR: Task 12 (layers/meta-overc/meta-pod/recipes-connectivity/etcd/etcd_git.bb, do_package) failed with exit code '1'
Signed-off-by: fupan li <fupan.li@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
submitted to upstream https://github.com/errordeveloper/oe-meta-go
go-cross: fix the building failed for quark bsp
Quark used i586 architecture, and golang dealt intel 32bit
architecture as 386, so export GOARCH = "386" when the TARGET_ARCH
is i586 to support quark bsp.
Signed-off-by: fupan li <fupan.li@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
submitted to upstream https://github.com/errordeveloper/oe-meta-go
go-cross: fix the bug of cross building error
When a package's recipe inherit "cross" bbclass, its CC and CXX are defined
as the host native gcc and g++ instead of the host cross toolchain, fot this
case, CC_FOR_TARGET and CXX_FOR_TARGET should be defined the same with CC and
CXX, instead they are should be define as host cross toolchain's CC and CXX,
otherwise, it will build failed for target arm architecture as below:
| # Building packages and commands for linux/arm.
| + CC='gcc '
| + bitbake_build/tmp/work/x86_64-wrs-linux-gnueabi/go-cross/1.4-r0/go/pkg/tool/linux_amd64/go_bootstrap install -ccflags '' -gcflags '' -ldflags '' -v std
| runtime
| errors
| sync/atomic
| unicode
| unicode/utf8
| math
| sort
| encoding
| unicode/utf16
| container/list
| crypto/subtle
| runtime/cgo
| container/ring
| image/color
| runtime/race
| # runtime/cgo
| gcc: error: unrecognized command line option '-marm'
Signed-off-by: fupan li <fupan.li@windriver.com>
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The current version of docker (1.6.2) requires go 1.3
See go 1.4 sqlite issue:
https://github.com/docker/docker/issues/9649
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Add the protobuf's pkgconfig path into PKG_CONFIG_PATH
so that pkg-config can find the protoc from sysroot in the configure process.
And don't conflict even if installing the protobuf in the localhost.
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Problem: Logs are nice in that they report the source file,
routine, and line number where an issue occurs. But the
file is printed as the absolute filename. Users do not
need to see a long spew of path directory names where the package
just happened to have been built on some host somewhere. It
can be confusing to anyone other than the developer.
Solution: Introduce a configure option to chop off all leading
directories so that just the source filename ie. basename is printed.
[ Upstream status: Not needed. These absolute filenames are a
consequence of poky/bitbake feeding the absolute filenames to
the compiler. If you build lxc outside of poky/bitbake, just
the basenames are fed to the compiler. ]
Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
We build libvirt without support for sd_notify (dbus) therefor we have
to run libvirtd as a 'forking daemon' (per commit
055744cdbc we pass --daemon)
We need to update the systemd service file to reflect this such that
the libvirtd.service can be properly stopped. If we ever enable
sd_notify support in libvirt we can revert back to using the 'notify'
systemd type. Without this change libvirtd continue to run even if the
stop command is issued, subsequent attempts to start the service will
fail.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The release notes is http://libvirt.org/news.html
Signed-off-by: Roy Li <rongqing.li@windriver.com>
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
When systemd starts libvirtd we want to make sure we pass the correct
arguments to run the daemon. If we fail to do so the libvirtd service
will restart about once a minute and not allow for VMs to properly be
instantiated. libvirtd now runs with the same args as when we use
sysvinit.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
While testing libvirt with the new systemd init I found that the
libvirt-guests service was failing to run since the libvirt-guests.sh
script was not where it was expected. If we are building for systemd
init system use the default installation location which is used
upstream for the libvirt-guests.sh script.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Commit d114a62dd8 [libvirt: kill
update-rc.d when not using sysvinit] resulted in libvirt services not
starting automatically at boot when using systemd. The upstream
libvirt package already has the necessary systemd service files so it
is just a matter of activating them via the '--with-init-script'
configure option and making the recipe use these.
We always set '--with-init-script' to 'systemd' regardless of
the systemd vs sysvinit DISTRO_FLAG since our sysvinit scripts are
external and thus not affected by this setting when building for
sysvinit.
Both sysvinit and systemd packages will be libvirt-libvirtd, the
bbclasses ensure that only the files for one init system will exist in
the package, so this 'overloading' is acceptable.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
We have had a persistent issue of contention with multiple instances
of dnsmasq. When libvirtd is started it will attempt and fail to
create virbr0 that includes a dnsmasq binding (dnsmasq complains that
the port is already in use). The root cause being that the base
dnsmasq configuration uses the 'default' binding, meaning it will be
greedy and bind to all available interfaces, along with any new
interfaces that appear. This prevents any new instances of dnsmasq to
fail. By changing the base dnsmasq configuration to use 'bind-dynamic'
we will be able to create new interfaces and if we want to attach a
new dnsmasq instance for the new interface we can, without contention.
Overall this change should not change the default behavior (other then
fixing the contention) as the 'bind-dynamic' mode will allow the base
config to attach to new interfaces which are not be bound to new
dnsmasq instances.
Removing dnsmasq_exclude_virbr.conf which was a previous (partial)
attempt that was made to resolve this issue.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Uprev to 1.1.3
Remove Generate-lxc-restore-net-properly.patch since related code
has been removed.
Signed-off-by: He Zhe <zhe.he@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Grasp withval for libcap-ng in configure.ac.
Signed-off-by: Ming Liu <ming.liu@windriver.com>
Signed-off-by: Jianchuan Wang <jianchuan.wang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Using a wildcard will simplify things when using meta-virtualization
against different yocto or oe branches and prevent having to make
future updates to keep in step with package uprevs.
The changes found within these bbappend tend to be generic and
non-version specific, thus safe for 'porting' via wildcard.
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Fixes the following QA warning:
WARNING: QA Issue: libvirt-ptest rdepends on libtasn1, but it isn't a build dependency? [build-deps]
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Configure searches for and sets XSLTPROC and will not get a proper
value unless we have made sure libxslt-native is built prior to
libvirt. So we need to add it as a DEPENDS. Failing to do this we
could end up with libvirt configuring before libxslt-native has built
and installed xlstproc in the -native sysroot, resulting potential
host contamination or in a potential build error:
cat: acl.html.tmp: No such file or directory
Makefile:2215: recipe for target 'acl.html' failed
(xsltproc is used in the generation of acl.html.tmp)
Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The networking configuration that is part of the lxc-setup package is
not appropriate for all use cases, or init systems.
To avoid having this configuration be pulled in by default, we create
an empty -networking package that handles the configuration. Images
can enable this step by including lxc-networking in the install package
list.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
These files are now installed post 4.5.0 and as such they need to be
placed into appropriate packages.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The xen-fsimage package contains shared libraries which depend on the
shared libraries from libext2fs so there needs to be a RDEPEND set.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The xen-mfndump utility was broken out into xen-xen-mfndump which is
clearly a typo for xen-mfndump but the xen.inc file which is also used
for 4.5.0 places this binary into xen-misc so remove these lines and let
it go into xen-misc.
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>
Update the SRC_URI to the author's new site where the hosted files match
the existing md5sum and sha256sum.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
With the recent python-simplejson:upgrade 3.6.2->3.7.3, docker-registry
was broken due to unsatisfied dependencies. The docker-registry builds and
passes basic testing with 3.7.3 (verified by jason.wessel@windriver.com),
updating the dependency requirement to >= 3.6.2
Signed-off-by: Amy Fong <amy.fong@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
docbook2man fails to build the man pages in poky
due to missing the ancient Davenport 3.0 DTD.
Poky meta has the Oasis 3.1 version so upgrade
to use that instead.
Signed-off-by: Jim Somerville <Jim.Somerville@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* Fixes a dependency on a nonexistent initscripts-functions package.
Signed-off-by: Noor Ahsan <noor_ahsan@mentor.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
This layer depends on openembedded-core and meta-openembedded so
recommend the actual URLs and not the obsolete ones.
Signed-off-by: Doug Goldstein <cardoe@cardoe.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
