linux/meta-virtualization.git/conf, branch mickledore

conf: introduce container configuration values

2023-03-08T22:08:02+00:00

From the configuration file itself: These variables represent groupings of functionality in the CNCF landscape. In particular, they are areas where there is a choice between more than one implementation or an area where abstraction is beneficial. The contents of the variables are are runtime components that recipes may use for RDEPENDS. Build dependencies are not typically flexible, so do not currently have DEPENDS equivalents for the components (i.e. DEPENDS on runc versus crun). Distro features such as kubernetes or other container stacks can be used to set different defaults for these variables. Note: these are "global" values, since they represent choices. If more than of a grouping is required on target, then the variable can be appended or set to multiple values. That being said, Recipes should generally agree on the values, hence the global namespace. Recipe specific choices can still be done, but they risk conflicting on target or causing runtime issues / errors. ## CNCF "components" # engines: docker-ce/docker-moby, virtual-containerd, cri-o, podman VIRTUAL-RUNTIME_container_engine ??= "podman" # runtime: runc, crun, runv, runx VIRTUAL-RUNTIME_container_runtime ??= "virtual-runc" # networking: cni, netavark VIRTUAL-RUNTIME_container_networking ??= "cni" # dns: cni, aardvark-dns VIRTUAL-RUNTIME_container_dns ??= "cni" # orchestration: k8s, k3s VIRTUAL-RUNTIME_container_orchestration ??= "k3s" ## Kubernetes terminology "components" VIRTUAL-RUNTIME_cri ??= "containerd" VIRTUAL-RUNTIME_cni ??= "cni" Signed-off-by: Bruce Ashfield

conf: add reference container multiconfig

2023-02-10T17:36:11+00:00

This is the start of a container multiconfig reference. See the container-host image type for an example use of the configuration. As usual, ensure that: BBMULTICONFIG = "container" is in your configuration to fully enable its use. Signed-off-by: Bruce Ashfield

xen: Bump default version to 4.17 stable

2023-01-10T18:58:07+00:00

Reviewed-by: Christopher Clark Signed-off-by: Michal Orzel Signed-off-by: Bruce Ashfield

conf: mark layer compatible with mickledore

2023-01-04T01:24:47+00:00

Signed-off-by: Bruce Ashfield

layer.conf: set langdale compatibility

2022-09-30T03:08:52+00:00

Signed-off-by: Bruce Ashfield

Revert "qemuboot, xen-image-minimal: enable runqemu for qemuarm Xen images"

2022-05-09T16:22:11+00:00

This reverts commit 1c746a976830ebaf85c7c8c25612bea349b0a7c5. Signed-off-by: Bruce Ashfield

qemuboot, xen-image-minimal: enable runqemu for qemuarm Xen images

2022-05-09T12:08:25+00:00

The Xen hypervisor built for Arm 32-bit targets can be launched with runqemu by providing a u-boot script and configuration for Qemu, which enables interactive testing of Xen images. Add qemuboot-xen-u-boot.bbclass to add a new bitbake task for generating the u-boot script. Since this increases the number of qemuboot-specific classes that are inherited by the xen-image-minimal recipe, change the inherit of all of these to only apply to qemu machines with the qemuall override. Update qemuboot-xen-defaults.bbclass to supply working default parameters for the qemuarm machine needed to boot successfully in testing. Also change all the arch-specific variable overrides into narrower qemu platform overrides instead to avoid unnecessary interactions with other Arm platform machines. Signed-off-by: Christopher Clark Signed-off-by: Bruce Ashfield

xen: Add recipes for stable Xen 4.16 release and update master

2022-04-20T18:09:23+00:00

Add recipes for Xen 4.16 release as, according to the documentation we shall have recipes for the latest stable major version of Xen before the next Yocto release. Bump PREFERED_VERSION to 4.16 as well. Take the opportunity to update SRCREV of xen recipes for master and bump XEN_REL version to 4.17 as this is the current development version. Signed-off-by: Michal Orzel Reviewed-by: Christopher Clark Reviewed-by: Bertrand Marquis Signed-off-by: Bruce Ashfield

conf: drop honister from compatibility

2022-02-22T00:31:32+00:00

The variable renames in OE core are parse errors, not warnings, so maintaining compatibility for both honister and kirkstone in the same branch isn't feasible. So we drop honister in preparation for release. Signed-off-by: Bruce Ashfield

conf: add kirkstone to layer compatibility

2022-02-18T13:59:50+00:00

Signed-off-by: Bruce Ashfield