Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
95 lines (92 sloc) 3.25 KB
# Handle updatehub image integration
#
# Required variables:
#
# UPDATEHUB_PRODUCT_UID
#
# The UPDATEHUB_PRODUCT_UID identifies the product id in use. This is
# used by the updatehub server to identify the product and track the
# possible versions for rollouts.
#
# UPDATEHUB_UHUPKG_PUBLIC_KEY
# UPDATEHUB_UHUPKG_PRIVATE_KEY
#
# The UPDATEHUB_UHUPKG_PUBLIC_KEY and UPDATEHUB_UHUPKG_PRIVATE_KEY
# variables are required to point to the keys which are used to
# validate and sign the update package.
#
# The keys may or not be stored on the layer. Commonly the keys are
# not available for developers and passed to the build system using
# the local.conf file of the autobuilder.
#
# UPDATEHUB_IMAGE_TYPE
#
# The updatehub can operate using different setup which can be chosen
# using the UPDATEHUB_IMAGE_TYPE variable. It supports different
# values, as below:
#
# initramfs
#
# Enables the updatehub gold firmware support; this adds an
# initramfs based image which is used for the upgrade process. In
# this mode, the updatehub agent is ran inside an initramfs image
# which allows for the image to be changed without the need of a
# spare storage space.
#
#
# active/inactive
#
# Allow the use of active and inactive images schema. This reduces
# the downtime of the system as the image can be change without
# rebooting. The new image is installed in a spare storage area
# and in next reboot the new image is used. The
# UPDATEHUB_ACTIVE_INACTIVE_BACKEND variable need to set depending
# of the machine requirement.
#
# UPDATEHUB_ACTIVE_INACTIVE_BACKEND
#
# The active and inactive image schema requires a backend to identify
# and choose the image to be used for next boot. It supports:
# 'u-boot', 'grub' or 'grub-efi'.
#
# UPDATEHUB_INSTALL_MODE
#
# There are multiple installation modes supported. This is usually
# machine dependent as it depends on the storate type in
# use. Supported values are: 'copy', 'flash', 'raw', 'tarball',
# 'ubifs' and 'imxkobs'.
#
# UPDATEHUB_FILESYSTEM_SUPPORT
#
# When using the 'copy' or 'tarball' installation mode, some
# filesystem support packages are required. This variable controls
# which filesystems should be supported. It supports different
# values, as 'btrfs', 'ext2', 'ext3', 'ext4', 'f2fs', 'jffs2',
# 'ubifs', 'vfat' and 'xfs'.
#
# Optional variables:
#
# UPDATEHUB_SERVER_URL
#
# Specifies the updatehub Server address to use. This is required in
# case you are running it inside your private clould.
#
# UPDATEHUB_ACCESS_ID
# UPDATEHUB_ACCESS_SECRET
#
# When using the uhupush task we can override the Access Id and the
# corresponding Secret for use. This is usually used in auto builders
# as they may require different credentials depending on the product
# being build.
#
# UPDATEHUB_CUSTOM_CA_CERTS
#
# Specify the CA certificate bundle to be used for uhupush task. It
# is currently used by updatehub staging server for tests but may be
# interesting for other users when doing custom server deployments.
#
# Copyright 2017 (C) O.S. Systems Software LTDA.
# Allow Go cross compiling with the SDK
TOOLCHAIN_HOST_TASK_append = " packagegroup-go-cross-canadian-${MACHINE}"
TOOLCHAIN_TARGET_TASK_append = " packagegroup-go-sdk-target"
inherit updatehub-image-tasks
You can’t perform that action at this time.