linux/meta-virtualization.git/classes, branch dunfell

conf: defer DISTRO_FEATURE check to bbclass processing

2020-02-10T15:28:38+00:00

We were using USER_CLASS loading to allow conditional checking on DISTRO_FEATURES, which triggered distro feature specific version pinning. It was found that DISTRO_FEATURES set in local.conf is not consistently available at layer.conf parse time, hence our checks were not always working as expected (i.e. the version files are not included). If we move the DISTRO_FEATURE check to the bbclasses, and use it to trigger the include, we should have a consistent set of variable resolution and consistent behaviour. Signed-off-by: Bruce Ashfield

conf: add k8s distro feature

2019-12-10T07:25:21+00:00

Add support for a new distro feature to control kubernetes versions and related configuration. Signed-off-by: Bruce Ashfield

conf: fix meta-virt version / config include

2019-12-06T18:51:57+00:00

As was reported: https://lists.yoctoproject.org/g/meta-virtualization/message/4173?p=,,,20,0,0,0::Created,,conf%2Flayer.conf+is+broken,20,2,0,61269733 The conditional include of the meta-virt versions and config was not working properly due to parse time constraints. This commit fixes that by following the example of the meta-cube layer and instead using a user bbclass to load the .inc file after distro/distro features have been resolved by bitbake. Signed-off-by: Bruce Ashfield

containers: introduce image-oci

2019-02-27T16:46:25+00:00

This image class creates an oci image spec directory from a generated rootfs. The contents of the rootfs do not matter (i.e. they need not be container optimized), but by using the container image type and small footprint images, we can create directly executable container images. Once the tarball (or oci image directory) has been created of the OCI image, it can be manipulated by standard tools. For example, to create a runtime bundle from the oci image, the following can be done: Assuming the image name is "container-base": If the oci image was a tarball, extract it (skip, if a directory is being directly used) % tar xvf container-base--.rootfs-oci-latest-x86_64-linux.oci-image.tar And then create the bundle: % oci-image-tool create --ref name=latest container-base--.rootfs-oci container-base-oci-bundle Or to copy (push) the oci image to a docker registry, skopeo can be used (vary the tag based on the created oci image: % skopeo copy --dest-creds : oci:container-base--:latest docker://zeddii/container-base The following image variables are available to customize the details of the constructed image (defaults as shown): OCI_IMAGE_AUTHOR ?= "${PATCH_GIT_USER_NAME}" OCI_IMAGE_AUTHOR_EMAIL ?= "${PATCH_GIT_USER_EMAIL}" OCI_IMAGE_TAG ?= "latest" OCI_IMAGE_RUNTIME_UID ?= "" OCI_IMAGE_ARCH ?= "${TARGET_ARCH}" OCI_IMAGE_SUBARCH ?= "${@oci_map_subarch(d.getVar('TARGET_ARCH'), d.getVar('TUNE_FEATURES'), d)}" OCI_IMAGE_ENTRYPOINT ?= "sh" OCI_IMAGE_ENTRYPOINT_ARGS ?= "" OCI_IMAGE_WORKINGDIR ?= "" //List of ports to expose from a container running this image: //PORT[/PROT] // format: /tcp, /udp, or (same as /tcp). OICI_IMAGE_PORTS ?= "" // key=value list of labels OCI_IMAGE_LABELS ?= "" // key=value list of environment variables OCI_IMAGE_ENV_VARS ?= "" Signed-off-by: Bruce Ashfield

sanity-meta-virt: Watch for SanityCheck event

2017-10-13T01:59:51+00:00

The ConfigParsed event is raised multiple times during a build which resulted in the sanity warning appearing up to 4 times per build. Instead we should be watching for the SanityCheck event (this is what the sanity checks in oe-core watch for). Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield

sanity-meta-virt: Make skip variable name layer specific

2017-10-13T01:59:51+00:00

The variable used to skip the sanity check should be named in a layer specific way. This will ensure there is no confusion if other layers use a similar sanity check. Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield

sanity-meta-virt.bbclass: add class for bbappend files checking

2017-10-02T13:39:26+00:00

Add a new class, sanity-meta-virt.bbclass, to check for whether necessary settings are available for bbappend files in this layer to be effective, and warn users if not. In addition, a variable SKIP_SANITY_BBAPPEND_CHECK is added to enable users to explicitly skip the checking to avoid unwanted warnings. Signed-off-by: Chen Qi Signed-off-by: Bruce Ashfield

housekeeping: swap out go-osarchmap in favor of goarch

2017-04-12T03:09:01+00:00

Continue work to use go infra in oe-core instead of the support for go previously found in meta-virt. This is a 1:1 drop in replacement and removes one more go piece from meta-virt in favor of the common support found in oe-core. Signed-off-by: Mark Asselstine Signed-off-by: Bruce Ashfield

Remove True option to getVar calls

2017-01-03T15:28:33+00:00

getVar() now defaults to expanding by default. Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield

go-osarchmap: Skip golang recipes for unsupported architectures

2017-01-03T15:28:33+00:00

Building any recipe for a mips-based machine like arduino-yun currently leads to errors in go_map_arch(). Instead, errors should only be raised if a recipe which uses golang is built. This is achieved using the same error handling seen in recipes-extended/xen. Signed-off-by: Paul Barker Signed-off-by: Bruce Ashfield