The patch configures the LXC recipe to include configuration examples
or containers in the default package - lxc, not in the documentation
one - lxc-doc.
By default, bitbake will split a specific package into multiple sections,
based on meaning - binaries, libraries, documentation, configs, etc. The
sections will then be assembled into individual packages, such as e.g lxc,
lxc-doc, lxc-dbg and so on. The packages are mutually exclusive with
respect to the sections they contain.
LXC installation provides several example configuration files for various
usage scenarios. The twist is that LXC build scripts place these config
examples in a relative path that is identified by bitbake as belonging to
documentation. This patch places these configuration files in the main
package, where they normally belong.
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@freescale.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
The provided patch makes a modification to the LXC busybox template (the
template that creates a minimal container with Busybox).
This type of container will start the udhcpc service - the DHCP client - on
init. For an embedded Linux image, we might assume that the majority of
containers will have manual / static networking configuration on start.
Considering this, starting the udhcpc service by default is useless, since
the service will then has to be killed. The containers that use DHCP for
networking can start udhcpc after container boot, or alter the busybox
template locally to do so by default.
The patch deactivates the default start of the DHCP client on a Busybox
container init.
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@freescale.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Introducing the LXC 0.9.0 recipe.
Maintainer log for intermediate versions since LXC 0.8.0. This only contains
the major differences between versions. You may find the complete log on the
SourceForge LXC devel mailing list [1].
0.9.0.alpha1:
- Introduction of the new liblxc API
- Python bindings
- New tools:
- lxc-device
- lxc-start-ephemeral
- python version of lxc-ls
- lxc.autodev support
- oracle template
- reworked lxc-attach
- /etc/lxc/lxc.conf configuration
- Switch to new docbook
- A lot of other improvements, new features and bugfixes
0.9.0.alpha2: bug fix for issue with 0.9.0.alpha1 - no significant changes
0.9.0.alpha3:
- Android support
- New lua binding
- User namespace support
- Oracle template
- Manpage updates
- POSIX shell support for most scripts
- Improved systemd support
- Various API improvements
- Logging improvements
0.9.0.rc1:
- Addition of -P option to all executables (to specify lxcpath)
- Rework of the cgroup handling code
- Rework of lxc-attach for userns
- Updates to the alpine, archlinux, opensuse, oracle and ubuntu
templates. Removal of the lenny template.
- Introduction of a new lxc.stopsignal option
- Introduction of a new lxc.kmsg option
- Various userns improvements
- New --host option in lxc-ps
- Introduction of a few examples lxc hooks
- Support for nested containers in lxc-ls
- Introduction of get_version in the C API.
- And a variety of bugfixes
0.9.0:
Feature changes include:
- Support for ephemeral containers in lxc-clone
- --clear-env/--keep-env support in lxc-attach
- -n option to lxc-start-ephemeral
Everything else is bugfixes on top of rc1.
Tests done by maintainers:
- Test build on my machine (up to date Ubuntu 13.04)
- Test build on Launchpad (Ubuntu 12.04, 12.10 and 13.04)
- Test build on an armhf board running Ubuntu 13.04
- Test build for Android cross-compiling on my laptop
- Ran our test suite on the x86 binaries
- Ran a quick test (start/stop/info/wait) on Android
- Tested the API and tools on ARM
- Rebuilt all my local templates (~20 containers) on a variety of
architectures (i386, amd64, armel and armhf)
[1] https://lists.sourceforge.net/lists/listinfo/lxc-develIntroducing the LXC 0.9.0 recipe.
Signed-off-by: Bogdan Purcareata <bogdan.purcareata@freescale.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
If the host machine has dtrace, or systemtap development libraries
installed, libvirt will detect their headers and enable dtrace probe
support.
But since we don't have a dependency on dtrace, the build will fail
with:
| compilation terminated.
| In file included from ./internal.h:297:0,
| from util/bitmap.h:27,
| from util/bitmap.c:33:
| ./libvirt_probes.h:9:21: fatal error: sys/sdt.h: No such file or directory
There are three problems:
- a host contamination issue
- dtrace/probes being automatically enabled
- a lack of integrated systemtap/dtrace solution
Fixing any of the above will make the problem go away, to fix currently
broken builds, we can fix the problem by adding dtrace as a PACKAGECONFIG
option, and leaving it disabled. This change doesn't add a dtrace/systemtap
dependency to the config entry, since they haven't been confirmed at this
point.
In the future, we should either fix the host contamination or do a full
systemtap/dtrae integration, but for now, simply disabling it is the
best choice.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
As the number of meta-virtualization users grows, the need to document
various parts of the layer grows as well. Rather than rely only on
wiki and online docs, we'll create a layer-local holding tank for relevant
bits of documentation.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Depending on the requirements of a system, interrupt balancing may
be desireable.
This commit adds irqbalance to provide a daemon to balance interrupts
across multiple CPUs, which can lead to better performance and IO
balance on SMP systems.
Signed-off-by: Mark Asselstine <mark.asselstine@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>
This package provides:
- multipath: scans the system for multipathed devices, assembles
- multipathd: waits for maps events then execs multipath
- kpartx: maps linear devmaps to device partitions, which makes
multipath maps partionable
......
Now,It can be used for kvm disk img partion mounting for me.
Signed-off-by: Lei Yang <lei.yang@windriver.com>
The ebtables-save script uses perl so it's been added to the recipe.
Signed-off-by: Mihai Prica <mihai.prica@intel.com>
Signed-off-by: Raymond Danks <ray.danks@se-eng.com>
Virsh uses dnsmasq for its default bridged network. The dnsmasq daemon is
configured to starts on all public interfaces. Modified the config file
of the libvirtd daemon to stop the existing dnsmasq daemon to enable virsh
to work properly.
Signed-off-by: Mihai Prica <mihai.prica@intel.com>
Signed-off-by: Raymond Danks <ray.danks@se-eng.com>
* the package can now be customized using PACKAGECONFIG
* fixed to use target include files for python
Signed-off-by: Mihai Prica <mihai.prica@intel.com>
Signed-off-by: Raymond Danks <ray.danks@se-eng.com>
