linux/meta-updater.git/classes/sota.bbclass, branch feat/OTA-719/nodeploy

Add SOTA_DEPLOY_CREDENTIALS variable to control whether the built image should be provisioned

2018-10-01T08:44:50+00:00

ostree-initrd: Make it an initramfs, not initrd

2018-08-14T14:03:10+00:00

The reasoning here is to allow initramfs generated by this recipe to be included in FIT. To do so w/o changing openembedded-core (it allows only cpio format) - init script should be able to execute from a rootfs (i.e. true initramfs), not ramdisk (initrd). See [1] for more information on these keywords. The gist of this change is switch from `pivot_root` to `switch_root`. This also allows to get rid of some clutter, since `switch_root` handles transition to new sysroot all by itself. Again, see [1] for details on these utility/syscall. [1] https://www.kernel.org/doc/Documentation/filesystems/ramfs-rootfs-initramfs.txt Signed-off-by: Yevgeny Popovych

classes, images: Use standard variables for initramfs

2018-08-14T14:03:10+00:00

This will reduce the level of indirection and improve compatibility with the rest of OE. For example, FIT that includes initramfs may now be built. Signed-off-by: Yevgeny Popovych

Add support for building ota-tar.xz, and fixes from review comments

2018-07-11T00:28:40+00:00

Adding support for creating an otaimg.tar file in addition to the ext4 image

2018-06-30T00:43:39+00:00

sota.bbclass: remove obsolete/incorrect comment.

2018-06-19T10:44:37+00:00

Fix boot on qemux86-64

2018-05-16T10:37:19+00:00

It needs a plain compressed file system and not an u-boot legacy image

Replace INITRAMFS_FSTYPES with OSTREE_INITRAMFS_FSTYPES

2018-05-16T08:28:12+00:00

User is able to customize the init script via OSTREE_INITRAMFS_IMAGE but there is no way to set INITRAMFS_FSTYPES as it gets defined by sota.bbclass. Create a new variable called OSTREE_INITRAMFS_IMAGE to handle the INITRAMFS_FSTYPES update, and also allow the user to override it. Signed-off-by: Ricardo Salveti

sota: introduce INITRAMFS_FSTYPES

2018-05-15T08:49:49+00:00

RAMDISK_EXT and IMAGE_FSTYPES of initramfs-ostree-image should not be defined separately, because they are representing the same fstype of a same initramfs image, or else, they turn out to be inconsistent if the users change one of them. So we use INITRAMFS_FSTYPES already defined in bitbake.conf, to be able to set fstype for initramfs. And it should default to ext4.gz.u-boot or ext4.gz depending on what OSTREE_BOOTLOADER is being set. Signed-off-by: Ming Liu

Add support for custom garage target version and url

2018-05-11T13:59:17+00:00

Both values can be defined by the user, allowing a custom version id and URL, which is specially useful for CI builds. Signed-off-by: Ricardo Salveti